CN112036594B

CN112036594B - Riding order management method and system

Info

Publication number: CN112036594B
Application number: CN202010912719.8A
Authority: CN
Inventors: 肖中中
Original assignee: Beijing Didi Infinity Technology and Development Co Ltd
Current assignee: Beijing Didi Infinity Technology and Development Co Ltd
Priority date: 2020-09-02
Filing date: 2020-09-02
Publication date: 2024-05-07
Anticipated expiration: 2040-09-02
Also published as: CN112036594A

Abstract

The embodiment of the specification provides a method and a system for managing a riding order, wherein the method comprises the following steps: receiving an access request initiated by a user terminal through scanning an access code corresponding to a vehicle; the access code uniquely corresponds to the vehicle and comprises vehicle information of the vehicle, and the access request comprises user side information and the vehicle information; determining the user identity of the user side according to the user side information and the vehicle information; and sending an access interface matched with the user identity to the user side so that the user side can input riding order information related to the user side through the access interface.

Description

Riding order management method and system

Technical Field

One or more embodiments of the present disclosure relate to the field of travel, and in particular, to a method and system for managing a riding order.

Background

In life and travel of people, taxis are a common transportation means. When people take a taxi, such off-line take orders as taxi orders generally have no corresponding background record, so that passengers are difficult to retrospectively know information of the off-line take orders, and meanwhile difficulty is brought to supervision of the off-line take orders as taxi orders.

Therefore, how to manage the on-line riding orders is a problem to be solved.

Disclosure of Invention

One of the embodiments of the present specification provides a method of ride order management, the method comprising: receiving an access request initiated by a user terminal through scanning an access code corresponding to a vehicle; the access code uniquely corresponds to the vehicle and comprises vehicle information of the vehicle, and the access request comprises user side information and the vehicle information; determining the user identity of the user side according to the user side information and the vehicle information; and sending an access interface matched with the user identity to the user side so that the user side can input riding order information related to the user side through the access interface.

One of the embodiments of the present specification provides a system for ride order management, the system comprising: the receiving module is used for receiving an access request initiated by a user side through scanning an access code corresponding to the vehicle; the access code uniquely corresponds to the vehicle and comprises vehicle information of the vehicle, and the access request comprises user side information and the vehicle information; the identity determining module is used for determining the user identity of the user terminal according to the user terminal information and the vehicle information; and the sending module is used for sending an access interface matched with the user identity to the user side so that the user side can input riding order information related to the user side through the access interface.

One of the embodiments of the present specification provides an apparatus comprising a processor and a memory; the memory is used for storing instructions, and the device is characterized in that when the instructions are executed by the processor, the device realizes operations corresponding to the method according to any one of the technical schemes.

One of the embodiments of the present disclosure provides a computer-readable storage medium storing computer instructions that, when executed by a computer, perform the method according to any one of the above claims.

Drawings

One or more embodiments of the present specification will be further illustrated by way of example embodiments, which will be described in detail with reference to the accompanying drawings. The embodiments are not limiting, in which like numerals represent like structures, wherein:

FIG. 1 is an application scenario diagram of a system for ride order management according to some embodiments of the present description;

FIG. 2 is an exemplary flow chart of a method of ride order management according to some embodiments of the present description;

FIG. 3 is a flow chart of determining trip information for a method of ride order management according to some embodiments of the present description;

FIG. 4 is a flow chart of a method of ride order management pushing personalized recommended content to a user according to some embodiments of the present description;

FIG. 5 is a block diagram of a system for ride order management according to some embodiments of the present description.

Detailed Description

In order to more clearly describe the technical solutions of one or more embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly described below. It will be apparent to those of ordinary skill in the art from this disclosure that the drawings in the following description are merely examples or embodiments of the present disclosure and that one or more embodiments of the present disclosure may be applied to other similar situations in light of the drawings without undue effort. Unless otherwise apparent from the context of the language or otherwise specified, like reference numerals in the figures refer to like structures or operations.

It will be appreciated that "system," "unit," and/or "module" as used herein is one method for distinguishing between different components, elements, parts, portions, or assemblies of different levels. However, if other words can achieve the same purpose, the words may be replaced by other expressions.

As used in this specification, one or more embodiments and in the claims, the terms "a," "an," "the," and/or "the" are not intended to be special purpose, but rather are intended to include the singular as well, unless the context clearly indicates otherwise. In general, the terms "comprises" and "comprising" merely indicate that the steps and elements are explicitly identified, and they do not constitute an exclusive list, as other steps or elements may be included in a method or apparatus.

Flowcharts are used in one or more embodiments to describe the operations performed by systems according to one or more embodiments of the present description. It should be appreciated that the preceding or following operations are not necessarily performed in order precisely. Rather, the steps may be processed in reverse order or simultaneously. Also, other operations may be added to or removed from these processes.

