CN111144603A

CN111144603A - Service information pushing method and device, electronic equipment and storage medium

Info

Publication number: CN111144603A
Application number: CN201811303621.1A
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: 2018-11-02
Filing date: 2018-11-02
Publication date: 2020-05-12

Abstract

The application provides a service information pushing method and device, electronic equipment and a storage medium, and relates to the field of network appointment. The service information pushing method includes the steps that firstly, travel address information selected by a service request end through a list sending page is obtained; the trip address information comprises a trip starting point; and finally, sending the updated page information of the order-issuing page to the service request end, wherein the updated page information of the order-issuing page carries the waiting time for getting on the bus. Furthermore, the method provided by the application informs the service requester of the boarding waiting time before the service requester places the travel order, so that the service requester can accurately judge whether the service requester needs to place the travel order according to the travel starting point, and the accuracy of placing the travel order is improved to a certain extent.

Description

Service information pushing method and device, electronic equipment and storage medium

Technical Field

The application relates to the field of network appointment, in particular to a service information pushing method and device, electronic equipment and a storage medium.

Background

In recent years, with the prosperity of internet technology, some emerging industries based on internet technology, such as internet appointment carts, appear.

The occurrence of network taxi appointment brings great convenience to a service requester and a service provider, the service requester can place an order before going out to reserve the travel time and the travel place in advance, so that a large amount of time is spent on waiting for a taxi at the roadside when going out; the taxi service provider can select the service requester to be transported according to the destination expected by the service requester, and then both the service requester and the service provider can better arrange own travel.

Disclosure of Invention

The application aims to provide a service information pushing method and device, electronic equipment and a storage medium.

In some embodiments, a service information pushing method includes:

acquiring travel address information selected by a service request end through a list sending page; the trip address information comprises a trip starting point;

determining boarding waiting time of a service request end according to a trip starting point;

and sending the updated page information of the invoice page to the service request terminal, wherein the updated page information of the invoice page carries the boarding waiting time.

In some embodiments, determining the boarding waiting time of the service requester according to the trip starting point includes:

determining current service capability information matched with the trip starting point, and determining boarding waiting time of a service request end according to the current service capability information;

in some embodiments, the current service capability information includes at least one of:

the number of service request terminals competing for queuing currently; the service request end competing for queuing at present is the service request end which selects a place with the distance from the travel starting point within a set distance range as the travel starting point;

the number of service providers finishing the travel order at a place within a set distance range from the travel starting point within a preset time;

the number of service providers which are in an idle state at the place with the distance from the travel starting point within the set distance range at present.

In some embodiments, the travel address information further includes a travel destination; the updated page information of the invoice page also comprises estimated arrival time; the method further comprises the following steps:

and determining the estimated arrival time according to the navigation route from the trip starting point to the trip end point and the current road condition information corresponding to the navigation route.

In some embodiments, determining the estimated arrival time according to a navigation route from a travel starting point to a travel ending point and current road condition information corresponding to the navigation route includes:

determining estimated arrival time corresponding to each vehicle type according to a navigation route from a trip starting point to a trip end point, current road condition information corresponding to the navigation route and at least one preset vehicle type;

taking the minimum value of the estimated arrival time respectively corresponding to the various vehicle types as the estimated arrival time carried in the updated page information of the issue list page; or taking the average value of the estimated arrival time corresponding to each of the multiple vehicle types as the estimated arrival time carried in the updated page information of the invoice page.

In some embodiments, the updated page information of the invoice page further includes vehicle types, and the estimated arrival time includes estimated arrival times respectively corresponding to each vehicle type; determining estimated arrival time according to a navigation route from a trip starting point to a trip end point and current road condition information corresponding to the navigation route, wherein the method comprises the following steps:

according to a navigation route from a trip starting point to a trip end point, current road condition information corresponding to the navigation route and at least one preset vehicle type, respectively corresponding estimated arrival time of each vehicle type is determined, and the respectively corresponding estimated arrival time of the specified vehicle types is used as the estimated arrival time carried in the page information of the updated invoice page.

In some embodiments, the updated page information of the invoice page further includes vehicle types associated with the service request end, and the estimated arrival times include estimated arrival times respectively corresponding to the vehicle types associated with the service request end; determining estimated arrival time according to a navigation route from a trip starting point to a trip end point and current road condition information corresponding to the navigation route, wherein the method comprises the following steps:

according to a navigation route from a trip starting point to a trip end point, current road condition information corresponding to the navigation route and vehicle types relevant to a service request end, estimated arrival time corresponding to each vehicle type relevant to the service request end is determined, and the estimated arrival time corresponding to each vehicle type relevant to the service request end is used as the estimated arrival time carried in the page information of the updated invoice page.

In some embodiments, the updated page information of the invoice page further includes an estimated taxi-taking fee; the method further comprises the following steps:

determining the estimated taxi taking cost according to the navigation distance from the trip starting point to the trip end point; or determining the estimated taxi taking cost according to the navigation distance from the trip starting point to the trip end point and the current road condition information.

In some embodiments, the updated page information of the invoice page further includes current ranking information; determining current ranking information according to the following steps:

and determining the current ranking information according to the number of the service request ends which select the places with the distance from the travel starting point within the set distance range as the travel starting point from the service request ends waiting for service currently.

In some embodiments, the page information of the pre-update invoice page and the page information of the post-update invoice page further include simultaneous call prompt information for multiple vehicle types.

In some embodiments, determining the boarding waiting time of the service request end according to the current service capability information comprises:

and obtaining the boarding waiting time of the service request terminal according to the current service capability information and a pre-trained boarding waiting time prediction model.

In some embodiments, the boarding wait time prediction model is trained according to the following steps:

obtaining historical trip data of a plurality of service request terminal samples; the historical trip data comprises boarding waiting time, the number of service request terminals competing for queuing when the service request terminal samples issue orders, the number of service providers finishing trip orders at a place which is within a set distance range from a trip starting point of a historical order within preset historical time, and the number of service providers in an idle state at a place which is within a set distance range from the trip starting point of the historical order when the service request terminal samples issue orders;

and training to obtain a boarding waiting time prediction model based on historical travel data of a plurality of service request end samples.

In some embodiments, a service information pushing apparatus includes:

the first acquisition module is used for acquiring the travel address information selected by the service request end through the issue page; the trip address information comprises a trip starting point;

the first determining module is used for determining the boarding waiting time of the service request end according to the trip starting point;

and the first sending module is used for sending the updated page information of the invoice page to the service request terminal, wherein the updated page information of the invoice page carries the boarding waiting time.

In some embodiments, the first determining module comprises:

the first determining unit is used for determining the current service capability information matched with the trip starting point and determining the boarding waiting time of the service request terminal according to the current service capability information;

In some embodiments, the travel address information further includes a travel destination; the updated page information of the invoice page also comprises estimated arrival time;

the device still includes:

and the second determining module is used for determining the estimated arrival time according to the navigation route from the trip starting point to the trip end point and the current road condition information corresponding to the navigation route.

In some embodiments, the second determining module comprises:

the second determining unit is used for determining estimated arrival time corresponding to each vehicle type according to a navigation route from the trip starting point to the trip end point, current road condition information corresponding to the navigation route and at least one preset vehicle type;

the first processing unit is used for taking the minimum value of the estimated arrival time corresponding to each of the multiple vehicle types as the estimated arrival time carried in the updated page information of the invoice page; or taking the average value of the estimated arrival time corresponding to each of the multiple vehicle types as the estimated arrival time carried in the updated page information of the invoice page.

In some embodiments, the updated page information of the invoice page further includes vehicle types, and the estimated arrival time includes estimated arrival times respectively corresponding to each vehicle type;

a second determination module comprising:

and the third determining unit is used for determining the estimated arrival time respectively corresponding to each vehicle type according to the navigation route from the trip starting point to the trip end point, the current road condition information corresponding to the navigation route and at least one preset vehicle type, and taking the estimated arrival time respectively corresponding to the specified vehicle types as the estimated arrival time carried in the page information of the updated invoice page.

In some embodiments, the updated page information of the invoice page further includes vehicle types associated with the service request end, and the estimated arrival times include estimated arrival times respectively corresponding to the vehicle types associated with the service request end;

a second determination module comprising:

and the fourth determining unit is used for determining the estimated arrival time corresponding to each vehicle type associated with the service request end according to the navigation route from the trip starting point to the trip end point, the current road condition information corresponding to the navigation route and the vehicle type associated with the service request end, and taking the estimated arrival time corresponding to each vehicle type associated with the service request end as the estimated arrival time carried in the page information of the updated invoice page.

