CN111435512A

CN111435512A - Service information acquisition method and device

Info

Publication number: CN111435512A
Application number: CN201910028738.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: 2019-01-11
Filing date: 2019-01-11
Publication date: 2020-07-21

Abstract

The application relates to the technical field of internet, in particular to a service information acquisition method and a service information acquisition device, wherein the method comprises the following steps: receiving a service order which is sent by a first service request end and is used for requesting service for a second service request end, and dispatching a service order corresponding to the service request to a service providing end; if it is detected that the first service request end requests to acquire service information generated in the process that the service order is executed, acquiring the service information from the service provider after it is detected that the service order is executed by the service provider; and notifying the acquired service information to the first service request terminal. By the method, the calling party can pay attention to the service information of the service order in real time, so that potential safety hazards possibly occurring in the service process can be effectively avoided, and the user experience degree is improved.

Description

Service information acquisition method and device

Technical Field

The present application relates to the field of internet technologies, and in particular, to a method and an apparatus for acquiring service information.

Background

In some application scenarios, there may be situations where a third party user requests a service from a service provider instead of an actual service requester. For example, in a taxi taking scene, a taxi calling party can use a terminal to initiate a taxi calling order, wherein actual taxi taking party information is recorded in the taxi calling order, a server can distribute the taxi calling order to a driver party providing a taxi taking service after receiving the taxi taking order, and a subsequent driver party can get in contact with the actual taxi taking party and provide the taxi taking service according to the taxi taking party information recorded in the taxi calling order.

However, in the case where a third-party user makes a call for a certain service, since the third-party user is not an actual service requester, it is difficult to know the actual service status of the service provider in the process of providing the service in time, which may cause a certain safety hazard.

Disclosure of Invention

In view of this, the embodiment of the present application provides a method and an apparatus for acquiring service information, so that a calling party can pay attention to the service information of a service order in real time, thereby effectively avoiding potential safety hazards that may occur in a service process and improving user experience.

Mainly comprises the following aspects:

in a first aspect, an embodiment of the present application provides a method for acquiring service information, which is applied to a server and includes:

receiving a service request which is sent by a first service request terminal and is used for requesting service for a second service request terminal, and dispatching a service order corresponding to the service request;

if it is detected that the first service request end requests to acquire service information generated in the process that the service order is executed, acquiring the service information from a service provider after it is detected that the service order is executed by the service provider;

and notifying the acquired service information to the first service request terminal.

In a possible implementation manner, after detecting that the first service request side requests to acquire service information generated in the process that the service order is executed, the method further includes:

sending an authorization request to the second service request terminal, wherein the authorization request is used for requesting authorization of the first service request terminal to acquire the service information;

before acquiring the service information from the service provider, the method further includes:

and receiving an indication of permission and authorization replied by the second service request terminal.

In a possible implementation manner, the first service request side is detected to request to acquire the service information generated in the process that the service order is executed according to the following manners:

and determining that the received service request carries the acquisition request information of the service information.

In a possible implementation manner, if it is determined that the received service request does not carry the acquisition request information of the service information, the method further includes:

sending prompt interface information to the first service request end, wherein the prompt interface information is used for prompting whether to request to acquire the service information;

and receiving the acquisition request information of the service information sent by the first service request end aiming at the prompt interface information.

In a possible implementation manner, after sending the prompt interface information to the first service request end, the method further includes:

and if the service order is executed by the service provider and the acquisition request information of the service information, which is sent by the first service request end aiming at the prompt interface information, is not received, indicating the first service request end to cancel displaying the prompt interface generated based on the prompt interface information.

In one possible embodiment, the method further comprises:

and if a function specification acquisition request sent by the first service request end is received, sending function specification interface information to the first service request end, wherein the function specification interface information is used for describing an acquisition mode of the service information.

In one possible embodiment, the method further comprises:

and sending a first application authorization prompt to the first service request end, wherein the first application authorization prompt is used for prompting that the server sends the authorization request to the second service request end after the service request is successfully sent.

In a possible implementation manner, after sending the authorization request to the second service request terminal, the method further includes:

and sending a second application authorization prompt to the first service request end, wherein the second application authorization prompt is used for prompting that the authorization request is sent to the second service request end.

In a possible implementation manner, after receiving the indication of grant authorization replied by the second service request end, the method further includes:

and sending a first authorization success prompt to the first service request end, and sending a second authorization success prompt to the second service request end.

and sending a third authorization success prompt to the service provider, wherein the third authorization success prompt is used for prompting that the service information is reported in the process that the service order is executed.

In a possible implementation manner, the notifying the first service request end of the acquired service information includes:

and if the first service request end is detected to send an acquisition request for acquiring the service information before the service order is executed and the end time exceeds the first set time length, notifying the acquired service information to the first service request end.

In one possible embodiment, the method further comprises:

after the service order is executed and the end time exceeds the first set time length, sending an acquisition prohibition prompt to the first service request end, wherein the acquisition prohibition prompt is used for prompting that the service information is prohibited to be acquired; and/or the presence of a gas in the gas,

and indicating the first service request terminal to hide a trigger option for acquiring the service information.

and sending the service information and display page information of the service information to the first service request terminal, wherein the display page information comprises at least one of identification, generation time and file size of the service information.

In one possible embodiment, the method further comprises:

and acquiring the service information of the set time period from the service providing terminal every set time period, updating the display page information of the service information, and notifying the updated display page information to the first service request terminal.

In one possible embodiment, the method further comprises:

and in the process of executing the service order, if the service information cannot be acquired from the service providing terminal within a second set time length, sending a first abnormal prompt to the first service request terminal, wherein the first abnormal prompt is used for prompting that the service information acquisition fails.

In one possible embodiment, the method further comprises:

and if the service order is detected to be executed in advance and finished, or the travel position in the service order execution process is detected not to be changed within a third set time length, sending a second abnormal prompt to the first service request end, wherein the second abnormal prompt is used for prompting to view the service information.

In one possible embodiment, the service information includes recorded content.

In a second aspect, an embodiment of the present application provides a method for acquiring service information, which is applied to a first service request end, and includes:

sending a service request for requesting service for a second service request terminal to a server, and requesting the server to acquire service information, wherein the service information is generated in the process that a service order corresponding to the service request is executed;

and after the service order is executed by a service providing terminal, acquiring the service information from the server.

In a possible implementation manner, the requesting the server for obtaining the service information includes:

detecting whether a first acquisition option in an order display interface of the first service request terminal is triggered, wherein the first acquisition option is used for requesting to acquire the service information;

and if the first acquisition option is detected to be triggered, sending a service request carrying the acquisition request information of the service information to the server.

In a possible implementation manner, if it is detected that the first obtaining option is not triggered, the method further includes:

receiving prompt interface information sent by the server, wherein the prompt interface information is used for prompting whether to request to acquire the service information;

