WO2019153944A1 - Systèmes et procédés de communication sécurisée d'informations de service - Google Patents

Systèmes et procédés de communication sécurisée d'informations de service Download PDF

Info

Publication number
WO2019153944A1
WO2019153944A1 PCT/CN2018/124606 CN2018124606W WO2019153944A1 WO 2019153944 A1 WO2019153944 A1 WO 2019153944A1 CN 2018124606 W CN2018124606 W CN 2018124606W WO 2019153944 A1 WO2019153944 A1 WO 2019153944A1
Authority
WO
WIPO (PCT)
Prior art keywords
service provider
target service
service
information
requester terminal
Prior art date
Application number
PCT/CN2018/124606
Other languages
English (en)
Inventor
Bo Zhang
Hongyan XING
Shasha JIAO
Ying QI
Yiliang YANG
Yu Yang
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
Application filed by Beijing Didi Infinity Technology And Development Co., Ltd. filed Critical Beijing Didi Infinity Technology And Development Co., Ltd.
Publication of WO2019153944A1 publication Critical patent/WO2019153944A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/02—Reservations, e.g. for tickets, services or events
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G06Q10/047—Optimisation of routes or paths, e.g. travelling salesman problem
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0609—Buyer or seller confidence or verification
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/06—Buying, selling or leasing transactions
    • G06Q30/0601—Electronic shopping [e-shopping]
    • G06Q30/0633—Lists, e.g. purchase orders, compilation or processing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/40—Business processes related to the transportation industry