In some embodiments, the updated page information of the invoice page further includes an estimated taxi-taking fee;

the device still includes:

the third determining module is used for determining the estimated taxi taking cost according to the navigation distance from the trip starting point to the trip end point; or determining the estimated taxi taking cost according to the navigation distance from the trip starting point to the trip end point and the current road condition information.

In some embodiments, the updated page information of the invoice page further includes current ranking information;

the device still includes:

and the fourth determining module is used for determining the current ranking information according to the number of the service request ends which select the places with the distance from the travel starting point within the set distance range as the travel starting point from the service request ends waiting for service currently.

In some embodiments, the first determining module comprises:

and the fifth determining unit is used for obtaining the getting-on waiting time of the service request terminal according to the current service capability information and the pre-trained getting-on waiting time prediction model.

In some embodiments, the apparatus further comprises:

the second acquisition module is used for acquiring historical trip data of a plurality of service request end samples; the historical trip data comprises boarding waiting time, the number of service request terminals competing for queuing when the service request terminal samples issue orders, the number of service providers finishing trip orders at a place which is within a set distance range from a trip starting point of a historical order within preset historical time, and the number of service providers in an idle state at a place which is within a set distance range from the trip starting point of the historical order when the service request terminal samples issue orders;

and the training module is used for training to obtain a getting-on waiting time prediction model based on historical travel data of a plurality of service request terminal samples.

In some embodiments, an electronic device comprises: the device comprises a processor, a storage medium and a bus, wherein the storage medium stores machine-readable instructions executable by the processor, when the electronic device runs, the processor and the storage medium are communicated through the bus, and the processor executes the machine-readable instructions to execute steps such as a service information pushing method.

In some embodiments, a computer readable storage medium has stored thereon a computer program which, when executed by a processor, performs the steps of the method as service information push.

The service information pushing method provided by the embodiment of the application comprises the steps of firstly obtaining travel address information selected by a service request end through a list page; the trip address information comprises a trip starting point; and finally, sending the updated page information of the order-issuing page to the service request end, wherein the updated page information of the order-issuing page carries the waiting time for getting on the bus. Furthermore, the service information pushing method provided by the application calculates the boarding waiting time of the service requester before the service requester places the trip order (when the service requester operates the issue page), and pushes the boarding waiting time to the service requester, so that the service requester can know how long it takes to get on if the service requester places the trip order before placing the trip order, thereby helping the service requester judge whether the service requester needs to place the trip order, and improving the condition that the service requester cancels the issued trip order to a certain extent.

In some embodiments, in addition to providing the service requester with the boarding waiting time for reference, the method provided by the present application may further include, for reference by the service requester, carrying at least one of the following information in the page information of the updated invoice page: estimating the arrival time, estimating the taxi taking cost and the current ranking information.

In some embodiments, the method provided by the application also considers specific vehicle types when calculating the waiting time for getting on the vehicle, the estimated arrival time, the estimated taxi taking cost and the current ranking information, so that the information referred to the service requester is more targeted.

In order to make the objects, features and advantages of the present application comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.

Fig. 1 shows a basic flowchart of a service information pushing method provided by an embodiment of the present application;

fig. 2 illustrates a specific embodiment of a service information pushing method in an embodiment of the present application;

fig. 3 illustrates another embodiment of a service information pushing method according to an embodiment of the present application, where the service information pushing method includes a form page;

fig. 4 is a schematic diagram illustrating a relative position relationship between a travel starting point (point a) and another point (point B, C, D, E, F) in the service information pushing method provided in the embodiment of the present application;

fig. 5 shows a block diagram of a service system in which a service information push method of some embodiments of the present application is located;

fig. 6 shows a schematic diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. The components of the embodiments of the present application, generally described and illustrated in the figures herein, can be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, presented in the accompanying drawings, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments of the application. All other embodiments, which can be derived by a person skilled in the art from the embodiments of the present application without making any creative effort, shall fall within the protection scope of the present application.

In the related art, with the rise of internet technology, many emerging industries, such as internet appointment carts, are generated. Due to the fact that the network appointment car is arranged, great convenience is brought to the traveling of the service requester and the work of the service provider.

When the network car booking service is used, firstly, a service requester operates a mobile phone to input a travel starting point (a place where a service provider receives the service requester) and a travel ending point (a destination where the service provider delivers the service requester) in an order sending page of network car booking software, and clicking an order button in the order page, the mobile phone will issue a travel order (a travel starting point and a travel ending point are usually carried in the travel order) to the service platform, then, the service platform judges whether the travel order issued by the service requester is a malicious order or not based on the travel starting point and the travel ending point, if the travel order is not a malicious order, the service platform broadcasts the travel order to a large number of service providers, so that the service provider replies to the travel order, and the service platform determines to which service provider the travel order is allocated according to the reply result of the service provider. After the travel order is assigned to the specified service provider, the service provider can carry the service requester as required in the travel order (e.g., pick up the service requester from the travel starting point and carry the service requester to the travel ending point at the specified time).

In the related art, in order to improve the service requester's perceptibility, after the service requester places a travel order to the service platform by operating a mobile phone, a boarding waiting time (the boarding waiting time refers to a time from a travel starting point to the service requester by a service provider, or a time from a current time to a travel starting point by the service provider) is calculated by a predetermined algorithm. After calculating the boarding wait time, the service platform sends the boarding wait time to the mobile phone operated by the service requester, so that the service requester knows how long the service provider is probably able to receive itself. The method for informing the service requester of the waiting time for getting on the bus improves the sensitivity of the service requester to a certain extent, so that the service requester can know how long the service requester takes to call the bus.

However, the method for prompting the service requester to wait for getting on the bus after the service requester places an order also has certain disadvantages, for example, after the service requester sees the waiting time for getting on the bus, if the waiting time for getting on the bus is considered to be not in accordance with the expectation of the service requester, the issued travel order is cancelled, and the behavior of cancelling the issued travel order affects the credit of the service requester. Meanwhile, because the information transmission has a certain hysteresis, if the service requester cancels the travel order only after the service platform allocates the travel order to the specified service provider, the service platform also needs to compensate the service provider allocated with the travel order. It can be seen that, although providing the service requester with the boarding waiting time after the service requester places the travel order can improve the service requester's perceptibility, there are certain disadvantages.

In view of the above situation, the inventor of the present application believes that the accuracy of placing a travel order by a service requester can be improved by informing the service requester of the waiting time for getting on a vehicle before the service requester places the travel order.

Further, as shown in fig. 1, the present application provides a service information pushing method, including the following steps:

s101, obtaining travel address information selected by a service request end through a list sending page; the trip address information comprises a trip starting point;

s102, determining boarding waiting time of a service request end according to a trip starting point;

and S103, sending the updated page information of the invoice page to the service request terminal, wherein the updated page information of the invoice page carries the boarding waiting time.

The issue page refers to a page where the network car-booking software in the mobile phone is located before the service requester (such as a passenger) operates the service requester (such as a mobile phone) to send a travel order to the server (the execution bodies of steps S101 to S103).

As shown in fig. 2, a specific embodiment of the invoice page of the network appointment software is shown. In fig. 2, the lower box is the trip starting point that the service requester has input, and in fig. 2, the middle box encloses a positioning pointer, and the location corresponding to the positioning pointer is the trip starting point in the map. That is, the page shown in fig. 2 is a page in which the starting point of the trip has been input, but the ending point of the trip has not been input, and the page may be regarded as a shipping page.

As shown in fig. 3, another embodiment of the invoice page of the network appointment software is shown. Fig. 3 shows an interface of the network appointment software after the service requester has input the trip start point and the trip end point into the service requester. In the interface, the lowermost button (the button marked with "call express") is a button capable of triggering the service requester to send a travel order to the server, that is, if the service requester presses the button for calling express immediately, the service requester will immediately send the travel order to the server. That is, the page shown in fig. 3, on which whether to place a travel order is to be confirmed, may also be regarded as an order issuing page.

Two embodiments of the invoice page are shown in fig. 2 and 3, but in practice, the form of the invoice page is not limited to the form shown in fig. 2 and 3.

In step S101, at least a travel starting point should be included in the travel address information selected by the service requester through the issue sheet, for example, the travel starting point may be a "lake natatorium" circled in the lower box of fig. 2. After the service requester selects the travel address information on the issue sheet page by operating the service requester, the service requester can actively or passively send the travel address information to the server.