after a prompt interface is generated and displayed based on the prompt interface information, whether a second acquisition option in the prompt interface is triggered or not is detected, wherein the second acquisition option is used for requesting to acquire the service information;

and if the second acquisition option is detected to be triggered, transmitting acquisition request information of the service information to the server.

In one possible embodiment, the method further comprises:

if the fact that the function description option in the order display interface is triggered is detected, sending a function description obtaining request to the server;

and receiving function explanation interface information sent by the server, and displaying a function explanation interface generated based on the function explanation interface information, wherein the function explanation interface information is used for describing an acquisition mode of the service information.

In one possible embodiment, the method further comprises:

and receiving a first application authorization prompt sent by the server, wherein the first application authorization prompt is used for prompting that the server sends the authorization request to the second service request terminal after the service request is successfully sent.

In a possible implementation manner, after requesting the server to obtain the service information, the method further includes:

and receiving a second application authorization prompt sent by the server, wherein the second application authorization prompt is used for prompting that the authorization request is sent to the second service request terminal.

In a possible implementation manner, before obtaining the service information from the server, the method further includes:

and receiving an authorization success prompt sent by the server, wherein the authorization success prompt is used for prompting that the second service request end authorizes the first service request end to obtain the service information.

In a possible implementation, the obtaining the service information from the server includes:

sending an acquisition request for acquiring the service information to the server before the service order is executed and the end time exceeds the first set time length;

and receiving the service information sent by the server.

In one possible embodiment, the method further comprises:

after the service order is executed and the end time exceeds the first set time length, receiving an acquisition prohibition prompt sent by the server, wherein the acquisition prohibition prompt is used for prompting prohibition of acquiring the service information; and/or the presence of a gas in the gas,

hiding a trigger option for acquiring the service information under the instruction of the server.

In a possible implementation manner, the receiving the service information sent by the server includes:

receiving the service information sent by the server and display page information of the service information, wherein the display page information comprises at least one of identification, generation time and file size of the service information;

and generating a display page based on the display page information.

In one possible embodiment, after generating the presentation page based on the presentation page information, the method further comprises:

and updating the content displayed in the display page under the instruction of the server.

In one possible embodiment, the service information includes recorded content.

In a third aspect, an embodiment of the present application provides a service information obtaining apparatus, including:

the receiving module is used for receiving a service request which is sent by a first service request end and requests a service for a second service request end;

the order dispatching module is used for dispatching the service order corresponding to the service request;

the processing module is used for acquiring the service information from the service providing terminal after detecting that the service order is executed by the service providing terminal if the first service request terminal requests to acquire the service information generated in the process that the service order is executed is detected;

and the sending module is used for notifying the acquired service information to the first service request terminal.

The specific interaction flow of the modules may refer to the content in the first aspect or any one of the possible embodiments of the first aspect.

In a fourth aspect, an embodiment of the present application provides a service information obtaining apparatus, including:

the sending module is used for sending a service request for requesting service for a second service request end to a server and requesting the server to acquire service information, wherein the service information is generated in the process that a service order corresponding to the service request is executed;

and the receiving module is used for acquiring the service information from the server after the service order is executed by the service providing end.

The specific interactive flows of the modules can be referred to in the second aspect or any one of the possible embodiments of the second aspect.

In a fifth aspect, an embodiment of the present application further provides an electronic device, including: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, the processor and the memory communicate via the bus when the electronic device is running, and the machine-readable instructions, when executed by the processor, perform the steps of the service information acquisition method according to the first aspect or any one of the possible implementations of the first aspect.

In a sixth aspect, an embodiment of the present application further provides an electronic device, including: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, the processor and the memory communicate via the bus when the electronic device is running, and the machine-readable instructions, when executed by the processor, perform the steps of the second aspect described above, or the service information acquisition method described in any one of the possible embodiments of the second aspect.

In a seventh aspect, this application embodiment further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program is executed by a processor to perform the steps of the service information acquisition method in the first aspect or any one of the possible implementations of the first aspect, or the computer program is executed by the processor to perform the steps of the service information acquisition method in the second aspect or any one of the possible implementations of the second aspect.

In the manner provided by the application, the server can receive the service request of the first service request terminal requesting service for the second service request terminal, and dispatch the service order corresponding to the service request, and if it is detected that the first service request terminal requests to acquire service information, when the service order is in an executed state, the server can acquire the service information from the service providing terminal and timely notify the service information to the first service request terminal, so that the first service request terminal can timely acquire the service information of the service order of the substitute call and timely acquire the status of the service order in the execution process, thereby effectively avoiding potential safety hazards, improving the operation experience of third-party users, and improving the user experience.

In order to make the aforementioned objects, features and advantages of the embodiments of the present application more comprehensible, 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 it will be apparent to those skilled in the art that other related drawings can be obtained from the drawings without inventive effort.

Fig. 1 is a schematic diagram illustrating a service system provided by an embodiment of the present application;

fig. 2 is a schematic flowchart illustrating a service information obtaining method provided in an embodiment of the present application;

fig. 3 is a first schematic flowchart illustrating a process of detecting that a first service request end requests to acquire service information according to an embodiment of the present application;

fig. 4 is a schematic diagram illustrating an order display interface of a first service request end according to an embodiment of the present application;

fig. 5 illustrates a second flowchart of detecting that a first service request end requests to acquire service information according to the embodiment of the present application;

fig. 6 is a schematic diagram illustrating a waiting order receiving interface of a first service request end according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating a presentation interface of the sound recording content of the first service request end according to the embodiment of the present application;

fig. 8 is a schematic diagram illustrating a travel state interface of a first service request end according to an embodiment of the present application;

FIG. 9 is a schematic diagram illustrating an interaction flow of a trigger function explanation interface according to an embodiment of the present application;

fig. 10 is a schematic diagram illustrating a travel state interface of a first service request end in an abnormal situation according to an embodiment of the present application;

fig. 11 is a first schematic structural diagram of a service information acquisition apparatus according to an embodiment of the present application;

fig. 12 is a schematic structural diagram of a service information acquisition apparatus according to an embodiment of the present application;

fig. 13 shows a first structural diagram of an electronic device provided in an embodiment of the present application;

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

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, 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 the embodiments. The following detailed description of the embodiments of the present application 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.

First, an application scenario to which the present application is applicable will be described. The method and the device for requesting the service are applicable to an application scene that a third-party user replaces an actual service requester to request a certain service from a service provider. For example, the embodiment of the present application may be applied to a scenario in which a third-party user requests a driver for a riding service instead of an actual passenger, or may also be applied to a scenario in which a third-party user requests a courier for a delivery service instead of an actual meal orderer, or may also be applied to a scenario in which a third-party user requests a courier for a delivery service instead of an actual courier, and the like. Of course, other scenarios involving a third-party user requesting a certain service instead of an actual service requester may be applicable to the embodiment of the present application, and the present application is not limited thereto.

