WO2019219088A1 - Systèmes et procédés d'attribution de commandes - Google Patents

Systèmes et procédés d'attribution de commandes Download PDF

Info

Publication number
WO2019219088A1
WO2019219088A1 PCT/CN2019/087496 CN2019087496W WO2019219088A1 WO 2019219088 A1 WO2019219088 A1 WO 2019219088A1 CN 2019087496 W CN2019087496 W CN 2019087496W WO 2019219088 A1 WO2019219088 A1 WO 2019219088A1
Authority
WO
WIPO (PCT)
Prior art keywords
order
location
vehicle
user terminal
route
Prior art date
Application number
PCT/CN2019/087496
Other languages
English (en)
Inventor
Lu Li
Niping ZHANG
Lei YIN
Jing Lin
Xin Yan
Wei Zhang
Original Assignee
Beijing Didi Infinity Technology And Development Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from CN201810482072.2A external-priority patent/CN108805411A/zh
Priority claimed from CN201810573367.0A external-priority patent/CN110570263B/zh
Application filed by Beijing Didi Infinity Technology And Development Co., Ltd. filed Critical Beijing Didi Infinity Technology And Development Co., Ltd.
Publication of WO2019219088A1 publication Critical patent/WO2019219088A1/fr

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/02Reservations, e.g. for tickets, services or events
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q10/00Administration; Management
    • G06Q10/06Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063Operations research, analysis or management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION 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
    • G06Q50/00Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40Business processes related to the transportation industry