Here, the passive sending of the travel address information to the server by the service request end may refer to: after the trip starting point is input, the service requester can click a sending button (such as a button marked with "send trip address information") on the service request terminal, so that the service request terminal can actively send the trip address information to the server;

the step of actively sending the travel address information to the server by the service request terminal may be: after the service request end detects that the service request end has input the trip start point (for example, when the service request end detects that the service request end has not modified the trip start point within the preset time, it indicates that the service request end has input the trip start point), the service request end does not need to click any button, and the service request end automatically sends the trip address information containing the trip start point to the server.

Whether the service requester actively sends the travel address information or passively sends the travel address information, after the server receives the travel starting point in the travel address information, in step S102, a boarding waiting time of the service requester, which refers to a time from the travel starting point to the service requester by a service provider (e.g., a driver) (specifically, a time value at a certain time, such as 12:57 minutes), or a time from a current time to a time when the service provider moves to the travel starting point (specifically, a remaining time, such as 3 minutes, after the service provider reaches the travel starting point), may be determined according to the travel starting point. Specifically, in step S102, when the boarding waiting time is determined, the service requester has not issued a travel order, and at this time, since it is not determined which service provider carries the service requester, the boarding waiting time can be calculated only by estimation.

There are many ways to estimate the waiting time for getting on a vehicle, and only three are listed below:

firstly, estimating which service provider has the highest probability of receiving a travel order if a service requester places the travel order at a current travel starting point, then calculating the time required by a target service provider to reach the travel starting point from the current position of the target service provider according to the current position of the service provider (the target service provider) with the highest probability of receiving the travel order and the position of the travel starting point, and taking the time as the boarding waiting time;

secondly, the time (target time) from the current position to the travel starting point of each service provider among the service providers close to the travel starting point is respectively estimated, and the boarding waiting time is calculated by adopting a weighting and averaging mode according to the plurality of target times.

These two ways of estimating the boarding wait time are merely exemplary and do not represent only two of the intended scope of protection of the solution provided by the present application.

And thirdly, obtaining the boarding waiting time of the service request terminal according to the current service capability information and a pre-trained boarding waiting time prediction model.

Different from the two ways for calculating the boarding waiting time, the third way for calculating the boarding waiting time uses a trained boarding waiting time prediction model for prediction, which mainly considers that the factors influencing the boarding waiting time are more, and if the factors are simply analyzed by people, the factors are more difficult, so that the method provided by the application introduces a way for predicting by using the model.

Furthermore, first, the factors that influence the boarding waiting time will be described, and generally, the factors that can directly influence the boarding waiting time are mainly the current service capability, which may be composed of the following elements:

the first element forming the current service capability, the number of service request terminals competing and queuing currently;

the second kind of element forming the current service capability, the number of service providers completing the travel order in the place with the distance from the travel starting point within the set distance range within the preset time;

the third type is an element constituting the current service capability, which is the number of service providers currently in an idle state at a point within a set distance range from the travel starting point.

The service requester currently competing for queuing is the service requester that selects a point within the set distance range from the trip start point in step S101 as the trip start point. Further, the service requester in competition queuing is specifically a service requester that is in a process of calling a network to order a car (a process in which a travel order has been placed to a server, but the travel order has not been assigned to a certain service provider), and takes a place that is close to the travel place in step S101 according to a preset requirement (for example, sufficiently close to the travel place) as a travel starting point (a travel starting point in the placed travel order). In other words, it is understood that the service requester currently competing for queuing, that is, the service requester used by the other service requester calling the network car reservation when step S101 or S102 is executed, and the travel start point selected by the other service requester is sufficiently close to the travel start point in operation S101.

As shown in fig. 4, a schematic diagram of the relative positional relationship between the travel starting point (point a) and the other point (point B, C, D, E, F) in step S101 is shown. As can be seen from the figure, points within the predetermined range of travel starting point (inside the circle of fig. 4) share points B, C and D, and points outside the predetermined range of travel starting point (outside the circle of fig. 4) share points E and F. Furthermore, if another service requester (other than the service requester in step S101) is currently in the competitive queuing and takes one of the points B, C and D as its travel starting point, then the other service requester should be the service requester currently in the competitive queuing; correspondingly, if another service request end (other than the service request end in step S101) currently takes one of points E and F as its travel starting point, the other service request end should not be taken as the service request end currently competing for queuing. In fig. 4, a point within a circle is set as a point within a set distance range from the travel starting point, and in specific execution, a point within a region where a regular pattern such as a square is located may be set as a point within a set distance range from the travel starting point, or a point within a region where another irregular pattern is located may be set as a point within a set distance range from the travel starting point.

The present herein is referred to as being in the process of being performed by the present method. Specifically, it may be during the execution of step S102.

The number of service providers who complete a travel order at a point within a set distance range from a travel starting point within a predetermined time is a number of terminals used by a service provider, the service providers correspond to service requesters, the service requesters are terminals expected to be used by service requesters who receive network car booking services, and the service providers are terminals expected to be used by service requesters who provide network car booking services. The number of service providers that complete the travel order refers to the number of service providers that carry the service requester to the destination. In other words, the number is: the number of service providers that will complete the delivery service requester task at a position closer to the travel start point in step S101 is predetermined.

Further, the service provider that completes the travel order at a point within the set distance range from the travel starting point within the predetermined time may be a terminal used by the service provider that completes the task of the delivery service requester at a position closer to the travel starting point in step S101 (within the predetermined time).

The number of service providers currently in an idle state at a location within a set distance from the travel starting point is the number of service providers currently in an idle state or not in a state of completing a travel order. More specifically, the number of service providers currently in an idle state at a location within a set distance range from the starting point of travel shall mean the number of service providers that are not in a state of completing a travel order, as well as being in an idle state (the service provider can report to the server whether the service provider is in an idle state or not by reporting to the server whether the service provider is in a delivery service requester or not). Since the travel order is distributed to the service provider by the server, the server necessarily knows whether the service provider is distributed with the travel order, and after the travel order is completed, the service provider or the service requester sends a feedback message to the server to indicate whether the distributed travel order is completed.

Compared with the above three elements constituting the current service capability, the first element constituting the current service capability reflects the situation of other service requesters, that is, if there is a conflict between the other service requesters and the service requester in step S101 when calling a network car reservation (the start point of travel selected by the other service requester is too close to the start point of travel in step S101), the influence of the other network car reservation on the waiting time for getting on the car should be considered, because the other network car reservation has already made a travel order, and therefore, the server should assign the service provider to the travel orders issued by the other service requesters preferentially when assigning the travel orders.

The second element that constitutes the current service capability reflects the situation of the service provider that is about to complete the travel order. That is, if other service providers are about to complete a travel order (delivery completed service requester) at a position closer to the travel starting point in step S101, these service providers may also take the new travel order, and therefore, these service providers should also be considered.

The third element that constitutes the current service capability reflects the situation where there is no service provider currently carrying a service requester. That is, if the service provider is not assigned a travel order (more precisely, the service provider is not assigned a travel order and does not carry a service requester other than a travel order, such as a service requester for a roadside taxi); or if travel orders have been allocated but completed, these service providers should also be considered.

The three elements constituting the current service capability may be used to calculate the boarding wait time by using only one of the three elements, or may be used to calculate the boarding wait time by using any two of the three elements, but it is preferable to calculate the boarding wait time by using the three elements simultaneously.

That is, step S102 may be performed as follows:

the current service capability information includes at least one of:

the number of service request terminals competing for queuing currently;

Further, after the boarding waiting time is determined, the boarding waiting time may be transmitted to the service requester for reference in step S103.

Specifically, the form of sending the boarding waiting time to the service request end by the server is to carry the boarding waiting time in the page information of the issue sheet for sending, and then, after the service request end receives the updated page information of the issue sheet, the boarding waiting time carried in the updated page information of the issue sheet can be displayed on the current page of the service request end. As shown in fig. 2, after the travel start point is input by the service requester, the service requester displays the boarding waiting time, and in the drawing, "boarding after 3 minutes" is the boarding waiting time. Of course, the specific representation of the boarding waiting time is not limited to this, but may also be used to describe that the vehicle can be picked up extremely, for example, the boarding waiting time may be "will be picked up at 15 o 'clock and 5 o' clock".

In connection with the above description, in order to calculate the boarding waiting time more accurately, the boarding waiting time prediction model may be introduced to perform accurate calculation, and accordingly, the boarding waiting time prediction model may be trained according to the following steps:

The historical travel data refers to the real data that has already occurred, and the travel waiting time prediction model is trained by using the real data, so that the travel waiting time prediction model can accurately identify the corresponding relationship between the travel waiting time and other data (the number of service request terminals competing for queuing when the service request terminal samples are issued, the number of service providers completing the travel order at a place within a set distance range from the travel starting point of the historical order within a predetermined historical time, and the number of service providers idle at a place within a set distance range from the travel starting point of the historical order when the service request terminal samples are issued), and further, when step S102 is executed, the corresponding travel waiting time can be determined according to the obtained current service capability information.

The boarding wait time prediction model used herein may be selected from common classifiers such as logistic Regression (logistic Regression) model, Support Vector Machine (Support Vector Machine) model, Decision Tree (Decision Tree) model, and Gradient Boosting Decision Tree (Gradient Boosting Decision Tree) model. In addition to this, deep machine learning (neural network) models may also be used as an option. If a neural network model is used, before data is input into the model, normalization processing needs to be performed on the data, and a proper initialization scheme is adopted to ensure that the model can be converged to a better state.

The service information pushing method provided by the application calculates the boarding waiting time of the service requester before the service requester places the trip order (when the service requester operates the order issuing page), and pushes the boarding waiting time to the service requester, so that the service requester can know how long to get on if the service requester places the trip order before placing the trip order, and the service requester can help the service requester judge whether the service requester places the trip order, so that the service requester informs the service requester of the boarding waiting time after the service requester places the trip order to a certain extent, and the service requester cancels the issued trip order.

In the above, the service requester is provided with the boarding waiting time before going down to a trip, so that the service requester can judge whether the service requester needs to place a trip order according to the boarding waiting time.

Specifically, in the method provided by the application, the travel address information may further include a travel destination, and the updated page information of the invoice page may further include estimated arrival time;

furthermore, the service information pushing method provided by the present application further includes:

step 201, generating a navigation route from a travel starting point to a travel end point according to the travel starting point and the travel end point;

step 202, determining estimated arrival time according to a navigation route from a trip starting point to a trip end point and current road condition information corresponding to the navigation route.

After the navigation route is determined, the length of the navigation route can be determined, meanwhile, the moving speed is determined by the road condition information (if the road condition is congested, the moving speed is low, and if the road condition is unobstructed, the moving speed is high), and further, after the length of the navigation route and the moving speed are determined, the estimated arrival time from the trip starting point to the trip end point can be determined. It should be noted that, in general, the waiting time for getting on the vehicle needs to be considered when calculating the estimated arrival time, because only after getting on the vehicle, the calculation of the time spent by the delivery service requester can be started, that is, the estimated arrival time should be divided into two parts, namely the waiting time for getting on the vehicle and the time of the delivery service requester, but the waiting time for getting on the vehicle has a separate calculation method, so the content of calculating the estimated arrival time in the present application refers to the time spent by the delivery service requester.

In a specific implementation, the route from the starting point of the trip to the ending point of the trip may not be the only route, and the scheme for calculating the estimated arrival time may be divided into the following two specific implementation manners:

in a first embodiment of calculating the estimated time of arrival,

step 201 comprises:

step 2011, determining a plurality of navigation routes from the travel starting point to the travel destination according to the travel destination, the travel starting point and the road connection condition (which roads are connected is reflected);

step 202, comprising:

step 2021, determining travel time corresponding to each navigation route according to the determined navigation route and the current road condition information corresponding to the navigation route;

step 2022, the travel time with the minimum value in the travel times corresponding to the multiple navigation routes is taken as the estimated arrival time.

A second specific way of calculating the transit time using the navigation route,

step 201 comprises:

step 2012, determining a plurality of navigation routes from the travel starting point to the travel destination according to the travel destination, the travel starting point and the road communication condition (which reflects which roads are connected);

step 2023, determining travel time corresponding to each navigation route according to the determined navigation route and the current road condition information corresponding to the navigation route;

step 2024, calculating the estimated arrival time according to the travel time corresponding to each navigation route by using a weighted averaging method.

In the two steps, the road connection condition can reflect whether different roads are connected or not and the connection positions. Generally, since there are many roads in a city, many navigation routes from a travel end point to a travel start point can be determined.

Step 2021 and step 2023 are performed in the same manner. The two steps are both aimed at calculating the travel time of each navigation route, and when calculating, the moving speed is firstly determined, wherein the moving speed is influenced by the current road condition information, if the road is congested, the moving speed is lower, otherwise, if the road is smooth, the moving speed is higher. Further, in step 2022, the travel time with the shortest time may be used as the estimated arrival time. In addition to using the travel time with the shortest time as the transit time, in step 2024, a weighted average of the travel times is calculated according to the travel time corresponding to each navigation route by using a weighted averaging method, and the weighted average is used as the estimated arrival time.

As mentioned above, the current traffic information determines the moving speed, or the current traffic information can affect the moving speed to some extent, and specifically, the traffic information may include any one or more of the following information:

the current road congestion information, the current road traffic accident information, the current weather condition information and the current road closing information.

The congestion information of the current road is usually determined according to the running speed of the vehicle on the specified road, and the mode of acquiring the running speed of the vehicle on the specified road can be determined through position information uploaded by the driver terminal in real time. The congestion is serious when the running speed of the vehicle is slow, and the congestion is light when the running speed of the vehicle is fast.

The traffic accident information of the current road reflects the situation of the traffic accident occupying the lane. For example, the accident situation of two-vehicle collision occurs on the main road or loop, or other accidents that can cause the vehicle to stop only on the main road (for example, the vehicle collides with the road bed unilaterally, which causes the accident of occupying the traffic lane).

The current weather condition information reflects specific weather conditions such as rain, snow, hail, strong wind, fog, etc. It is expected that different weather conditions will have different effects on traffic. For example, when raining, snowing and heavy fog occur, vehicles can run slowly to ensure safety, and thus road congestion is increased. Different from the congestion information of the current road, the congestion information of the current road reflects the actual congestion condition, and the current weather condition information reflects a tendency that the weather condition affects the congestion condition. For example, if the congestion information of the current road reflects that the current road is medium congestion, the approximate probability is also medium congestion ten minutes later, if the other information is not changed. However, if the congestion information of the current road reflects that the current road is in medium congestion and snows, the current road is probably heavily congested ten minutes later without changing other information. That is, the impact of weather conditions on congestion generally does not occur immediately, but rather occurs with a delay. Therefore, the condition of future congestion can be more accurately judged according to the weather condition, and a positive effect is generated for calculating the estimated arrival time.

The current road closing information reflects the road communication condition, namely which road can pass and which road can not pass. When some roads cannot pass, the pressure of traveling on the road is transferred to other roads nearby, so that the pressure of traffic on other roads nearby is increased, or other roads nearby become more congested. Similar to the influence of the weather condition on congestion, the current road blocking information does not directly influence the current road congestion condition, but can more accurately judge the future congestion condition, so that a positive effect is generated for calculating the estimated arrival time.

The 4 pieces of information (congestion information of a current road, traffic accident information of the current road, current weather condition information, and current traffic information) respectively reflect factors that can affect a moving speed from different angles, and when the information is used specifically, the information about the current traffic condition may include one of the 4 pieces of information, the information about the current traffic condition may include only two of the 4 pieces of information, or the information about the current traffic condition may include only three of the 4 pieces of information, and of course, the information about the current traffic condition may include the four pieces of information at the same time.

By simultaneously providing the estimated arrival time and the boarding waiting time for the service requester, the service requester can better judge whether the service requester needs to generate a trip order by the currently input trip starting point and trip ending point, and places the trip order to the server. For example, if the service requester considers that the estimated arrival time is too late, the service requester may choose to give up the current operation (not placing the travel order), or change the travel address information (such as the travel start point or the travel end point), and then decide whether to place the travel order according to the changed travel address information.

Besides providing the estimated arrival time and the boarding waiting time for the service requester, the estimated taxi taking cost can be carried in the updated page information of the invoice page so as to be referred to the service requester. That is, in the service information pushing method provided by the application, the updated page information of the invoice page further includes the estimated taxi taking cost;

specifically, the prepaid car fare can be calculated in the following two ways:

in a first way of calculating and estimating taxi-taking fees,

calculating the taxi taking cost only according to the distance of the navigation route (namely the navigation distance), namely, the method provided by the application further comprises the following steps:

determining the estimated taxi taking cost according to the navigation distance from the trip starting point to the trip end point;

it is obvious that the first way of calculating the estimated taxi-taking cost only takes into account the influence of the navigation distance on the taxi-taking cost, and generally, the longer the navigation distance is, the higher the estimated taxi-taking cost is. The relationship between the navigation distance and the taxi-taking fee may be positively correlated.

Besides the estimated taxi taking cost is determined according to the navigation distance, the taxi taking cost can be further determined according to the road condition information, namely, a second mode of calculating and estimating the taxi taking cost is adopted.

A second way to calculate and estimate taxi-taking fees,

meanwhile, the taxi taking cost is calculated according to the distance of the navigation route (namely the navigation distance) and the current road condition information, namely, the method provided by the application further comprises the following steps:

and determining the estimated taxi taking cost according to the navigation distance from the trip starting point to the trip end point and the current road condition information.

The road condition information mainly reflects the congestion condition of the road, and the more congested the road, the more time the vehicle is congested on the road, and further, the time that the vehicle is congested on the road (although the vehicle does not move a lot) should also be converted into the cost, that is, the road congestion condition reflected by the current road condition information should also be positively correlated with the estimated vehicle cost.

Further, in addition to providing the estimated arrival time and the boarding waiting time for the service requester, the current ranking information (which indicates how many travel orders of other service requesters are allocated to the service provider in preference to the own travel order if the service requester places the travel order at present) may be carried in the page information of the updated issue page to refer to the service requester.

Specifically, the current ranking information may be determined according to the following steps:

The service requester currently waiting for service refers to a service requester which has already placed a travel order to the server, but the placed travel order is not yet assigned to a specific service provider. These travel orders have been placed, but the placed travel orders have not been allocated to the service requesters of the specific service provider, and the number of service requesters whose travel starting point carried by the travel order is closer to the travel starting point in step S101 is the number of service requesters whose travel starting point is a point within the set distance range from the travel starting point.

This amount reflects that if the service requester immediately places a travel order using the start of travel in step S101, the placed travel order will be broadcast to the service provider in the next order. For example, the current ranking information shows that there are 3 service requesters that issue target trip orders (the target trip order is a trip order that has been issued to the server but is not allocated to the service provider, and the distance between the trip start point in the target trip order and the trip start point in step S101 is less than a predetermined value), then the current ranking information should show that "three service requesters are already queued", or "the current number of queued people is 3". Further, if the service requester immediately places the trip order including the trip start point in step S101 to the server, the rank of the service requester should be 4.

In a specific implementation, only after all the previous 3 target travel orders are broadcast or allocated to the service provider, the travel order including the travel starting point in step S101 can be broadcast or allocated.

By carrying the current ranking information in the updated page information of the issue sheet, the service requester can request what the current waiting time for getting on the bus is longer (whether the number of people in queue is too large) and further help the service requester to make a decision whether to use the trip starting point in step S101 to place a trip order.

In the concrete implementation, when considering that the service requester uses the network car reservation, the vehicle types that can be selected are many, for example, the vehicle types include: car sharing vehicles, special cars, express cars, taxis, tailgating vehicles and the like. Different vehicle types have different effects on calculating the boarding wait time. For example, under the condition that the environmental conditions corresponding to each vehicle type are the same, the boarding waiting time of the car pool is slower than that of the special car, and mainly the car pool usually needs to receive a certain number of other service requesters before receiving the users of the service requesters; the special car is directly connected with the user of the service request end. For another example, the waiting time for getting on a taxi is relatively slow compared to the waiting time for getting on a express bus, and mainly, the taxi may carry a service requester for roadside hire, and the taxi service provider is likely to take a travel order after the service requester for roadside hire is not carried, at this time, the taxi service provider can only carry the service requester for roadside hire to a destination before receiving the service requester for a travel order, and the express bus usually does not have such problems. When the environmental conditions corresponding to each vehicle type are different (in most cases, the environmental conditions corresponding to each vehicle type are different, for example, in the area a, the number of express buses is much larger than the number of special buses, and the waiting time for getting on a bus in the area a to call an express bus is shorter than the waiting time for getting on a bus to call a special bus), the waiting time for getting on a bus corresponding to each vehicle type is usually different.

It follows that the times at which different types of vehicles receive a service requester may differ. Further, in order to improve the usability of the service requester, more specific calculation may be performed in consideration of the vehicle type when calculating the estimated arrival time.

Furthermore, the above scheme for calculating the boarding waiting time can be divided into four specific implementation manners as follows:

a first specific way of calculating the boarding waiting time,

determining current service capability information matched with a trip starting point, determining boarding waiting time of a service request end according to the current service capability information, and executing the following steps:

step 1021, determining current service capability information corresponding to at least one vehicle type matched with the trip starting point, and determining boarding waiting time corresponding to each vehicle type according to the current service capability information corresponding to at least one vehicle type;

step 1022, taking the minimum value of the boarding waiting time corresponding to each of the plurality of vehicle types as the boarding waiting time carried in the updated page information of the invoice page;

that is, the current service capability information may be further subdivided according to vehicle types, and the current service capability corresponding to each vehicle type may be different. For example, under the condition that other conditions are not changed, the number of taxis near the trip starting point is far larger than that of special taxis, the current service capacity corresponding to the taxi should be larger than that of the special taxi, and the boarding waiting time corresponding to the taxi should be shorter than that of the special taxi.

In step 1021, the preset vehicle type may be pre-specified by the service requester (the vehicle type sent to the server by the service requester through operating the service requester may be the preset vehicle type), or may be determined by the server according to the trip habit of the service requester (for example, when the service requester places a trip order using the service requester, some vehicle types are often selected, and these often selected vehicle types may be used as the preset vehicle types).

After the execution of step 1021 is finished, the boarding waiting time corresponding to each travel type may be formed, and may be in the form shown in table 1 below:

TABLE 1

As can be seen from table 1, the boarding waiting time for each vehicle type is different, but this does not mean that the vehicle types are different, and the boarding waiting times are different.

Then, the minimum value of the calculated boarding waiting time can be used as the boarding waiting time carried in the updated page information of the invoice page. By sending the minimum boarding waiting time to the service requester, the service requester can know how long the boarding can be performed, so that the service requester can conveniently decide whether to place a travel order.

A second specific way of calculating the boarding wait time,

step 1023, determining current service capability information corresponding to at least one vehicle type matched with the trip starting point, and determining getting-on waiting time corresponding to each vehicle type according to the current service capability information corresponding to at least one vehicle type;

step 1024, taking the average value of the boarding waiting time corresponding to each of the plurality of vehicle types as the boarding waiting time carried in the updated page information of the invoice page;

the execution manner of step 1023 is substantially the same as that of step 1021, and will not be described herein too much.

Different from the first method for calculating the boarding waiting time, in the second method for calculating the boarding waiting time, after the boarding waiting time corresponding to each vehicle type is calculated, a weighted average method is adopted, a weighted average value is calculated according to the boarding waiting time corresponding to each vehicle type, and the calculated weighted average value is used as the boarding waiting time carried in the page information of the updated invoice page. By informing the service requester of the weighted average, the service requester is enabled to have substantial knowledge of the approximate time of waiting.

A third specific way of calculating the boarding wait time,

determining current service capability information corresponding to each vehicle type matched with the trip starting point, determining boarding waiting time corresponding to each vehicle type according to the current service capability information corresponding to each vehicle type, and taking the boarding waiting time corresponding to each vehicle type of the specified type as the boarding waiting time carried in the updated page information of the invoice page.

Different from the first two ways of calculating the getting-on waiting time, the third way of calculating the getting-on waiting time is to send the getting-on waiting time respectively corresponding to the specified types of vehicles to the service requester for reference, and the service requester can know the getting-on waiting time more comprehensively by the way. In a third specific implementation manner of calculating the boarding waiting time, the boarding waiting times respectively corresponding to the specified types of vehicles may refer to the calculated boarding waiting time respectively corresponding to each type of vehicle, or may be a part of the calculated boarding waiting time respectively corresponding to each type of vehicle.

Furthermore, the updated page information of the invoice page further includes vehicle types, and the boarding waiting time includes boarding waiting time corresponding to each vehicle type.

A fourth way to calculate the boarding wait time taking into account the vehicle type:

determining current service capability information corresponding to the vehicle type associated with the service request end, determining boarding waiting time respectively corresponding to each vehicle type associated with the service request end according to the current service capability information corresponding to the vehicle type associated with the service request end, and taking the boarding waiting time respectively corresponding to each vehicle type associated with the service request end as the boarding waiting time carried in the page information of the updated invoice page.

Here, each vehicle type associated with the service requester may be pre-specified by the service requester (the service requester sends the vehicle type to the server by operating the service requester and indicates that the vehicle type is a common type of the service requester, and the server may use the vehicle type sent by the service requester as the vehicle type associated with the service requester), or may be determined by the server according to travel habits of the service requester (for example, when the service requester places a travel order using the service requester, the vehicle type/types often selected may be used as the preset vehicle type).

Furthermore, the updated page information of the service order page further includes vehicle types associated with the service request terminals, and the boarding waiting time includes boarding waiting times respectively corresponding to the vehicle types associated with the service request terminals.

In addition to determining the boarding wait time based on the vehicle type, the estimated arrival time may also be determined based on the vehicle type.

Specifically, when the estimated arrival time is calculated in consideration of the vehicle type, there may be four ways as follows:

the first way to calculate the estimated time of arrival considering the vehicle type:

step 202 may include the steps of:

step 2025, determining estimated arrival time corresponding to each vehicle type according to a navigation route from the trip starting point to the trip end point, current road condition information corresponding to the navigation route, and at least one preset vehicle type;

step 2026, taking the minimum value of the estimated arrival time corresponding to each of the plurality of vehicle types as the estimated arrival time carried in the updated page information of the invoice page;

in step 2025, the preset vehicle type may be pre-specified by the service requester (the vehicle type sent to the server by the service requester through operating the service requester may be the preset vehicle type), or may be determined by the server according to the travel habit of the service requester (for example, when the service requester places a travel order using the service requester, some vehicle types are often selected, and these often selected vehicle types may be used as the preset vehicle types).

Step 2025 may form an estimated arrival time corresponding to each travel type after the execution is finished, where the estimated arrival time may be in a form shown in table 2 below:

TABLE 2

As can be seen from table 2, the estimated arrival time corresponding to each vehicle type is different, but this does not mean that the vehicle types are different, and the corresponding estimated arrival times are different.

Then, in step 2026, the minimum value of the calculated estimated arrival time is used as the estimated arrival time carried in the page information of the updated invoice page. By sending the estimated arrival time with the minimum value to the service requester, the service requester can know how long the service can arrive most quickly, so that the service requester can conveniently decide whether to place a travel order.

The second approach to calculating the estimated time of arrival considering the vehicle type:

step 202 may include the steps of:

step 2027, determining estimated arrival time corresponding to each vehicle type according to a navigation route from the trip start point to the trip end point, current road condition information corresponding to the navigation route, and at least one preset vehicle type;

step 2028, taking the average value of the estimated arrival time corresponding to each of the plurality of vehicle types as the estimated arrival time carried in the updated page information of the invoice page.

The execution manner of step 2027 is substantially the same as that of step 2025, and will not be described herein too much.

Different from the first way of calculating the estimated arrival time, in the second way of calculating the estimated arrival time, after the estimated arrival time respectively corresponding to each vehicle type is calculated, a weighted average is calculated according to the estimated arrival time respectively corresponding to each vehicle type by adopting a weighted averaging way, and the calculated weighted average is used as the estimated arrival time carried in the page information of the updated invoice page. By informing the service requester about the weighted average, the service requester is enabled to have substantial knowledge of the approximate time of arrival.

The third way to calculate the estimated time of arrival considering the vehicle type:

step 202 may include the steps of:

Different from the first two ways of calculating the estimated arrival time, the third way of calculating the estimated arrival time is to send the estimated arrival time corresponding to the vehicle types of the specified types to the service requester for reference, so that the service requester can know the estimated arrival time more comprehensively. Specifically, in step 2029, the estimated arrival time corresponding to each of the specified vehicle types may refer to the calculated estimated arrival time corresponding to each of the vehicle types, or may be a part of the calculated estimated arrival time corresponding to each of the vehicle types.

Furthermore, the updated page information of the invoice page further includes vehicle types, and the estimated arrival time includes estimated arrival time corresponding to each vehicle type.

A fourth way to calculate the estimated time of arrival taking into account the vehicle type:

step 202 may include the steps of:

Furthermore, the updated page information of the invoice page further comprises vehicle types related to the service request end, and the estimated arrival time comprises estimated arrival times respectively corresponding to the vehicle types related to the service request end.

As shown in table 3 below, one form of pre-storing the vehicle type associated with the service request terminal in the server is shown:

TABLE 3

As can be seen from table 3, each service request terminal corresponds to at least one vehicle type, and further, when step 202 is executed, the estimated time of arrival of the specified ones having more reference value to the service request party can be determined according to the corresponding vehicle type.

Of course, the calculation of the estimated taxi hiring fee and the current ranking information may also take into account the vehicle type, in addition to the boarding wait time and the estimated arrival time.

Furthermore, in calculating the estimated taxi taking fee, if the vehicle type is considered, the method provided by the application can calculate the estimated taxi taking fee as follows:

determining the estimated taxi taking expense corresponding to the specified vehicle type according to the navigation distance from the trip starting point to the trip end point;

alternatively, the first and second electrodes may be,

and determining the estimated taxi taking cost corresponding to the specified vehicle type according to the navigation distance from the trip starting point to the trip end point and the current road condition information.

After the estimated taxi taking cost corresponding to the specified vehicle type is calculated, one or more of the calculated estimated taxi taking costs can be carried in the updated page information of the invoice page according to specific use requirements. Further, the page information carried in the updated invoice page should include the designated vehicle type and the taxi-taking fee corresponding to the vehicle type.

Specifically, the specified vehicle type may be pre-specified by the service requester (the service requester sends the vehicle type to the server by operating the service requester, and the server may use the vehicle type sent by the service requester as the vehicle type associated with the service requester), or may be determined by the server according to travel habits of the service requester (for example, when the service requester places a travel order using the service requester, a certain vehicle type or types are often selected, and the vehicle type or types often selected may be used as the preset vehicle type). Further, the specified vehicle type may be any one or more of: car sharing vehicles, special cars, express cars, taxis and tailgating vehicles.

Similar to the calculation of the estimated taxi-taking cost, if the vehicle type is considered when calculating the current ranking information, the method provided by the application can calculate the estimated taxi-taking cost as follows:

and determining the current ranking information corresponding to the specified vehicle type according to the number of the service request ends and the selected vehicle type, wherein the service request ends are selected from the service request ends waiting for service, and the places, the distances of which from the travel starting point are within the set distance range, are used as the travel starting point.

That is, when the current ranking information is determined, the current ranking information corresponding to the specified one or more vehicle types is determined. As shown in table 4 below, the current ranking information for different vehicle types is shown:

TABLE 4

Furthermore, in a specific implementation, information of any one or more rows in the table may be sent to the service requester for reference by the service requester.

Different from the calculation of the waiting time for getting on the vehicle and the estimation of the arrival time, the meaning of sending the minimum value or the average value to the service request party for reference is not great when the estimation of the taxi taking cost and the calculation of the current ranking information are calculated, so in the scheme provided by the application, the estimation of the taxi taking cost and the calculation of the current ranking information are sent, the estimation of the taxi taking cost with the minimum value or the current ranking information are not selected to be sent to the service request party, and the weighted average value of the estimation of the taxi taking cost or the weighted average value of the current ranking information are not selected to be sent to the service request party.

The above disclosure discloses that after the vehicle type is introduced, the determined boarding waiting time, estimated arrival time, estimated taxi taking cost and current ranking information may all correspond to the trip type.

Further, the following table 5 may be formed:

TABLE 5

The waiting time for getting on the vehicle, the estimated arrival time, the estimated taxi taking cost and the current ranking information corresponding to each vehicle type are shown in table 5. In a specific implementation, one or more rows in the table may be sent to the service requester or one or more columns may be sent to the service requester according to the selection of the service requester.

Specifically, when the updated page information of the invoice page is sent to the service requester, the updated page information may only carry at least one of the boarding waiting time and other three information (estimated arrival time, estimated taxi-taking cost, and current ranking information).

That is, the updated page information of the invoice page may carry the boarding waiting time and the estimated arrival time, or the boarding waiting time, the estimated arrival time, and the current ranking information. Of course, the information combination carried in the updated page information of the invoice page may also have other forms, but at least the waiting time for getting on the bus should be carried.