It is worth noting that, in the above scenario where a third-party user replaces an actual service requester to request a certain service, because the third-party user is not an actual service requester, if the third-party user wants to know an actual service status of a service provider in a service providing process, the third-party user needs to contact the actual service requester or the service provider by himself/herself, which may cause a problem that the actual service status is not obtained timely or the obtaining is failed, on one hand, a certain potential safety hazard may be caused, for example, the potential safety hazard may be caused by a collision between the service provider and a second service provider, and on the other hand, the operation experience of the third-party user may be affected, which may cause a poor user experience.

In view of the above problems, embodiments of the present application provide a method and an apparatus for obtaining service information, where a server may receive a service request that a first service request end requests a second service request end to service, and dispatch a service order corresponding to the service request, and if it is detected that the first service request end requests to obtain service information, when the service order is in an executed state, the server may obtain the service information from a service providing end and timely notify the service information to the first service request end, so that the first service request end may timely obtain service information of a service order of a substitute call, and timely obtain a status of the service order in an execution process, thereby effectively avoiding a potential safety hazard, improving an operation experience of a third-party user, and improving a user experience.

In an example, in a taxi taking scene, the service information is, for example, a travel record, the first service request terminal is after the second service request terminal is substituted for the taxi taking order, and the server can obtain the travel record from the service provider terminal during the execution of the taxi taking order by the service provider terminal, so that the first service request terminal can pay attention to the order information in real time, thereby effectively avoiding potential safety hazards in the service process and improving user experience.

Before describing the specific embodiments provided in the present application, first, the related terms applied in the embodiments of the present application and the service system to which the embodiments of the present application are applicable will be described.

(1) The terms "first service requestor", "third party user", or "surrogate party" are used interchangeably in this application, and "first service requestor", "third party user terminal", or "surrogate party" are used interchangeably to refer to an individual, entity device, or tool, etc., that is capable of requesting or subscribing to a service in place of the actual service requestor.

(2) The terms "second service requestor", "service actual demander" or "actual service requestor" in this application are used interchangeably, and "second service requestor" or "actual service requestor" are used interchangeably to refer to an individual, entity device or tool, etc. that actually has a service requirement and accepts the service. In one example, in a taxi taking scene, the second service provider is a passenger, and the second service provider is a terminal used by a bus.

(3) The term "service provider" or "service provider" in this application is used to refer to an individual, entity or tool that can provide a service. In one example, in a taxi taking scene, the service provider is a driver, and the service provider is a terminal used by the driver.

(4) The term "service order" in this application is to generate a service order based on information included in a service request sent by a first service request end, and the type of the service order differs according to different service scenarios, for example, the service order may be a bus taking order, an outgoing order, a mail sending order, and the like, which is not limited in this application. In addition, the types of service orders are also differentiated for the same service scenario, for example, in a taxi taking scenario, the taxi taking orders include, but are not limited to, the following order types: express orders, taxi orders, special car orders, tailgating orders, and car pooling orders.

(5) The term "service information" in the present application is different depending on the service scenario and the service order. In an example, in a taxi taking scene, the service order is a bus taking order, and then the service information is, for example, recorded content generated in the process of executing the bus taking order.

Furthermore, it should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the presence of the features stated hereinafter, but does not exclude the addition of further features. In the embodiments of the present application, ordinal numbers such as "first", "second", etc. will be used only for distinguishing technical features, and do not imply a front-back order, priority, or importance.

Referring to fig. 1, a schematic diagram of a service system according to an embodiment of the present application is shown. Illustratively, the service system may be an online transportation service platform for a transportation service such as a taxi, a designated drive service, a express, a carpool, a bus service, a driver rental, or a shift service, or any combination thereof. In an application scenario of the embodiment of the application, the service system 100 may include one or more of a server 110, a network 120, a first service request end 130, a service provider end 140, a database 150, and a second service request end 160, and the server 110 may include a processor for executing instruction operations.

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 terminals. In an example, the server 110 may access information and/or data stored in the first service requestor 130, the service provider 140, the database 150, or the second service requestor 160, or any combination thereof, via the network 120. In another example, the server 110 may be directly connected to at least one of the first service requester 130, the service provider 140, the database 150, and the second service requester 160 to access the stored information and/or data.

Network 120 may be used for the exchange of information and/or data. In some embodiments, one or more components (e.g., server 110, first service requestor 130, service provider 140, database 150, second service requestor 160) in the service system 100 may send information and/or data to other components. For example, the server 110 may obtain a service request from the first service requester 130 via the network 120. In some embodiments, network 120 may be any type of wired or wireless network, or combination thereof, which is not limited in this application.

The first service requester 130 may be a terminal that sends a service request instead of an actual demander of the service. The second service requester 160 may be a terminal used by the actual demander of the service. For example, the user a of the first service request end 130 may use the first service request end 130 to initiate a service request for the service actual demander B (i.e., the second service request end 160), for example, the user a may initiate a bus taking request for the service actual demander B, and the first service request end 130 may also receive service information or instructions from the server 110.

The service provider 140 may be a similar or identical device as the first service requester 130 or the second service requester 160. In some embodiments, the service provider 140 may further be configured to collect service information generated during the execution of the service order and send the collected service information to the server 110, for example, the service provider 140 may collect audio recording content during the execution of the order and send the collected audio recording content to the server 110. In some embodiments, the service provider 140 may be a device with location technology that may locate the location of the second service provider and/or the service provider and send 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 first service requestor 130, the second service requestor 160, and/or the service provider 140, as well as data and/or instructions of the exemplary methods described herein. In some embodiments, one or more components in service system 100 may access data or instructions stored in database 150 via network 120. In some embodiments, database 150 may also be part of server 110.

In combination with the above application scenario, terms used in the present application, and descriptions of the service system provided in the present application, the following describes in detail a service information obtaining method provided in the embodiments of the present application.

Referring to fig. 2, a flowchart of a service information obtaining method provided in an embodiment of the present application is schematically shown, where the flowchart describes an interaction flow between a server and a first service request end, a second service request end, and a service provider end in a service system when executing the service information obtaining method, and includes the following steps:

step 201, the first service request terminal sends a service request for requesting a service for the second service request terminal to the server.

The service request carries information such as contact information of the second service request end and requested service content. The contact information includes, for example, a name or a mobile phone number of the second service requester, so that the second service provider can be contacted after the service provider receives the order. The requested service content includes at least one of a service type and a specific service item, for example, taking a taxi taking scene as an example, the service type may be a taxi calling service, and the specific service item includes information such as a start position and a destination position.

Step 202, the server receives a service request sent by the first service request terminal and requesting service for the second service request terminal, and dispatches a service order corresponding to the service request.