The embodiment of the application relates to a method and a system for managing a riding order, wherein the method for managing the riding order determines the user identity of a user by receiving an access request initiated by a user end through scanning an access code corresponding to a vehicle, and transmits an access interface matched with the user identity to the user end, so that the user end can input riding order information through the access interface, and the riding order information is online. By the method, the system for managing the riding orders can receive and record the information of the online riding orders, so that the management of the online riding orders is realized. The access code is used as a contact for converting an off-line order into an on-line record, so that the management of the off-line riding order can be simply and efficiently realized. The access code corresponding to the vehicle can be applied to taxis for pickup, other vehicles reserved in line (such as freight vehicles, rescue vehicles and the like), and the like.

FIG. 1 is an application scenario diagram of a system for ride order management according to some embodiments of the present description. The system for managing the riding orders can be used for an on-line management platform of taxi companies (or freight companies, road rescue companies and the like). Hereinafter, a vehicle will be described as an example of a taxi. In some embodiments, the ride order management system may record order information for passengers riding taxis. As shown in fig. 1, the system 100 for ride order management of the present application may include a server 110, a passenger side 120, a driver side 130, a database 140, a network 150, and an access code 160.

In some embodiments, server 110 may be used to process information and/or data related to ride order management. The server 110 may be a stand-alone server or a group of servers. The server farm may be centralized or distributed (e.g., server 110 may be a distributed system). The server 110 may be regional or remote in some embodiments. For example, server 110 may access information and/or profiles stored at passenger side 120, and/or database 140, via network 150. In some embodiments, the server 110 may be directly connected to the passenger side 120 and/or the database 140 to access information and/or material stored therein. In some embodiments, server 110 may execute on a cloud platform. For example, the cloud platform may include one of a private cloud, a public cloud, a hybrid cloud, a community cloud, a decentralized cloud, an internal cloud, or the like, or any combination thereof.

In some embodiments, server 110 may include a processing device. The processing device may process data and/or information related to the service request to perform one or more of the functions described in the present application. For example, the processing device may collect information related to a riding order through an access interface based on acquiring an access request initiated by a user side (the passenger side 120 or the driver side 130) through scanning an access code corresponding to a vehicle, and providing the user side with an access interface matched with a user identity. In some embodiments, the processing device may include one or more sub-processing devices (e.g., a single core processing device or a multi-core processing device). By way of example only, a processing device may include a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), an Application Specific Instruction Processor (ASIP), a Graphics Processor (GPU), a Physical Processor (PPU), a Digital Signal Processor (DSP), a Field Programmable Gate Array (FPGA), an editable logic circuit (PLD), a controller, a microcontroller unit, a Reduced Instruction Set Computer (RISC), a microprocessor, and the like, or any combination thereof.

In some embodiments, passenger side 120 may be understood as the user side used by the passenger riding the vehicle and driver side may be understood as the user side used by the driver driving the vehicle. In some embodiments, passenger side 120 and driver side 130 may be a variety of smart devices including cameras. For example, the passenger side 120 and the driver side 130 may be mobile devices, tablet computers, laptops, etc. In some embodiments, the mobile device may include a wearable device, a smart mobile device, a virtual reality device, an augmented reality device, and the like, or any combination thereof. In some embodiments, the wearable device may include a smart wristband, smart footwear, smart glasses, smart helmets, smart watches, smart clothing, smart back bags, smart accessories, and the like, or any combination thereof. In some embodiments, the smart mobile device may include a smart phone, a Personal Digital Assistant (PDA), a gaming device, a navigation device, a POS device, etc., or any combination thereof. In some embodiments, the metaverse device and/or augmented reality device may include a metaverse helmet, metaverse glasses, metaverse eyepieces, augmented reality helmet, augmented reality glasses, augmented reality eyepieces, and the like, or any combination of the above examples. In some embodiments, the passenger side 120 and the driver side 130 may include devices with positioning functions to determine the position of the passenger side 120 and/or the driver side 130.

Database 140 may store materials and/or instructions. In some embodiments, database 140 may store vehicle information and information obtained from the user's side, such as order information, a driver's library, and the like. In some embodiments, database 140 may store information and/or instructions for execution or use by server 110 to perform the exemplary methods described in this disclosure. In some embodiments, database 140 may include mass storage, removable storage, volatile read-write memory (e.g., random access memory RAM), read-only memory (ROM), and the like, or any combination thereof. In some embodiments, database 140 may be implemented on a cloud platform. For example, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a decentralized cloud, an internal cloud, and the like, or any combination thereof.

In some embodiments, the database 140 may be in communication with one or more components of the system 100 for ride order management (e.g., the server 110, the passenger side 120, etc.). One or more components of the system 100 for ride order management may access materials or instructions stored in the database 140 via the network 150. In some embodiments, the database 140 may be directly connected to or in communication with one or more components (e.g., the server 110, the passenger side 120, etc.) in the system 100 for ride order management. In some embodiments, database 140 may be part of server 110.