Furthermore, in order to further improve the sensitivity of the service requester, the method provided by the application further includes a prompt message for calling multiple vehicle types simultaneously in the page information of the list-issuing page before updating and the page information of the list-issuing page after updating, and further, the prompt message for calling multiple vehicle types simultaneously can be displayed on the service request terminal. Specifically, the presentation form of the prompt message for calling multiple vehicle types simultaneously on the service request end may be displaying a key, where the key is marked with "calling multiple types of vehicles by one key", and further, when the service request party presses the key, the service request end may automatically send out a travel order for calling multiple types of vehicles simultaneously to the server.

After receiving the travel orders which are sent by the service request terminal and represent that the various vehicle types are called at the same time, the server broadcasts the travel orders which represent that the various vehicle types are called at the same time to the service providing terminals corresponding to the various vehicle types.

The service provider here refers to a terminal used by a service provider. Furthermore, service providers of different vehicle types can receive the travel orders, and the efficiency of distributing the travel orders is greatly improved. Of course, after the travel order is distributed to the service provider of a certain vehicle type, the broadcast of the travel order should be stopped immediately to avoid the service providers of other vehicle types from accepting the travel order again.

As shown in fig. 5, a block diagram of a service system 100 in which the service information pushing method of some embodiments of the present application is located is shown. For example, the service system 100 may be an online transportation service platform for transportation services such as taxi cab, designated drive service, express, carpool, bus service, driver rental, or shift service, or any combination thereof. The service system 100 may include one or more of a server 110 (an execution subject of the method provided herein), a network 120, a service requester terminal 130 (a service requester), a service provider terminal 140 (a service provider), and a database 150, and the server 110 may include a processor therein to perform instruction operations.

In some embodiments, the server 110 may be a single server or a group of servers. The set of servers can be centralized or distributed (e.g., the servers 110 can be a distributed system). In some embodiments, the server 110 may be local or remote to the terminal. For example, the server 110 may access information and/or data stored in the service requester terminal 130, the service provider terminal 140, or the database 150, or any combination thereof, via the network 120. As another example, the server 110 may be directly connected to at least one of the service requester terminal 130, the service provider terminal 140, and the database 150 to access stored information and/or data. In some embodiments, the server 110 may be implemented on a cloud platform; by way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud (community cloud), a distributed cloud, an inter-cloud, a multi-cloud, and the like, or any combination thereof. In some embodiments, the server 110 may be implemented on an electronic device 1000 having one or more of the components illustrated in FIG. 6 herein.

Network 120 may be used for the exchange of information and/or data. In some embodiments, one or more components in the service system 100 (e.g., the server 110, the service requester terminal 130, the service provider terminal 140, and the database 150) may send information and/or data to other components. For example, the server 110 may obtain a service request from the service 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. Merely by way of example, Network 130 may include a wired Network, a Wireless 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 WLAN, a Metropolitan Area Network (MAN), a Wide Area Network (WAN), a Public Switched Telephone Network (PSTN), a bluetooth Network, a ZigBee Network, a Near Field Communication (NFC) Network, or the like, or any combination thereof. In some embodiments, network 120 may include one or more network access points. For example, network 120 may include wired or wireless network access points, such as base stations and/or network switching nodes, through which one or more components of serving system 100 may connect to network 120 to exchange data and/or information.

In some embodiments, the service requester of the service requester terminal 130 may be a person other than the actual demander of the service. For example, the service requester a of the service requester terminal 130 may use the service requester terminal 130 to initiate a service request for the service actual demander B (for example, the service requester a may call a car for its friend B), or receive service information or instructions from the server 110. In some embodiments, the service requester of the service provider terminal 140 may be the actual provider of the service or may be another person than the actual provider of the service. For example, the service requester C of the service provider terminal 140 may use the service provider terminal 140 to receive a service request for services provided by the service provider entity D (e.g., the service requester C may order the service provider entity D employed by itself), and/or information or instructions from the server 110. In some embodiments, "service requester" and "service requester terminal" may be used interchangeably, and "service provider" and "service provider terminal" may be used interchangeably.

In some embodiments, the service requester terminal 130 may comprise a mobile device, a tablet computer, a laptop computer, or a built-in device in a motor vehicle, etc., or any combination thereof. In some embodiments, the mobile device 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. In some embodiments, the smart home devices may include smart lighting devices, control devices for smart electrical devices, smart monitoring devices, smart televisions, smart cameras, or walkie-talkies, or the like, or any combination thereof. In some embodiments, the wearable device may include a smart bracelet, a smart lace, smart glass, a smart helmet, a smart watch, a smart garment, a smart backpack, a smart accessory, and the like, or any combination thereof. In some embodiments, the smart mobile device may include a smartphone, a Personal Digital Assistant (PDA), a gaming device, a navigation device, or a point of sale (POS) device, or the like, or any combination thereof. In some embodiments, the virtual reality device and/or the augmented reality device may include a virtual reality helmet, virtual reality glass, a virtual reality patch, an augmented reality helmet, augmented reality glass, an augmented reality patch, or the like, or any combination thereof. For example, the virtual reality device and/or augmented reality device may include various virtual reality products and the like. In some embodiments, the built-in devices in the motor vehicle may include an on-board computer, an on-board television, and the like. In some embodiments, the service requester terminal 130 may be a device having a location technology for locating the location of the service requester and/or service requester terminal.

In some embodiments, the service provider terminal 140 may be a similar or identical device as the service requestor terminal 130. In some embodiments, the service provider terminal 140 may be a device with location technology for locating the location of the service provider and/or the service provider terminal. In some embodiments, the service requester terminal 130 and/or the service provider terminal 140 may communicate with other locating devices to determine the location of the service requester, service requester terminal 130, service provider, or service provider terminal 140, or any combination thereof. In some embodiments, the service requester terminal 130 and/or the service provider terminal 140 may transmit the location information to the server 110.

Database 150 may store data and/or instructions. In some embodiments, the database 150 may store data obtained from the service requester terminal 130 and/or the service provider terminal 140. In some embodiments, database 150 may store data and/or instructions for the exemplary methods described herein. In some embodiments, database 150 may include mass storage, removable storage, volatile Read-write Memory, or Read-Only Memory (ROM), among others, or any combination thereof. By way of example, mass storage may include magnetic disks, optical disks, solid state drives, and the like; removable memory may include flash drives, floppy disks, optical disks, memory cards, zip disks, tapes, and the like; volatile read-write memory may include Random Access Memory (RAM); the RAM may include Dynamic RAM (DRAM), Double data Rate Synchronous Dynamic RAM (DDR SDRAM); static RAM (SRAM), Thyristor-Based Random Access Memory (T-RAM), Zero-capacitor RAM (Zero-RAM), and the like. By way of example, ROMs may include Mask Read-Only memories (MROMs), Programmable ROMs (PROMs), Erasable Programmable ROMs (PERROMs), Electrically Erasable Programmable ROMs (EEPROMs), compact disk ROMs (CD-ROMs), digital versatile disks (ROMs), and the like. In some embodiments, database 150 may be implemented on a cloud platform. By way of example only, the cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, across clouds, multiple clouds, or the like, or any combination thereof.

Corresponding to the method, the application also provides a service information pushing device, which comprises:

Preferably, the first determining module includes:

preferably, the current service capability information includes at least one of:

Preferably, the trip address information further includes a trip destination; the updated page information of the invoice page also comprises estimated arrival time;

the device still includes:

Preferably, the second determining module includes:

Preferably, the updated page information of the invoice page further includes vehicle types, and the estimated arrival time includes estimated arrival time corresponding to each vehicle type;

a second determination module comprising:

Preferably, the updated page information of the invoice page further includes vehicle types associated with the service request end, and the estimated arrival time includes estimated arrival times respectively corresponding to the vehicle types associated with the service request end;

a second determination module comprising:

Preferably, the updated page information of the invoice page further comprises estimated taxi taking cost;

the device still includes:

Preferably, the updated page information of the invoice page further includes current ranking information;

the device still includes:

Preferably, the page information of the invoice page before updating and the page information of the invoice page after updating further include prompt information for simultaneous calling of multiple vehicle types.

Preferably, the first determining module includes:

Preferably, the apparatus further comprises:

Corresponding to the above method, the present application also provides a computer-readable storage medium having a computer program stored thereon, where the computer program is executed by a processor to perform the steps of the service information pushing method.