In some embodiments, after receiving the service request, the server may generate a service order corresponding to the service request based on the information carried in the service request and distribute the service order to the service provider. And, after identifying that the service requested by the first service request end is requested by the second service request end, that is, the service requested by the first service request end is the substitute service, the server may perform a subsequent step to further determine whether to provide the first service request end with the service information generated in the process of executing the service order.

Step 203, the server detects that the first service request end requests to acquire service information generated in the process of executing the service order.

The service information is generated in the process of executing the service order, and includes, for example, recorded content in the process of executing the service order. Taking a taxi taking scene as an example, considering that a service provider (i.e. a driver) needs to send a second service provider (i.e. a passenger) to a destination position from an initial position after taking a taxi, in a journey of a taxi to the destination position, recording content in the journey can be collected, so that a third party user using a first service request end can know the journey condition by acquiring the recording content.

It should be noted that, step 202 and step 203 may not be sequential in specific implementation, that is, the server detects that the first service request end requests to obtain the service order, and may detect when receiving the service request, or detect in a process of receiving the service request and starting to dispatch the service order.

In some embodiments, the manner in which the server detects that the first service request terminal requests the service information includes, but is not limited to, the following embodiments:

in the first embodiment, when receiving a service request, it is detected that a first service request end requests to acquire service information.

The specific detection process refers to the flow diagram shown in fig. 3, and includes the following steps:

step 301, the first service request end detects whether a first obtaining option in an order display interface of the first service request end is triggered, where the first obtaining option is used for requesting to obtain service information.

And the third-party user can input the contact information of the second service request terminal, the requested service content and other information on the order display interface. And the order display interface can be also configured with a first acquisition option so that the third-party user can select whether to request to acquire the service information.

Step 302, if the first service request end detects that the first obtaining option is triggered, the first service request end sends a service request carrying obtaining request information of the service information to the server.

Step 303, the server receives the service request and determines that the received service request carries the acquisition request information of the service information.

For example, taking a car-call-in-place service as an example, a service order is a car-call-in-place order, a service request is a car-call-in-place request, an order display interface of a first service request end is shown in fig. 4, the order display interface 400 may include a passenger information filling area 401, a personalized option area 402, and a service request triggering option 403, where the passenger information filling area 401 may be used to fill in passenger information, that is, information of an actual demander is served, for example, a passenger name, a contact manner, and the like; the personalized option area 402 has a first acquisition option 4021 set therein. In addition, the order display interface 400 may further include a service content filling area 404 for filling service content, such as a vehicle starting position, a vehicle destination position, and the like.

If the first service request end detects that the first obtaining option 4021 is triggered, it may be determined that it needs to request to obtain service information, and after further detecting that the service request triggering option 403 is triggered, a service request may be sent to the server, where the service request includes the obtaining request information of the service information.

In the second embodiment, the first service request terminal is detected to request to acquire the service information in the process of receiving the service request and starting to serve the service order.

The specific detection process refers to the flow diagram shown in fig. 5, and includes the following steps:

step 501, if the server determines that the received service request does not carry the acquisition request information of the service information, the server sends prompt interface information to the first service request end, where the prompt interface information is used to prompt whether to request to acquire the service information.

And 502, after the first service request end receives the prompt interface information sent by the server, generating a prompt interface based on the prompt interface information and displaying the prompt interface.

Step 503, the first service request end detects whether a second obtaining option in the prompt interface is triggered, where the second obtaining option is used to request to obtain service information.

Step 504, if the first service request end detects that the second obtaining option is triggered, the first service request end sends obtaining request information of the service information to the server.

Step 505, after receiving the obtaining request information of the service information, the server determines that the first service request end requests to obtain the service information.

In addition, if the server does not receive the acquisition request information of the service information sent by the first service request end aiming at the prompt interface information after the service order is executed by the service providing end, the server can also instruct the first service request end to cancel the display of the prompt interface generated based on the prompt interface information.

For example, continuing to use the above example, taking a car-ordering service as an example, the service order is a car-ordering order, and during the period that the server receives the service request and dispatches the service order corresponding to the service request, the display interface of the first service request end may display a waiting order receiving interface, as shown in fig. 6, map information is displayed in the waiting order receiving interface 600, where the map information may display, for example, a riding start point position P. If the first obtaining option 4021 in the order display interface 400 is not triggered when the first service request end initiates a service request, the server may push prompt interface information after the first service request end jumps to the waiting order receiving interface 600, and accordingly, the first service request end may generate the prompt interface 601 based on the prompt interface information, where the display mode of the prompt interface 601 is, for example, a half-screen pop-up window mode, so that the prompt interface 601 and the waiting order receiving interface 600 may be simultaneously displayed in the display interface. The prompt interface 601 includes a prompt information area 6011 and a selection area 6012, where the selection area includes a second acquisition option 6013 and may further include a non-acquisition option 6014. The prompt information displayed in the prompt information area 6011 is, for example, "do you need to obtain service information? ". If the first service request end detects that the second obtaining option 6013 is triggered, the obtaining request information of the service information may be sent to the server.

In the two embodiments, in the first embodiment, the third-party user may autonomously select whether to request to acquire the service information in the process of initiating the service request, and if the third-party user does not select to request to acquire the service information in the process of initiating the service request, the second embodiment may be enabled, and the server may prompt the first service request terminal again, so that the first service request terminal determines whether to acquire the service information.

In some embodiments, the server may apply for authorization from the second service provider if the server allows providing the service information to the first service requester. The specific authorization process comprises the following steps:

step 204, the server sends an authorization request to the second service request terminal, wherein the authorization request is used for requesting the first service request terminal to be authorized to acquire the service information.

Illustratively, the manner in which the server sends the authorization request includes, but is not limited to, short message, email, push message in the client, and the like.

For example, taking the car-calling-as-a-service as an example, if the authorization request is sent to the second service request terminal by using a short message, the content of the short message is, for example, "hello, < calling-as-a-party > initiates an authorization request of [ obtaining service information ] to your in an order called by your generation in order to better pay attention to your travel state. Grant please reply 1, not grant without reply. "

Step 205, the server receives the indication of grant authorization replied by the second service request terminal.

Step 206, the server sends a first authorization success prompt to the first service request end.

And step 207, the server sends a second authorization success prompt to the second service request end.

And step 208, the server sends a third authorization success prompt to the service provider.

In the execution sequence of the above steps 206 to 208, the first authorization success prompt and the second authorization success prompt are used to prompt the first service request end and the second service request end to take effect in authorization, and the third authorization success prompt is used to prompt the service information to be reported in the process of executing the service order.

The three authorization success prompts sent by the server include but are not limited to short messages, mails, message pushing in the client and the like.

For example, taking the car-calling service as an example, and taking the service information as the recording content as an example, the server sends a first authorization success prompt to the first service request end, where the prompt content is, for example, "the passenger has granted authorization, and you can obtain the recording of the trip after the trip starts. "; the server sends a second authorization success prompt to the second service request end, and the prompt content is, for example, an authorization request that "you have agreed < the called party > to initiate [ get the travel record ], and the called party can listen to the travel record within 30 minutes after the travel is finished. "; the server sends a third authorization success prompt to the service provider, where the prompt content is, for example, "the calling party has successfully authorized to obtain the travel record, and the travel record needs to be reported after the travel starts. ".