In some embodiments, one or more components (e.g., server 110, passenger side 120, etc.) in the system 100 for ride order management may have access to the database 140. In some embodiments, one or more components (e.g., server 110, passenger side 120, etc.) in the ride order management system 100 may read and/or modify information related to the user, and/or common general knowledge when one or more conditions are met.

Network 150 may facilitate the exchange of data and/or information. In some embodiments, one or more components in the ride order management system 100 (e.g., the server 110, the passenger side 120, and the database 140) may send data and/or information to other components in the ride order management system 100 over the network 150. For example, the server 110 may obtain/obtain access requests or ride order information associated with the customer from the customer via the network 150. In some embodiments, network 150 may be any type of wired or wireless network. For example, the network 150 may include a cable network, a wired network, a fiber optic network, a telecommunications network, an intranet, the Internet, a Local Area Network (LAN), a Wide Area Network (WAN), a Wireless Local Area Network (WLAN), a Metropolitan Area Network (MAN), a Public Switched Telephone Network (PSTN), a Bluetooth network, a ZigBee network, a Near Field Communication (NFC) network, and the like, or any combination thereof. In some embodiments, network 150 may include one or more network access points. For example, the network 150 may include wired or wireless network access points, such as base stations and/or internet switching points, through which one or more components of the system 100 for ride order management may connect to the network 150 to exchange data and/or information.

In some embodiments, the vehicle may be a taxi, a reserved truck, a reserved rescue car, or other car for off-line service, or the like. The access code 160 is uniquely associated with the vehicle and is generated based on information about the vehicle. The access code 160 may be a bar code, a two-dimensional code, a three-dimensional code, or the like, or may be a picture with a special identifier. The access code 160 may be displayed in the form of a picture in a car interior or body of the car, etc. In some embodiments, after the passenger side 120 or the driver side 130 scans the access code 160 corresponding to the vehicle, an access request may be initiated, and the access request may be sent to the server 110 through the network 150, and the server 110 may establish communication with and interact with the corresponding passenger side 120 or the driver side 130 through the network 150. The server 110 may identify whether the terminal scanning the access code 160 is the passenger side 120 or the driver side 130, and thus transmit a corresponding access interface (e.g., account registration interface, account login interface, information filling interface, etc.) to the terminal scanning the access code 160.

FIG. 2 is an exemplary flow chart of a method of ride order management according to some embodiments of the present description. In particular, the method of ride order management may be performed by a processing device (e.g., server 110). For example, the method of taking order management may be stored in a storage device (e.g., a storage device of a server, a memory) in the form of a program or instructions that when executed by a system (e.g., a processing device) of taking order management may implement the method of taking order management. As shown in fig. 2, a flow 200 of a method of ride order management may include the steps of:

step 210, receiving an access request initiated by a user terminal through scanning an access code corresponding to a vehicle; the access code uniquely corresponds to the vehicle and contains the vehicle information, and the access request comprises user side information and vehicle information. In particular, step 210 may be performed by the receiving module 510.

In this embodiment, the vehicle may be a taxi, a reserved truck, a reserved rescue vehicle, or other off-line service vehicle. For example, the vehicle may be a taxi that a passenger takes, or the vehicle may be a vehicle that the passenger reserves for moving or road rescue. The access code may be a two-dimensional code, a bar code, a three-dimensional code, or a picture with a special identification. An access code may be understood as a server access interface generated based on information of a vehicle, the access code uniquely corresponding to the vehicle. In some embodiments, the access code may be formed by encoding a URL link uniquely corresponding to the vehicle, and the operation of generating the access code may be performed by a server, or may be performed by other systems or devices for generating the access code based on vehicle information. After the user side scans the access code, the URL link can be accessed, vehicle information is obtained, and an access request is initiated. The access code may be displayed on or in the vehicle body in the form of a picture, for example, the picture printed with the access code may be glued to the seat back of the vehicle, or the access code may be displayed on the vehicle's center screen.

In some embodiments, the vehicle information includes at least identification information of the vehicle, which may be understood as information specific to each vehicle that can distinguish one vehicle from other vehicles. For example, the vehicle identification may be a license plate number, a frame number, an engine number, etc. of the vehicle. In addition, the vehicle information may further include one or more of driver information, operator information to which the vehicle belongs, city information to which the vehicle belongs, and the like. The driver information may include one or more of name, photo, identification number, driver license expiration date, etc. The vehicle information of each vehicle may include driver information of a plurality of drivers operating the vehicle. The operator information of the vehicle may include one or more of a name of the operator of the vehicle, a legal name, a tax payer identification number, a registered address, and the like. The information of the operating city of the vehicle may include one or more of the name of the city, longitude and latitude, etc.

