# US 2019/0172009 A1 · Freight Logistics Systems and Methods > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2019/0172009 A1 - Document ID: US20190172009A1 - Status: Published application - Kind: A1 - Application number: 16/207,928 - Filed: 2018-12-03 - Published: 2019-06-06 - Earliest claimed: 2017-12-06 - Inventors: Vitali Iavorschii - Web page: https://patentgrep.com/patent/US20190172009A1 ## CPC - G06Q 10/0835: Relationships between shipper or supplier and carriers - G06F 16/9537: Spatial or temporal dependent retrieval, e.g. spatiotemporal queries - G06F 16/9538: Presentation of query results - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract The present disclosure provides a system and method that receives load data from publicly available freight exchanges, enables users to post and search for loads and trucks, and automatically calls the parties listed in the search results. By calling on a number of available loads or trucks at a time, the freight logistics system increases a user's likelihood of obtaining a load or truck for shipment, the success of which is scalable when used by a freight broker or a shipper having a large amount of freight to be transported. ## Claims ### Claim 1 A system comprising: a controller; a memory coupled to the controller, wherein the memory is configured to store program instructions executable by the controller; wherein in response to executing the program instructions, the controller is configured to: receive a load data for shipment from a shipper, wherein the load data includes an amount of load, and a date for delivery; receive locomotive availability information associated with a carrier, wherein the locomotive availability information includes carrier contact information, dates of availability, and a space amount of availability, wherein the locomotive availability information is stored in a database in communication with the controller; select carriers from the database based on matching the load data for shipment with the received locomotive availability information associated with a carrier; generating a likelihood of success for shipment of the load data by the date of delivery for each of the selected carriers; identifying the carrier contact information associated with each carrier associated with a likelihood of success greater than a predefined success value; contacting the identified carrier contact information; receiving confirmation to ship the freight data by the requested delivery date from at least one contacted carrier; and displaying the confirmed carrier information to a user interface associated with the shipper associated with the load data. ### Claim 2 (depends on 1) The system of claim 1, wherein the shipper is a publicly available freight exchange. ### Claim 3 (depends on 1) The system of claim 1, wherein contacting the locomotive contact information includes contacting the locomotive contact information associated with each carrier associated with a likelihood of success greater than a predefined success value from a user device associated with the shipper. ### Claim 4 (depends on 1) The system of claim 1, wherein contacting the locomotive contact information includes simultaneously calling up to five of the identified carrier contact information. ### Claim 5 (depends on 4) The system of claim 4, wherein once a call is accepted from an identified locomotive contact information, the remaining simultaneous calls are placed on hold. ### Claim 6 (depends on 5) The system of claim 5, wherein when the call ends, a new call is established automatically with a first identified carrier contact information on hold. ### Claim 7 (depends on 1) The system of claim 1, wherein the controller is configured to automatically contact the carrier contact information associated with each carrier associated with a likelihood of success greater than a predefined success value. ### Claim 8 (depends on 1) The system of claim 1, wherein the controller is further configured to receive a carrier search request including at least one of a pick-up date, a delivery date, a pick-up location, a destination location, a truck type, and a load weight; select a matching load request from the database, wherein the matching load request is compatible with the received search request; and display the matching load request on a user interface associated with the carrier associated with the carrier search request. ### Claim 9 (depends on 8) The system of claim 8, wherein the controller is configured to automatically contact the shipper associated with the matching load request. ### Claim 10 (depends on 8) The system of claim 8, wherein the controller is configured to display on a user interface associated with the carrier contacting information associated with the shipper associated with the matching load request. ### Claim 11 (depends on 8) The system of claim 8, wherein the controller is configured to automatically contact the shipper associated with the matching load request, wherein the controller is configured to display carrier information associated with the matching load request, wherein the carrier information includes at least one of a carrier contact information, the pick-up date, the delivery date, the pick-up location, the destination location, the truck type, and the load weight.