It should be noted that the authorization process is optional, and in a specific implementation, whether the authorization process is needed or not may be determined according to actual requirements. Moreover, the prompting process after the authorization is successful is also optional, and can be configured according to actual requirements, which is not limited in the present application.

Step 209, after detecting that the service order is executed by the service provider, the server obtains the service information from the service provider.

In some embodiments, there are multiple ways in which the server determines that the service order is to be executed by the service provider. For example, in a car-taking scenario, after a service order is dispatched to a service provider used by a driver, a process of receiving the order, receiving the driving, and confirming the start of a journey after a passenger gets on the car is executed. In another possible embodiment, the driver may click a journey start option displayed in the service provider after confirming that the passenger gets on the vehicle, the service provider may send a journey start instruction to the server after confirming that the journey start option is triggered, and the server determines that the service order is executed by the service provider after receiving the journey start instruction. Of course, the actual application is not limited to the manner given in the above example, and in other application scenarios, the service provider may also use other manners to indicate that the service order is executed, which is not limited in this application.

In some embodiments, before obtaining the service information from the service provider, it is first confirmed that the service provider has started the function of uploading the service information. For example, if the service information is the recorded content, before the service provider starts to receive the order, the server may instruct the service provider to start the recording function and instruct the service provider to authorize the server to obtain the recorded content. In addition, it should be noted that, in some application scenarios, the server may also obtain the service information from the second service request end (i.e., the terminal of the actual service recipient), and a specific obtaining manner is similar to the above-mentioned manner of obtaining the service information from the service provider end, and a description thereof is not repeated here.

In some embodiments, in the process of acquiring the service information from the service provider, the server may collect the service information generated in the set time period every set time period, and may cache the service information in the database or notify the first service request terminal after collecting the service information in the set time period each time.

Step 210, before the server finishes executing the service order and the finishing time exceeds the first set time length, the first service request end sends an obtaining request for obtaining the service information to the server.

In step 211, after receiving the obtaining request, the server notifies the first service request end of the service information obtained from the service providing end.

For example, in the process of notifying the first service request end of the service information, the server may specifically send the service information and the display page information of the service information to the first service request end, where the display page information includes, but is not limited to, at least one of an identifier, a generation time, and a file size of the service information.

Accordingly, after receiving the display interface information, the first service request end may generate a display interface of the service information based on the display interface information. At least one of the identification, the generation time, the file size and the like of the service information can be displayed in the display interface of the service information. For example, if the first service request end detects that the first service request party selects the identifier of a certain service information, the service information matching the selected identifier of the service information may be provided to the first service request party.

In a specific implementation, if the server acquires the service information of the set time period from the service providing terminal every set time period, after the service information of the set time period is acquired each time, the display page information of the service information may be updated, and the updated display page information is notified to the first service requesting terminal, so that the first service requesting terminal updates and updates the content displayed in the display page.

For example, referring to fig. 7, assuming that the service information is a recording content, taking the car-call service as an example, the information of the recording content collected every set period of time (e.g., 5 minutes) may be displayed in the presentation interface 700 of the recording content, for example, the information includes "recording content a", "recording content B", "recording content C", and "recording content D", and the generation time and the file size of each recording content may be displayed, for example, the generation time is "2019/1/107: 00 to 7: 05" and the file size is 5M under "recording content a", the generation time is "2019/1/107: 05 to 7: 10" and the file size is 5M under "recording content B", and so on.

In addition, the recording status may also be displayed in the interface 700 for displaying the recording content, for example, if the server is still obtaining the recording content in the travel, then the interface 700 for displaying the recording content may also display the recording status "in the travel continuous recording". In addition, if the server interrupts acquiring the recording content in the trip, the recording status displayed in the display interface 700 of the recording content may be changed to "trip recording stop".

Step 212, after the service order execution is finished and the finishing time exceeds the first set time length, the server sends an acquisition prohibition prompt to the first service request end, where the acquisition prohibition prompt is used for prompting prohibition of acquiring service information.

In some embodiments, in consideration of timeliness of the service information and privacy of the service provider and the second service requester, the first service requester may be allowed to have the right to acquire the service information only before the service order is executed and the end time exceeds the first set time length.

For example, a trigger option for acquiring service information may be displayed in a display interface of the first service request end, where the trigger option only takes effect within a specified time period, and the specified time period in this embodiment of the present application is a corresponding time period before the service order is executed and the end time exceeds a first set time period. In a specified time period, the first service request end has the authority of acquiring the service information, the third-party user can use the first service request end to select the trigger option, and then the first service request end can send an acquisition request to the server.

Further, when the specified time period is exceeded, the first service request end does not have the authority to acquire the service information, and in this case, the server prompts the first service request end to prohibit acquiring the service information. In some embodiments, the server may further instruct the first service request end to hide a trigger option for acquiring the service information, or instruct the trigger option to fail, thereby prohibiting the first service request end from initiating a process of acquiring the service information.

For example, a car-ordering service is taken as an example, a service order is a car-ordering order, service information is, for example, recording content, and after a service providing end receives an order, a travel state interface can be displayed in the service providing end and a first service requesting end. Referring to fig. 8, the journey status interface 800 includes a journey navigation area 801, and the journey navigation area 801 includes a current driving position of the vehicle, a navigation path between the current driving position and a riding destination, and the like. The trip status interface 800 further includes a trip status display area 802, for example, which can display that the trip status is "in-trip", and an information area 803 of the service provider, which can display one or more of the license plate number, model number, appearance, driver name, evaluation value, and the number of orders to be picked up of the vehicle driven by the service provider.

The journey status interface 800 may further include a trigger option 804, where the trigger option 804 is effective within the specified time period, and when the trigger option 804 is effective, the journey status interface may be displayed as "listen to the journey record", and when the trigger option 804 is triggered, the presentation interface 700 for the record content shown in fig. 7 may be displayed.

The above implementation flow describes a general interaction flow between the server and the first service request end, the second service request end, and the service provider end in the service system when executing the service information obtaining method. Through the implementation process, the first service request terminal can timely acquire the service information of the service order of the substitute call and timely acquire the condition of the service order in the execution process, so that potential safety hazards can be effectively avoided, the operation experience of a third-party user can be improved, and the user experience is improved.

In some embodiments, some prompt contents may be further added in the interaction flow between the server and the first service request end, so as to further improve the user experience.

In an example, after receiving the acquisition request information of the service information and determining that the first acquisition option is triggered, the server may further send a first application authorization prompt to the first service request end, where the first application authorization prompt is used to prompt the server to send an authorization request to the second service request end after the service request is successfully sent. Therefore, the third party user can be prompted to perform an authorization process after the service request is initiated.