In some embodiments, the client information may include at least client account information. The user account information may be understood as information of an account registered by the user in the background of the riding order management system. For example, the account information may include one or more of a user name of the account, a phone number used to register the account, a registration time, and the like. In some embodiments, the user side information may also be information of other registered account numbers of the APP with the code scanning function used by the user. It can be understood that the account information of the user in the scan code APP may be universal with the account information of the riding order management system, for example, openID, mobile phone number or a certain certificate number is used as the account information, so when the access request includes the account information of the scan code APP, the riding order management system can still determine the user information of the user terminal based on the account information. In some embodiments, the client information may further include time information of the client scanning the access code and/or location information of the client, etc. The location information of the ue may include a location of a time when the ue scans the access code, and may further include a real-time location of the ue during a period from when the ue scans the access code to when the ride is completed.

In some embodiments, for the ue, when the ue scans the access code, it may jump to the access interface (or the web page interface) pointed by the URL included in the access code. Therefore, the act of the user side scanning the access code can be regarded as initiating an access request, and the URL is bound to the vehicle information, so that the background of the riding order management system can learn the vehicle information. In addition, when the user side scans the access code, the user side information (such as account information of the system or account information of the code scanning APP) is also automatically uploaded, so that the user side information and the vehicle information can be carried in the access request. Correspondingly, the background of the riding order management system can acquire the vehicle information and the user side information through the access request behavior of the user scanning the access code. In some embodiments, the user side may also obtain the URL and the vehicle information by scanning the access code, generate an access request, and carry the vehicle information obtained by identifying the access code and the user side information of the user side in the request, and then send the access request (or the access instruction) to the background (such as the server 110) of the riding order management system through the URL.

Step 220, determining the user identity of the user terminal according to the user terminal information and the vehicle information. In particular, step 220 may be performed by identity determination module 520.

In some embodiments, the user identity includes at least a passenger identity and a driver identity. The user identity may also include manager identity, unregistered user identity, and the like.

In some embodiments, the user account information may include a user identity (e.g., an identification bit indicating that the user is a passenger identity or a driver identity), and the identity determination module 520 may determine the user identity directly from the user identity information.

In other embodiments, step 220 may further comprise: searching in a driver library, if the mapping record of the user side information and the vehicle information is searched, determining the user identity as a driver, otherwise, determining the user identity as a passenger. The driver library comprises a plurality of mapping records of user side information and vehicle information. The driver database can be pre-stored with the mapping record of the user information and the vehicle information used by the driver, i.e. the driver binding data with the vehicle driven and operated by the driver is stored in the driver database. Thus, if a mapping record of the user side information and the vehicle information is searched in the driver's cabin, the identity determination module 520 may determine that the user side is used as a driver, and otherwise determine that the user side is used as a passenger. By such arrangement, one user side can have multiple user identities (both driver and passenger), and the user identity of the user side can be accurately determined in different scenes. For example, when a driver uses a client to scan a vehicle that is not being driven by the driver, the identity determination module 520 determines the identity of the user as a passenger because there is no mapping record in the driver's library of the client used by the driver and the vehicle information that is not being driven by the driver.

Further, when the mapping record of the user side information and the vehicle record is not searched in the driver's cabin, searching can be performed in the passenger cabin, if the mapping record of the user side information and the vehicle information is searched in the passenger cabin, the user identity can be determined to be a registered passenger, and if the mapping record of the user side information and the vehicle information is not searched, the user identity can be determined to be an unregistered user.

Step 230, the access interface matched with the user identity is sent to the user side, so that the user side can input the riding order information related to the user side through the access interface. In particular, step 230 may be performed by the transmitting module 530.

In some embodiments, the ride order information may include a combination of one or more of a start location, a destination, a ride mode (e.g., whether to share a ride), a number of passengers, and the like of the ride.

In some embodiments, the access interfaces that match the user identity include an access interface corresponding to the passenger identity and an access interface corresponding to the driver identity. Specifically, when the user identity of the user terminal is a passenger, the transmitting module 530 transmits the access interface corresponding to the passenger identity to the user terminal, and when the user identity of the user terminal is a driver, the transmitting module 530 transmits the access interface corresponding to the driver identity to the user terminal. The access interface may be a software, applet, or web interface of the ride order management system, which may include a variety of different interfaces. The interface can be an access link, and clicking on the access link at the user end can jump to a sub-page for further information entry or presentation. The interface can also be a layout which is visually presented in the interface, such as an information input or information display layout on a webpage. The interface can also be a control, and when the interface is clicked on the user side, the background can be triggered to record, switch state or update state. The user inputs the riding order information related to the user side, and the riding order information, the user side information and the vehicle information are bound together and recorded in the background.