As shown in fig. 6, a schematic view of an electronic device provided in an embodiment of the present application, the electronic device 1000 includes: the system comprises a processor 1001, a memory 1002 and a bus 1003, wherein the memory 1002 stores execution instructions, when the electronic device runs, the processor 1001 and the memory 1002 communicate through the bus 1003, and the processor 1001 executes the steps of the service information pushing method stored in the memory 1002.

It is clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not described herein again.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A service information pushing method is characterized by comprising the following steps:

determining boarding waiting time of the service request terminal according to the trip starting point;

2. The method of claim 1, wherein determining the boarding waiting time of the service requester according to the trip starting point comprises:

and determining current service capability information matched with the trip starting point, and determining boarding waiting time of the service request terminal according to the current service capability information.

3. The method of claim 2, wherein the current service capability information comprises at least one of:

the number of service request terminals competing for queuing currently; the service request end competing for queuing currently is a service request end which selects a place with a distance from the travel starting point within a set distance range as the travel starting point;

4. The method of claim 1, wherein the travel address information further includes a travel destination; the updated page information of the invoice page also comprises estimated arrival time; the method further comprises the following steps:

and determining the estimated arrival time according to the navigation route from the travel starting point to the travel end point and the current road condition information corresponding to the navigation route.

5. The method of claim 4, wherein determining the estimated arrival time according to a navigation route from the travel starting point to the travel ending point and current road condition information corresponding to the navigation route comprises:

determining estimated arrival time corresponding to each vehicle type according to a navigation route from the trip starting point to the trip end point, current road condition information corresponding to the navigation route and at least one preset vehicle type;

taking the minimum value of the estimated arrival time corresponding to each of the plurality of vehicle types as the estimated arrival time carried in the updated page information of the invoice page; or taking the average value of the estimated arrival time corresponding to each of the plurality of vehicle types as the estimated arrival time carried in the updated page information of the invoice page.

6. The method according to claim 4, wherein the updated page information of the invoice page further includes vehicle types, and the estimated arrival time includes estimated arrival times respectively corresponding to each vehicle type; determining the estimated arrival time according to a navigation route from the travel starting point to the travel end point and current road condition information corresponding to the navigation route, wherein the method comprises the following steps:

and determining estimated arrival time respectively corresponding to each vehicle type according to a navigation route from the trip starting point to the trip end point, current road condition information corresponding to the navigation route and at least one preset vehicle type, and taking the estimated arrival time respectively corresponding to the specified vehicle types as the estimated arrival time carried in the page information of the updated invoice page.

7. The method according to claim 4, wherein the updated page information of the invoice page further includes vehicle types associated with the service request end, and the estimated arrival times include estimated arrival times respectively corresponding to the vehicle types associated with the service request end; determining the estimated arrival time according to a navigation route from the travel starting point to the travel end point and current road condition information corresponding to the navigation route, wherein the method comprises the following steps:

and determining estimated arrival time respectively corresponding to each vehicle type associated with the service request end according to the navigation route from the trip starting point to the trip end point, the current road condition information corresponding to the navigation route and the vehicle type associated with the service request end, and taking the estimated arrival time respectively corresponding to each vehicle type associated with the service request end as the estimated arrival time carried in the page information of the updated invoice page.

8. The method of claim 1, wherein the page information of the updated invoice page further includes an estimated taxi fare; the method further comprises the following steps:

9. The method of claim 1, wherein the page information of the updated invoice page further comprises current ranking information; determining the current ranking information according to the following steps:

10. The method according to any one of claims 5 to 7, wherein the page information of the invoice page before updating and the page information of the invoice page after updating further comprise a plurality of vehicle type simultaneous call prompt information.

11. The method of claim 2, wherein determining the boarding wait time of the service requester based on the current service capability information comprises:

12. The method of claim 11, wherein the boarding wait time prediction model is trained according to the following steps:

obtaining historical trip data of a plurality of service request terminal samples; the historical travel data comprises boarding waiting time, the number of service request ends competing for queuing when the service request end samples are issued, the number of service providers finishing the travel orders at a place which is within a set distance range from the travel starting point of the historical orders within preset historical time, and the number of service providers in an idle state at a place which is within a set distance range from the travel starting point of the historical orders when the service request end samples are issued;

and training to obtain the getting-on waiting time prediction model based on historical travel data of the multiple service request terminal samples.

13. A service information pushing apparatus, comprising:

the first determining module is used for determining the boarding waiting time of the service request terminal according to the trip starting point;

14. The apparatus of claim 13, wherein the first determining module comprises:

a first determining unit, configured to determine current service capability information matched with the trip starting point, and determine boarding waiting time of the service request terminal according to the current service capability information.

15. The apparatus of claim 13,

the current service capability information includes at least one of:

16. The apparatus according to claim 13, wherein the travel address information further includes a travel destination; the updated page information of the invoice page also comprises estimated arrival time;

the device further comprises:

and the second determining module is used for determining the estimated arrival time according to the navigation route from the travel starting point to the travel destination and the current road condition information corresponding to the navigation route.

17. The apparatus of claim 16, wherein the second determining module comprises:

a second determining unit, configured to determine estimated arrival times corresponding to respective vehicle types according to a navigation route from the travel starting point to the travel destination, current road condition information corresponding to the navigation route, and at least one preset vehicle type;

the first processing unit is used for taking the minimum value of the estimated arrival time corresponding to each of the plurality of vehicle types as the estimated arrival time carried in the page information of the updated invoice page; or taking the average value of the estimated arrival time corresponding to each of the plurality of vehicle types as the estimated arrival time carried in the updated page information of the invoice page.

18. The apparatus according to claim 16, wherein the updated page information of the invoice page further includes vehicle types, and the estimated arrival time includes estimated arrival times respectively corresponding to each vehicle type;

the second determining module includes:

and a third determining unit, configured to determine estimated arrival times respectively corresponding to each vehicle type according to a navigation route from the travel starting point to the travel destination, current road condition information corresponding to the navigation route, and at least one preset vehicle type, and take the estimated arrival times respectively corresponding to the specified vehicle types as the estimated arrival times carried in the page information of the updated invoice page.

19. The apparatus according to claim 16, wherein the updated page information of the invoice page further includes vehicle types associated with the service request end, and the estimated arrival times include estimated arrival times respectively corresponding to the vehicle types associated with the service request end;

the second determining module includes:

a fourth determining unit, configured to determine estimated arrival times respectively corresponding to each vehicle type associated with the service request end according to the navigation route from the trip start point to the trip end point, the current road condition information corresponding to the navigation route, and the vehicle type associated with the service request end, and use the estimated arrival times respectively corresponding to each vehicle type associated with the service request end as the estimated arrival times carried in the page information of the updated invoice page.

20. The apparatus of claim 13, wherein the page information of the updated invoice page further comprises an estimated taxi fare;

the device further comprises:

the third determining module is used for determining the estimated taxi taking expense according to the navigation distance from the trip starting point to the trip end point; or determining the estimated taxi taking cost according to the navigation distance from the trip starting point to the trip end point and the current road condition information.

21. The apparatus of claim 13, wherein the page information of the updated invoice page further comprises current ranking information;

the device further comprises:

22. The apparatus according to any one of claims 17-19, wherein the page information of the pre-update invoice page and the page information of the post-update invoice page further comprise a plurality of vehicle type simultaneous call prompt messages.

23. The apparatus of claim 13, wherein the first determining module comprises:

and the fifth determining unit is used for obtaining the getting-on waiting time of the service request terminal according to the current service capability information and a pre-trained getting-on waiting time prediction model.

24. The apparatus of claim 23, further comprising:

the second acquisition module is used for acquiring historical trip data of a plurality of service request end samples; the historical travel data comprises boarding waiting time, the number of service request ends competing for queuing when the service request end samples are issued, the number of service providers finishing the travel orders at a place which is within a set distance range from the travel starting point of the historical orders within preset historical time, and the number of service providers in an idle state at a place which is within a set distance range from the travel starting point of the historical orders when the service request end samples are issued;

and the training module is used for training to obtain the getting-on waiting time prediction model based on the historical travel data of the plurality of service request terminal samples.

25. An electronic device, comprising: a processor, a storage medium and a bus, the storage medium storing machine-readable instructions executable by the processor, the processor and the storage medium communicating via the bus when the electronic device is running, the processor executing the machine-readable instructions to perform the steps of the service information pushing method according to any one of claims 1 to 13.

26. A computer-readable storage medium, having stored thereon a computer program for performing the steps of the service information pushing method according to any one of claims 1 to 13 when the computer program is executed by a processor.