In another example, after sending the authorization request to the second service request end, the server may further send a second application authorization prompt to the first service request end, where the second application authorization prompt is used to prompt that the authorization request has been sent to the second service request end.

In some embodiments, in consideration that the third party user may not know the specific operation flow of obtaining the service information, a function description option may be further configured in the order display interface of the first service request end, and when the function description option is triggered, the first service request end may display the obtaining manner of the service information so as to inform the third party user of the obtaining manner of the service information. The specific interaction flow can refer to fig. 9:

step 901, if the first service request end detects that the function description option in the order display interface is triggered, the first service request end sends a function description acquisition request to the server.

Step 902, the server sends function description interface information to the first service request end, where the function description interface information is used to describe an obtaining manner of the service information.

Step 903, the first service request end receives the function description interface information sent by the server, and displays a function description interface generated based on the function description interface information.

The specific content of the function description interface information may be adaptively configured according to different service scenarios and different service information, which is not limited in the present application.

In some embodiments, in order to effectively avoid some potential safety hazards, in consideration of some abnormal situations that may be encountered during execution of a service order, the first service requester may be prompted in the abnormal situation.

The following lists the abnormal situation prompting flow in several implementation scenarios.

In the implementation scenario one, in the process of executing the service order, if the service information cannot be acquired from the service providing terminal within the second set time length, a first exception prompt is sent to the first service requesting terminal, and the first exception prompt is used for prompting that the service information acquisition fails.

For example, taking the service information as the recording content, if the server detects that the service provider closes the microphone permission and the closing duration exceeds the second set duration in the process of executing the service order, the server cannot successfully acquire the recording content, and at this time, the server may send a first exception prompt to the first service request terminal.

In an example, if the first service request end may display the journey status interface 800 shown in fig. 8 in the process that the service order is executed, after receiving the first exception prompt, as shown in fig. 10, the first exception prompt box 805 may be displayed in the journey status interface 800, and the first exception prompt box 805 may display "the journey record is closed, and please contact the vehicle in time to confirm the journey".

And in an implementation scenario II, if the service order is detected to be executed in advance and finished, sending a second abnormal prompt to the first service request end, wherein the second abnormal prompt is used for prompting to view service information.

In an example, taking the car-ordering service as an example, the service order is a car-ordering order, and if it is detected that the service provider does not reach a destination position specified in the car-ordering order, or the service order is ended before the expected arrival time is advanced for a long time, it may be determined that the service order is ended in advance. In this scenario, the second abnormal prompt sent by the server is, for example, "the journey is ended in advance, and the passenger is called to confirm the journey in time".

And in an implementation scenario III, if it is detected that the travel position in the service order execution process does not change within a third set time length, sending a second exception prompt to the first service request end, wherein the second exception prompt is used for prompting to check service information.

In an example, taking a car-ordering service as an example, the service order is a car-ordering order, and if it is detected that the travel position of the service provider stays at a certain position for a long time, it may be determined that the service order is abnormal. In this scenario, the second abnormal prompt sent by the server is, for example, "the journey is stopped abnormally, and the passenger is required to be contacted to confirm the journey in time".

Based on the same technical concept, a service information acquisition device corresponding to the service information acquisition method is also provided in the embodiments of the present application, and because the principle of solving the problem of the device in the embodiments of the present application is similar to that of the service information acquisition method in the embodiments of the present application, the implementation of the device can refer to the implementation of the method, and repeated details are not repeated.

Referring to fig. 11, a first schematic structural diagram of a service information acquiring apparatus provided in the embodiment of the present application is shown, where the apparatus 1100 includes: the receiving module 1101, the dispatching module 1102, the processing module 1103, and the sending module 1104 specifically:

a receiving module 1101, configured to receive a service request sent by a first service request end and requesting a service for a second service request end;

a dispatch module 1102, configured to dispatch a service order corresponding to the service request;

a processing module 1103, configured to, if it is detected that the first service request end requests to acquire service information generated in a process that the service order is executed, acquire the service information from a service provider after it is detected that the service order is executed by the service provider;

a sending module 1104, configured to notify the obtained service information to the first service request end.

In one possible design, the sending module 1104 is further configured to:

after the processing module 1103 detects that the first service request end requests to acquire service information generated in the process that the service order is executed, an authorization request is sent to the second service request end, where the authorization request is used to request that the first service request end is authorized to acquire the service information;

the receiving module 1101 is further configured to:

before the processing module 1103 obtains the service information from the service provider, an indication of authorization to agree with a reply from the second service requester is received.

In a possible design, when detecting that the first service request end requests to acquire service information generated in a process in which the service order is executed, the processing module 1103 is specifically configured to:

In one possible design, the sending module 1104 is further configured to:

if the processing module 1103 determines that the received service request does not carry the acquisition request information of the service information, the sending module 1104 sends prompt interface information to the first service request end, where the prompt interface information is used to prompt whether to request to acquire the service information;

the receiving module 1101 is further configured to:

In one possible design, after sending the prompt interface information to the first service request end, the sending module 1104 is further configured to:

if the receiving module 1101 has not received the service information obtaining request information sent by the first service request end for the prompt interface information after the service order is executed by the service provider, the sending module 1104 instructs the first service request end to cancel displaying the prompt interface generated based on the prompt interface information.

In one possible design, the receiving module 1101 is further configured to:

receiving a function description acquisition request sent by the first service request end;

the sending module 1104 is further configured to:

and sending function explanation interface information to the first service request terminal, wherein the function explanation interface information is used for describing an acquisition mode of the service information.

In one possible design, the sending module 1104 is further configured to:

sending a first application authorization prompt to the first service request end;

and the first application authorization prompt is used for prompting that the server sends the authorization request to the second service request terminal after the service request is successfully sent.

In one possible design, the sending module 1104, after sending the authorization request to the second service request end, is further configured to:

In one possible design, the sending module 1104 is further configured to:

after the receiving module 1101 receives the grant authorization indication returned by the second service request end, a first authorization success prompt is sent to the first service request end, and a second authorization success prompt is sent to the second service request end.

In one possible design, the sending module 1104 is further configured to:

after the receiving module 1101 receives the indication of authorization approval replied by the second service request end, a third authorization success prompt is sent to the service provider end, where the third authorization success prompt is used to prompt that the service information is reported in the process that the service order is executed.

In a possible design, when notifying the first service request end of the acquired service information, the sending module 1104 is specifically configured to:

if the processing module 1103 detects that the first service request end sends an obtaining request for obtaining the service information before the service order is executed and the end time exceeds the first set duration, the sending module 1104 notifies the obtained service information to the first service request end.

In one possible design, the sending module 1104 is further configured to:

In one possible design, the processing module 1103 is further configured to:

acquiring service information of the set time period from the service providing terminal every set time period, and updating display page information of the service information;