In some embodiments, the access interface corresponding to the passenger identity comprises a combination of one or more of the following interfaces: the system comprises a registered interface, a riding order information input interface, a vehicle information viewing interface, a journey cost payment interface, an evaluation interface, an alarm interface, a contact customer service interface and an advertisement viewing interface. By setting a registered interface, an unregistered user can perform account registration after scanning an access code. By providing an interface for entering ride order information, passengers may enter information related to the ride order, including, but not limited to: information such as origin, destination, departure time, etc. By setting an interface for checking vehicle information and an interface for checking journey information, passengers can more comprehensively know own on-line riding orders. By providing an interface for payment of travel fees, passengers can more conveniently pay for placing orders for a line. Through setting up the interface of evaluation and the interface of contact customer service, can make the passenger more convenient feedback the relevant problem of taking a bus order, promote user experience, also can carry out better supervision to driver's service simultaneously. Through setting up the interface of warning, can effectively guarantee the passenger safety in the order of taking a bus off line.

In some embodiments, when the user identity is determined to be a passenger, one or more of an interface for inputting the riding order information, an interface for viewing the vehicle information, an interface for viewing the journey information, an interface for paying journey fees, an interface for evaluating, an interface for alarming, an interface for contacting customer service, an interface for viewing advertisements and the like can be simultaneously transmitted to the corresponding user side, or transmitted to the user side according to a preset sequence. For example, the preset sequence may be an interface for inputting the riding order information, an interface for alarming, and an interface for contacting the customer, and then an interface for checking the vehicle information, and an interface for checking the travel information, an interface for payment of the travel cost, and an interface for evaluation are sent after the travel is finished. The sending sequence of each interface can be adjusted according to the use requirement, and the application is not limited further. When the determined user identity is an unregistered user, the registered interface may be sent to the corresponding user terminal first, and after the registration is completed, other interfaces may be sent to the corresponding user terminal.

The access interface corresponding to the driver's identity includes one or more of the following interfaces: a registered interface, a check-in interface, a check-out interface, a billing start interface, and an interface indicating arrival at the passenger destination. The sign-in interface and the sign-out interface can be in the form of controls, and when a driver clicks the sign-in interface and the sign-out interface on a user side, the background can perform operation starting of the driver or operation ending record of the driver. By setting the sign-in interface and the sign-out interface, the time for the driver to start driving the vehicle to operate and the time for the driver to end operating can be recorded on the background so as to conveniently monitor the driver. By setting the interface for starting charging and the interface for indicating the arrival of the passenger destination, the events of starting a riding order and ending the riding order of the vehicle can be recorded to the background, and the cost of the journey can be calculated more accurately by combining riding order information recorded by the passenger. Through setting up the interface of registering, can make things convenient for the driver to enter the binding relation with the vehicle by oneself (for example being applicable to the scene of personnel adjustment to the operator who binds with certain vehicle), and then the driver information of completion backstage (for example perfect the mapping record in the driver's hangar).

In some embodiments, when the user identity is determined to be the driver, one or more of the sign-in interface, the sign-out interface, the charging start interface, the passenger arrival destination interface, and the like may be simultaneously transmitted to the corresponding user side, or transmitted to the user side according to a preset sequence. The sending sequence of each interface can be adjusted according to the use requirement, and the application is not limited further.

FIG. 3 is a flow chart of determining trip information for a method of ride order management according to some embodiments of the present description. As shown in fig. 3, the process 300 of determining travel information includes the steps of:

in step 310, vehicle positioning information is obtained. In particular, step 310 may be performed by the positioning module 540.

The positioning information of the vehicle may include one or more combinations of longitude and latitude of the vehicle, an area in which the vehicle is located, a geographic grid in which the vehicle is located, and the like. In some embodiments, a vehicle-mounted positioning device may be installed on the vehicle, where the vehicle-mounted positioning device may implement positioning by a global positioning system, a global navigation satellite system, a galileo positioning system, or a beidou navigation system, and the above-mentioned vehicle-mounted positioning device may implement positioning by a positioning method based on a base station, a positioning method based on a wifi access point, a positioning method based on photographing, and the like, which is not limited in this application. In other embodiments, after the driver completes the check-in, the positioning information of the user side used by the driver may be used as the positioning information of the vehicle. In some embodiments, the vehicle positioning information may be uploaded to the server in real time so that the server knows the driving track of the vehicle in time.

Step 320, determining journey information corresponding to the riding order based on the riding order information and the vehicle positioning information input by the user side. In particular, step 320 may be performed by the trip determination module 550.

The travel information corresponding to the ride order may include a departure place, a destination, a travel start time, a travel end time, a travel path, and the like of the travel. In some embodiments, determining travel information corresponding to a ride order may be: and determining a travel path of the vehicle according to the vehicle positioning information, and determining a travel path corresponding to the riding order according to the starting place and the destination in the riding order information and the travel path of the vehicle.