Definitions

  • the present disclosure generally relates to service platforms, and in particular, to systems and methods for determining one or more service providers and information related to the one or more service providers for presentation on a requester terminal.
  • a requester may request for a transportation service from an online transportation service platform via his/her requester terminal.
  • the service platform may determine one or more service providers (e.g., one or more drivers) to provide the requested service to the requester.
  • the service platform may further determine and/or transmit information related to the one or more service providers to the requester terminal for presentation.
  • the service platform may determine the service providers according to one or more service requirements (e.g., a type of the requested service, an expected service time or location) of the requester without considering feedbacks regarding the service providers received from historical service requesters.
  • the requester may have been served by a specific service provider and gave a negative feedback regarding the specific service provider.
  • the service platform may determine the specific service provider as one of the service providers of the requester if the service platform determines the service providers without considering the negative feedback regarding the specific service provider, which may result in a poor user experience of the requester.
  • the information related to the determined service providers may normally be presented in the same manner, which is inconvenient and inefficient for the requester to choose a desired service provider from the service providers.
  • a system may include at least one storage medium and at least one processor in communication with the at least one storage medium.
  • the storage medium may include a set of instructions for determining information related to service providers for presentation.
  • the at least one processor may be configured to direct the system to receive a request for a service from a requester terminal via a user interface of the requester terminal.
  • the at least one processor may be configured to direct the system to identify a plurality of service providers in response to the request.
  • the at least one processor may be configured to direct the system to obtain performance information related to the plurality of service providers.
  • the at least one processor may also be configured to direct the system to determine a weight factor of at least one target service provider of the plurality of service providers based on the performance information.
  • the at least one processor may be further configured to direct the system to compile information of the at least one target service provider for presentation on the requester terminal via the user interface based on the weight factor of the at least one target service provider.
  • the request may be for a carpool service from a start location to a destination, and to identify a plurality of service providers in response to the request, the at least one processor may be configured to direct the system to obtain a plurality of travel routes of a plurality of candidate service providers.
  • the at least one processor may be configured to direct the system to match a route from the start location to the destination to each of the plurality of travel routes, and identify the plurality of service providers based on the matching result among the plurality of candidate service providers.
  • the at least one processor may be configured to direct the system to receive location information of the plurality of provider terminals from a plurality of provider terminals of a plurality of candidate service providers.
  • the location information may be acquired using a location detection mechanism of each of the plurality of provider terminals.
  • the at least one processor may also be configured to direct the system to identify the plurality of service providers based at least in part on the location information of the plurality of provider terminals among the plurality of candidate service providers.
  • the performance information related to the plurality of service providers may include one or more feedbacks with respect to the at least one target service provider, and to determine a weight factor of at least one target service provider
  • the at least one processor may be further configured to direct the system to determine whether the at least one target service provider has received a feedback from a user of the requester terminal based on the one or more feedbacks with respect to the at least one target service provider.
  • the at least one processor may also be configured to direct the system to designate the weight factor of the at least one target service provider as a first value according to the feedback received from the user of the requester terminal in response to a determination that the at least one target service provider has received a feedback from the user of the requester terminal.
  • the at least one processor may be further configured to direct the system to designate the weight factor as a second value in response to a determination that the at least one target service provider has not received a feedback from the user of the requester terminal.
  • the second value may be different from the first value.
  • the at least one processor may be further configured to direct the system to determine whether the at least one target service provider has been followed by the user of the requester terminal on a service platform.
  • the at least one processor may also be configured to direct the system to determine that the at least one target service provider has received a feedback from the user of the requester terminal in response to a determination that the at least one target service provider is followed by the user of the requester terminal on the service platform.
  • the performance information related to the plurality of service providers may include one or more feedbacks with respect to the at least one target service provider, and to determine the weight factor of at least one target service provider
  • the at least one processor may be further configured to direct the system to determine whether the at least one target service provider has received a historical feedback from a user of the requester terminal based on the one or more historical feedbacks with respect to the at least one target service provider.
  • the at least one processor may be configured to direct the system to determine the weight factor of the at least one target service provider according to the feedback received from the user of the requester terminal in response to a determination that the at least one target service provider has received a feedback from the requester terminal.
  • the at least one processor may be configured to direct the system to determine the weight factor of the at least one target service provider based on the one or more feedbacks with respect to the at least one target service provider in response to a determination that the at least one target service provider has not received a historical feedback from the user of the requester terminal.
  • the at least one processor may be further configured to direct the system to determine at least one representative historical feedback from the one or more feedbacks.
  • the at least one processor may be configured to direct the system to determine a credit score of the at least one target service provider based at least in part on the at least one representative feedback.
  • the at least one processor may be configured to direct the system to determine the weight factor of the at least one target service provider based on the credit score of the at least one target service provider.
  • the performance information related to the plurality of service providers may include one or more feedbacks with respect to the plurality of service providers, and to determine a weight factor of at least one target service provider of the plurality of service providers, the at least one processor may be further configured to direct the system to remove one or more service providers who have received a negative feedback from a user of the requester terminal from the plurality of service providers. The at least one processor may be configured to direct the system to determine the weight factor of the at least one target service provider of the remaining of the plurality of service providers based on the performance information.
  • the at least one target service provider may include a plurality of target service providers, and to compile information of the at least one target service provider based on the weight factor of the at least one target service provider, the at least one processor may be further configured to direct the system to determine a ranking of the plurality of target service providers based on the weight factors of the plurality of target service providers. The at least one processor may be configured to direct the system to compile the information of the plurality of target service providers into a list based on the ranking of the plurality of target service providers. The at least one processor may be configured to direct the system to transmit an instruction to the requester terminal to present the list via the user interface.
  • the at least one processor may be further configured to direct the system to transmit an instruction to present an invitation for a feedback regarding one or more of the at least one target service provider via the user interface to the requester terminal.
  • the service may include at least one of a taxi-hailing service, a chauffeur service, an express car service, a carpool service, a bus service, a driver hire service, a shuttle service, a meal delivery service, a delivery service, a meal service, or a shopping service.
  • the received request may be encrypted, and the at least one processor may be further configured to direct the system to decrypt the encrypted request.
  • the at least one processor may be further configured to direct the system to verify authentication information of the requester terminal or a user of the requester terminal before the decrypting.
  • the at least one processor may be further configured to direct the system to encrypt the compiled information of the at least one target service provider for presentation on the requester terminal via the user interface and transmit the encrypted information to the requester terminal.
  • the encrypted information may include authentication information of the requester terminal or a user of the requester terminal to authenticate the requester terminal or the user.
  • a terminal device may include a user interface, at least one storage medium including a set of instructions for displaying information related to service providers, and at least one processor in communication with the at least one storage medium.
  • the at least one processor may be configured to direct the terminal device to receive a request for a service via the user interface.
  • the at least one processor may be configured to direct the system to send the request to a service platform.
  • the at least one processor may be configured to direct the system to receive information of at least one target service provider from the service platform, and the received information may include a weight factor of the at least one target service provider.
  • the at least one processor may also be configured to direct the system to presenting the information of the at least one target service provider via the user interface according to the weight factor, and the weight factor of the at least one target service provider is associated with performance information of the at least one target service provider.
  • a method may be implemented on a computing device having at least one processor and at least one computer-readable storage medium including a set of instructions for determining information related to service providers for presentation.
  • the method may include receiving a request for a service from a requester terminal via a user interface of the requester terminal.
  • the method may include obtaining performance information related to the plurality of service providers.
  • the method may also include determining a weight factor of at least one target service provider of the plurality of service providers based on the performance information.
  • the method may further include compiling information of the at least one target service provider for presentation on the requester terminal via the user interface based on the weight factor of the at least one target service provider.
  • a method may be implemented on a terminal device having a user interface, at least one processor, and at least one storage medium including a set of instructions for determining information related to service providers for presentation.
  • the method may include receiving a request for a service via the user interface.
  • the method may include sending the request to a service platform.
  • the method may also include receiving information of at least one target service provider from the service platform, and the received information may include a weight factor of the at least one target service provider.
  • the method may further include presenting the information of the at least one target service provider via the user interface according to the weight factor, wherein the weight factor of the at least one target service provider is associated with performance information of the at least one target service provider.
  • the system for determining information related to service providers for presentation may include an obtaining module, an identifying module, a determination module, and a compiling module.
  • the obtaining module may be configured to receive a request for a service from a requester terminal via a user interface of the requester terminal and obtain performance information related to the plurality of service providers.
  • the identifying module may be configured to identify a plurality of service providers in response to the request.
  • the determination module may be configured to determine a weight factor of at least one target service provider of the plurality of service providers based on the performance information.
  • the compiling module may be configured to compile information of the at least one target service provider for presentation on the requester terminal via the user interface based on the weight factor of the at least one target service provider.
  • a terminal device may include a receiving module, a communication module, and a presentation module.
  • the receiving module may be configured to receive a request for a service via a user interface of the terminal device.
  • the communication module may be configured to send the request to a service platform, and receive information of at least one target service provider from the service platform, and the received information may include a weight factor of the at least one target service provider.
  • the presentation module may be configured to present the information of the at least one target service provider via the user interface according to the weight factor, wherein the weight factor of the at least one target service provider is associated with performance information of the at least one target service provider.
  • a non-transitory computer-readable storage medium may embody a computer program product.
  • the computer program product may include instructions configured to cause a computing device to perform a method.
  • the method may include receiving a request for a service via a user interface of a requester terminal.
  • the method may include sending the request to a service platform.
  • the method may also include receiving information of at least one target service provider from the service platform, and the received information may include a weight factor of the at least one target service provider.
  • the method may further include presenting the information of the at least one target service provider via the user interface according to the weight factor, wherein the weight factor of the at least one target service provider is associated with performance information of the at least one target service provider.
  • FIG. 1 is a block diagram illustrating an exemplary service system according to some embodiments of the present disclosure
  • FIG. 2 is a schematic diagram illustrating exemplary hardware and software components of an exemplary computing device according to some embodiments of the present disclosure
  • FIG. 3 is a schematic diagram illustrating exemplary hardware and/or software components of an exemplary mobile device according to some embodiments of the present disclosure
  • FIG. 4 is a block diagram illustrating an exemplary processing engine according to some embodiments of the present disclosure
  • FIG. 5 is a flowchart illustrating an exemplary process for determining information related to service providers for presentation on a user interface of a requester terminal according to some embodiments of the present disclosure
  • FIG. 6 is a flowchart illustrating an exemplary process for identifying a plurality of service providers in response to a request for a service according to some embodiments of the present disclosure
  • FIG. 7 is a flowchart illustrating an exemplary process for determining a weight factor of a target service provider according to some embodiments of the present disclosure
  • FIG. 8 is a flowchart illustrating an exemplary process for determining a weight factor of a target service provider based on one or more feedbacks with respect to the target service provider according to some embodiments of the present disclosure
  • FIG. 9A is a block diagram illustrating an exemplary requester terminal according to some embodiments of the present disclosure.
  • FIG. 9B is a flowchart illustrating an exemplary process for presenting information related to service providers on a user interface of a requester terminal according to some embodiments of the present disclosure
  • FIGs. 10 to 15 illustrate exemplary user interfaces of a requester terminal of a passenger for evaluating a driver according to some embodiments of the present disclosure
  • FIGs. 16 and 17 illustrate exemplary user interfaces of a requester terminal of a passenger for requesting a transportation service 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.
  • the system and method in the present disclosure is described primarily in regard to distributing a request for a transportation service, it should also be understood that the present disclosure is not intended to be limiting.
  • the system or method of the present disclosure may be applied to any other kind of services.
  • the system or method of the present disclosure may be applied to transportation systems of different environments including land, ocean, aerospace, or the like, or any combination thereof.
  • the vehicle of the transportation systems may include a taxi, a private car, a hitch, a bus, a train, a bullet train, a high speed rail, a subway, a vessel, an aircraft, a spaceship, a hot-air balloon, a driverless vehicle, or the like, or any combination thereof.
  • the transportation system may also include any transportation system for management and/or distribution, for example, a system for sending and/or receiving an express.
  • the application of the system or method of the present disclosure may be implemented on a user device and include a webpage, a plug-in of a browser, a client terminal, a custom system, an internal analysis system, an artificial intelligence robot, or the like, or any combination thereof.
  • passenger " “requester, “ “service requester, “ 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, “ and “service provider” 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.
  • service request “ “request for a service, “ “requests, “ and “order” in the present disclosure are used interchangeably to refer to a request that may be initiated by a passenger, a service requester, a customer, a driver, a provider, a service provider, or the like, or any combination thereof.
  • the service request may be accepted by any one of a passenger, a service requester, a customer, a driver, a provider, or a service provider.
  • the service request may be chargeable or free.
  • service provider terminal “provider terminal, ” and “driver terminal” in the present disclosure are used interchangeably to refer to a mobile terminal that is used by a service provider to provide a service or facilitate the providing of the service.
  • service requester terminal “ “requester terminal, ” and “passenger terminal” in the present disclosure are used interchangeably to refer to a mobile terminal that is used by a service requester to request or order a service.
  • the positioning technology used in the present disclosure may be based on a global positioning system (GPS) , a global navigation satellite system (GLONASS) , a compass navigation system (COMPASS) , a Galileo positioning system, a quasi-zenith satellite system (QZSS) , a wireless fidelity (WiFi) positioning technology, or the like, or any combination thereof.
  • GPS global positioning system
  • GLONASS global navigation satellite system
  • COMPASS compass navigation system
  • Galileo positioning system Galileo positioning system
  • QZSS quasi-zenith satellite system
  • WiFi wireless fidelity positioning technology
  • An aspect of the present disclosure relates to systems and methods for determining information related to service providers for presentation on a requester terminal.
  • the systems and methods may receive a request for a service from the requester terminal via a user interface of the requester terminal.
  • the systems and methods may identify a plurality of service providers in response to the request for service, and obtain performance information related to the plurality of service providers (e.g., one or more feedbacks regarding the service providers) .
  • the systems and methods may further determine a weight factor of at least one target service provider of the plurality of service providers based on the performance information, and compile information of the at least one target service provider for presentation on the requester terminal via the user interface based on the weight factor of the at least one target service provider.
  • the target service provider and the information thereof are determined based on the performance information of the service providers.
  • the systems and methods may determine the weight factor of a target service provider based on a feedback of the target service provider received from a requester of the requester terminal or other requesters.
  • the weight factor of the target service provider may be associated with what information related to the target service provider is to be presented on the requester terminal and/or the way of presentation of the information related to the target service provider.
  • the weight factor of the target service provider may be high (e.g., higher than a threshold) .
  • the information related to the target service provider may be presented in a more visible and/or accessible way such that the target service provider is more likely to be chosen by the requester.
  • the weight factor of the target service provider may be low (e.g., lower than a threshold) or the target service provider may be removed.
  • the information related to the target service provider may not be presented or be presented in a less visible and/or accessible way.
  • the systems and methods may allow use of information of multiple dimensions to determine or predict suitability of pairing a service provider with a service requester.
  • Information of multiple dimensions may include information from, e.g., different times (e.g., historical information, real time information) , different sources (information from different users including service requesters, service providers, etc. ) to improve reliability or accuracy of the determination or prediction.
  • the reliability or accuracy of the determination or prediction may be further improved by assigning different importance to different information of multiple dimensions based on, e.g., relevance of the information.
  • Information related to one or more target service providers so determined may be transmitted to a requester terminal for presentation.
  • the systems and methods may improve the presentation on the user interface by selectively identifying specific information to be presented in a specific manner.
  • the systems and methods may employ at least one of techniques including embedding authentication information in the request to the system (e.g., a service platform) and/or in the information to a requester terminal, encrypting data for transmission, decrypting received data if the embedded authentication information is verified, or the like, or a combination thereof.
  • This may allow secured communication and/or accurate transmission of specific data to specific requester terminals and/or users (service requesters, service providers, etc. ) .
  • One of the problems solved by the systems and methods of the present disclosure is the big data problem and its real time application faced by an online service system including, for example, an ineffective use of data for determine service providers and information related to service requesters.
  • Further problems solved by the systems and methods of the present disclosure include secured communication in real time between a large number of user devices (e.g., provider terminals, requester terminals) and/or accurate transmission of specific data to specific provider terminals and/or specific requester terminals.
  • FIG. 1 is a block diagram illustrating an exemplary service system according to some embodiments of the present disclosure.
  • the service system 100 may be configured to provide one or more services.
  • the service (s) may include any product, such as but not limited to food, medicine, commodity, chemical product, electrical appliance, clothing, car, housing, luxury, a servicing product, a financial product, a knowledge product, an Internet product.
  • the service (s) may include an online to offline (O2O) service.
  • O2O online to offline
  • Exemplary O2O services may include a transportation service (e.g., 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) , a meal delivery service, a delivery service, a meal service, a shopping service, or the like, or any combination thereof.
  • the service system 100 may be an online transportation service platform for transportation services, an online delivery service platform for meal delivery services, an online shopping service platform for shopping services, etc.
  • the service system 100 may include a server 110, a network 120, a requester terminal 130, a provider terminal 140, a vehicle 150, a storage device 160, and a navigation system 170.
  • 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.
  • the server 110 may include a processing engine 112.
  • the processing engine 112 may process information and/or data related to the service request to perform one or more functions described in the present disclosure. For example, the processing engine 112 may determine a plurality of service providers in response to a service request. The processing engine 112 may further obtain performance information related to the plurality of service providers, and determine a weight factor of at least one target service provider of the plurality of service providers based on the performance information.
  • the processing engine 112 may include one or more processing engines (e.g., single-core processing engine (s) or multi-core processor (s) ) .
  • the processing engine 112 may include a central processing unit (CPU) , an application-specific integrated circuit (ASIC) , an application-specific instruction-set processor (ASIP) , a graphics processing unit (GPU) , a physics processing unit (PPU) , a digital signal processor (DSP) , a field-programmable gate array (FPGA) , a programmable logic device (PLD) , a controller, a microcontroller unit, a reduced instruction-set computer (RISC) , a microprocessor, or the like, or any combination thereof.
  • CPU central processing unit
  • ASIC application-specific integrated circuit
  • ASIP application-specific instruction-set processor
  • GPU graphics processing unit
  • PPU physics processing unit
  • DSP digital signal processor
  • FPGA field-programmable gate array
  • PLD programmable logic device
  • controller a microcontroller unit, a reduced instruction-set computer (RISC) , a microprocessor, or the like, or any combination thereof.
  • RISC reduced
  • the network 120 may facilitate exchange of information and/or data. In some embodiments, the network 120 may facilitate a real-time exchange of information and/or data. In some embodiments, one or more components of the service system 100 (e.g., the server 110, the requester terminal 130, the provider terminal 140, the vehicle 150, the storage device 160, and the navigation system 170) may transmit information and/or data to other component (s) of the service system 100 via the network 120. For example, the server 110 may receive a service request from the requester terminal 130 via the network 120. In some embodiments, the network 120 may be any type of wired or wireless network, or combination thereof.
  • the network 120 may include a cable network, a wireline network, an optical fiber network, a telecommunications network, an intranet, an Internet, a local area network (LAN) , a wide area network (WAN) , a wireless local area network (WLAN) , a metropolitan area network (MAN) , a wide area network (WAN) , a public telephone switched network (PSTN) , a Bluetooth network, a ZigBee network, a near field communication (NFC) network, or the like, or any combination thereof.
  • the network 120 may include one or more network access points.
  • the network 120 may include wired or wireless network access points such as base stations and/or internet exchange points 120-1, 120-2, ..., through which one or more components of the service system 100 may be connected to the network 120 to exchange data and/or information.
  • a service requester 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 service requester. For example, an owner A of the requester terminal 130 may use the requester terminal 130 to transmit a service request for a service requester 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.
  • “requester, ” “service requester” and “requester terminal” may be used interchangeably, and “provider, ” “service provider, “ and “service provider terminal” may be used interchangeably.
  • the service 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 assistant (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, a virtual reality glass, a virtual reality patch, an augmented reality helmet, augmented reality glasses, an augmented reality patch, or the like, or any combination thereof.
  • the virtual reality device and/or the augmented reality device may include a Google TM Glass, an Oculus Rift, a HoloLens, a Gear VR, etc.
  • the built-in device in the vehicle 130-4 may include an onboard computer, an onboard television, etc.
  • the requester terminal 130 may be a device with positioning technology for locating the position of the service requester and/or the requester terminal 130.
  • the provider terminal 140 may include a plurality of service 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 services. 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 service requester, the requester terminal 130, the service provider, and/or the provider terminal 140.
  • the requester terminal 130 and/or the provider terminal 140 may transmit the positioning information to the server 110 periodically or in real time. In some embodiments, the provider terminal 140 may also transmit the availability status to the server 110 periodically or in real time. The availability status may indicate whether a vehicle 150 associated with the provider terminal 140 is available to carry a passenger. For example, 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. As another example, 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 online on-demand transportation service. In some embodiments, the provider terminal 140 may correspond to one or more vehicles 150.
  • the vehicles 150 may carry the service requester 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, 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 service system 100 (e.g., the server 110, the requester terminal 130, or the provider terminal 140) .
  • One or more components of the 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 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 navigation system 170 e.g., a satellite navigation system
  • one or more components of the service system 100 may have permissions to access the storage device 160.
  • one or more components of the service system 100 may read and/or modify information related to the service requester, service provider, and/or the public when one or more conditions are met.
  • the server 110 may read and/or modify one or more service requesters’ 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.
  • information exchanging of one or more components of the service system 100 may be initiated by way of requesting a service.
  • the object of the service request may be any product.
  • the product may include food, medicine, commodity, chemical product, electrical appliance, clothing, car, housing, luxury, or the like, or any combination thereof.
  • the product may include a servicing product, a financial product, a knowledge product, an Internet product, or the like, or any combination thereof.
  • the Internet product may include an individual host product, a web product, a mobile Internet product, a commercial host product, an embedded product, or the like, or any combination thereof.
  • the mobile internet product may be used in a software of a mobile terminal, a program, a system, or the like, or any combination thereof.
  • the mobile terminal may include a tablet computer, a laptop computer, a mobile phone, a personal digital assistant (PDA) , a smart watch, a point of sale (POS) device, an onboard computer, an onboard television, a wearable device, or the like, or any combination thereof.
  • the product may be any software and/or application used on the computer or mobile phone.
  • the software and/or application may relate to socializing, shopping, transporting, entertainment, learning, investment, or the like, or any combination thereof.
  • the software and/or application related to transporting may include a traveling software and/or application, a vehicle scheduling software and/or application, a mapping software and/or application, etc.
  • the vehicle may include a horse, a carriage, a rickshaw (e.g., a wheelbarrow, a bike, a tricycle, etc. ) , a car (e.g., a taxi, a bus, a private car, etc. ) , a train, a subway, a vessel, an aircraft (e.g., an airplane, a helicopter, a space shuttle, a rocket, a hot-air balloon, etc. ) , or the like, or any combination thereof.
  • a horse e.g., a carriage, a rickshaw (e.g., a wheelbarrow, a bike, a tricycle, etc. )
  • a car e.g., a taxi, a bus, a private car, etc.
  • a train e.g., a subway, a vessel, an aircraft (e.g., an airplane, a helicopter, a space shuttle, a rocket, a hot-air balloon, etc.
  • an element or component of the service system 100 performs, the element may perform through electrical signals and/or electromagnetic signals.
  • a requester terminal 130 transmits out a service request to the server 110
  • 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.
  • 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.
  • the output port of the requester terminal 130 may be one or more antennas, which convert the electrical signal to electromagnetic signal.
  • a provider terminal 140 may receive an instruction and/or service request from the server 110 via electrical signal or electromagnet signals.
  • an electronic device such as the requester terminal 130, the provider terminal 140, and/or the server 110, when a processor thereof processes an instruction, transmits out an instruction, and/or performs an action, the instruction and/or action is conducted via electrical signals.
  • the processor retrieves or saves data from a storage medium, it may transmit out electrical signals to a read/write device of the storage medium, which may read or write structured data in the storage medium.
  • the structured data may be transmitted to the processor in the form of electrical signals via a bus of the electronic device.
  • an electrical signal may refer to one electrical signal, a series of electrical signals, and/or a plurality of discrete electrical signals.
  • FIG. 2 is a schematic diagram illustrating exemplary hardware and software components of a computing device 200 according to some embodiments of the present disclosure.
  • the computing device 200 may be a special purpose computer in some embodiments.
  • the computing device 200 may be used to implement the service system 100 for the present disclosure.
  • the computing device 200 may implement any component of the service system 100 as described herein.
  • the server 110, the requester terminal 130, and/or the provider terminal 140 may be implemented on the computing device 200.
  • the processing engine 112 may be implemented on the computing device 200 and configured to perform functions of the processing engine 112 disclosed in this disclosure.
  • FIGs. 1-2 only one such computer device is shown purely for convenience purposes.
  • One of ordinary skill in the art would understood at the time of filing of this application that the computer functions relating to the service system 100 as described herein may be implemented in a distributed fashion on a number of similar platforms, to distribute the processing load.
  • the computing device 200 may include COM ports 250 connected to and from a network connected thereto to facilitate data communications.
  • the computing device 200 may also include a processor 220, in the form of one or more processors, for executing program instructions.
  • the processor 220 may include interface circuits and processing circuits therein.
  • the interface circuits may be configured to receive electronic signals from a bus 210, wherein the electronic signals encode structured data and/or instructions for the processing circuits to process.
  • the processing circuits may conduct logic calculations, and then determine a conclusion, a result, and/or an instruction encoded as electronic signals. Then the interface circuits may send out the electronic signals from the processing circuits via a bus 210.
  • the exemplary computer platform may include a program storage and a data storage of different forms, for example, a disk 270, and a read only memory (ROM) 230, or a random access memory (RAM) 240, for various data files to be processed and/or transmitted by the computer.
  • the exemplary computer platform may also include program instructions stored in the ROM 230, the RAM 240, and/or other type of non-transitory storage medium to be executed by the processor 220.
  • the methods and/or processes of the present disclosure may be implemented as the program instructions.
  • the computing device 200 may also include an I/O component 260, supporting input/output between the computer and other components therein such as a user interface element (not shown in FIG. 2) .
  • the computing device 200 may also receive programming and data via network communications.
  • processor 220 is described in the computing device 200.
  • the computing device 200 in the present disclosure may also include multiple processors, thus operations and/or method steps that are performed by one processor 220 as described in the present disclosure may also be jointly or separately performed by the multiple CPUs/processors.
  • the processor 220 of the computing device 200 executes both step A and step B, it should be understood that step A and step B may also be performed by two different processors jointly or separately in the computing device 200 (e.g., the first processor executes step A and the second processor executes step B, or the first and second processors jointly execute steps A and B) .
  • FIG. 3 is a schematic diagram illustrating exemplary hardware and/or software components of an exemplary mobile device 300 according to some embodiments of the present disclosure.
  • the mobile device 300 may implement any component of the service system 100 as described herein.
  • the requester terminal 130 and/or the provider terminal 140 may be implemented on the mobile device 300, respectively.
  • the mobile device 300 may include a communication platform 310, a display 320, a graphics processing unit (GPU) 330, a central processing unit (CPU) 340, an I/O 350, a memory 360, and 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.
  • one or more applications 380 may be loaded into the memory 360 from the storage 390 in order to be executed by the CPU 340.
  • the applications 380 may include a browser or any other suitable mobile apps for receiving and rendering information relating to the service system 100.
  • User interactions with the information stream may be achieved via the I/O 350 and provided to the processing engine 112 and/or other components of the service system 100 via the network 120.
  • 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 server if appropriately programmed.
  • FIG. 4 is a block diagram illustrating an exemplary processing engine according to some embodiments of the present disclosure.
  • the processing engine 112 may include an obtaining module 401, an identifying module 402, a determination module 403, a compiling module 404, and a transmission module 405.
  • the modules may be hardware circuits of all or part of the processing engine 112.
  • the modules may also be implemented as an application or set of instructions read and executed by the processing engine 112. Further, the modules may be any combination of the hardware circuits and the application/instructions.
  • the modules may be the part of the processing engine 112 when the processing engine 112 is executing the application/set of instructions.
  • the obtaining module 401 may be configured to obtain information related to the service system 100.
  • Exemplary information obtained by the obtaining module 401 may include a request for a service from a requester, performance information of a plurality of service providers (e.g., one or more feedbacks regarding the service providers) , a plurality of travel routes of a plurality of candidate service providers, information related to one or more target service providers (e.g., profile information) . More descriptions regarding the obtaining of the information may be found elsewhere in the present disclosure. See, e.g., FIGs. 5 and 6 and the relevant descriptions thereof.
  • the identifying module 402 may be configured to identify a plurality of service providers in response to the request received from the requester. In some embodiments, the identifying module 402 may identify a plurality of candidate service providers who can provide the requested service to the requester. The identifying module 402 may further identify the service providers who satisfy one or more conditions (e.g., a service requirement of the requester) among the candidate service providers. More descriptions regarding the identification of the service providers may be found elsewhere in the present disclosure. See, e.g., operation 520 and FIG. 6 and the relevant descriptions thereof.
  • the determination module 403 may be configured to determine a weight factor of at least one target service provider of the plurality of service providers based on performance information of the service providers. In some embodiments, the determination module 403 may determine whether the at least one target service provider has received a historical feedback from the requester. The determination module 403 may further determine the weight factor of the at least one target service provider according to the determination result. More descriptions regarding the determination of the weight factor may be found elsewhere in the present disclosure. See, e.g., operation 540 and FIG. 7 and relevant descriptions thereof.
  • the compiling module 404 may be configured to compile information of the at least one target service provider based on the weight factor of the at least one target service provider.
  • the compiling of the information may include information collection, information selection, information editing, information ranking, or any other suitable information processing operation, or any combination thereof. More descriptions regarding the compiling of information of the at least one target service provider may be found elsewhere in the present disclosure. See, e.g., operation 550 and relevant descriptions thereof.
  • the transmission module 405 may be configured to information and/or instructions to one or more components of the service system 100. For example, the transmission module 405 may transmit the compiled information to a requester terminal of the requester for presentation. As another example, the transmission module 405 may transmit an instruction to the requester terminal to present an invitation for a feedback regarding one or more of the at least one target service provider via the user interface. More descriptions regarding the transmission of the compiled information and/or the instruction to present the invitation may be found elsewhere in the present disclosure. See, e.g., FIG. 5 and relevant descriptions thereof.
  • any module mentioned above may be divided into two or more units.
  • one or more the above-mentioned modules may be omitted.
  • the compiling module 404 and/or the transmission module 405 may be omitted.
  • the processing engine 112 may further include one or more additional modules.
  • the processing engine 112 may further include an encrypt module configured to encrypt information and/or a decrypt module configured to decrypt information.
  • FIG. 5 is a flowchart illustrating an exemplary process for determining information related to service providers for presentation on a user interface of a requester terminal according to some embodiments of the present disclosure.
  • process 500 may be executed by the service system 100.
  • the process 500 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, the storage 390) .
  • the processing engine 112 e.g., the processor 220 of the computing device 200, the CPU 340 of the mobile device 300, and/or one or more modules illustrated in FIG. 4) may execute the set of instructions and may accordingly be directed to perform the process 500 in a service platform (e.g., the service system 100) .
  • the platform may be an Internet-based platform that connects service providers and requesters through the Internet.
  • the processing engine 112 may receive a request for a service from a requester terminal (e.g., the requester terminal 130) via a user interface of the requester terminal.
  • a requester terminal e.g., the requester terminal 130
  • the service requested by the requester terminal may be any product as described elsewhere in this disclosure (e.g., FIG. 1 and the relevant descriptions) , such as but not limited to food, medicine, commodity, chemical product, electrical appliance, clothing, car, housing, luxury, a servicing product, a financial product, a knowledge product, an internet product.
  • the present disclosure takes an O2O service as an example of the service requested by the requester terminal. It should be noted that this is not to be limiting, and the methods of the present disclosure may be applied to any other kind of services.
  • Exemplary O2O services may include a transportation service (e.g., 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) , a meal delivery service, a delivery service, a meal service, a shopping service, or the like, or any combination thereof.
  • a transportation service e.g., 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
  • a meal delivery service e.g., a delivery service, a delivery service, a meal service, a shopping service, or the like, or any combination thereof.
  • the request for the service may be inputted by a user of the requester terminal (also referred to as a requester herein) via the user interface of the requester terminal and be transmitted to the processing engine 112 by the requester terminal.
  • the requester may input the request in a specific field in an application installed on the requester terminal.
  • the requester may input the request via, for example, a typing mechanism (e.g., a keyboard) , a voice input mechanism (e.g., a microphone) , a gesture input mechanism (e.g., a touch screen) of the requester terminal, or the like, or any combination thereof.
  • the request may be encrypted by the requester terminal, and the processing engine 112 may decrypt the encrypted request after receiving the encrypted request.
  • the requester terminal may encrypt the request using its private key and/or digitally sign the request.
  • the processing engine 112 may decrypt the request using a public key of the requester terminal.
  • the encrypted request may include authentication information related to the requester terminal and/or the requester, such as an identification of the requester, a password inputted by the requester, and/or a digital signature of the requester terminal.
  • the processing engine 112 may verify the authentication information of the requester terminal and/or the requester before the decrypting.
  • the request may include one or more service requirements of the requester.
  • Exemplary service requirements may include a type of service requested by the requester, an expected service location, an expected service time (e.g., a time point or time period) , an expected service price, a requirement on service providers of the service, or the like, or any combination thereof.
  • the request may include a type of a vehicle requested by the requester, a current location of the requester, a start location of the transportation service, a destination of the transportation service, a departure time of the transportation service, a number of passengers of the transportation service, or the like, or any combination thereof.
  • the service requirement (s) may be inputted manually by the requester and/or determined by the processing engine 112.
  • the start location and/or the destination of the transportation service may be inputted by the requester via the user interface of the requester terminal.
  • the current location of the requester may be determined by the requester terminal in real time using a location detection mechanism (e.g., a GPS device) of the requester terminal.
  • the requester terminal may be configured to present a user interface for requesting a transportation service (e.g., a user interface 1600 as illustrated in FIG. 16 and/or a user interface 1700 as illustrated in FIG. 17) .
  • the requester may input one or more of the service requirements via the user interface and send the request for the transportation service to the service system 100. More descriptions regarding the user interface for requesting a transportation service may be found elsewhere in the present disclosure. See, e.g., FIGs. 16 and 17 and relevant descriptions thereof.
  • the processing engine 112 e.g., the identification module 402 (e.g., the processing circuits of the processor 220) may identify a plurality of service providers in response to the request for the service.
  • the service providers may include any service provider who can provide the requested service to the requester of the requester terminal.
  • the service providers may include a plurality of drivers.
  • the service providers may include a plurality of deliverymen.
  • the service providers may include any service providers who can provide the requested service to the requester and satisfy one or more conditions.
  • the conditions may be associated with the one or more service requirements of the request as described in connection with operation 510.
  • Exemplary conditions may include that the service providers can provide the requested service at the expected service time, that the service providers can provide the requested service at the expected service location, that the service providers satisfied the requester’s requirement on service providers, or the like.
  • the service providers may be drivers who are available at the expected service time and/or within a predetermined threshold distance from the start location.
  • the processing engine 112 may determine a plurality of candidate service providers in response to the request.
  • the candidate service providers may include any service provider who can provide the requested service to the requester, for example, all or a part of service providers registered on the service system 100.
  • the processing engine 112 may further identify, among the candidate service providers, service providers who satisfy the condition (s) as the service providers for the request.
  • the processing engine 112 may identify the service providers among the candidate service providers based on location information of the candidate service providers. For example, the processing engine 112 may receive location information of the candidate service providers from a plurality of provider terminals (e.g., the service provider terminals 140) of the candidate service providers. In some embodiments, the location information of the candidate service providers may be acquired using a location detection mechanism (e.g., a GPS device) of the provider terminals. The location information of the provider terminals may be transmitted to the processing engine 112 via the network 120 by the provider terminals in real-time or periodically. The processing engine 112 may further identify the service providers among the service providers based at least in part on the location information of the candidate service providers.
  • a location detection mechanism e.g., a GPS device
  • the processing engine 112 may identify the service providers who are within a threshold distance from the expected location of the service (e.g., a start location of a transportation service) .
  • the processing engine 112 may determine an estimated time of arrival (ETA) for each of the candidate service providers to arrive at the expected location of the service (e.g., a start location of a transportation service) based on the location information of the candidate service providers and/or other information that may influence the ETAs (e.g., e.g., traffic information and/or weather information) .
  • the processing engine 112 may rank the plurality of candidate service providers according to the respective ETAs according to a predetermined order (e.g., a descending order) . Further, the processing engine 112 may identify the service providers (e.g., top 1, top 2, top 5, top 10, top 1%, top 5%, top 10%) from the candidate service providers based on the ranking result.
  • the service may be a carpool service from a start location to a destination requested by a passenger.
  • the carpool service may refer to a service that a passenger shares a car journey with a driver and one or more other passengers (if any) .
  • the processing engine 112 may obtain a plurality of travel routes of a plurality of candidate service providers (e.g., a plurality of drivers providing the carpool service) . Further, the processing engine 112 may identify a plurality of service providers of the request by matching a route from the start location to the destination to each of the plurality of travel routes of the candidate service providers. In some embodiments, the processing engine 112 may identify the service provider (s) for the carpool service by performing one or more operations in process 600 as described in connection with FIG. 6.
  • the processing engine 112 e.g., the obtaining module 401 (e.g., the interface circuits of the processor 220) may obtain performance information related to the plurality of service providers.
  • the performance information related to a service provider may refer to any information reflecting the performance of the service provider.
  • the performance information of the service provider may include one or more feedbacks with respect to the service provider.
  • the feedback with respect to the service provider may include one or more feedbacks received from one or more historical service requesters who have been served by the service provider, a feedback regarding the service provider determined by one or more components of the service system 100, or the like, or any combination thereof.
  • the feedbacks received from the historical service requester (s) may include, for example, one or more performance scores of the service provider evaluated by the historical service requester (s) , one or more comments and/or complaints regarding the service provider made by the historical service requester (s) , one or more operations performed by the historical service requester (s) regarding the account of the service provider, or the like, or any combination thereof.
  • the one or more operations regarding the account of the service provider may include following the account of the service provider, adding the account of the service provider into a blacklist, giving a gift to the service provider, or the like, or any combination thereof.
  • a requester terminal (e.g., the requester terminal 130) may present a user interface for inviting the historical service requester to give a feedback regarding the service provider.
  • the historical service requester may input his/her feedback regarding the service provider via the user interface.
  • the requester terminal of the historical service requester may transmit the feedback regarding the service provider to one or more components of the service system 100.
  • the feedback regarding the service provider may be transmitted to a storage device (e.g., the storage device 160, the ROM 230, the RAM 240) and stored therein as a feedback.
  • the processing engine 112 may access the storage device and retrieve the feedback regarding the service provider for further analysis (e.g., for determining a weight factor of the service provider as described in connection with operation 540) . More descriptions regarding the user interface for inviting the service requester to give a feedback regarding the service provider may be found elsewhere in the present disclosure. See, e.g., FIGs. 10 to 15 and relevant descriptions thereof.
  • the performance information related to the service provider may include a feedback regarding the service provider given by one or more components of the service system 100, such as the processing engine 112.
  • the feedback regarding the service provider given by the processing engine 112 may include whether the service provider was late frequently or not, whether the service provider detoured frequently or not, whether the service provider cancelled service orders frequently, a credit score regarding the service provider, or the like, or any combination thereof.
  • the processing engine 112 may obtain information related to a plurality of historical service orders of the service provider, such as a plurality of driving routes of the service provider of the historical services orders, time information related to the historical service orders (e.g., a start time of each historical service order, an expected service time of each historical service order) , or the like, or any combination thereof. Further, the processing engine 112 may determine whether the service provider was late for the expected service time of the historical service orders frequently (e.g., more than a first certain number in a first predetermined period) based on the time information related to the historical service orders.
  • time information related to the historical service orders e.g., a start time of each historical service order, an expected service time of each historical service order
  • the processing engine 112 may determine whether the service provider was late for the expected service time of the historical service orders frequently (e.g., more than a first certain number in a first predetermined period) based on the time information related to the historical service orders.
  • the processing engine 112 may determine whether the service provider detoured frequently (e.g., more than a second certain number in a second predetermined period) based on the driving routes of the service providers of the historical service orders. As yet another example, the processing engine 112 may determine a credit score that measures the credibility and/or the service quality of the service provider by analyzing the information related to the historical service orders. More descriptions regarding the credit score may be found elsewhere in the present disclosure. See, e.g., FIG. 8 and relevant descriptions thereof.
  • a feedback related to a service provider may be classified as a positive feedback, a negative feedback, a neutral feedback, or the like, or any combination thereof.
  • the positive feedback may refer to a feedback that praises or recognizes the performance of the service provider.
  • the negative feedback may refer to a feedback that criticizes or complains about the performance of the service provider.
  • the neutral feedback may refer to a feedback that does not show a clear evaluation regarding the performance of the service provider. For example, it is assumed that the range of performance scores of the service provider is 0 to 10. A first performance score higher than 6 may be classified as a positive feedback, a second performance score lower than 4 may be classified as a negative feedback, and a third performance score in the range of 4 to 6 may be classified as a neutral feedback.
  • a comment showing that the historical service requester is expected to have a trip with the service provider again may be classified as a positive feedback.
  • a comment showing that the historical service requester is unwilling to have a trip with the service provider again may be classified as a negative feedback.
  • a comment showing that the historical service requester feels OK to have a trip with the service provider again may be classified as a neutral feedback.
  • an operation that the historical service requester gave a gift or followed the service provider may be classified as a positive feedback.
  • An operation that the historical service requester complained about the service provider or added the service provider into a blacklist may be classified as a negative feedback.
  • a determination that the service was late frequently and/or detoured frequently may be classified as a negative feedback to the service provider.
  • a determination that the service provider was not late frequently and/or not detoured frequently may be classified as a positive feedback.
  • a historical service requester may not provide a feedback regarding the service provider after the service order was completed. In this situation, the service provider may be regarded as receiving a neutral feedback from the historical service requester.
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may determine a weight factor of at least one target service provider of the plurality of service providers based on the performance information.
  • a target service provider may refer to a service provider who is recommended to provide the requested service to the requester of the requester terminal. For example, information related to the at least one target service provider may be compiled and transmitted to the requester terminal for presentation and/or for the requester of the requester terminal to choose.
  • the at least one target service provider may be any service provider among the plurality of service providers.
  • the weight factor of the target service provider may indicate a degree that the target service provider is recommended to the requester of the requester terminal. If a first target service provider has a higher weight factor than a second target service provider, the first target service provider is more recommended to the requester of the requester terminal than the second target service.
  • real time feedback from one or more other service requesters regarding a specific service provider or a group of service providers sharing a same or similar characteristic e.g., age, driving records, driving experience, education history, employment history, performance information, etc.
  • a service provider with a service requester means that identifying the service provider as a target service provider of a service request by the service requester.
  • the processing engine 112 may determine weight factors (which indicates the recommended degrees) for a plurality of target service providers.
  • the processing engine 112 may further compile information related to the target service providers according to the weight factors of the target service providers for presentation on the requester terminal.
  • the weight factors may be associated with what information related to the target service providers is to be presented on the requester terminal and/or the way of presentation of the information related to the target service providers.
  • a first target service provider has a higher weight factor than a second target service provider, more detailed information related to the first target service provider may be presented on the requester terminal than the second target service provider.
  • the information related the first target service provider may be presented in a more visible and/or accessible way than the information related to the second target service provider. In that way, it is more likely that the requester chooses a target service provider having a higher weight factor (i.e., a higher recommended degree) , which can improve the user experience. More descriptions regarding the compiling of the information related to the target service providers may be found elsewhere in the present disclosure. See, e.g., operation 550 and relevant descriptions thereof.
  • the processing engine 112 may determine the weight factor of a target service provider based on the performance information of the target service provider.
  • the performance information related to a service provider may include one or more feedbacks with respect to the service provider, such as one or more feedbacks received from one or more historical service requesters who have been served by the service provider, a feedback made by one or more components of the service system 100, or the like, or any combination thereof.
  • the processing engine 112 may determine the weight factor of the target service provider based on the feedback (s) with respect to the target service provider.
  • the weight factor of the target service provider may have a positive correlation with the proportion of the positive feedbacks to all the feedbacks that the target service provider has received, the higher the proportion is, the higher the weight factor of the target service provider may be.
  • the weight factor of the target service provider may be determined based on the average performance score evaluated by the one or more historical service requesters, the higher the average performance score is, the higher of the weight factor of the target service provider may be.
  • the processing engine 112 may assign a default weight factor to the target service provider. Further, the processing engine 112 may adjust the default weight factor according to the feedbacks of the target service provider, wherein the adjusted default weight factor may be regarded as the weight factor of the target service provider.
  • the processing engine 112 may add a*N to the default weight factor and subtract b*M from the default weight factor, in which a and b refer to a coefficient corresponding to positive feedbacks and negative feedbacks, respectively.
  • the processing engine 112 may determine whether the target service provider has received a feedback from the requester of the requester terminal. The processing engine 112 may further determine the weight factor of the target service provider according to the determination as to whether the target service provider has received a feedback from the requester of the requester terminal. For example, if the target service provider has received a feedback from the requester of the requester terminal, the processing engine 112 may determine the weight factor of the target service provider according to the feedback received from the requester of the requester terminal.
  • the processing engine 112 may determine the weight factor of the target service provider based on the one or more feedbacks with respect to the target service provider. In this way, the requester’s feedback regarding the target service provider may be taken into consideration in determining the weight factor of the target service provider, which may improve the accuracy of the weight factor. More descriptions regarding the determination of the weight factor may be found elsewhere in the present disclosure. See, e.g., FIG. 7 and relevant descriptions thereof.
  • the processing engine 112 may determine the weight factor of the target service provider based on a model, wherein information related to the target service provider (e.g., performance information, profile information) may be an input of the model and the weight factor of the target service provider may be an output of the model.
  • the model may be trained by information related to a plurality of samples using a machine learning method.
  • the model may be generated by training an initial model using information related to a plurality of historical service providers.
  • the historical service providers may include any service provider who has provided a service in the service system 100.
  • the information related to the historical service providers may include, for example, performance information, profile information, and weight factors of the historical service providers.
  • Exemplary machine learning algorithms used in the model training may include but not be limited to an artificial neural network algorithm, a deep learning algorithm, a decision tree algorithm, an association rule algorithm, an inductive logic programming algorithm, a support vector machine algorithm, a clustering algorithm, a Bayesian networks algorithm, a reinforcement learning algorithm, a representation learning algorithm, a similarity and metric learning algorithm, a sparse dictionary learning algorithm, a genetic algorithm, a rule-based machine learning algorithm, or the like, or any combination thereof.
  • each of the plurality of service providers determined in operation 530 may be regarded as a target service provider.
  • the processing engine 112 may determine a weight factor for each of the service providers. Alternatively, only a portion of the service providers may be regarded as target service provider (s) .
  • the processing engine 112 may determine a weight factor for each service provider of the portion of the service providers. In some embodiments, the processing engine 112 may remove one or more service providers who have received a negative feedback from the requester of the requester terminal.
  • the service providers who have received a negative feedback from the requester may include, for example, a service provider who has received a low performance score (e.g., a performance score lower than a threshold) evaluated by the requester, a service provider who has been added to the blacklist by the requester, a service provider who has been complained by the requester, a service provider who has received a negative comment from the requester (e.g., a comment showing that the requester is not willing to have a trip with the service provider again) , or the like, or any combination thereof.
  • the remaining service provider (s) of the plurality of service providers may be regarded as the target service provider (s) , and the processing engine 112 may further determine a weight factor of each target service provider. This may prevent the requester from being served by a service provider that he/she is not satisfied with.
  • the processing engine 112 e.g., the compiling module 404 (e.g., the processing circuits of the processor 220) may compile information of the at least one target service provider based on the weight factor of the at least one target service provider.
  • the compiled information may be used for presentation on the requester terminal via the user interface of the requester terminal.
  • the information of a target service provider may include profile information, performance information, location information, vehicle information, time information, or the like, or any combination thereof.
  • exemplary profile information of the target service provider may include the name, the gender, the age, contact information (e.g., a telephone number) , an education level, an address, an occupation, a marriage state, or the like, or any combination thereof.
  • exemplary performance information may include one or more feedbacks regarding the target service provider, an average performance score of the target service provider evaluated by historical service requesters, a credit score determined by the processing engine 112, the number (or rate) of being complained, or the like, or any combination thereof.
  • Exemplary location information may include a current location of the target service provider, the distance between the target service provider and the requester terminal, an ETA for the target service provider to arrive at an expected location for the requested service, a planned travel route of the target service provider, a route matching degree, or the like, or any combination thereof.
  • Exemplary vehicle information may include a license plate number of a vehicle of the target service provider, a color of the vehicle, a type of the vehicle, a brand name of the vehicle, a number of seats in the vehicle, a load capacity of the vehicle (e.g., a weight of products or a number of passengers that the vehicle can carry) , or the like, or any combination thereof.
  • Exemplary time information may include a departure time, a departure date, or the like, or the like, or any combination thereof.
  • the information to be presented on the requester terminal may include the same type or different types of information.
  • the compiling of the information may include information collection, information selection, information editing, information ranking, or any other suitable information processing operation, or any combination thereof.
  • the compiling may include acquiring the information of each of the at least one target service provider from a storage device (e.g., the storage device 160) of the service system 100 or an external source via the network 120. Additionally or alternatively, the compiling may include ranking the information of the at least one target service provider according to the respective weight factor of the at least one target service provider.
  • the at least one target service provider may include a plurality of target service providers.
  • the processing engine 112 may determine a ranking of the target service providers based on the weight factors of the target service providers in a certain order (e.g., a descending order or an ascending order) .
  • the processing engine 112 may compile the information of target service providers into a list according to the ranking of the target service providers. For example, the target service providers may be ranked according to the weight factors of the target service providers in a descending order.
  • the processing engine 112 may compile the information of the first target service provider in front of the information of the second target service provider in the list, so that the first target service provider having a higher weight factor is more likely to be viewed or selected by the requester. Further, the processing engine 112 may transmit an instruction to the requester terminal to present the list via the user interface. In some embodiments, the requester terminal may present the list by displaying the list on the user interface of the requester terminal and/or broadcasting the list via a loudspeaker.
  • the processing engine 112 may acquire different types of information for the target service providers according to the ranking result. For example, the processing engine 112 may acquire more detailed information (e.g., including more types of information) for the first target service provider than the second target service provider.
  • the processing engine 112 may encrypt the compiled information of the at least one target service provider for presentation on the requester terminal via the user interface.
  • the processing engine 112 may further transmit the encrypted information to the requester terminal.
  • the processing engine 112 may encrypt the compiled information using a public key of the requester terminal.
  • the requester terminal may decrypt the encrypted information using a private key of the requester terminal.
  • the encrypted information may include authentication information related to the requester terminal and/or the requester to authenticate the requester terminal and/or the requester.
  • the processing engine 112 may transmit to the requester terminal an instruction to present an invitation for a feedback regarding one or more of the at least one target service provider via the user interface.
  • the requester terminal presents the compiled information of the at least one target service provider.
  • the requester of the requester terminal may select one or more of the at least one target service provider to provide the requested service.
  • the processing engine 112 may transmit the instruction to the requester terminal to present the invitation for a feedback of the selected one or more target service providers after or during the service.
  • the invitation for a feedback may be presented as a question regarding the selected one or more target service providers (e.g., “Would you like to have a trip with the service provider again” , “Are you satisfied with the service provided by the service provider” ) , a requirement for the requester to give the feedback (e.g., “Please give your feedback regarding the service provider” ) , or in any other suitable form.
  • the requester of the requester terminal may input the feedback regarding the selected target service provider (s) via the user interface by typing and/or writing the feedback, recording the feedback, making a gesture, touching a certain interface element on the user interface, or the like, or any combination thereof.
  • the requester terminal may transmit the requester’s feedback to the processing engine 112 upon detecting the requester’s input.
  • the requester terminal may present one or more user interfaces as illustrated in FIGs. 10 to 15 to invite the requester to give a feedback regarding the selected target service provider (s) .
  • the process 500 may be accomplished with one or more additional operations not described and/or without one or more of the operations herein discussed. Additionally or alternatively, the order in which the operations of the process 500 as illustrated in FIG. 5 and described above is not intended to be limiting. For example, operation 560 may be omitted. As another example, the process 500 may further include an operation to transmit an instruction to the requester terminal to present the compiled information after operation 550.
  • FIG. 6 is a flowchart illustrating an exemplary process for identifying a plurality of service providers in response to a request for a service according to some embodiments of the present disclosure.
  • process 600 may be executed by the service system 100.
  • the process 600 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, the storage 390) .
  • the processing engine 112 e.g., the processor 220 of the computing device 200, the CPU 340 of the mobile device 300, and/or one or more modules illustrated in FIG. 4) may execute the set of instructions and may accordingly be directed to perform the process 600 in a service platform (e.g., the service system 100) .
  • the platform may be an Internet-based platform that connects service providers and requesters through the Internet.
  • the process 600 may be performed to achieve at least part of operation 520 as described in connection with FIG. 5, wherein the requested service is a carpool service from a start location to a destination.
  • the requester may input a request for the carpool service via a user interface of a requester terminal in, for example, a similar manner as described in connection with operation 510.
  • the processing engine 112 may perform the process 600 to determine a plurality of service providers who can provide the requested carpool service to the requester.
  • the processing engine 112 e.g., the obtaining module 401 (e.g., the interface circuits of the processor 220) may obtain a plurality of travel routes of a plurality of candidate service providers.
  • the candidate service providers may include any service provider who can provide the carpool service to the user.
  • the candidate service providers may include registered drivers of the service system 100 who provide carpool services.
  • the candidate service providers may include registered drivers of the service system 100 who provide carpool services and satisfy one or more certain conditions, for example, being in the same city as the user, being within a predetermined threshold distance from the start location.
  • the travel route of a candidate service provider may refer to a route that the target service provider plans to travel at a planned travel time (e.g., a time point or a period) .
  • the travel route may start from a planned start location to a planned destination of the candidate service provider.
  • the planned start location and the planned destination may be provided by the candidate service provider, and the travel route may be determined by the processing engine 112 based on the planned start location and the planned destination.
  • the processing engine 112 may determine a plurality of routes from the planned start location to the planned destination, and select a route (e.g., the route having the shortest travel time or length) from the routes as the travel route of the candidate service provider.
  • the travel route may be selected by the candidate service provider from the plurality of routes determined by the processing engine 112 or be provided by the candidate service provider to the service system 100 via a provider terminal (e.g., the provider terminal 140) .
  • the processing engine 112 may obtain or determine other information related to the candidate service provider and/or the travel route, such as but not limited to a current location of the candidate service provider, a length of the travel route of the candidate service provider, an estimated travel time along the travel route, the planned travel time, vehicle information related to a vehicle of the candidate service provider (e.g., the number of seats in the vehicle, a load capacity of the vehicle, a vehicle type, a brand of the vehicle, the age of the vehicle) , an estimated price for the carpool service, or the like, or any combination thereof.
  • vehicle information related to a vehicle of the candidate service provider e.g., the number of seats in the vehicle, a load capacity of the vehicle, a vehicle type, a brand of the vehicle, the age of the vehicle
  • an estimated price for the carpool service or the like, or any combination thereof.
  • the processing engine 112 e.g., the identification module 402 (e.g., the processing circuits of the processor 220) may match a route from the start location to the destination to each of the plurality of travel routes.
  • the route from the start location to the destination may be provided by the requester to the service system 100 via the requester terminal.
  • the route may be determined by the processing engine 112 in a similar manner with the travel route of a candidate service provider as described in connection with operation 610.
  • the processing engine 112 may match the route of the requester to each of the travel routes of candidate service providers, respectively. In some embodiments, the processing engine 112 may determine a matching degree between the route of the requester and each of the travel routes of candidate service providers.
  • the matching degree between the route of the requester and a travel route of a candidate service provider may refer to an overlapping ratio between the route of the requester and the travel route of the candidate service provider.
  • the overlapping ratio may refer to a ratio of a length of an overlapped route between the route and the travel route to a length of the route.
  • the route may be represented as a plurality of first road sections along the route, and each travel route may be represented as a plurality of second road sections along the travel route.
  • the processing engine 112 may determine a portion of the first road sections that are overlapped with the second road sections.
  • the processing engine 112 may further determine a ratio of the total length of the portion of the first road sections to the length of the route, which may be designated as the matching degree between the route and the travel route.
  • the requester may designate an expected service time (e.g., a time point or time period) for the carpool service.
  • the processing engine 112 may take the expected service time into consideration in determining the matching degrees between the route of the requester and the travel routes of the candidate service providers. For example, for a candidate service provider, the processing engine 112 may determine whether the candidate service provider can provide the carpool service to the requester at the expected service time based on the planned travel time of the candidate service providers. If the expected service time is within or close to the planned travel time of the candidate service provider, the processing engine 112 may determine that the candidate service provider can provide the carpool service at the expected service time.
  • the processing engine 112 may determine the overlapping ratio between the route and the travel route of the candidate service provider as the matching degree. In response to a determination that the candidate service provider is unable to provide the carpool service to the requester, the processing engine 112 may remove the candidate service provider. Alternatively, the processing engine 112 may determine an overlapping ratio between the route and the travel route of the candidate service provider. The processing engine 112 may further adjust the overlapping ratio by, for example, subtracting a certain value from the overlapping ratio, wherein the adjusted overlapping ratio may be designated as the matching degree between the route of the requester and the travel route of the candidate service provider.
  • the processing engine 112 e.g., the identification module 402 (e.g., the processing circuits of the processor 220) may identify, among the plurality of candidate service providers, the plurality of service providers based on the matching results of the plurality of travel routes.
  • the matching results may include a plurality of matching degrees between the route of the requester and the travel routes of the candidate service providers as described in connection with operation 620.
  • the processing engine 112 may identify the service providers among the candidate service providers based on the matching degrees. For example, the processing engine 112 may identify one or more candidate service providers whose matching degrees are equal to or greater than a threshold (e.g., 50%, 60%, 70%, 80%, 90%) as the service providers. As another example, the processing engine 112 may rank the candidate service providers according to the respective matching degrees to the route of the requester in a descending order) . The processing engine 112 may further identify top N candidate service providers in the ranking result as the service providers. N may be any positive value, such as 3, 5, 10, 10%, 30%, 50%, or the like.
  • process 600 is merely provided for the purposes of illustration, and not intended to limit the scope of the present disclosure.
  • process 600 may be accomplished with one or more additional operations not described and/or without one or more of the operations herein discussed. Additionally, the order in which the operations of the process 600 as illustrated in FIG. 6 and described above is not intended to be limiting.
  • FIG. 7 is a flowchart illustrating an exemplary process for determining a weight factor of a target service provider according to some embodiments of the present disclosure.
  • process 700 may be executed by the service system 100.
  • the process 700 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, the storage 390) .
  • the processing engine 112 e.g., the processor 220 of the computing device 200, the CPU 340 of the mobile device 300, and/or one or more modules illustrated in FIG.
  • the platform may be an Internet-based platform that connects service providers and requesters through the Internet.
  • the process 700 may be performed to achieve at least part of operation 540 as described in connection with FIG. 5.
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may determine whether the target service provider has received a feedback from a user of the requester terminal (also referred to as the requester) based on one or more feedbacks regarding the target service provider.
  • the target service provider may receive one or more feedbacks from one or more historical service requesters who have been served by the target service provider.
  • the feedbacks may include one or more performance scores of the service provider evaluated by the historical service requesters, one or more comments and/or complaints regarding the service provider made by the historical service requesters, one or more operations regarding the account of the service provider performed by the historical service requesters, or the like, or any combination thereof.
  • the processing engine 112 may obtain the feedbacks of the target service provider from a storage device (e.g., the storage device 160) , and determine whether the target service provider has received a feedback from the requester based on the feedbacks. For example, the processing engine 112 may determine whether the target service provider has received a performance score or a comment from the requester. If the target service provider has received a performance score or a comment from the requester, the processing engine 112 may determine that the target service provider has received a feedback from the requester. As another example, the processing engine 112 may determine whether the target service provider has been followed by the requester on the service system 100.
  • a storage device e.g., the storage device 160
  • the processing engine 112 may determine that the target service provider has received a feedback from the requester. On the other hand, if the target service provider has neither received a performance score or a comment from the requester nor been followed by the requester, the processing engine 112 may determine that the target service provider has not received a feedback from the requester.
  • the processing engine 112 may determine whether the target service provider has been followed by the requester on the service system 100 based on one or more corresponding relationships between the target service provider and one or more followers of the target service provider on the service system 100.
  • the corresponding relationship (s) between the target service provider and his/her followers may be stored in a storage device (e.g., the storage device 160, the ROM 230, the RAM 240) of the service system 100 in the form of, for example, a corresponding table.
  • the processing engine 112 may access the storage device and retrieve one or more corresponding relationship (s) . Further, the processing engine 112 may determine whether the one or more followers include the requester.
  • the processing engine 112 may determine that the target service provider has been followed by the requester on the service system 100. If the one or more followers do not include the requester, the processing engine 112 may determine that the target service provider has not been followed by the requester on the service system 100.
  • the process 700 in response to the determination that the target service provider has received a feedback from the requester, the process 700 may proceed to 720. On the other hand, in response to the determination that the target service provider has not received a feedback from the requester, the process 700 may proceed to 730 or 740.
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may determine the weight factor of the target service provider according to the feedback received from the user of the requester terminal.
  • the processing engine 112 may determine the weight factor of the target service provider as a first value according to the type of the feedback received from the requester. Merely by way of example, if the feedback received from the requester is a positive feedback (e.g., being followed by the requester) , the processing engine 112 may designate the weight factor of the target service provider as a value A.
  • the processing engine 112 may remove the target service provider and not determine the weight factor of the target service provider, or designate the weight factor of the target service provider as a value B (which is smaller than A) . If the feedback received from the requester is a neutral feedback, the processing engine 112 may designate the weight factor of the target service provider as a value C (which is smaller than A and larger than B) .
  • the values A, B, and C may be default settings of the service system 100 or be manually input by a user of the service system 100. For example, the values A, B, and C may be 100%, 10%, and 50%, respectively. Alternatively, the target service provider may have received a plurality of feedbacks from the requester.
  • the processing engine 112 may determine at least one of the values A, B, and C based on the feedbacks regarding the target service provider received from the requester. For example, the processing engine 112 may determine the value A based on the number of positive feedbacks of the target service provider received from the requester. The more positive feedbacks received from the requester, the higher value A may be.
  • the processing engine 112 may determine the weight factor of the target service provider based on a base weight factor and the type of the feedback received from the requester.
  • the base weight factor may be a default setting of the service system 100 or pre-determined by the service system 100.
  • the processing engine 112 may determine the weight factor of the target service provider by adding a first coefficient on the base weight factor. If the feedback received from the requester is a negative feedback, the processing engine 112 may remove the target service provider and not determine the weight factor of the target service provider, or determine the weight factor of the target service provider by subtracting a second coefficient from the base weight factor.
  • the first and the second coefficients may be any positive value. If the feedback received from the requester is a neutral feedback, the processing engine 112 may designate the base weight factor as the weight factor of the target service provider.
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may designate the weight factor of the target service provider as a second value in response to a determination that the target service provider has not received a feedback from the user of the requester terminal.
  • the second value may be different from the first value.
  • the second value may be lower than the value A or C which is designated as the weight factor when the feedback received from the requester is a positive feedback or a neutral feedback.
  • the second value may be higher than the value B which is designated as the weight factor when the feedback received from the requester is a negative feedback.
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may determine the weight factor of the target service provider based on the one or more feedbacks with respect to the target service provider in response to the determination that the target service provider has not received a feedback from the requester.
  • the processing engine 112 may determine the weight factor (s) of the target service provider in a similar manner as described in operation 540.
  • the weight factor may be determined based on a proportion of positive feedbacks to all the feedbacks that the target service provider has received, an average performance score evaluated by the historical service provider (s) , a model for determining weight factors, or the like, or any combination thereof.
  • the processing engine 112 may determine the weight factor of the target service provider based on a credit score of the target service provider.
  • the credit score may be a measurement representing the credibility and/or the service quality of the target entity. More descriptions regarding the determination of the weight factor based on the credit score may be found elsewhere in the present disclosure. See, e.g., FIG. 8 and relevant description thereof.
  • process 700 is merely provided for the purposes of illustration, and not intended to limit the scope of the present disclosure.
  • process 700 may be accomplished with one or more additional operations not described, and/or one or more of the operations herein discussed may be combined as one operation.
  • operation 730 or 740 may be omitted.
  • the order in which the operations of the process 700 as illustrated in FIG. 7 and described above is not intended to be limiting.
  • FIG. 8 is a flowchart illustrating an exemplary process for determining a weight factor of a target service provider based on one or more feedbacks with respect to the target service provider according to some embodiments of the present disclosure.
  • process 800 may be executed by the service system 100.
  • the process 800 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, the storage 390) .
  • the processing engine 112 e.g., the processor 220 of the computing device 200, the CPU 340 of the mobile device 300, and/or one or more modules illustrated in FIG.
  • the platform may be an Internet-based platform that connects service providers and requesters through the Internet.
  • the process 800 may be performed to achieve at least part of operation 740 and/or 540.
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may determine at least one representative feedback from the one or more feedbacks with respect to the target service provider.
  • the at least one representative feedback regarding the target service provider may include one or more positive feedbacks among the feedbacks, such as a high performance score (e.g., a performance score higher than a first threshold) , a positive comment (e.g., a praise) , one or more certain operations regarding the target service provider (e.g., giving a gift to the target service provider, following the account of the target service provider) .
  • a high performance score e.g., a performance score higher than a first threshold
  • a positive comment e.g., a praise
  • certain operations regarding the target service provider e.g., giving a gift to the target service provider, following the account of the target service provider
  • the at least one representative feedback regarding the target service provider may include one or more negative feedbacks among the feedbacks, such as a low performance score (e.g., a performance score lower than a second threshold) , a negative comment (e.g., a criticism) , one or more certain operations regarding the target service provider (e.g., adding the account of the target service provider into a blacklist) , a determination that the target service provider cancelled service orders, be late, or detoured frequently.
  • the at least one representative feedback may be received by the target service provider in a predetermined period (e.g., a week, a month, half a year, a year) .
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may determine a credit score of the target service provider based at least in part on the at least one representative feedback.
  • the credit score may be a measurement reflecting the credit and/or the service quality of the target service provider.
  • each representative feedback (or each type of representative feedback) may correspond to a unit score
  • the weight factor may be a weighted sum of the unit score of each representative feedback (or each type of representative feedback) .
  • the credit score of the target service provider may be determined according to Equation (1) as below:
  • s represents the credit score of the target service provider
  • si represents the unit score of the i th type of representative feedback
  • ki represents a weight corresponding to the i th type of representative feedback.
  • s1 may represent a first unit score corresponding to a determination that the target service provider cancelled service orders frequently
  • s2 may represent a second unit score corresponding to negative feedbacks (e.g., being complained by historical service requesters)
  • s3 may represent a third unit score corresponding to positive feedbacks.
  • the unit score of a certain representative feedback may be a default score of the service system 100 or be manually inputted by a user of the service system 100.
  • a unit score corresponding to a positive feedback that a historical service requester was expected to have a trip with the target service provider again, a neutral feedback that a historical service requester felt OK to have a trip with the target service provider again, and a negative feedback that the historical service requester was unwilling to have a trip with the target service provider again is 0.05, -1.8, and -2.7, respectively.
  • the unit score may be determined by the processing engine 112.
  • the unit score of a certain type of representative feedback may be determined based on a number of times that the target service provider received the certain type of representative feedback, and/or a proportion of the representative feedback to a total number of feedbacks or service orders of the target service provider.
  • the processing engine 112 e.g., the determination module 403 (e.g., the processing circuits of the processor 220) may determine the weight factor of the target service provider based on the credit score of the target service provider.
  • the weight factor of the target service provider may have a positive correlation with the credit score of the target service provider. The higher the credit factor is, the higher the weight factor of the target service provider may be. In some embodiments, the weight factor of the target service provider may be determined based on the credit score and a corresponding relationship between credit scores and weight factors.
  • the corresponding relationship between credit scores and weight factors may be denoted in any suitable form and stored in a storage device of the service system 100. Merely by way of example, the corresponding relationship between credit scores and weight factors may be denoted in the form of a table recording different credit scores and their corresponding weight factors.
  • the table may record that the weight factor may be equal to 75%, 70%, or 50%when the credit score is equal to 80, 70, or 60, respectively.
  • the corresponding relationship between credit scores and weight factors may be denoted as a mathematical formula between credit scores and weight factors.
  • the processing engine 112 may obtain the corresponding relationship between credit scores and weight factors from the storage device, and determine the weight factor based on the weight factor and the corresponding relationship, for example, by looking up the table or inputting the weight factor into the mathematical formula.
  • process 800 may be accomplished with one or more additional operations not described, and/or one or more of the operations herein discussed may be combined as one operation.
  • operation 810 may be omitted and the credit score of the target service provider may be determined based on the one or more feedbacks with respect to the target service provider.
  • FIG. 9A is a block diagram illustrating an exemplary requester terminal according to some embodiments of the present disclosure.
  • the requester terminal 130 may include a receiving module 901, a communication module 902, and a presentation module 903.
  • the modules may be hardware circuits of all or part of the requester terminal 130.
  • the modules may also be implemented as an application or set of instructions read and executed by the requester terminal 130. Further, the modules may be any combination of the hardware circuits and the application/instructions.
  • the modules may be the part of the requester terminal 130 when the requester terminal 130 executes the application/set of instructions.
  • the receiving module 901 may be configured to receive a request for a service via a user interface of the requester terminal 130.
  • the requested service may include any product, such as an O2O service.
  • the request for the service may be inputted by a user of the requester terminal 130 (also referred to as a requester) via the user interface. More descriptions regarding the receiving of the request for the service may be found elsewhere in the present disclosure. See, e.g., operation 910 and relevant descriptions thereof.
  • the communication module 902 may be configured to communicate with one or more components of the service system 100. For example, the communication module 902 may send the request to a service platform (e.g., the service system 100) . Additionally or alternatively, the communication module 902 may receive information of at least one target service provider from the service platform. The information may include a weight factor of the at least one target service provider. More descriptions regarding the sending of the request and the information related to the at least one target service provider may be found elsewhere in the present disclosure. See, e.g., operations 920 and 930 and relevant descriptions thereof.
  • the presentation module 903 may be configured to present information. For example, the presentation module 903 may present the information of the at least one target service provider via the user interface according to the weight factor of the at least one target service provider. As another example, the presentation module 903 may be further configured to present an invitation for a feedback regarding one or more of the at least one target service provider via the user interface. More descriptions regarding the presentation of the information of the at least one target service provider and the invitation for a feedback regarding one or more of the at least one target service provider may be found elsewhere in the present disclosure. See, e.g., operations 940 and 950 and relevant descriptions thereof.
  • the requester terminal 130 may further include one or more additional modules or one or more above-mentioned modules may be omitted.
  • the requester terminal 130 may further include a compiling module configured to compile the information of the at least one target service provider.
  • the requester terminal 130 may further include an encrypt module configured to encrypt information and/or a decrypt module configured to decrypt information.
  • FIG. 9B is a flowchart illustrating an exemplary process for presenting information related to service providers on a user interface of a requester terminal according to some embodiments of the present disclosure.
  • process 900 may be executed by the service system 100.
  • the process 900 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, the storage 390) .
  • a requester terminal 130 e.g., a CPU or GPU of the requester terminal 130, and/or one or more modules illustrated in FIG. 9A
  • the platform may be an Internet-based platform that connects service providers and requesters through the Internet.
  • the requester terminal 130 may receive a request for a service via a user interface of the requester terminal 130.
  • the requested service may include any product, such as an O2O service.
  • the request for the service may be inputted by a user of the requester terminal 130 (also referred to as a requester) via the user interface.
  • the requester terminal 130 may present a specific user interface (e.g., a user interface as illustrated in FIG. 16) for the requester to input the request.
  • the requester may input the request in a specific field in the user interface of the requester terminal 130. More descriptions regarding the request for service may be found elsewhere in the present disclosure. See, e.g., operation 510 and relevant descriptions thereof.
  • the requester terminal 130 may encrypt the received request, and send the encrypted request to the service platform.
  • the requester terminal 130 may encrypt the request using its private key and/or digitally sign the request.
  • the encrypted request may include authentication information related to the requester terminal 130 and/or the requester, such as an identification of the requester, a password inputted by the requester, a digital signature of the requester terminal 130. The authentication information may allow the service platform to verify the requester terminal 130 and/or the requester.
  • the requester terminal 130 may send the request for the service to a service platform (e.g., the service system 100) .
  • a service platform e.g., the service system 100
  • the requester terminal 130 may receive information at least one target service provider from the service platform.
  • the information may include a weight factor of the at least one target service provider.
  • the at least one target service provider may include one or more service providers who are recommended to provide the requested service to the requester.
  • the weight factor of the at least one target service provider may indicate a degree that the at least one target service provider is recommended to the requester.
  • the weight factor may be associated with performance information of the at least one target service provider.
  • the at least one target service provider and the weight factor of the at least one target service provider may be determined by one or more components of the service platform (e.g., the processing engine 112) in response to the request.
  • the processing engine 112 may perform operations 520 to 540 to determine the weight factor of the at least one target service provider based on the performance information of the at least one target service provider.
  • the performance information of the at least one target service provider may include one or more feedbacks with respect to the at least one target service provider.
  • the value of the weight factor may be determined based at least in part on a determination as to whether the at least one target service provider has received a feedback from the requester of the requester terminal 130.
  • the processing engine 112 may perform one or more operations in the process 700 to determine the weight factor.
  • the information of the at least one target service provider may include profile information, performance information, location information, vehicle information, time information, related to each of the at least one target service provider or the like, or any combination thereof.
  • the information may include acquired by one or more components of the service platform (e.g., the processing engine 112) from one or more storage devices that store the information.
  • the information may include compiled information related to the at least one target service provider generated by the processing engine 112 as described in connection with operation 550.
  • the at least one target service provider may include a plurality of target service providers.
  • the information may be a list including information related to each of the target service providers, in which the information related to the target service providers is presented in a descending order according to the respective weight factors of the target service providers.
  • the compiled information may be encrypted by the service platform.
  • the requester terminal 130 may decrypt the received information.
  • the service platform may encrypt the compiled information using a public key of the requester terminal 130.
  • the requester terminal 130 may decrypt the encrypted information using a private key of the requester terminal 130.
  • the received information may include authentication information related to the requester terminal 130 and/or requester (e.g., the public key of the requester terminal 130 and/or an identification of the requester) that allows authentication of the requester terminal 130 and/or the requester.
  • the requester terminal 130 may present the information of the at least one target service provider via the user interface according to the weight factor.
  • the at least one target service provider may include a plurality of target service providers.
  • the information received from the service platform may include information related to each of the target service providers.
  • the requester terminal 130 may compile the information related to each of the target service providers, and present the compiled information. For example, the requester terminal 130 may determine a ranking of the target service providers based on the weight factors in, for example, a descending order according to the respective weight factors.
  • the requester terminal 130 may further compile the information related to the target service providers into a list based on the ranking of the target service providers, in which the information related to the target service providers is sorted according to the ranking of the target service providers.
  • the information received from the service platform may include compiled information related to the target service providers generated by the processing engine 112.
  • the requester terminal 130 may directly present the compiled information via the user interface.
  • the requester terminal 130 may present an invitation for a feedback regarding one or more of the at least one target service provider via the user interface.
  • the requester terminal 130 after the requester terminal 130 presents the information (or compiled information) of the at least one target service provider.
  • the requester may select one or more of the at least one target service provider to provide the requested service for him/her.
  • the requester terminal 130 may present the invitation for a feedback of the selected one or more target service providers after or during the service.
  • the invitation for a feedback may be presented on the user interface as a question regarding the selected one or more target service providers, a requirement for the requester to give the feedback, or in any other suitable form.
  • the requester may input the feedback regarding the selected target service provider (s) via the user interface.
  • the requester terminal 130 may transmit the requester’s feedback to the processing engine 112 upon detecting the requester’s input. More descriptions regarding the invitation for the feedback regarding one or more of the at least one target service provider may be found elsewhere in the present disclosure. See, e.g., operation 560, FIGs. 10 to 15 and relevant descriptions thereof.
  • the process 900 may be accomplished with one or more additional operations not described and/or without one or more of the operations herein discussed.
  • operation 950 may be omitted.
  • one or more operations of the process 900 may be divided into a plurality of sub-operations.
  • operation 940 may be divided into a first sub-operation in which the requester terminal 130 compiles the information of the at least one target service provider and a second sub-operation in which the requester terminal 130 presents the compiled information.
  • the order in which the operations of the process as illustrated in FIG. 9 and described above is not intended to be limiting.
  • FIGs. 10 to 15 illustrate exemplary user interfaces of a requester terminal 130 of a passenger for evaluating a driver according to some embodiments of the present disclosure.
  • the requester terminal 130 of the passenger may present the user interface 1000 to invite the passenger to give a feedback (or evaluation) regarding the driver.
  • the user interface 1000 may display a question regarding the driver, and provide one or more elements corresponding to different feedbacks for the passenger to choose from. For example, as illustrated in FIG. 10, the user interface 1000 displays a question “Would you like to have a trip with the driver again? ” and interface elements 1010, 1020, and 1030. The passenger may click the interface element 1030 to show that he/she expects to have a trip with the driver again (i.e., give a positive feedback regarding the driver) .
  • the passenger may click the interface element 1020 to show that he/she can accept to have a trip with the driver again (i.e., give a neutral feedback regarding the driver) .
  • the passenger may click the interface element 1010 to show that he/she is not willing to have a trip with the driver again (i.e., give a negative feedback regarding the driver) .
  • the feedback of the passenger regarding the driver may be transmitted to one or more other components of the service system 100 (e.g., the processing engine 112, the storage device160) for further analysis (e.g., for further analysis in order allocation) .
  • the user interface 1000 may turn to a user interface 1100 as shown in FIG. 11.
  • the user interface 1100 may present an evaluation regarding the passenger received from the driver. For example, the driver’s evaluation regarding the passenger is illustrated in a region 1110 of the user interface 1100, which shows that the driver expects to have a trip with the passenger and thinks the passenger is a stylish and punctual girl.
  • the user interface 1100 may also present an interface element 1120 for following the driver and/or an interface element (e.g., an icon) 1130 for giving a gift to the driver.
  • the user interface 1100 may turn to a user interface 1200 as shown in FIG. 12. Similar to the user interface 1100, the user interface 1200 may also present the evaluation regarding the passenger received from the driver as shown in a region1210 of the user interface 1200. Below the region 1210, the user interface 1200 may present one or more interface elements (i.e., interface elements 1220, 1230, and 1240) corresponding to one or more gifts that the passenger can give to the driver. For example, the passenger may click the interface element 1220 to give the driver a trophy for rewarding the driver’s service. As another example, the passenger may click the interface element 1230 to give the driver a cup of beer to show his/her goodwill. As yet another example, the passenger may click the interface element 1230 to give the driver a medal to express thanks to the driver.
  • interface elements 1220, 1230, and 1240 corresponding to one or more gifts that the passenger can give to the driver.
  • the passenger may click the interface element 1220 to give the driver a trophy for rewarding the driver’s service.
  • the user interface 1000 may turn to a user interface 1300 as shown in FIG. 13.
  • the user interface 1300 may present an evaluation regarding the driver received from the passenger. For example, the passenger’s complains about the driver is illustrated in a region 1310 of the user interface 1300.
  • the evaluation regarding the driver may be anonymous and not visible to the driver. Additionally or alternatively, the user interface 1300 may also present an interface element 1320 for the passenger to view driver’s evaluation on the passenger.
  • the user interface 1300 may turn to a user interface 1400 as shown in FIG. 14.
  • the user interface 1400 may present an evaluation regarding the passenger received from the driver. For example, as illustrated in a region 1410, the driver expects to have a trip with the passenger again and thinks the passenger is punctual, beautiful, and friendly.
  • the user interface 1400 may also present an interface element 1420 to add the driver to a blacklist.
  • the user interface 1400 may turn to a user interface 1500 as shown in FIG. 15.
  • the user interface 1500 may present a message to remind the passenger about the consequence of adding the driver to the blacklist.
  • a prompt box 1510 may appear on the user interface 1500 in response to the click of the interface element 1420 to remind the passenger that he/she will not view each other’s order after adding the driver to the blacklist.
  • the passenger may click an interface element 1520 or 1530 to confirm or cancel the operation of adding the driver to the blacklist.
  • the user interface 1500 may turn back to the user interface 1400 if the passenger clicks the interface element 1530.
  • FIGs. 16 and 17 illustrate exemplary user interfaces of a requester terminal 130 of a passenger for requesting a transportation service according to some embodiments of the present disclosure.
  • the user interface 1600 may present information related to the request of a transportation service. For example, as illustrated in FIG. 16, the user interface 1600 presents available types of vehicles in a region 1610, a start location in a region 1610, a destination in a region 1620, the number passenger and a departure time in a region 1640, and price information related to the transportation service in a region 1650.
  • the information presented on the user interface 1600 may be provided by the requester terminal 130, the processing engine 112, the passenger, or the like, or any combination thereof.
  • the start location may be determined by a location detection mechanism (e.g., a GPS) of the requester terminal 130 and filled in the region 1610 automatically by the requester terminal 130.
  • the destination may be input manually by the passenger.
  • the start location and/or the destination may be determined by the processing engine 112 by, for example, analyzing historical service orders of the passenger and provided to the requester terminal 130.
  • the passenger may click an interface element 1630 to send the request after confirming the information related to the request.
  • the requester terminal 130 may send the request to the processing engine 112.
  • the processing engine 112 may perform one or more processes disclosed in the present disclosure to process the request.
  • the processing engine 112 may perform the process 500 to determine one or more target service providers for the request and a weight factor of each of the target service providers.
  • the processing engine 112 may further compile information related to the target service providers according to the weight factors of the target service providers, and transmit the compiled information to the requester terminal 130 for presentation.
  • the processing engine 112 may transmit the weight factors of the target service providers and the information related to the target service provider to the requester terminal 130.
  • the requester terminal 130 may compile the information related to the target service providers for presentation.
  • the compiled information related to the target service providers may be presented as a list of the information related to the target service provider.
  • the information related to the target service provider in the list may be sorted according to a ranking of the target service provider (e.g., a ranking determined based on the respective weight factors of the target service providers in a descending order) .
  • a ranking of the target service provider e.g., a ranking determined based on the respective weight factors of the target service providers in a descending order
  • the processing engine 112 determines drivers A, B, and C (i.e., target service providers) for the request, and determines that the weight factors of A, B, and C are 70%, 60%, and 50%, respectively.
  • the information of the drivers A, B, and C may be presented in an order as illustrated on a user interface 1700 in FIG. 17.
  • the passenger may then select one driver of the drivers A, B, and C to make a reservation according to the information of the drivers.
  • the passenger may click an interface element 1710 as illustrated in FIG. 17 so that the processing engine 112 may automatically select a suitable driver (e.g., on the top of the list or with the highest route matching degree) for the passenger.
  • the user interface 1700 may present the average waiting time for the target service providers to arrive at the start location of the request, for example, at a region 1720. Additionally or alternatively, the user interface 1700 may display an interface element 1730 for cancelling reservation as illustrated in FIG. 17.
  • the interface elements (e.g., 1020, 1030, 1120, 1130, 1220, 1230, and 1240) of the user interfaces 1000 to 1700 are merely illustrative, and these interface elements may be configured in any other suitable shape, size, and/or position.
  • one or more of the interface elements of the user interfaces 1000 to 1700 illustrated in figures may be omitted, and the user interfaces 1000 to 1700 may include one or more additional interface elements.
  • 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)
  • Economics (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Tourism & Hospitality (AREA)
  • Finance (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Game Theory and Decision Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

La présente invention concerne un procédé de détermination d'informations relatives à des fournisseurs de services en vue de leur présentation. Le procédé peut consister à recevoir une demande pour un service en provenance d'un terminal demandeur par l'intermédiaire d'une interface utilisateur du terminal demandeur, et à identifier une pluralité de fournisseurs de services en réponse à la demande. Le procédé peut en outre consister à obtenir des informations de performances relatives à la pluralité de fournisseurs de services, et à déterminer un facteur de pondération d'au moins un fournisseur de services cible parmi la pluralité de fournisseurs de services sur la base des informations de performances. Le procédé peut également consister à compiler des informations sur le ou les fournisseurs de services cibles en vue de leur présentation sur le terminal demandeur par l'intermédiaire de l'interface utilisateur, sur la base du facteur de pondération du ou des fournisseurs de services cibles.
PCT/CN2018/124606 2018-02-12 2018-12-28 Systèmes et procédés de communication sécurisée d'informations de service WO2019153944A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810144636.1 2018-02-12
CN201810144636.1A CN110163702A (zh) 2018-02-12 2018-02-12 业务处理方法、装置和存储介质

Publications (1)

Publication Number Publication Date
WO2019153944A1 true WO2019153944A1 (fr) 2019-08-15

Family

ID=67549221

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/124606 WO2019153944A1 (fr) 2018-02-12 2018-12-28 Systèmes et procédés de communication sécurisée d'informations de service

Country Status (2)

Country Link
CN (1) CN110163702A (fr)
WO (1) WO2019153944A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355714A (zh) * 2007-07-24 2009-01-28 梁宇杰 一种实时拼车系统和方法
CN101751775A (zh) * 2008-11-28 2010-06-23 上海迪哈大计算机科技有限公司 一种搭车请求处理系统以及相应的控制方法
CN102479431A (zh) * 2010-11-23 2012-05-30 互动网数位科技股份有限公司 具配对功能的计程车叫车系统及其方法
US20160034828A1 (en) * 2014-08-04 2016-02-04 Uber Technologies, Inc. Determining and providing predetermined location data points to service providers

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5973619A (en) * 1997-06-10 1999-10-26 Paredes; Alexis Automated vehicle dispatch and payment honoring system
CN103996290B (zh) * 2014-06-09 2016-08-24 北京东方车云信息技术有限公司 一种提供叫车服务的方法、服务器及系统
CN104794887B (zh) * 2014-10-27 2017-01-25 北京东方车云信息技术有限公司 在网络租车中利用收藏夹派车的系统和方法
CN106559313B (zh) * 2015-09-30 2021-10-26 百度在线网络技术（北京）有限公司 拼车的方法和服务器
CN106447074A (zh) * 2016-12-30 2017-02-22 北京东方车云信息技术有限公司 一种将订单信息推送给司机客户端的方法、装置及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101355714A (zh) * 2007-07-24 2009-01-28 梁宇杰 一种实时拼车系统和方法
CN101751775A (zh) * 2008-11-28 2010-06-23 上海迪哈大计算机科技有限公司 一种搭车请求处理系统以及相应的控制方法
CN102479431A (zh) * 2010-11-23 2012-05-30 互动网数位科技股份有限公司 具配对功能的计程车叫车系统及其方法
US20160034828A1 (en) * 2014-08-04 2016-02-04 Uber Technologies, Inc. Determining and providing predetermined location data points to service providers

Also Published As

Publication number Publication date
CN110163702A (zh) 2019-08-23

Similar Documents

Publication Publication Date Title
US10989548B2 (en) Systems and methods for determining estimated time of arrival
CN109478275B (zh) 分配服务请求的系统和方法
US10997857B2 (en) Methods and systems for carpooling
AU2019246799B2 (en) Systems and methods for distributing a service request for an on-demand service
WO2017088828A1 (fr) Systèmes et procédés pour attribuer des commandes partageables
US20210140774A1 (en) Systems and methods for recommending pick-up locations
US20200011692A1 (en) Systems and methods for recommending an estimated time of arrival
AU2017400606B2 (en) Systems and methods for providing a navigation route
US20200300650A1 (en) Systems and methods for determining an estimated time of arrival for online to offline services
US20180053277A1 (en) Systems and methods for carpooling
US20180202818A1 (en) Systems and methods for distributing request for service
WO2018191856A1 (fr) Système et procédé de détermination d'un score de sécurité de conducteur
WO2021012342A1 (fr) Systèmes et procédés de prédiction de trafic
WO2018209551A1 (fr) Systèmes et procédés permettant de déterminer une heure d'arrivée estimée
US20210327015A1 (en) Systems and methods for carpooling
US20200167812A1 (en) Systems and methods for determining a fee of a service request
WO2020113626A1 (fr) Systèmes et procédés de détermination d'heure d'arrivée estimée
US20200143415A1 (en) Systems and methods for feed stream transmission
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
WO2019153944A1 (fr) Systèmes et procédés de communication sécurisée d'informations de service

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: 18905791

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: 18905791

Country of ref document: EP

Kind code of ref document: A1