Definitions

  • an order allocation system may include at least one storage device, and at least one processor in communication with the at least one storage device.
  • the at least one storage device may include a set of instructions.
  • the at least one processor may be directed to obtain a departure location of an order and a current location of a vehicle; determine a first route from the current location of the vehicle to the departure location of the order, and determine a direction adjustment location of the vehicle based on the first route, the direction adjustment location being used for adjusting a driving direction of the vehicle; in response to a determination that the first estimated duration is greater than or equal to a first predetermined duration, allocate the order to the vehicle; or in response to a determination that the first estimated duration is less than the first predetermined duration, determine an expected driving route of the vehicle, and determine whether to allocate the order to the vehicle based on the expected driving route of the vehicle.
  • FIG. 1 is a schematic diagram illustrating an exemplary online to offline (O2O) service system according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating an exemplary process for car-hailing order allocation according to some embodiments of the present disclosure
  • FIG. 13 is a flowchart illustrating an exemplary process for order allocation according to some embodiments of the present disclosure
  • FIG. 15 is a block diagram illustrating an exemplary order allocation device 1500 according to some embodiments of the present disclosure.
  • FIG. 16 is a block diagram illustrating an exemplary allocation unit 1506 according to some embodiments of the present disclosure.
  • FIG. 17 is a schematic block diagram of a computer device 1700 according to some embodiments of the present disclosure.
  • the flowcharts used in the present disclosure illustrate operations that systems implement according to some embodiments in the present disclosure. It is to be expressly understood, the operations of the flowchart may be implemented not in order. Conversely, the operations may be implemented in inverted order, or simultaneously. Moreover, one or more other operations may be added to the flowcharts. One or more operations may be removed from the flowcharts.
  • Embodiments of the present disclosure may be applied to different transportation systems including but not limited to land transportation, sea transportation, air transportation, space transportation, or the like, or any combination thereof.
  • a vehicle of the transportation systems may include a rickshaw, travel tool, taxi, chauffeured car, hitch, bus, rail transportation (e.g., a train, a bullet train, high-speed rail, and subway) , ship, airplane, spaceship, hot-air balloon, driverless vehicle, or the like, or any combination thereof.
  • the transportation system may also include any transportation system that applies management and/or distribution, for example, a system for sending and/or receiving an express.
  • passenger, ” “requester, ” “requestor, ” “service requester, ” “service requestor” and “customer” in the present disclosure are used interchangeably to refer to an individual, an entity or a tool that may request or order a service.
  • driver, ” “provider, ” “service provider, ” and “supplier” in the present disclosure are used interchangeably to refer to an individual, an entity or a tool that may provide a service or facilitate the providing of the service.
  • user in the present disclosure may refer to an individual, an entity or a tool that may request a service, order a service, provide a service, or facilitate the providing of the service.
  • the user may be a requester, a passenger, a driver, an operator, or the like, or any combination thereof.
  • requester and “requester terminal” may be used interchangeably, and “provider” and “provider terminal” may be used interchangeably.
  • An aspect of the present disclosure provides devices and methods for order allocation.
  • the devices and methods may receive location information including departure location information and destination information of a user terminal (e.g., a driver terminal) sent by the user terminal.
  • the devices and methods may send at least one order that matches the location information to the user terminal, and receive an order acceptance to one order of the at least one order from the user terminal.
  • the devices and methods may further determine whether to allocate the order to the user terminal based on a screening model.
  • the devices and methods may obtain a departure location of an order and a current location of a vehicle.
  • the devices and methods may determine a first route from the current location of the vehicle to the departure location of the order, and determine a direction adjustment location of the vehicle based on the first route.
  • the direction adjustment location may be used for adjusting a driving direction of the vehicle.
  • the devices and methods may determine a first estimated duration driving from the current location to the direction adjustment location.
  • the devices and methods may allocate the order to the vehicle.
  • the devices and methods may determine an expected driving route of the vehicle, and determine whether to allocate the order to the vehicle based on the expected driving route of the vehicle
  • the O2O service system 100 may provide a plurality of services.
  • Exemplary service may include a taxi-hailing service, a chauffeur service, an express car service, a carpool service, a bus service, a driver hire service, and a shuttle service.
  • the O2O service may be any online service, such as booking a meal, shopping, or the like, or any combination thereof.
  • the server 110 may be a single server or a server group.
  • the server group may be centralized, or distributed (e.g., the server 110 may be a distributed system) .
  • the server 110 may be local or remote.
  • the server 110 may access information and/or data stored in the requester terminal 130, the provider terminal 140, and/or the storage device 160 via the network 120.
  • the server 110 may be directly connected to the requester terminal 130, the provider terminal 140, and/or the storage device 160 to access stored information and/or data.
  • the server 110 may be implemented on a cloud platform.
  • the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an inter-cloud, a multi-cloud, or the like, or any combination thereof.
  • the server 110 may be implemented on a computing device 200 having one or more components illustrated in FIG. 2 in the present disclosure.
  • a passenger may be an owner of the requester terminal 130. In some embodiments, the owner of the requester terminal 130 may be someone other than the passenger. For example, an owner A of the requester terminal 130 may use the requester terminal 130 to transmit a service request for a passenger B or receive a service confirmation and/or information or instructions from the server 110.
  • a service provider may be a user of the provider terminal 140. In some embodiments, the user of the provider terminal 140 may be someone other than the service provider. For example, a user C of the provider terminal 140 may use the provider terminal 140 to receive a service request for a service provider D, and/or information or instructions from the server 110.
  • passenger and “passenger terminal” may be used interchangeably, and “service provider” and “provider terminal” may be used interchangeably.
  • the provider terminal may be associated with one or more service providers (e.g., a night-shift service provider, or a day-shift service provider) .
  • the requester terminal 130 may include a mobile device 130-1, a tablet computer 130-2, a laptop computer 130-3, a built-in device in a vehicle 130-4, or the like, or any combination thereof.
  • the mobile device 130-1 may include a smart home device, a wearable device, a smart mobile device, a virtual reality device, an augmented reality device, or the like, or any combination thereof.
  • the smart home device may include a smart lighting device, a control device of an intelligent electrical apparatus, a smart monitoring device, a smart television, a smart video camera, an interphone, or the like, or any combination thereof.
  • the wearable device may include a smart bracelet, a smart footgear, smart glasses, a smart helmet, a smart watch, smart clothing, a smart backpack, a smart accessory, or the like, or any combination thereof.
  • the smart mobile device may include a smartphone, a personal digital assistance (PDA) , a gaming device, a navigation device, a point of sale (POS) device, or the like, or any combination thereof.
  • the virtual reality device and/or the augmented reality device may include a virtual reality helmet, virtual reality glasses, a virtual reality patch, an augmented reality helmet, augmented reality glasses, an augmented reality patch, or the like, or any combination thereof.
  • the provider terminal 140 may include a plurality of provider terminals 140-1, 140-2, ..., 140-n. In some embodiments, the provider terminal 140 may be similar to, or the same device as the requester terminal 130. In some embodiments, the provider terminal 140 may be customized to be able to implement the O2O service 100. In some embodiments, the provider terminal 140 may be a device with positioning technology for locating the service provider, the provider terminal 140, and/or a vehicle 150 associated with the provider terminal 140. In some embodiments, the requester terminal 130 and/or the provider terminal 140 may communicate with another positioning device to determine the position of the passenger, the requester terminal 130, the service provider, and/or the provider terminal 140.
  • the requester terminal 130 and/or the provider terminal 140 may periodically transmit the positioning information to the server 110.
  • the provider terminal 140 may also periodically transmit the availability status to the server 110.
  • the availability status may indicate whether a vehicle 150 associated with the provider terminal 140 is available to carry a passenger.
  • the requester terminal 130 and/or the provider terminal 140 may transmit the positioning information and the availability status to the server 110 every thirty minutes.
  • the requester terminal 130 and/or the provider terminal 140 may transmit the positioning information and the availability status to the server 110 each time the user logs into the mobile application associated with the O2O transportation service 100.
  • the provider terminal 140 may include a processing device similar to or the same as the processing device 112. In some embodiments, the provider terminal 140 may correspond to one or more vehicles 150.
  • the vehicles 150 may carry the passenger and travel to the destination.
  • the vehicles 150 may include a plurality of vehicles 150-1, 150-2, ..., 150-n.
  • One vehicle may correspond to one type of services (e.g., a taxi-hailing service, a chauffeur service, an express car service, a carpool service, a bus service, a driver hire service, or a shuttle service) .
  • the storage device 160 may store data and/or instructions. In some embodiments, the storage device 160 may store data obtained from the requester terminal 130 and/or the provider terminal 140. In some embodiments, the storage device 160 may store data and/or instructions that the server 110 may execute or use to perform exemplary methods described in the present disclosure. In some embodiments, the storage device 160 may include a mass storage, removable storage, a volatile read-and-write memory, a read-only memory (ROM) , or the like, or any combination thereof. Exemplary mass storage may include a magnetic disk, an optical disk, solid-state drives, etc. Exemplary removable storage may include a flash drive, a floppy disk, an optical disk, a memory card, a zip disk, a magnetic tape, etc.
  • Exemplary volatile read-and-write memory may include a random-access memory (RAM) .
  • RAM may include a dynamic RAM (DRAM) , a double date rate synchronous dynamic RAM (DDR SDRAM) , a static RAM (SRAM) , a thyristor RAM (T-RAM) , and a zero-capacitor RAM (Z-RAM) , etc.
  • Exemplary ROM may include a mask ROM (MROM) , a programmable ROM (PROM) , an erasable programmable ROM (EPROM) , an electrically-erasable programmable ROM (EEPROM) , a compact disk ROM (CD-ROM) , and a digital versatile disk ROM, etc.
  • MROM mask ROM
  • PROM programmable ROM
  • EPROM erasable programmable ROM
  • EEPROM electrically-erasable programmable ROM
  • CD-ROM compact disk ROM
  • digital versatile disk ROM etc.
  • the storage device 160 may be implemented on a cloud platform.
  • the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an inter-cloud, a multi-cloud, or the like, or any combination thereof.
  • the storage device 160 may be connected to the network 120 to communicate with one or more components of the O2O service system 100 (e.g., the server 110, the requester terminal 130, or the provider terminal 140) .
  • One or more components of the O2O service system 100 may access the data or instructions stored in the storage device 160 via the network 120.
  • the storage device 160 may be directly connected to or communicate with one or more components of the O2O service system 100 (e.g., the server 110, the requester terminal 130, the provider terminal 140) .
  • the storage device 160 may be part of the server 110.
  • the navigation system 170 may determine information associated with an object, for example, one or more of the requester terminal 130, the provider terminal 140, the vehicle 150, etc.
  • the navigation system 170 may be a global positioning system (GPS) , a global navigation satellite system (GLONASS) , a compass navigation system (COMPASS) , a BeiDou navigation satellite system, a Galileo positioning system, a quasi-zenith satellite system (QZSS) , etc.
  • the information may include a location, an elevation, a velocity, or an acceleration of the object, or a current time.
  • the navigation system 170 may include one or more satellites, for example, a satellite 170-1, a satellite 170-2, and a satellite 170-3.
  • the satellites 170-1 through 170-3 may determine the information mentioned above independently or jointly.
  • the satellite navigation system 170 may transmit the information mentioned above to the network 120, the requester terminal 130, the provider terminal 140, or the vehicle 150 via wireless connections.
  • one or more components of the O2O service system 100 may have permissions to access the storage device 160.
  • one or more components of the O2O service system 100 may read and/or modify information related to the passenger, service provider, and/or the public when one or more conditions are met.
  • the server 110 may read and/or modify one or more passengers’ information after a service is completed.
  • the server 110 may read and/or modify one or more service providers’ information after a service is completed.
  • an element or component of the O2O service system 100 performs, the element may perform through electrical signals and/or electromagnetic signals.
  • a processor of the requester terminal 130 may generate an electrical signal encoding the request.
  • the processor of the requester terminal 130 may then transmit the electrical signal to an output port. If the requester terminal 130 communicates with the server 110 via a wired network, the output port may be physically connected to a cable, which further may transmit the electrical signal to an input port of the server 110.
  • FIG. 2 illustrates a schematic diagram of an exemplary computing device according to some embodiments of the present disclosure.
  • the computing device may be a computer, such as the server 110 in FIG. 1 and/or a computer with specific functions, configured to implement any particular system according to some embodiments of the present disclosure.
  • Computing device 200 may be configured to implement any components that perform one or more functions disclosed in the present disclosure.
  • the server 110 may be implemented in hardware devices, software programs, firmware, or any combination thereof of a computer like computing device 200.
  • FIG. 2 depicts only one computing device.
  • the functions of the computing device, providing function that recommending pick-up locations may require may be implemented by a group of similar platforms in a distributed mode to disperse the processing load of the system.
  • Computing device 200 may include a communication terminal 250 that may connect with a network that may implement the data communication.
  • Computing device 200 may also include a processor 220 that is configured to execute instructions and includes one or more processors.
  • the schematic computer platform may include an internal communication bus 210, different types of program storage units and data storage units (e.g., a hard disk 270, a read-only memory (ROM) 230, a random-access memory (RAM) 240) , various data files applicable to computer processing and/or communication, and some program instructions executed possibly by the processor 220.
  • Computing device 200 may also include an I/O device 260 that may support the input and output of data flows between computing device 200 and other components. Moreover, computing device 200 may receive programs and data via the communication network.
  • FIG. 3 is a schematic diagram illustrating exemplary hardware and/or software components of an exemplary mobile device on which a terminal may be implemented according to some embodiments of the present disclosure.
  • the mobile device 300 may include a communication platform 310, a display 320, a graphic processing unit (GPU) 330, a central processing unit (CPU) 340, an I/O 350, a memory 360, a mobile operating system (OS) 370, a storage 390.
  • any other suitable component including but not limited to a system bus or a controller (not shown) , may also be included in the mobile device 300.
  • a mobile operating system 370 e.g., iOS TM , Android TM , Windows Phone TM , etc.
  • the applications 380 may include a browser or any other suitable mobile apps for receiving and rendering information relating to image processing or other information from the O2O service system 100.
  • User interactions with the information stream may be achieved via the I/O 350 and provided to the database 130, the server 105 and/or other components of the O2O service system 100.
  • the mobile device 300 may be an exemplary embodiment corresponding to the requester terminal 130 or the provider terminal 140.
  • computer hardware platforms may be used as the hardware platform (s) for one or more of the elements described herein.
  • a computer with user interface elements may be used to implement a personal computer (PC) or any other type of work station or terminal device.
  • PC personal computer
  • a computer may also act as a system if appropriately programmed.
  • FIG. 4 is a flowchart illustrating an exemplary process for car-hailing order allocation according to some embodiments of the present disclosure.
  • one or more operations of process 400 may be implemented on the O2O service system 100 as illustrated in FIG. 1, or the computing device 200 as illustrated in FIG. 2, or the mobile device 300 as illustrated in FIG. 3.
  • one or more operations in the process 400 may be stored in the storage device 150 and/or the storage (e.g., the ROM 230, the RAM 240, etc. ) as a form of instructions, and invoked and/or executed by the server 110 (e.g., the processing device 112 in the server 110, or the processor 220 of the processing device 112 in the server 110, or one or more units as illustrated in FIG. 6) .
  • the instructions may be transmitted in a form of electronic current or electrical signals.
  • the process 400 for car-hailing order allocation may include: operation 402, receiving location information sent by a driver terminal (e.g., the provider terminal 140, also referred to as a user terminal) , wherein the location information includes departure location information and destination information of the driver terminal; operation 404, sending order details of at least one car-hailing order (also referred to as “order” for briefly) that matches the location information to the driver terminal; operation 406, receiving an order acceptance to one car-hailing order of the at least one car-hailing order from the driver terminal; and operation 408, determining whether to allocate the car-hailing order to the driver terminal based on a screening model.
  • a driver terminal e.g., the provider terminal 140, also referred to as a user terminal
  • order details of at least one car-hailing order also referred to as “order” for briefly
  • the processing device 112 may be described as a subject to perform the process 400.
  • the processing device 112 may receive location information sent by a driver terminal (also referred to as a user terminal) .
  • the driver terminal may include a driver terminal providing hitchhike services, a driver terminal providing express car service, a driver terminal providing taxi services, a driver terminal providing carpool services, or the like.
  • the processing device 112 may receive the location information from the driver terminal via the network 120.
  • the location information may include departure location information of the driver terminal, destination information of the driver terminal, or the like.
  • the departure location information and/or the destination information may be represented by coordinates (e.g., latitude-longitude coordinates) .
  • the departure location information and/or the destination information may be represented by a name of a community (e.g., a home address of a user) , a name of a company (e.g., a work address of the user) , a name of a market, a name of a hospital, a name of a bus station, a name of a metro station, a name of a train station, a name of a hotel, a name of food plaza, a name of a scenic area, a name of a street, or the like.
  • a name of a community e.g., a home address of a user
  • a name of a company e.g., a work address of the user
  • a name of a market e.g., a name of a hospital
  • a name of a bus station e.g., a name of a metro station
  • a name of a hotel e.g., a name of a hotel
  • the departure location information and/or the destination information may be inputted, by a user (e.g., a driver) , via a character input device (e.g., a keyboard, a touch screen) of the driver terminal or a microphone of the driver terminal.
  • a character input device e.g., a keyboard, a touch screen
  • the departure location information may be a current location of the driver terminal, which may be automatically determined by GPS installed in the driver terminal.
  • the processing device 112 may send at least one car-hailing order (also referred to as “order” for briefly) that matches the location information to the driver terminal.
  • the processing device 112 may send order details of the at least one car-hailing order that matches the location information to the driver terminal.
  • the order details of an order may include a departure location of the order, a destination of the order, an order departure time, a travel distance of the order, a number of passengers, an estimated price of the order, or the like, or any combination thereof.
  • an order pool may include a plurality of orders (or car-hailing orders) .
  • the plurality of car-hailing orders may include real-time orders, reserved orders, local orders, city-to-city orders, hitchhike orders, express car orders, taxi orders, carpool orders, or the like.
  • the processing device 112 may determine a matching reference based on the departure location information and the destination information. For example, the processing device 112 may determine the matching reference based on a driver route formed by the departure location information and the destination information of the driver terminal. For an order (i.e., a car-hailing order) in the order pool, the processing device 112 (e.g., the calculation unit 610) may determine a matching degree between the order and the matching reference. In some embodiments, the matching degree may be related to a similarity between the driver route and an order route formed by a departure location and a destination of the order. The higher the similarity is, the higher the matching degree is.
  • the similarity between the driver route and the order route may be measured by an overlapping ratio between the driver route and the order route, a direction angle between the driver route and the order route, etc. For example, if the overlapping ratio is greater than or equal to 30%, and the direction angle is within 30°, the processing device 112 may determine that the similarity between the driver route and the order route satisfies a predetermined similarity threshold, and the processing device 112 may send the order to the driver terminal.
  • the processing device 112 may determine whether a distance between the departure location of the order and the departure location information of the driver terminal is less than a first predetermined distance threshold.
  • the first predetermined distance threshold may be a default value or an empirical value related to the O2O service system 100.
  • the processing device 112 may determine that the order does not match the driver terminal, and may not send the order to the driver terminal.
  • the processing device 112 may further determine the matching degree between the order and the matching reference based on a plurality of first parameters and a correspondent weight thereof.
  • the plurality of first parameters may include a distance between the departure location and a destination of the order, a detour ratio, a carpool ratio, or the like, or any combination thereof.
  • the processing device 112 may determine the detour ratio based on the driver route and the order route.
  • the detour ratio may relate to the overlapping ratio between the driver route and the order route, a direction angle between the driver route and the order route, a distance between the departure location of the order and the departure location information of the driver terminal, a distance between the destination of the order and the departure location information of the driver terminal, etc.
  • the detour ratio may be represented by a percentage, such as 10%, 15%, 40%, 55%, etc.
  • the carpool ratio may be related to the number of passengers carried by the driver of the driver terminal, the destination of the passengers, the routes of the passengers, etc.
  • the processing device 112 may determine the matching degree between the order and the matching reference of the driver terminal based on the distance between the departure location and the destination of the order, the detour ratio, the carpool ratio, and the correspondent weight thereof.
  • the processing device 112 may determine whether the matching degree of the order is greater than or equal to a predetermined matching threhosld. In response to a determination that the matching degree of the order is greater than or equal to the predetermined matching threshold, the processing device 112 may designate the order as one of the at least order (or car-hailing order) , and send the order (specifically order details of the order) to the driver terminal. Alternatively, in response to a determination that the matching degree of the order is less than the predetermined matching threshold, the processing device 112 may not send the order to the driver terminal. The processing device 112 may determine another driver terminal that matches the orders according to the operation described in the present disclosure. In some embodiments, the processing device 112 may match the order to multiple driver terminals, and the processing device 112 may send the order to the multiple matched driver terminals.
  • the predetermined matching threshold may be a default value or an empirical value related to the O2O service system 100.
  • the predetermined matching threshold may be manually set or adjusted by a user (e.g., a driver of the driver terminal) .
  • the predetermined matching threshold may be represented by a percentage. The higher the value of the predetermined matching threshold is, the less the number of orders that match the driver terminal is. In some embodiments, if there are plentiful orders in the order pool, the predetermined matching threshold may be given a larger value, while if the orders in the order pool are short, the predetermined matching threshold may be given a smaller value. In this case, it can ensure that a suitable number of orders are sent to the driver terminal, or at least one order is sent to the driver terminal.
  • the location information of the driver terminal may include a current location of the driver terminal.
  • the order pool may include one or more real-time orders (or real-time car-hailing orders) and one or more reserved orders (or reserved car-hailing orders) .
  • the processing device 112 may determine a distance between a departure location of the real-time order and the current location of the driver terminal. If the distance between the departure location of the real-time order and the current location of the driver terminal is less than or equal to a second predetermined distance threshold, the processing device 112 may send the real-time order to the driver terminal.
  • the processing device may determine a distance between a departure location of the reserved order and the current location of the driver terminal is less than or equal to a third predetermined distance threshold, the processing device 112 may send the reserved order to the driver terminal.
  • the matching degree may only be related to the current location of the driver terminal and the departure location of the order (e.g., a real-time order, a reserved order) . Therefore, the driver terminal may receive multiple orders.
  • the second predetermined distance threshold and/or the third predetermined distance threshold may be a default value or an empirical value related to the O2O service system 100.
  • the second predetermined distance threshold may be less than or equal to the third predetermined distance threshold.
  • the second predetermined distance threshold may be equal to the first predetermined distance threshold.
  • the processing device 112 may receive an order acceptance to one order (or car-hailing order) of the at least one order (or car-hailing orders) from the driver terminal.
  • the driver terminal receives an order and order details of the order
  • the driver may initiate an order acceptance operation for the order on an order selection page of the driver terminal.
  • the processing device 112 may receive the order acceptance from the driver terminal.
  • the processing device 112 may receive more than one order acceptance from different driver terminals for the order within a predetermined time period (e.g., 30 seconds, 1 minutes, 2 minutes, 5 minutes) .
  • the processing device 112 may determine whether to allocate the order (e.g., the car-hailing order) to the driver terminal based on a screening model. In some embodiments, in the predetermined time period, if the order is accepted by a plurality of driver terminals, the processing device 112 may determine to allocate the order to which driver terminal of the plurality of driver terminals. In some embodiments, the processing device 112 may preliminarily screen out a portion of the driver terminals, and then determine a target driver terminal from the screened driver terminals. After the preliminarily screening, the processing device 112 may determine the target driver terminal among a lesser number of driver terminals, which may reduce the computing load and improve the processing efficiency.
  • the order e.g., the car-hailing order
  • the processing device 112 may determine at least two authorized driver terminals among the plurality of driver terminals based on the screening model. In some embodiments, the processing device 112 may determine the at least two authorized driver terminals based on a response time to the order, a route between the current location of the driver terminal and the departure location of the order, traffic conditions corresponding to the route, or the like. For example, the driver terminals quickly responding to the order may be determined as the authorized driver terminals. As another example, the driver terminals with good traffic conditions may be determined as the authorized driver terminals. The processing device 112 may determine a target driver terminal from the at least two authorized driver terminals based on the screening model and a plurality of second parameters.
  • the screening model may be a machine leaning model.
  • the machine learning model may include but is not limited to a Logistic Regression (LR) , a Gradient Booting Decision Tree (GBDT) , a Support Vector Machine (SVM) , a neural network model, or the like.
  • the plurality of second parameters may include the matching degree between the order and a driver terminal, geographical location information, historical driving information of a driver terminal, historical evaluation for a driver of a driver terminal, historical transaction rate, probability of accepting other orders, or the like, or any combination thereof.
  • the processing device 112 may input information of two authorized driver terminals into the screening model.
  • the screening model may be used to compare (also referred to as “PK” ) the two authorized driver terminals based on the plurality of second parameters and its corresponding weight, and output the target driver terminal that is eligible to be allocated the order.
  • the processing device 112 may allocate the order to the target driver terminal.
  • the present disclosure provides an order allocation process considering driver’s preference for orders, which may improve the response rate and transaction rate of orders, further accelerating the order allocation efficiency and the processing speed of orders, and saving system resources.
  • the processing device 112 may determine at least one car-hailing order in the order pool that matches the location information of the driver terminal, and send the order details of the at least one car-hailing order to the driver terminal.
  • the processing device 112 may determine a target driver terminal based on a screening model.
  • the present disclosure may help to improve the transport capacity, increase the transaction rate of orders, and improve the user experience (e.g., passenger’s experience, driver’s experience) .
  • the processing device 112 may allocate the order to the driver terminal.
  • FIG. 5 is a flowchart illustrating an exemplary process for car-hailing order allocation according to some embodiments of the present disclosure.
  • one or more operations of process 500 may be implemented on the O2O service system 100 as illustrated in FIG. 1, or the computing device 200 as illustrated in FIG. 2, or the mobile device 300 as illustrated in FIG. 3.
  • one or more operations in the process 500 may be stored in the storage device 150 and/or the storage (e.g., the ROM 230, the RAM 240, etc. ) as a form of instructions, and invoked and/or executed by the processing device 112, or the processor 220 of the processing device 112, or one or more units as illustrated in FIG. 7) .
  • the instructions may be transmitted in a form of electronic current or electrical signals.
  • the processing device 112 may send location information of a driver terminal (also referred to as a user terminal) to a server via an order selection page.
  • the processing device 112 e.g., the second receiving unit 706 may receive at least car-hailing order (also referred to as order) that matches the location information sent by the server.
  • the processing device 112 may receive order details of the at least one car-hailing order that matches the location information sent by the server.
  • an O2O service (e.g., car-hailing service) platform of the driver terminal may have a home page, which includes an order selection interface.
  • the home page may be switched to the order selection page via the order selection interface.
  • the order selection page may include a location interface (including a departure location input box and a destination input box) .
  • the processing device 112 may detect departure location information and destination information of the driver terminal received via the location interface.
  • the order selection page may further include an order search button.
  • the processing device 112 may send the departure location information and the destination information of the driver terminal to the server, and receive one or more orders (e.g., order details of the one or more orders) that matches the departure location information and the destination information of the driver terminal sent by the server.
  • the one or more orders that matches the driver terminal may refer to that the matching degree between the order (s) and the driver terminal is greater than or equal to the predetermined matching threshold. More descriptions regarding the determination of the matching degree between the order (s) and the driver terminal may be found elsewhere in the present disclosure (e.g., operations 404 of process 400 and the relevant descriptions thereof) .
  • the processing device 112 may sequentially display the at least one car-hailing order (e.g., the order details of the at least one car-hailing order) on an order list page based on a predetermined sequencing rule.
  • Each of the order (or the at least one car-hailing order) may be displayed via an order card.
  • the order card may include an order acceptance interface configured to perform an order acceptance operation for the order (or the car-hailing order) , and to send the order acceptance to the server after performing the order acceptance operation.
  • the order card of an order may include an order departure time, the matching degree of the order, a travel distance of the order, a departure location of the order, a distance between the departure location of the order and the departure location information, a destination of the order, a distance between the destination of the order and the destination information, or the like, or any combination thereof.
  • the at least one order may include a plurality of real-time orders and a plurality of reserved orders.
  • the processing device 112 e.g., the sequencing unit 708, may sequence the plurality of real-time orders in front of the plurality of reserved orders. In this case, sequencing the real-time orders before the reserved orders may facilitate the driver of the driver terminal to request the real-time orders timely.
  • the processing device 112 e.g., the sequencing unit 708, may sequence the plurality of real-time orders based on estimated times of the plurality of real-time orders and/or matching degrees of the plurality of real-time orders.
  • the processing device 112 may sequence the plurality of real-time orders based on the estimated times of the plurality of real-time orders in an ascending order, e.g., real-time orders with shorter estimated times lying in front and real-time orders with longer estimated times lying in the back.
  • the processing device 112 may sequence the plurality of real-time orders based on the matching degrees of the plurality of real-time orders in a descending order, e.g., real-time orders with higher matching degrees lying in front and real-time orders with lower matching degrees lying in the back.
  • the processing device 112 may sequence the plurality of real-time orders based on the estimated times of the plurality of real-time orders, the matching degrees of the plurality of real-time orders, and the corresponding weight thereof.
  • the processing device 112 e.g., the sequencing unit 708 may sequence the plurality of reserved orders based on estimated times of the plurality of reserved orders and/or matching degrees of the plurality of reserved orders.
  • the processing device 112 may sequence the plurality of reserved orders in a similar manner with the plurality of real-time orders, and the descriptions thereof are not repeated.
  • the processing device 112 (e.g., the display unit 704) may display the sequenced real-time orders and reserved orders on the order list page.
  • the processing device 112 may detect a current location of the driver terminal via the location interface.
  • the current location of the driver terminal may be automatically obtained by GPS installed in the driver terminal.
  • the processing device 112 may send the current location of the driver terminal to the server, and receive one or more close-to-the current -location orders that matches the current location of the user terminal sent by the server.
  • the order selection page may include a preview area (e.g., the order display area 1006 as shown in FIG. 12B) for the one or more close-to-the current -location orders. If the one or more close-to-the current -location orders are more than one, the processing device 112 may display a predetermined portion of the one or more close-to-the current -location orders on the preview area.
  • the preview area may include a checking interface (e.g., the “check all hitchhike orders” button as shown in FIG. 12B) configured to display all the one or more close-to-the current -location orders and switch the order selection page to the order list page.
  • the processing device 112 e.g., the sequencing unit 708) may sequence the one or more close-to-the current -location orders based on departure times of the one or more close-to-the current -location orders.
  • the order card of a close-to-the current -location order may include a departure time, a departure location and a destination of the close-to-the current -location order, or a distance between the departure location and the current location of the user terminal, or the like, or any combination thereof.
  • the processing device 112 may refresh the order list page based on a predetermined period (e.g., 1 minute, 5 minutes, 10 minutes, etc. ) .
  • a predetermined period e.g. 1 minute, 5 minutes, 10 minutes, etc.
  • the processing device 112 may display the new order on the order list page. By refreshing the order list page and displaying new order (s) on the order list page, it may improve the instantaneity of checking orders and improve the efficiency of order allocation.
  • FIG. 6 is a block diagram illustrating an exemplary device for order allocation according to some embodiments of the present disclosure.
  • the device 600 (also referred to as the order allocation device 600) may be applicable to a server.
  • the order allocation device 600 may include a first receiving unit 602, a first sending unit 604, a determination unit 606, a generation unit 608, and a calculation unit 610.
  • the first receiving unit 602 may be configured to receive location information sent by a driver terminal.
  • the processing device 112 may receive the location information from the driver terminal via the network 120.
  • the location information may include departure location information, destination information of the driver terminal, or the like.
  • the location information may include a current location of the driver terminal. More descriptions of the location information may be found elsewhere in the present disclosure (e.g., operation 402 of process 400 and the descriptions thereof) .
  • the first receiving unit 602 may further be configured to receive an order acceptance to one car-hailing order (or order) from the driver terminal. After the driver terminal receives an order and order details of the order, if the driver of the driver terminal wants to accept the order, the driver may initiate an order acceptance operation for the order on an order selection page of the driver terminal. The first receiving unit 602 may receive the order acceptance from the driver terminal. In some embodiments, the first receiving unit 602 may receive more than one order acceptance from different driver terminals for the order within a predetermined time period (e.g., 30 seconds, 1 minutes, 2 minutes, 5 minutes) .
  • a predetermined time period e.g. 30 seconds, 1 minutes, 2 minutes, 5 minutes
  • the first sending unit 604 may be configured to send at least one car-hailing order (or order) that matches the location information to the driver terminal. For example, the first sending unit 604 may send order details of the at least one car-hailing order to the driver terminal. The first sending unit 604 may determine whether a matching degree of the order and the driver terminal is greater than or equal to a predetermined matching threshold. In response to a determination that the matching degree of the order is greater than or equal to a predetermined matching threshold, the first sending unit 604 may designate the order as one of the at least order (or car-hailing order) , and send the order (e.g., order details of the order) to the driver terminal.
  • the order e.g., order details of the order
  • the first sending unit 604 may not send the order to the driver terminal.
  • the order may be matched to multiple driver terminals, and the first sending unit 604 may send the order to the multiple matched driver terminals.
  • an order pool may include one or more real-time orders and one or more reserved orders.
  • the location information of the driver terminal may include the current location of the driver terminal.
  • the processing device 112 may determine a distance between a departure location of the real-time order and the current location of the driver terminal. If the distance between the departure location of the real-time order and the current location of the driver terminal is less than or equal to a second predetermined distance threshold, the processing device 112 may send the real-time order to the driver terminal.
  • the processing device may determine a distance between a departure location of the reserved order and the current location of the driver terminal is less than or equal to a third predetermined distance threshold, the processing device 112 may send the reserved order to the driver terminal.
  • the determination unit 606 may be configured to determine whether to allocate the car-hailing order to the driver terminal based on a screening model. In some embodiments, in a predetermined time period, if the order is accepted by a plurality of driver terminals, the determination unit 606 may determine to allocate the order to which driver terminal of the plurality of driver terminals. In some embodiments, the processing device 112 may determine at least two authorized driver terminals among the plurality of driver terminals based on the screening model. The processing device 112 may determine a target driver terminal from the at least two authorized driver terminals based on the screening model and a plurality of second parameters.
  • the generation unit 608 may be configured to generate a matching reference based on the departure location information and the destination information.
  • the processing device 112 may determine the matching reference based on a driver route formed by the departure location information and the destination information of the driver terminal.
  • the calculation unit 610 may be configured to determine a matching degree between the order and the driver terminal.
  • the matching degree may be related to a similarity between the driver route and an order route formed by a departure location and a destination of the order, such as an overlapping ratio between the driver route and the order route, a direction angle between the driver route and the order route, etc. The higher the similarity is, the higher the matching degree is.
  • the calculation unit 610 may determine the matching degree between the order and the matching reference of the driver terminal based on a plurality of first parameters and a correspondent weight thereof, such as a distance between the departure location and a destination of the order, a detour ratio, a carpool ratio.
  • the order allocation device 600 in the present disclosure may be used to perform one or more operations of process 400 as described in FIG. 4.
  • the implementation principle and technical effects of the order allocation device 600 may be similar to the process 400, which can refer to the descriptions in FIG. 4 and is not repeated herein.
  • the units of the device 600 may be hardware circuits of all or part of the processing device 112.
  • the units of the device 600 may also be implemented as an application or set of instructions read and executed by the processing device 112. Further, the units may be any combination of the hardware circuits and the application/instructions.
  • the units may be the part of the processing device 112 when the processing device 112 is executing the application/set of instructions.
  • the order allocation device 600 may further include a storage unit (not shown) .
  • the storage unit may be configured to store data generated during any process performed by the above mentioned units.
  • FIG. 7 is a block diagram illustrating an exemplary device for order allocation according to some embodiments of the present disclosure.
  • the device 700 (also referred to as the order allocation device 700) may be applicable to a user terminal (e.g., a driver terminal) .
  • the order allocation device 700 may include a second sending unit 702, a display unit 704, a second receiving unit 706, a sequencing unit 708, and a refreshing unit 710.
  • the second sending unit 702 may be configured to send location information of a driver terminal to a server via an order selection page.
  • the second sending unit 702 may detect departure location information and destination information of the driver terminal received via the location interface, and send the departure location information and the destination information of the driver terminal to the server.
  • the second sending unit 702 may detect a current location of the driver terminal via the location interface, and send the current location of the driver terminal to the server.
  • the second receiving unit 706 may be configured to receive at least one car-hailing order (or order) that matches the location information sent by the server.
  • the second receiving unit 706 may receive one or more orders (e.g., order details of the one or more orders) that matches the departure location information and the destination information of the driver terminal sent by the server.
  • the second receiving unit 706 may receive one or more close-to-the current -location orders that matches the current location of the user terminal sent by the server.
  • the display unit 704 may be configured to, if the at least one order is more than one, sequentially display the order details of the at least one car-hailing order on an order list page based on a predetermined sequencing rule.
  • the order details of each order (or the at least one car-hailing order) may be displayed via an order card.
  • the order card may include an order acceptance interface configured to perform an order acceptance operation for the order (or the car-hailing order) , and to send the order acceptance to the server after performing the order acceptance operation.
  • the sequencing unit 708 may be configured to sequence the at least one order (or the at least one car-hailing order) .
  • the at least one order may include a plurality of real-time orders and a plurality of reserved orders.
  • the sequencing unit 708 may sequence the plurality of real-time orders in front of the plurality of reserved orders.
  • the sequencing unit 708 may sequence the plurality of real-time orders based on estimated times of the plurality of real-time orders and/or matching degrees of the plurality of real-time orders.
  • the sequencing unit 708 may sequence the plurality of reserved orders based on estimated times of the plurality of reserved orders and/or matching degrees of the plurality of reserved orders. Then the sequenced real-time orders and reserved orders may be displayed by the display unit 704.
  • the refreshing unit 710 may be configured to refresh the order list page based on a predetermined period (e.g., 1 minute, 5 minutes, 10 minutes, etc. ) .
  • a predetermined period e.g. 1 minute, 5 minutes, 10 minutes, etc.
  • the refreshing unit 710 may display the new order on the order list page.
  • the order allocation device 700 in the present disclosure may be used to perform one or more operations of process 500 as described in FIG. 5.
  • the implementation principle and technical effects of the order allocation device 700 may be similar to the process 500, which can refer to the descriptions in FIG. 5 and is not repeated herein.
  • the units of the device 700 may be hardware circuits of all or part of the processing device 112.
  • the units of the device 700 may also be implemented as an application or set of instructions read and executed by the processing device 112. Further, the units may be any combination of the hardware circuits and the application/instructions.
  • the units may be the part of the processing device 112 when the processing device 112 is executing the application/set of instructions.
  • FIG. 8 is a flowchart illustrating an exemplary process for car-hailing order allocation according to some embodiments of the present disclosure.
  • one or more operations of process 800 may be implemented on the O2O service system 100 as illustrated in FIG. 1, or the computing device 200 as illustrated in FIG. 2, or the mobile device 300 as illustrated in FIG. 3.
  • one or more operations in the process 800 may be stored in the storage device 150 and/or the storage (e.g., the ROM 230, the RAM 240, etc. ) as a form of instructions, and invoked and/or executed by the processing device 112, or the processor 220 of the processing device 112) .
  • the instructions may be transmitted in a form of electronic current or electrical signals.
  • the processing device 112 may match the real-time order to a driver terminal, and determine whether the real-time order matches the driver terminal. In some embodiments, the processing device 112 may determine a distance between the departure location of the real-time order and a current location of the driver terminal. If the distance between the departure location of the real-time order and the current location of the driver terminal is less than or equal to a second predetermined distance threshold, the processing device 112 may determine that the real-time order matches the driver terminal. In some embodiments, the processing device 112 may match the real-time order to more than one driver terminal. In response to a determination that the real-time order matches the driver terminal, the processing device 112 may proceed to operation 806.
  • the processing device 112 may send the real-time order to the driver terminal. For example, the processing device 112 may send the order details of the real-time order to the driver terminal. In some embodiments, if the real-time order matches more than one driver terminal, the processing device 112 may send the order details of the real-time order to the more than one driver terminal. In 808, the processing device 112 may determine whether to allocate the order to the driver terminal based on a screening model.
  • the processing device 112 may send the departure location information and the destination information of the driver terminal to a server to perform the search operation.
  • the processing device 112 may receive one or more orders that matches the departure location information and the destination information of the driver terminal sent by the server.
  • the processing device 112 may access an order list page to check the one or more orders.
  • the order list page may include order details of the one or more orders.
  • the processing device 112 may send an order acceptance of the driver terminal via a “take” button (e.g., the take button as illustrated in FIG. 10B) .
  • the processing device 112 may determine whether the order is successfully taken by the driver terminal.
  • the order display area 1006 may display the total number of hitchhike orders (e.g., 20 orders as shown in FIG. 10B) and displays one or more hitchhike orders. As shown in FIG. 10D, a hitchhike order may be displayed via an order card 1010.
  • the order card 1010 may be configured to display order details of an order, such as a departure time, a travel distance, a departure location, a destination, a portrait of passenger, a matching degree, or the like, or any combination thereof.
  • the order card 1010 may further include a “take” button to help a driver of the driver terminal to accept the order.
  • the order display area 1006 may further include a “check all hitchhike orders” button at the bottom of the order display area 1006.
  • the order selection page may be switch to an order list page, e.g., the hitchhike order list page as shown in FIG. 10E.
  • the hitchhike order list page includes location input box 1002 and the order display area 1006.
  • the location input box 1002 includes a departure location “Houchangcun Road No. 30, South Gate” and a destination “Xi’erqi Bridge East, Bus Station. ”
  • the order display area 1006 shows the total number of hitchhike orders, e.g., 13 orders.
  • the user may check all the hitchhike orders by sliding up the hitchhike order list page.
  • the hitchhike orders may be sequenced based on the matching degree between the order and the driver terminal and/or the departure time of the order. In some embodiments, the orders with higher matching degree may be sequenced before the orders with lower matching degree. In some embodiments, the hitchhike orders may include real-time orders whose departure time is “depart now” , and reserved orders whose departure time is displayed as today, tomorrow, the day after tomorrow, or a specific data format (e.g., 2019/01/14) , etc. The real-time orders may be sequenced before the reserved orders to ensure the real-time orders are timely checked by the driver terminal.
  • a distance between the departure location of the real-time orders and the current location of the vehicle may be less than 3km such that the driver terminal can pick-up the passenger of the order timely.
  • the hitchhike orders may be refreshed based on a specific cycle. In some embodiments, the hitchhike orders may be refreshed automatically. Alternatively, the refreshment of the hitchhike orders may be initiated by the user (e.g., the driver) . For example, the user may slide up the hitchhike order list page to load new hitchhike orders.
  • the user may click the “I know” button to return the order selection page and/or the hitchhike order list page.
  • a prompt “successfully taken” may be displayed.
  • the hitchhike order list page may be switched to a pick-up page.
  • FIG. 10I shows an exemplary close-to-the current -location order list according to some embodiments of the present disclosure.
  • the close-to-the current -location order list only includes an order display area 1014.
  • the order display area 1014 shows the total number of close-to-the current -location orders (e.g., 23 close-to-the current -location orders) .
  • the user may check all the hitchhike orders by sliding up the hitchhike order list page.
  • Each close-to-the current -location order may be displayed via an order card 1014.
  • the order card 1014 may be configured to display order details of a close-to-the current -location order, such as a departure time, a travel distance, a departure location, a destination, a portrait of passenger, a matching degree, or the like, or any combination thereof.
  • the order card 1014 may further include a “take” button to help a driver of the driver terminal to accept the order.
  • the driver may select a hitchhike order.
  • the driver may select a close-to-the current -location order.
  • FIG. 11 is a block diagram illustrating an exemplary server according to some embodiments of the present disclosure.
  • the server 1100 may include a storage 1102, a processor 1104, and an order allocation device 1106.
  • the storage 1102 may store a set of instructions.
  • the processor 1104 may execute the set of instructions to implement one or more operations of the above order allocation process (e.g., the process 400, the process 800) .
  • the processor 1104 may execute the set of instructions to implement the order allocation device 1106 or the order allocation device 600.
  • the present disclosure may further provide a non-transitory computer-readable storage medium.
  • the non-transitory computer-readable storage medium may include computer programs.
  • the computer programs may be executed by a processor (e.g., the processor 1204) to implement operations including: sending location information of a driver terminal to a server via an order selection page, and receiving order details of at least one car-hailing order that matches the location information sent by the server; and if the at least one order is more than one, sequentially displaying the order details of the at least one car-hailing order on an order list page based on a predetermined sequencing rule, the order details of each of the at least one order being displayed via an order card, wherein the order card includes an order acceptance interface configured to perform an order acceptance operation for the order and to send the order acceptance to the server after performing the order acceptance operation.
  • the implementation principle and technical effects of the non-transitory computer readable storage medium may be similar to the process 500, which can refer to the descriptions in FIG. 5 and is not repeated herein.
  • the first route may be determined based on, e.g., a distance between the current location of the vehicle and the departure location of the order, a predicted travel time (e.g., a historical average travel time) driving from the current location of the vehicle to the departure location of the order, a traffic condition, the service provider’s preference, or the like, or any combination thereof.
  • the first route may be a route with a smallest distance, a route with a least predicted travel time, or a route chosen by most historical drivers.
  • the first route may also be designated by the service requester (e.g., the driver of the vehicle) .
  • the first predetermined duration may be a default value or an empirical value related to the O2O service system 100.
  • the first predetermined duration may vary with different scenarios.
  • the first predetermined duration may include a duration for the vehicle to change lanes, a response duration of the service provider (e.g., the driver of the vehicle) , a response duration of the O2O service system 100, a duration when the vehicle is banned from changing lanes near the direction adjustment location (for example, the vehicle is banned from changing lanes within a threshold distance to the direction adjustment location) , or the like, or any combination thereof.
  • the response duration of the service provider may be a time spent by the service provider from receiving an order to confirming the order.
  • the response duration of the O2O service system 100 may be a time spent from allocating the order to the service provider to being received by the service provider.
  • the machine learning model may include one or more model parameters, such as real-time road conditions, road grades, a historical average speed of a lane in which the vehicle is running, an average speed of the vehicle, a request time of the order, traffic regulations, or the like, or any combination thereof.
  • Each model parameter may be given a corresponding weight.
  • a comparison result may be determined based on the classification model.
  • the classification model may output the comparison result based on an input of the first predetermined duration and the first predetermined information, and/or the model parameter (s) and its corresponding weight.
  • the processing device 112 may allocate the order to the vehicle. If the first estimation duration is less than the first predetermined duration, which indicates that the service provider does not have enough time to adjust the driving direction of the vehicle at the direction adjustment location, the processing device 112 may further analyze a driving behavior of the service provider to determine whether to allocate the order to the vehicle. For example, the processing device 112 may determine an expected driving route of the vehicle, and further determine whether to allocate the order to the vehicle.
  • the processing device 112 may obtain a plurality of candidate driving route, and select one of the plurality of candidate driving routes as the expected driving route of the vehicle based on second predetermined information.
  • the processing device 112 may further determine whether to allocate the order to the vehicle based on the expected driving route of the vehicle.
  • the processing device 112 may determine a driving direction of the vehicle at the direction adjustment location of the vehicle based on the expected driving route.
  • the processing device 112 may allocate the order to the vehicle.
  • the expected driving route may be a segment of the first route, therefore the driving direction of the expected driving route is consistent with the first route, and it is suitable for the vehicle to execute the order.
  • the processing device 112 may determine an expected location on the expected driving route after a second predetermined duration.
  • the expected location may refer to a location after passing the direction adjustment location.
  • the processing device 112 may determine a cost for accepting the order based on the departure location and the expected location of the vehicle. For example, the processing device 112 may determine whether a distance between the expected location and the departure location of the order is less than or equal to a predetermined distance, and whether a second estimated duration driving from the expected location to the departure location of the order is less than or equal to a third predetermined duration.
  • the processing device 112 may allocate the order to the vehicle. More descriptions regarding whether to allocate the order to the vehicle may be found elsewhere in the present disclosure (e.g., FIG. 14 and the descriptions thereof) .
  • the processing device 112 may determine whether to allocate an order to a vehicle by considering the driving status of the vehicle, which may avoid the driver of the vehicle to make a detour to pick up a passenger of the order, saving the time of the driver and/or the passenger. Besides, the processing device 112 may allocate orders to suitable vehicles (or drivers) , which may improve the transaction rate of orders, increasing the efficiency of order allocation and saving computing load.
  • the processing device 112 may allocate the order to the vehicle.
  • FIG. 14 is a flowchart illustrating an exemplary process for order allocation according to some embodiments of the present disclosure.
  • one or more operations of process 1400 may be implemented on the O2O service system 100 as illustrated in FIG. 1, or the computing device 200 as illustrated in FIG. 2, or the mobile device as illustrated in FIG. 3.
  • one or more operations in the process 1400 may be implemented as a set of instructions (e.g., an application) stored in a storage device (e.g., the storage device 160, the ROM 230, the RAM 240, and/or the storage 390) .
  • a storage device e.g., the storage device 160, the ROM 230, the RAM 240, and/or the storage 390.
  • the processing device 112 may execute the set of instructions and may accordingly be directed to perform the process 1400.
  • the instructions may be transmitted in a form of electronic current or electrical signals.
  • the processing device 112 may obtain a departure location of an order and a current location of a vehicle.
  • the processing device 112 e.g., the obtaining unit 1502 may determine a first route from the current location of the vehicle to the departure location of the order, and determine a direction adjustment location of the vehicle based on the first route.
  • the processing device 112 e.g., the prediction unit 1504 may determine a first estimated duration driving from the current location to the direction adjustment location based on a first predetermined information.
  • Operations 1402-1406 may be performed in a similar manner with operations 1302-1306, and the descriptions thereof are not repeated herein.
  • the processing device 112 may determine whether the first estimated duration is greater than or equal to a first predetermined duration.
  • the processing device 112 may allocate the order to the vehicle.
  • the processing device 112 may determine an expected driving route of the vehicle. More descriptions regarding the determination of the expected driving route may be found elsewhere in the present disclosure. See, e.g., operation 1308 and the relevant descriptions thereof.
  • the processing device 112 may determine an expected location on the expected driving route after a second predetermined duration, and determine a distance between the expected location and the departure location of the order and a second estimated duration driving from the expected location to the departure location of the order.
  • the second predetermined duration may be a default value or an empirical value related to the O2O service system 100.
  • the second predetermined duration may refer to a period that the processing device 112 spent on determining the expected driving route.
  • the vehicle may have traveled a distance on the expected driving route after the second predetermined duration.
  • the expected location may refer to a location on the expected driving route where the vehicle locates after the second predetermined duration.
  • the expected location may refer to a location after passing the direction adjustment location.
  • the expected location may be determined based on, e.g., the second predetermined duration, a type of a lane in which the vehicle is running, a current speed of the vehicle, real-time road conditions, a number of vehicles at the direction adjustment location, or the like, or any combination thereof.
  • the processing device 112 may obtain the distance between the expected location and the departure location of the order from a storage device (e.g., the storage device 150) of the O2O service system 100 or an external source (e.g., a third-party map) . Similar to the determination of the first estimated duration, the second estimated duration may be determined based on a third predetermined information.
  • the third predetermined information may include the distance between the expected location and the departure location of the order, a type of a lane in which the vehicle is running, a current speed of the vehicle, road grades, speed grades, real-time road conditions, a number of vehicles on the expected driving route, or the like, or any combination thereof.
  • the second estimated duration may be determined based on the distance between the expected location and the departure location of the order, the current speed of the vehicle, or the like.
  • the processing device 112 may determine whether the distance is less than or equal to a predetermined distance and whether the second estimated duration is less than or equal to a third predetermined duration.
  • the predetermined distance and/or the third predetermined duration may be an empirical value or a default value stored in the O2O system 100.
  • the predetermined distance and/or the third predetermined duration may be set or adjusted by a passenger (e.g., a service requester) or a driver (e.g., a service provider) .
  • the predetermined distance and/or the third predetermined duration may vary under different conditions. For example, the predetermined distance may be set with a relatively small value and the third predetermined duration may be set with a relatively great value in the peak hours.
  • the processing device 112 may proceed to operation 1418.
  • the processing device 112 e.g., the allocation sub-unit 1608 of the allocation unit 1506 may allocate the order to the vehicle.
  • the processing device 112 may proceed to operation 1420.
  • the processing device 112 e.g., the allocation sub-unit 1608 of the allocation unit 1506
  • the candidate vehicle may satisfy that the distance between a current location of the candidate vehicle and the departure location of the order is less than or equal to the predetermined distance, and a second estimated duration from the current location of the candidate vehicle to the departure location of the order is less than or equal to the third predetermined duration.
  • the processing device 112 may allocate the order to the vehicle, ensuring that the order may be accepted by at least one vehicle.
  • the processing device 112 may determine whether to allocate the order to the vehicle based on the distance between the expected location of the vehicle and the departure location of the order, or the second estimated duration driving from the expected location to the departure location of the order. For example, if the distance is less than or equal to the predetermined distance, the processing device 112 may allocate the order to the vehicle. As another example, if the second estimated duration is less than or equal to the third predetermined duration, the processing device 112 may allocate the order to the vehicle.
  • FIG. 15 is a block diagram illustrating an exemplary order allocation device 1500 according to some embodiments of the present disclosure.
  • the order allocation device 112 may include an obtaining unit 1502, a prediction unit 1504, and an allocation unit 1506.
  • the obtaining unit 1502 may be configured to obtain a departure location of an order and a current location of a vehicle.
  • the obtaining unit 1502 may further be configured to determine a first route from the current location of the vehicle to the departure location of the order, and determine a direction adjustment location of the vehicle based on the first route. More descriptions regarding the departure location of an order and the current location of a vehicle may be found elsewhere in the present disclosure. See, e.g., operation 1302 of process 1300 and the relevant descriptions thereof. More descriptions regarding the determination of the first route and the determination of the direction adjustment location may be found elsewhere in the present disclosure. See, e.g., operation 1304 of process 1300 and the relevant descriptions thereof.
  • the obtaining unit 1502 may obtain information of the order and/or information of the vehicle.
  • the information of the order may include an order number, a coordinate of the departure location (e.g., latitude-longitude coordinates) , a coordinate of a destination (e.g., latitude-longitude coordinates) , a departure time, contact information (e.g., a telephone number, a Wechat TM account, a QQ TM account, etc. ) , or the like, or any combination thereof.
  • the information of the vehicle may include a coordinate of the current location (e.g., latitude-longitude coordinates) , a serial number of a driver (e.g., a service provider) of the vehicle, driving experience, a vehicle type, a license plate number, a driving license number, or the like, or any combination thereof.
  • the prediction unit 1504 may be configured to determine a first estimated duration driving from the current location to the direction adjustment location.
  • the first estimated duration may be determined based on a first predetermined information. More descriptions regarding the determination of the first estimated duration may be found elsewhere in the present disclosure. See, e.g., operation 1306 of process 1300 and the relevant descriptions thereof.
  • the allocation unit 1506 may be configured to determine whether to allocate the order to the vehicle. In response to a determination that the first estimated duration is greater than or equal to a first predetermined duration, the allocation unit 1506 may be configured to allocate the order to the vehicle. In response to a determination that the first estimated duration is less than the first predetermined duration, the allocation unit 1506 may be configured to determine an expected driving route of the vehicle, and determine whether to allocate the order to the vehicle based on the expected driving route of the vehicle. More descriptions regarding the allocation of the order, the determination of the expected driving route, and whether to allocate the order to the vehicle may be found elsewhere in the present disclosure. See, e.g., operation 1308 of process 1300 and the relevant descriptions thereof.
  • the units may be hardware circuits of all or part of the processing device 112.
  • the units may also be implemented as an application or set of instructions read and executed by the processing device 112. Further, the units may be any combination of the hardware circuits and the application/instructions.
  • the units may be the part of the processing device 112 when the processing device 112 is executing the application/set of instructions.
  • the units in the order allocation device 1500 may be connected to or communicate with each other via a wired connection or a wireless connection.
  • the wired connection may include a metal cable, an optical cable, a hybrid cable, or the like, or any combination thereof.
  • the wireless connection may include a Local Area Network (LAN) , a Wide Area Network (WAN) , a Bluetooth, a ZigBee, a Near Field Communication (NFC) , or the like, or any combination thereof.
  • LAN Local Area Network
  • WAN Wide Area Network
  • NFC Near Field Communication
  • Two or more of the modules may be combined into a single module, and any one of the modules may be divided into two or more units.
  • the allocation unit 1506 may be divided into a plurality of sub-units. In some embodiments, one or more of the units mentioned above may be omitted. In some embodiments, one or more of the modules mentioned above may be combined into a single module. For example, the prediction unit 1504 and the allocation unit 1506 may be integrated into a single module. In some embodiments, the order allocation device 1500 may further include one or more additional units, such as a storage unit.
  • FIG. 16 is a block diagram illustrating an exemplary allocation unit 1506 according to some embodiments of the present disclosure.
  • the allocation unit 1506 may include a route determination sub-unit 1602, a calculation sub-unit 1604, a judgment sub-unit 1606, and an allocation sub-unit 1608.
  • the route determination sub-unit 1602 may be configured to determine an expected driving route of a vehicle. In some embodiments, if the vehicle does not have an on-going order, the route determination sub-unit 1602 may be configured to obtain a plurality of candidate driving routes, and select one of the plurality of candidate driving routes as the expected driving route of the vehicle based on a first predetermined information. If the vehicle has an on-going order, the route determination sub-unit 1602 may be configured to obtain a second route related to the on-going order, and determine the second route as the expected driving route of the vehicle. The second route may be a route from the current location of the vehicle to a departure location or a destination of the on-going order. More descriptions regarding the determination of the expected driving route may be found elsewhere in the present disclosure. See, e.g., operation 1308 of process 1300 and the relevant descriptions thereof.
  • the calculation sub-unit 1604 may be configured to determine an expected location on the expected driving route after a second predetermined duration, and determine a distance between the expected location and the departure location of the order and a second estimated duration driving from the expected location to the departure location of the order. More descriptions regarding the determination of the expected location, and the determination of the distance and the second estimated duration may be found elsewhere in the present disclosure. See, e.g., operation 1414 of process 1400 and the relevant descriptions thereof.
  • the judgment unit 1606 may be configured to determine whether the distance is less than or equal to a predetermined distance and whether the second estimated duration is less than or equal to a third predetermined duration. More descriptions of the predetermined distance and the third predetermined duration may be found elsewhere in the present disclosure. See, e.g., operation 1416 of process 1400 and the relevant descriptions thereof.
  • the allocation sub-unit 1608 may be configured to determine the order to the vehicle or other vehicles. In response to a determination that the distance is less than or equal to the predetermined distance and the second estimated duration is less than or equal to the third predetermined duration, the allocation sub-unit 1608 may allocate the order to the vehicle. In response to a determination that the distance is greater than the predetermined distance or the second estimated duration is greater than the third predetermined duration, the allocation sub-unit 1608 may allocate the order to other vehicles (e.g., a candidate vehicle) . If no candidate vehicle is available, the allocation sub-unit 1608 may allocate the order to the vehicle. More descriptions regarding the allocation of the order may be found elsewhere in the present disclosure. See, e.g., operations 1418 and 1420 of process 1400 and the relevant descriptions thereof.
  • the above descriptions of the allocation unit 1506 is provided for the purposes of illustration, and is not intended to limit the scope of the present disclosure. For persons having ordinary skills in the art, multiple variations and modifications may be made under the teachings of the present disclosure. However, those variations and modifications do not depart from the scope of the present disclosure.
  • one or more of the sub-units mentioned above may be omitted.
  • one or more of the sub-units mentioned above may be combined into a single unit.
  • the judgment sub-unit 1606 and the allocation sub-unit 1608 may be integrated into a single unit.
  • the allocation unit 1506 may further include one or more additional sub-units, such as a storage sub-unit.
  • FIG. 17 is a schematic block diagram of a computer device 1700 according to some embodiments of the present disclosure.
  • the computer device 1700 may include a storage 1702 and a processor 1704.
  • the storage 1702 may include a set of instructions.
  • the processor 1704 may execute the set of instructions to implement one or more operations of the process for order allocation (e.g., the process 1300, the process 1400) .
  • the present disclosure may further provide a non-transitory computer-readable storage medium.
  • the non-transitory computer-readable storage medium may include computer programs.
  • the computer programs may be executed by a processor (e.g., the processor 1704) to implement one or more operations of the process for order allocation (e.g., the process 1300, the process 1400) .
  • aspects of the present disclosure may be illustrated and described herein in any of a number of patentable classes or context including any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof. Accordingly, aspects of the present disclosure may be implemented entirely hardware, entirely software (including firmware, resident software, micro-code, etc. ) or combining software and hardware implementation that may all generally be referred to herein as a "block, " “module, ” “engine, ” “unit, ” “component, ” or “system. ” Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer readable media having computer readable program code embodied thereon.
  • a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including electro-magnetic, optical, or the like, or any suitable combination thereof.
  • a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that may communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
  • Program code embodied on a computer readable signal medium may be transmitted using any appropriate medium, including wireless, wireline, optical fiber cable, RF, or the like, or any suitable combination of the foregoing.
  • Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB. NET, Python or the like, conventional procedural programming languages, such as the “C” programming language, Visual Basic, Fortran 1703, Perl, COBOL 1702, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) or in a cloud computing environment or offered as a service such as a software as a service (SaaS) .
  • LAN local area network
  • WAN wide area network
  • an Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, etc.
  • SaaS software as a service

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Human Resources & Organizations (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Finance (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Accounting & Taxation (AREA)
  • Tourism & Hospitality (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Game Theory and Decision Science (AREA)
  • Educational Administration (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Traffic Control Systems (AREA)

Abstract

L'invention concerne un procédé d'attribution de commandes. Le procédé peut consister à recevoir des informations d'emplacement comprenant des informations d'emplacement de départ et des informations de destination d'un terminal utilisateur envoyées par le terminal utilisateur. Le procédé peut en outre consister à envoyer au moins une commande qui correspond aux informations d'emplacement au terminal utilisateur, et à recevoir une acceptation de commande pour une commande de la ou des commandes à partir du terminal utilisateur. Le procédé peut en outre consister à déterminer s'il faut attribuer la commande au terminal utilisateur sur la base d'un modèle de criblage.
PCT/CN2019/087496 2018-05-18 2019-05-17 Systèmes et procédés d'attribution de commandes WO2019219088A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN201810482072.2A CN108805411A (zh) 2018-05-18 2018-05-18 网约车订单分配方法、装置、服务器、终端和可读存储介质
CN201810482072.2 2018-05-18
CN201810573367.0 2018-06-06
CN201810573367.0A CN110570263B (zh) 2018-06-06 2018-06-06 订单分配方法、分配系统、计算机设备及可读存储介质

Publications (1)

Publication Number Publication Date
WO2019219088A1 true WO2019219088A1 (fr) 2019-11-21

Family

ID=68539521

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/087496 WO2019219088A1 (fr) 2018-05-18 2019-05-17 Systèmes et procédés d'attribution de commandes

Country Status (1)

Country Link
WO (1) WO2019219088A1 (fr)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111008792A (zh) * 2019-12-24 2020-04-14 北京三快在线科技有限公司 订单分配方法、装置、服务器和存储介质
CN111222911A (zh) * 2019-12-03 2020-06-02 佛山欧神诺云商科技有限公司 基于线上特权订单的客户跟踪方法、设备、介质及系统
CN111461485A (zh) * 2020-03-02 2020-07-28 平安国际智慧城市科技股份有限公司 任务分配方法、装置、设备及计算机可读存储介质
CN111738409A (zh) * 2020-05-14 2020-10-02 华为技术有限公司 一种资源调度的方法及其相关设备
CN111832875A (zh) * 2020-03-19 2020-10-27 北京嘀嘀无限科技发展有限公司 数据处理方法、可读存储介质和电子设备
CN111932050A (zh) * 2020-05-26 2020-11-13 浙江数链科技有限公司 派单方法、装置、计算机设备和计算机可读存储介质
CN113112046A (zh) * 2020-01-13 2021-07-13 北京嘀嘀无限科技发展有限公司 一种出行订单状态的更新方法及更新装置
CN113240897A (zh) * 2020-01-23 2021-08-10 奥迪股份公司 车辆调度方法、系统和计算机可读存储介质
CN113393003A (zh) * 2021-05-27 2021-09-14 浙江吉利控股集团有限公司 一种订单处理方法、装置、服务器及存储介质
CN113469514A (zh) * 2021-06-25 2021-10-01 广州宸祺出行科技有限公司 一种基于预约订单的网约车派单方法、装置及电子设备
CN113990092A (zh) * 2021-09-24 2022-01-28 青岛海尔科技有限公司 出行规划信息的确定方法和装置、存储介质及电子装置
CN114548682A (zh) * 2022-01-19 2022-05-27 浙江吉利控股集团有限公司 订单派发方法、订单派发装置、及计算机可读存储介质
CN115660758A (zh) * 2022-11-21 2023-01-31 苏州大学 网约拼车计费方法及系统

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104167093A (zh) * 2014-08-04 2014-11-26 北京嘀嘀无限科技发展有限公司 基于司机住址信息的顺风车运营系统
CN105957337A (zh) * 2016-06-02 2016-09-21 深圳市永兴元科技有限公司 订单处理方法及装置
CN107016864A (zh) * 2016-01-27 2017-08-04 滴滴(中国)科技有限公司 基于gps的终端信息展示方法及装置
CN108805411A (zh) * 2018-05-18 2018-11-13 北京嘀嘀无限科技发展有限公司 网约车订单分配方法、装置、服务器、终端和可读存储介质

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104167093A (zh) * 2014-08-04 2014-11-26 北京嘀嘀无限科技发展有限公司 基于司机住址信息的顺风车运营系统
CN107016864A (zh) * 2016-01-27 2017-08-04 滴滴(中国)科技有限公司 基于gps的终端信息展示方法及装置
CN105957337A (zh) * 2016-06-02 2016-09-21 深圳市永兴元科技有限公司 订单处理方法及装置
CN108805411A (zh) * 2018-05-18 2018-11-13 北京嘀嘀无限科技发展有限公司 网约车订单分配方法、装置、服务器、终端和可读存储介质

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111222911A (zh) * 2019-12-03 2020-06-02 佛山欧神诺云商科技有限公司 基于线上特权订单的客户跟踪方法、设备、介质及系统
CN111008792A (zh) * 2019-12-24 2020-04-14 北京三快在线科技有限公司 订单分配方法、装置、服务器和存储介质
CN113112046A (zh) * 2020-01-13 2021-07-13 北京嘀嘀无限科技发展有限公司 一种出行订单状态的更新方法及更新装置
CN113240897A (zh) * 2020-01-23 2021-08-10 奥迪股份公司 车辆调度方法、系统和计算机可读存储介质
CN111461485A (zh) * 2020-03-02 2020-07-28 平安国际智慧城市科技股份有限公司 任务分配方法、装置、设备及计算机可读存储介质
CN111832875A (zh) * 2020-03-19 2020-10-27 北京嘀嘀无限科技发展有限公司 数据处理方法、可读存储介质和电子设备
CN111738409B (zh) * 2020-05-14 2024-05-24 华为技术有限公司 一种资源调度的方法及其相关设备
CN111738409A (zh) * 2020-05-14 2020-10-02 华为技术有限公司 一种资源调度的方法及其相关设备
CN111932050A (zh) * 2020-05-26 2020-11-13 浙江数链科技有限公司 派单方法、装置、计算机设备和计算机可读存储介质
CN113393003A (zh) * 2021-05-27 2021-09-14 浙江吉利控股集团有限公司 一种订单处理方法、装置、服务器及存储介质
CN113393003B (zh) * 2021-05-27 2023-11-24 浙江吉利控股集团有限公司 一种订单处理方法、装置、服务器及存储介质
CN113469514B (zh) * 2021-06-25 2024-03-08 广州宸祺出行科技有限公司 一种基于预约订单的网约车派单方法、装置及电子设备
CN113469514A (zh) * 2021-06-25 2021-10-01 广州宸祺出行科技有限公司 一种基于预约订单的网约车派单方法、装置及电子设备
CN113990092A (zh) * 2021-09-24 2022-01-28 青岛海尔科技有限公司 出行规划信息的确定方法和装置、存储介质及电子装置
CN114548682A (zh) * 2022-01-19 2022-05-27 浙江吉利控股集团有限公司 订单派发方法、订单派发装置、及计算机可读存储介质
CN115660758A (zh) * 2022-11-21 2023-01-31 苏州大学 网约拼车计费方法及系统

Similar Documents

Publication Publication Date Title
WO2019219088A1 (fr) Systèmes et procédés d'attribution de commandes
US20190120639A1 (en) Systems and methods for route planning
CN109478364B (zh) 确定预计到达时间的方法及系统
US20210140774A1 (en) Systems and methods for recommending pick-up locations
US11003677B2 (en) Systems and methods for location recommendation
CN109478275B (zh) 分配服务请求的系统和方法
WO2017181932A1 (fr) Systèmes et procédés de recommandation d'heure d'arrivée estimée
CN109429520B (zh) 用于检查作弊服务订单的方法、系统、设备及可读介质
WO2018209551A1 (fr) Systèmes et procédés permettant de déterminer une heure d'arrivée estimée
WO2018227387A1 (fr) Procédés et systèmes de planification d'itinéraire
US20200300650A1 (en) Systems and methods for determining an estimated time of arrival for online to offline services
WO2021012342A1 (fr) Systèmes et procédés de prédiction de trafic
WO2019196509A1 (fr) Systèmes et procédés de détermination d'informations d'invite
WO2017107932A1 (fr) Systèmes et procédés permettant de mettre à jour une séquence de services
JP2021521549A (ja) 走行サービスを推奨するためのシステムおよび方法
CN110839346A (zh) 用于分配服务请求的系统和方法
US11255684B2 (en) Systems and methods for allocating a service request
WO2019158066A1 (fr) Systèmes et procédés d'affichage d'informations
WO2019174620A1 (fr) Dispositifs et procédés de traitement de demande de service
US20220214185A1 (en) Systems and methods for recommendation and display of point of interest
WO2021012244A1 (fr) Systèmes et procédés de répartition de commandes
WO2019154208A1 (fr) Systèmes et procédés de détermination d'une stratégie de fonctionnement pour plateforme de services
WO2019158004A1 (fr) Systèmes et procédés de traitement de demandes de service
WO2020151725A1 (fr) Procédé et dispositif de prédiction d'emplacement

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19804594

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 19804594

Country of ref document: EP

Kind code of ref document: A1