Optionally, step 330 may further include determining a trip cost corresponding to the order based on the trip information. In particular, step 330 may be performed by billing module 560.

In some embodiments, the billing rules may be stored in advance in a database in the background, and when the trip determination module 550 determines the trip information corresponding to the riding order, the billing module 560 may calculate the trip cost based on the billing rules and the trip information. When the interface for payment of the travel cost is clicked on the user side, the travel cost calculated by the billing module 560 may be displayed, and the user side may further pay according to the displayed travel cost.

In some embodiments, the billing module 560 may begin calculating the trip cost at the end of the trip (e.g., the driver clicks on an interface on his user's side indicating arrival at the passenger's destination). In other embodiments, billing module 560 may calculate travel costs in real-time during a journey based on the journey that has been traveled, so that the passenger can learn about the current travel costs in real-time.

FIG. 4 is a flow chart of a method of ride order management pushing personalized recommended content to a user according to some embodiments of the present description. As shown in fig. 4, a process 400 for pushing personalized recommended content to a user includes the steps of:

Step 410, obtaining user attribute information according to the user side information, wherein the user attribute information at least reflects the historical behavior characteristics of the user. In particular, step 410 may be performed by attribute determination module 570.

In some embodiments, the ride order management system may store user attribute information associated with the user-side information, which may further include user portraits (e.g., user personality preferences) or historical behavioral characteristics of the user. The user attribute information may be determined based on user operational behavior (e.g., evaluation, purchase of services, etc.) in the ride order management system or historical trip order information. The historical behavioral characteristics of the user may include a plurality of dimensions, for example, the historical behavioral characteristics may include one or more combinations of locations frequented by the user (e.g., the home or company of the passenger), specific behaviors of the user at specific times (e.g., the driver's behavior to refuel at specific gas stations at specific times of the day), business areas frequented by the user, and the like.

Step 420, according to the user attribute information, personalized recommended content is pushed to the user through the access interface. In particular, step 420 may be performed by the push module 580.

The personalized recommended content may be a functional interface, link, or interface, etc., which may each contain specific content. For example, the user's attribute information indicates that the driver is 18 pm every day: about 00a, to refuel, and then sign out to shift. The push module 580 may be at 17 pm every day: 30 to push the gas station near the current position to the user side used by the driver, or to push the path planning from the current position of the driver to the gas station frequently visited by the driver to the user side used by the driver, etc. As another example, the attribute information of the user indicates that the driver is going to the restaurant at 12:00-13:00 noon each day, and the push module 580 may push the restaurant near the current location of the driver to the user end used by the driver at 12:00 noon each day. Also for example, if the attribute information of the user indicates that the passenger frequently goes to a mall, the pushing module 580 may push a preferential advertisement of the mall to the user side used by the passenger.

FIG. 5 is a block diagram of a system for ride order management according to some embodiments of the present description. As shown in fig. 5, the system 500 for ride order management may include a receiving module 510, an identity determination module 520, a transmitting module 530, a positioning module 540, a journey determination module 550, a billing module 560, an attribute determination module 570, and a pushing module 580.

The receiving module 510 may be configured to receive an access request initiated by a user terminal by scanning an access code corresponding to a vehicle; the access code uniquely corresponds to the vehicle and contains the vehicle information, and the access request comprises user side information and vehicle information. The vehicle information includes at least a vehicle identification. The vehicle information may also include driver information, operator information to which the vehicle belongs, and/or vehicle operation city information. The user terminal information at least comprises user terminal account information. The user side information also comprises time information of the user side scanning access codes and/or position information of the user side.

The identity determination module 520 may be configured to determine a user identity of the user based on the user information and the vehicle information. The identity determining module 520 is further configured to search in a driver's library, and if a mapping record of the user side information and the vehicle information is searched, determine the user identity as a driver, otherwise determine the user identity as a passenger; the driver library comprises a plurality of mapping records of user side information and vehicle information.

The sending module 530 may be configured to send an access interface matched with the user identity to the user side, so that the user side enters the riding order information related to the user side through the access interface. The access interfaces that match the user identity include an access interface corresponding to the passenger identity and an access interface corresponding to the driver identity. Wherein the access interface corresponding to the passenger identity comprises a combination of one or more of the following interfaces: the system comprises a registered interface, an interface for inputting riding order information, an interface for checking vehicle information, an interface for checking journey information, an interface for paying journey fees, an interface for evaluating, an interface for alarming, an interface for contacting customer service and an interface for checking advertisements; the access interface corresponding to the driver's identity includes one or more of the following interfaces: registered interfaces, check-in interfaces, check-out interfaces, start billing interfaces, and arrival at the passenger destination interfaces.

The location module 540 may be used to obtain location information of a vehicle.

The trip determination module 550 may be configured to determine trip information corresponding to the riding order based on riding order information entered by the user side and vehicle positioning information.

The billing module 560 may be configured to determine a trip cost corresponding to the ride order based on the trip information.

The attribute determining module 570 may be configured to obtain user attribute information according to user side information, where the user attribute information at least reflects a historical behavior feature of a user.

The pushing module 580 may be configured to push personalized recommended content to the user through the access interface according to the user attribute information.

Possible benefits of embodiments of the present description include, but are not limited to: (1) After the user side initiates an access request by scanning an access code corresponding to the vehicle, the riding order management system can judge the user identity of the user side and acquire riding order information input by the user side, so that an off-line riding order is recorded on line, passengers can conveniently trace the off-line riding order, and monitoring of the off-line riding order is facilitated; (2) The access code is used as a contact for converting an off-line riding order into on-line recording, so that the management of the off-line riding order is simply and efficiently realized; (3) Based on the user identity of the user terminal as a driver or a passenger, different access interfaces are sent to the corresponding user terminal, so that the driver and the passenger can use various online functions, and the user experience is improved; (4) The riding safety of passengers of the off-line riding order is effectively ensured; (5) the travel cost can be calculated more accurately; (6) Personalized recommended content can be pushed to the user based on the historical behavior characteristics of the user, and user experience is improved. It should be noted that, the advantages that may be generated by different embodiments may be different, and in different embodiments, the advantages that may be generated may be any one or a combination of several of the above, or any other possible advantages that may be obtained.

The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

While the basic concepts have been described above, it will be apparent to those skilled in the art that the foregoing detailed disclosure is by way of example only and is not intended to be limiting. Although not explicitly described herein, various modifications, improvements, and adaptations to the present disclosure may occur to one skilled in the art. Such modifications, improvements, and modifications are intended to be suggested within this specification, and therefore, such modifications, improvements, and modifications are intended to be included within the spirit and scope of the exemplary embodiments of the present invention.

Meanwhile, the specification uses specific words to describe the embodiments of the specification. Reference to "one embodiment," "an embodiment," and/or "some embodiments" means that a particular feature, structure, or characteristic is associated with at least one embodiment of the present description. Thus, it should be emphasized and should be appreciated that two or more references to "an embodiment" or "one embodiment" or "an alternative embodiment" in various positions in this specification are not necessarily referring to the same embodiment. Furthermore, certain features, structures, or characteristics of one or more embodiments of the present description may be combined as suitable.

Furthermore, those skilled in the art will appreciate that the various aspects of the specification can be illustrated and described in terms of several patentable categories or circumstances, including any novel and useful procedures, machines, products, or materials, or any novel and useful modifications thereof. Accordingly, aspects of the present description may be performed entirely by hardware, entirely by software (including firmware, resident software, micro-code, etc.), or by a combination of hardware and software. The above hardware or software may be referred to as a "data block," module, "" engine, "" unit, "" component, "or" system. Furthermore, aspects of the specification may take the form of a computer product, comprising computer-readable program code, embodied in one or more computer-readable media.

The computer storage medium may contain a propagated data signal with the computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take on a variety of forms, including electro-magnetic, optical, etc., or any suitable combination thereof. A computer storage medium may be any computer readable medium that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, or device. Program code located on a computer storage medium may be propagated through any suitable medium, including radio, cable, fiber optic cable, RF, or the like, or a combination of any of the foregoing.

Computer program code necessary for operation of portions of the present description may be written in any one or more programming languages, including an object oriented programming language such as Java, scala, smalltalk, eiffel, JADE, emerald, C ++, c#, vb net, python and the like, a conventional programming language such as C language, visualBasic, fortran2003, perl, COBOL2002, PHP, ABAP, dynamic programming languages such as Python, ruby and Groovy, or other programming languages and the like. The program code may execute entirely on the user's computer or 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. In the latter scenario, the remote computer may be connected to the user's computer through any form of network, such as 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), or the use of services such as software as a service (SaaS) in a cloud computing environment.

Furthermore, the order in which the specification processes elements and sequences, the use of numerical letters, or other designations are used is not intended to limit the order in which the specification flows and methods are performed unless explicitly recited in the claims. While certain presently useful inventive embodiments have been discussed in the foregoing disclosure, by way of various examples, it is to be understood that such details are merely illustrative and that the appended claims are not limited to the disclosed embodiments, but, on the contrary, are intended to cover all modifications and equivalent arrangements included within the spirit and scope of the embodiments of the present disclosure. For example, while the system components described above may be implemented by hardware devices, they may also be implemented solely by software solutions, such as installing the described system on an existing server or mobile device.

Likewise, it should be noted that in order to simplify the presentation disclosed in this specification and thereby aid in understanding one or more inventive embodiments, various features are sometimes grouped together in a single embodiment, figure, or description thereof. This method of disclosure does not imply that the subject matter of the present description requires more features than are set forth in the claims. Indeed, less than all of the features of a single embodiment disclosed above.

Finally, it should be understood that the embodiments in this specification are merely illustrative of the principles of the embodiments in this specification. Other variations are possible within the scope of this description. Thus, by way of example, and not limitation, alternative configurations of embodiments of the present specification may be considered as consistent with the teachings of the present specification. Accordingly, the embodiments of the present specification are not limited to only the embodiments explicitly described and depicted in the present specification.

Claims

1. A method of ride order management, comprising:

Receiving an access request initiated by a user terminal through scanning an access code corresponding to a vehicle; the access code uniquely corresponds to a vehicle and comprises vehicle information of the vehicle, the access request comprises user side information and the vehicle information, the vehicle information at least comprises a vehicle identifier, and the user side information at least comprises user side account information;

Searching in a driver library, if the mapping record of the user side information and the vehicle information is searched, determining the user identity of the user side as a driver, otherwise, determining the user identity as a passenger; the driver library comprises a plurality of mapping records of user side information and vehicle information;

Transmitting an access interface matched with the user identity to the user side so that the user side can input riding order information related to the user side through the access interface, wherein the access interface matched with the user identity comprises an access interface corresponding to the passenger identity and an access interface corresponding to the driver identity; wherein,

The access interface corresponding to the passenger identity comprises a combination of one or more of the following interfaces: the system comprises a registered interface, an interface for inputting riding order information, an interface for checking the vehicle information, an interface for checking journey information, an interface for paying journey fees, an interface for evaluating, an interface for alarming, an interface for contacting customer service and an interface for checking advertisements;

the access interface corresponding to the driver identity comprises one or more of the following interfaces: a registered interface, a check-in interface, a check-out interface, a billing start interface, and an interface indicating arrival at the passenger destination.

2. The method of claim 1, wherein the vehicle information further comprises driver information, operator information to which the vehicle belongs, and/or vehicle city information.

3. The method of claim 1, wherein the client information further comprises time information for the client to scan the access code and/or location information for the client.

4. The method of claim 1, wherein the method further comprises:

acquiring vehicle positioning information;

And determining the journey information corresponding to the riding order based on the riding order information and the vehicle positioning information which are input by the user side.

5. The method of claim 4, wherein the method further comprises:

and determining the journey cost corresponding to the riding order based on the journey information.

6. The method as recited in claim 1, further comprising:

Acquiring user attribute information according to the user side information, wherein the user attribute information at least reflects the historical behavior characteristics of a user;

and pushing personalized recommended content to the user through the access interface according to the user attribute information.

7. A system for ride order management, comprising:

The receiving module is used for receiving an access request initiated by a user side through scanning an access code corresponding to the vehicle; the access code uniquely corresponds to a vehicle and comprises vehicle information of the vehicle, the access request comprises user side information and the vehicle information, the vehicle information at least comprises a vehicle identifier, and the user side information at least comprises user side account information;

The identity determining module is used for searching in a driver library, if the mapping record of the user side information and the vehicle information is searched, determining the user identity of the user side as a driver, otherwise, determining the user identity as a passenger; the driver library comprises a plurality of mapping records of user side information and vehicle information;

The sending module is used for sending an access interface matched with the user identity to the user side so that the user side can input riding order information related to the user side through the access interface, and the access interface matched with the user identity comprises an access interface corresponding to the passenger identity and an access interface corresponding to the driver identity; wherein,

8. The system of claim 7, wherein the vehicle information further comprises driver information, operator information to which the vehicle belongs, and/or vehicle city information.

9. The system of claim 7, wherein the client information further comprises time information for the client to scan the access code and/or location information for the client.

10. The system as recited in claim 7, further comprising:

the positioning module is used for acquiring positioning information of the vehicle;

And the journey determining module is used for determining journey information corresponding to the riding order based on the riding order information and the vehicle positioning information which are input by the user side.

11. The system of claim 10, further comprising a billing module for determining a trip cost corresponding to the ride order based on the trip information.

12. The system as recited in claim 7, further comprising:

the attribute determining module is used for acquiring user attribute information according to the user side information, wherein the user attribute information at least reflects the historical behavior characteristics of a user;

And the pushing module is used for pushing personalized recommended content to the user through the access interface according to the user attribute information.

13. A ride order management device, the device comprising a processor and a memory; the memory is configured to store instructions, wherein the apparatus implements operations corresponding to the method of any one of claims 1 to 6 when the instructions are executed by the processor.

14. A computer readable storage medium storing computer instructions which, when read by a computer executing instructions in the storage medium, perform the method of any one of claims 1 to 6.