the sending module 1104 is further configured to:

and informing the updated display page information to the first service request terminal.

In one possible design, the sending module 1104 is further configured to:

in the process of executing the service order, if the processing module 1103 detects that the service information cannot be obtained from the service provider within a second set time duration, the sending module 1104 sends a first exception prompt to the first service request end;

the first abnormal prompt is used for prompting that the service information acquisition fails.

In one possible design, the sending module 1104 is further configured to:

if the processing module 1103 detects that the service order is executed in advance, or detects that the travel position in the service order execution process is not changed within a third set time period, the sending module 1104 sends a second exception prompt to the first service request end;

and the second abnormal prompt is used for prompting to view the service information.

In one possible design, the service information includes recorded content.

The interaction process of each module refers to the record of the method embodiment, and is not described herein again.

By the aid of the device, the first service request terminal can timely acquire service information of the service order of the substitute call and timely acquire conditions of the service order in the execution process, so that potential safety hazards can be effectively avoided, operation experience of a third-party user can be improved, and user experience is improved.

Referring to fig. 12, a second schematic structural diagram of a service information acquiring apparatus 1200 provided in the embodiment of the present application is shown, where the apparatus 1200 includes: the sending module 1201, the receiving module 1202, and the processing module 1203 specifically:

a sending module 1201, configured to send a service request for requesting a service for a second service request end to a server, and request the server to obtain service information, where the service information is generated in a process in which a service order corresponding to the service request is executed;

a receiving module 1202, configured to obtain the service information from the server after the service order is executed by a service provider.

In one possible design, the apparatus further includes:

a processing module 1203, configured to detect whether a first obtaining option in an order displaying interface of the first service request end is triggered, where the first obtaining option is used to request to obtain the service information;

the sending module 1201, when requesting to acquire service information from the server, is specifically configured to:

if the processing module 1203 detects that the first obtaining option is triggered, the sending module 1201 sends a service request carrying obtaining request information of the service information to the server.

In one possible design, the receiving module 1202 is further configured to:

if the processing module 1203 detects that the first obtaining option is not triggered, receiving prompt interface information sent by the server, where the prompt interface information is used to prompt whether to request to obtain the service information;

the processing module 1203 is further configured to:

the sending module 1201 is further configured to:

if the processing module 1203 detects that the second obtaining option is triggered, the sending module 1201 sends obtaining request information of the service information to the server.

In one possible design, the sending module 1201 is further configured to:

if the detection module detects that a function description option in the order display interface is triggered, the sending module 1201 sends a function description obtaining request to the server;

the receiving module 1202 is further configured to:

In one possible design, the receiving module 1202 is further configured to:

after the sending module 1201 requests the server to acquire service information, a second application authorization prompt sent by the server is received, where the second application authorization prompt is used to prompt that the authorization request is sent to the second service request terminal.

In one possible design, the receiving module 1202 is further configured to:

and before the service information is acquired from the server, receiving an authorization success prompt sent by the server, wherein the authorization success prompt is used for prompting that the second service request terminal authorizes the first service request terminal to acquire the service information.

In one possible design, the sending module 1201 is specifically configured to:

the receiving module 1202 is specifically configured to:

and receiving the service information sent by the server.

In one possible design, the receiving module 1202 is further configured to:

the processing module 1203 is further configured to:

In a possible design, when receiving the service information sent by the server, the receiving module 1202 is specifically configured to:

the processing module 1203 is further configured to:

and generating a display page based on the display page information.

In one possible design, the processing module 1203, after generating the presentation page based on the presentation page information, is further configured to:

In one possible design, the service information includes recorded content.

Through the device, potential safety hazards can be effectively avoided, the operation experience of third-party users can be improved, and the user experience degree is improved.

Referring to fig. 13, a first structural schematic diagram of an electronic device according to an embodiment of the present application is shown, where the electronic device 130 includes: a processor 131, a memory 132, and a bus 133;

the memory 132 stores machine-readable instructions executable by the processor 131 (for example, execution instructions corresponding to the receiving module 1101, the dispatching module 1102, the processing module 1103, and the sending module 1104 in fig. 11, and the like), when the electronic device 130 runs, the processor 131 communicates with the memory 132 through the bus 133, and when the machine-readable instructions are executed by the processor 131, the following processes are performed:

The specific processing flow of the processor 131 may refer to the description of the above method embodiment, and is not described herein again.

Referring to fig. 14, a schematic structural diagram of an electronic device provided in an embodiment of the present application is shown, where the electronic device 140 includes: processor 141, memory 142, and bus 143;

the memory 142 stores machine-readable instructions executable by the processor 141 (for example, the execution instructions corresponding to the sending module 1201 and the receiving module 1202 in fig. 12, and the like), when the electronic device 140 runs, the processor 141 and the memory 142 communicate via the bus 143, and when the machine-readable instructions are executed by the processor 141, the following processes are performed:

the server sends a service request for requesting service for a second service request terminal, and requests the server to acquire service information, wherein the service information is generated in the process that a service order corresponding to the service request is executed;

The specific processing flow of the processor 141 may refer to the description of the above embodiments, and is not described herein again.

Based on the same technical concept, embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and the computer program is executed by a processor to perform the steps of the service information obtaining method.

Specifically, the storage medium can be a general storage medium, such as a mobile disk, a hard disk, and the like, and when a computer program on the storage medium is run, the service information acquisition method can be executed, so that potential safety hazards are avoided, the operation experience of a third-party user is improved, and the user experience is improved.

Based on the same technical concept, embodiments of the present application further provide a computer program product, which includes a computer-readable storage medium storing a program code, where instructions included in the program code may be used to execute the steps of the service information acquisition method, and specific implementation may refer to the above method embodiments, and is not described herein again.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the system and the apparatus described above may refer to the corresponding processes 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 acquisition method is applied to a server and is characterized by comprising the following steps:

2. The method of claim 1, wherein after detecting that the first service request end requests to obtain the service information generated during the execution of the service order, the method further comprises:

3. The method according to claim 1 or 2, characterized by detecting that the first service request side requests to obtain the service information generated in the process of executing the service order according to the following manner:

4. The method of claim 3, wherein if it is determined that the received service request does not carry the acquisition request information of the service information, further comprising:

5. The method of claim 4, after sending the hint interface information to the first service request side, further comprising:

6. The method of claim 3, wherein the method further comprises:

7. The method of claim 3, wherein the method further comprises:

8. The method of claim 2, after sending an authorization request to the second service requestor, further comprising:

9. The method of claim 2, wherein after receiving the grant authorization indication replied by the second service request terminal, further comprising:

10. The method of claim 2, wherein after receiving the grant authorization indication replied by the second service request side, further comprising:

11. The method as claimed in claim 1, wherein said notifying the first service request end of the acquired service information comprises:

12. The method of claim 11, wherein the method further comprises:

13. The method as claimed in claim 11, wherein said notifying the first service request end of the acquired service information comprises:

14. The method of claim 13, wherein the method further comprises:

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

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

17. The method of claim 1, wherein the service information comprises recorded content.

18. A service information acquisition method is applied to a first service request terminal, and is characterized by comprising the following steps:

19. The method of claim 18, wherein said requesting service information from the server comprises:

20. The method of claim 19, wherein if it is detected that the first acquisition option is not triggered, further comprising:

21. The method of claim 19, wherein the method further comprises:

22. The method of claim 19, wherein the method further comprises:

23. The method of claim 18, after requesting service information from the server, further comprising:

24. The method of claim 23, prior to obtaining the service information from the server, further comprising:

25. The method of claim 18, wherein obtaining the service information from the server comprises:

and receiving the service information sent by the server.

26. The method of claim 25, wherein the method further comprises:

27. The method of claim 25, wherein the receiving the service information sent by the server comprises:

and generating a display page based on the display page information.

28. The method of claim 27, wherein after generating a presentation page based on the presentation page information, the method further comprises:

29. The method of claim 18, wherein the service information comprises recorded content.

30. A service information acquisition apparatus, characterized by comprising:

31. The apparatus of claim 30, wherein the sending module is further configured to:

after the processing module detects that the first service request end requests to acquire service information generated in the process that the service order is executed, an authorization request is sent to the second service request end, wherein the authorization request is used for requesting the first service request end to be authorized to acquire the service information;

the receiving module is further configured to:

and receiving an indication of authorization for agreement replied by the second service request terminal before the processing module acquires the service information from the service provider terminal.

32. The apparatus according to claim 30 or 31, wherein the processing module, when detecting that the first service request side requests to obtain the service information generated in the process of executing the service order, is specifically configured to:

33. The apparatus of claim 32, wherein the sending module is further configured to:

if the processing module determines that the received service request does not carry the acquisition request information of the service information, the sending module sends prompt interface information to the first service request end, wherein the prompt interface information is used for prompting whether to request to acquire the service information;

the receiving module is further configured to:

34. The apparatus as claimed in claim 33, wherein said sending module, after sending the prompt interface information to the first service request end, is further configured to:

if the receiving module still does not receive the service information acquisition request information sent by the first service request end aiming at the prompt interface information after the service order is executed by the service provider end, the sending module indicates the first service request end to cancel displaying the prompt interface generated based on the prompt interface information.

35. The apparatus of claim 32, wherein the receiving module is further configured to:

the sending module is further configured to:

36. The apparatus of claim 32, wherein the sending module is further configured to:

37. The apparatus of claim 31, wherein the sending module, after sending the authorization request to the second service requestor, is further configured to:

38. The apparatus of claim 31, wherein the sending module is further configured to:

after the receiving module receives the indication of agreeing to authorization replied by the second service request terminal, a first authorization success prompt is sent to the first service request terminal, and a second authorization success prompt is sent to the second service request terminal.

39. The apparatus of claim 31, wherein the sending module is further configured to:

and after the receiving module receives an authorization approval indication replied by the second service request terminal, sending a third authorization success prompt to the service providing terminal, wherein the third authorization success prompt is used for prompting that the service information is reported in the process that the service order is executed.

40. The apparatus of claim 30, wherein the sending module, when notifying the first service request end of the acquired service information, is specifically configured to:

and if the processing module detects that the first service request end sends an acquisition request for acquiring the service information before the service order is executed and the end time exceeds the first set time length, the sending module notifies the acquired service information to the first service request end.

41. The apparatus of claim 40, wherein the sending module is further configured to:

42. The apparatus of claim 40, wherein the sending module, when notifying the first service request end of the acquired service information, is specifically configured to:

43. The apparatus of claim 42, wherein the processing module is further configured to:

the sending module is further configured to:

44. The apparatus of claim 30, wherein the sending module is further configured to:

in the process of executing the service order, if the processing module detects that the service information cannot be acquired from the service provider within a second set time length, the sending module sends a first exception prompt to the first service request end;

45. The apparatus of claim 30, wherein the sending module is further configured to:

if the processing module detects that the service order is executed in advance, or detects that the travel position in the service order execution process is not changed within a third set time length, the sending module sends a second exception prompt to the first service request end;

46. The apparatus of claim 30, wherein the service information comprises recorded content.

47. A service information acquisition apparatus, characterized by comprising:

48. The apparatus of claim 47, wherein the apparatus further comprises:

the processing module is used for detecting whether a first acquisition option in an order display interface of the first service request terminal is triggered, wherein the first acquisition option is used for requesting to acquire the service information;

the sending module, when requesting to obtain the service information from the server, is specifically configured to:

if the processing module detects that the first acquisition option is triggered, the sending module sends a service request carrying the acquisition request information of the service information to the server.

49. The apparatus of claim 48, wherein the receiving module is further configured to:

if the processing module detects that the first acquisition option is not triggered, receiving prompt interface information sent by the server, wherein the prompt interface information is used for prompting whether to request to acquire the service information;

the processing module is further configured to:

the sending module is further configured to:

and if the processing module detects that the second acquisition option is triggered, the sending module sends acquisition request information of the service information to the server.

50. The apparatus of claim 48, wherein the sending module is further configured to:

if the detection module detects that the function specification option in the order display interface is triggered, the sending module sends a function specification obtaining request to the server;

the receiving module is further configured to:

51. The apparatus of claim 48, wherein the receiving module is further configured to:

52. The apparatus of claim 47, wherein the receiving module is further configured to:

and after the sending module requests the server to acquire service information, receiving a second application authorization prompt sent by the server, wherein the second application authorization prompt is used for prompting that the authorization request is sent to the second service request terminal.

53. The apparatus of claim 52, wherein the receiving module is further configured to:

54. The apparatus of claim 47, wherein the sending module is specifically configured to:

the receiving module is specifically configured to:

and receiving the service information sent by the server.

55. The apparatus of claim 54, wherein the receiving module is further configured to:

the processing module is further configured to:

56. The apparatus of claim 54, wherein the receiving module, when receiving the service information sent by the server, is specifically configured to:

the processing module is further configured to:

and generating a display page based on the display page information.

57. The apparatus of claim 56, wherein the processing module, after generating a presentation page based on the presentation page information, is further to:

58. The apparatus of claim 47, wherein the service information comprises recorded content.

59. 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 operating, the processor executing the machine-readable instructions to perform the steps of the service information acquisition method according to any one of claims 1 to 17.

60. 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 operating, the processor executing the machine-readable instructions to perform the steps of the service information acquisition method according to any one of claims 18 to 29.

61. A computer-readable storage medium, having stored thereon a computer program which, when being executed by a processor, is adapted to carry out the steps of the service information acquisition method according to any one of claims 1 to 17 or the steps of the service information acquisition method according to any one of claims 18 to 29.