CN114237938B

CN114237938B - Vehicle driving service processing method and device

Info

Publication number: CN114237938B
Application number: CN202111555762.4A
Authority: CN
Inventors: 郭炯光; 李辉; 牛秀元; 李廷温; 卢声晓; 王赛; 王勇; 钟宜冉
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2021-12-17
Filing date: 2021-12-17
Publication date: 2024-05-07
Anticipated expiration: 2041-12-17
Also published as: CN114237938A

Abstract

The embodiment of the specification provides a vehicle driving service processing method and a device, wherein the vehicle driving service processing method is applied to a user terminal and comprises the following steps: the service subprogram of the application program calls a near field communication interface to establish near field communication connection with the target vehicle; displaying an access prompt of a driving mode through the application program; sending a verification request to a first server after the access prompt is triggered so as to verify service data pushing based on the near field communication connection and remote connection; and entering a driving mode of the application program, and updating application page display based on the service data of the driving mode pushed by the first server.

Description

Vehicle driving service processing method and device

Technical Field

The present document relates to the field of data processing technologies, and in particular, to a vehicle driving service processing method and device.

Background

With the continuous development of economy and the increasing improvement of the living standard of users, motor vehicles are rapidly popularized, the demand of users for the motor vehicles is also continuously increased, the holding quantity of the motor vehicles is continuously increased, private vehicles are frequently and frequently traveling, and the demand of users in the driving traveling process is also diversified. Meanwhile, along with the increasing of the intelligent level of the vehicle terminal, how to effectively combine the improvement of the intelligent level of the vehicle terminal with the actual vehicle driving scene, thereby providing convenience for the vehicle driving of users and becoming the focus of increasing attention of vehicle enterprises and vehicle service providers.

Disclosure of Invention

One or more embodiments of the present specification provide a vehicle driving service processing method, which is applied to a user terminal, and the method includes: the service subroutine of the application program invokes the near field communication interface to establish a near field communication connection with the target vehicle. And displaying the access prompt of the driving mode through the application program. And sending a verification request to the first server after the access prompt is triggered so as to verify service data pushing based on the near field communication connection and remote connection. And entering a driving mode of the application program, and updating application page display based on the service data of the driving mode pushed by the first server.

One or more embodiments of the present specification provide another vehicle driving service processing method applied to a first server, the method including: receiving a verification request of a driving mode of an application program submitted by a user terminal; the verification request is generated by a service subroutine of the application. And based on the verification request, verifying service data pushing based on near field communication connection and remote connection in the driving mode. And pushing the service data of the driving mode to the user terminal according to the verification result.

One or more embodiments of the present specification provide a vehicle driving service processing apparatus, which operates in a user terminal, the apparatus including: and the near field communication connection establishment module is configured to call a near field communication interface by a service subprogram of the application program to establish near field communication connection with the target vehicle. And the access prompt display module is configured to display the access prompt of the driving mode through the application program. And the verification request sending module is configured to send a verification request to the first server after the access prompt is triggered so as to verify service data pushing based on the near field communication connection and remote connection. And the driving mode entering module is configured to enter a driving mode of the application program and update application page display based on the service data of the driving mode pushed by the first server.

One or more embodiments of the present specification provide another vehicle driving service processing apparatus, which operates on a first server, the apparatus including: the verification request receiving module is configured to receive a verification request of a driving mode of an application program submitted by a user terminal; the verification request is generated by a service subroutine of the application. And the service data pushing verification module is configured to verify service data pushing based on near field communication connection and remote connection in the driving mode based on the verification request. And the service data pushing module is configured to push the service data of the driving mode to the user terminal according to the verification result.

One or more embodiments of the present specification provide a vehicle driving service processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: the service subroutine of the application program invokes the near field communication interface to establish a near field communication connection with the target vehicle. And displaying the access prompt of the driving mode through the application program. And sending a verification request to the first server after the access prompt is triggered so as to verify service data pushing based on the near field communication connection and remote connection. And entering a driving mode of the application program, and updating application page display based on the service data of the driving mode pushed by the first server.

One or more embodiments of the present specification provide another vehicle driving service processing apparatus including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to: receiving a verification request of a driving mode of an application program submitted by a user terminal; the verification request is generated by a service subroutine of the application. And based on the verification request, verifying service data pushing based on near field communication connection and remote connection in the driving mode. And pushing the service data of the driving mode to the user terminal according to the verification result.

One or more embodiments of the present specification provide a storage medium storing computer-executable instructions that, when executed by a processor, implement the following: the service subroutine of the application program invokes the near field communication interface to establish a near field communication connection with the target vehicle. And displaying the access prompt of the driving mode through the application program. And sending a verification request to the first server after the access prompt is triggered so as to verify service data pushing based on the near field communication connection and remote connection. And entering a driving mode of the application program, and updating application page display based on the service data of the driving mode pushed by the first server.

One or more embodiments of the present specification provide another storage medium storing computer-executable instructions that, when executed by a processor, implement the following: receiving a verification request of a driving mode of an application program submitted by a user terminal; the verification request is generated by a service subroutine of the application. And based on the verification request, verifying service data pushing based on near field communication connection and remote connection in the driving mode. And pushing the service data of the driving mode to the user terminal according to the verification result.

Drawings

For a clearer description of one or more embodiments of the present description or of the solutions of the prior art, the drawings that are needed in the description of the embodiments or of the prior art will be briefly described below, it being obvious that the drawings in the description that follow are only some of the embodiments described in the present description, from which other drawings can be obtained, without inventive faculty, for a person skilled in the art;

FIG. 1 is a process flow diagram of a vehicle driving service processing method provided in one or more embodiments of the present disclosure;

FIG. 2 is a timing diagram of a vehicle driving service processing method for use in a vehicle driving scenario according to one or more embodiments of the present disclosure;

FIG. 3 is a process flow diagram of another vehicle driving service processing method provided by one or more embodiments of the present disclosure;

FIG. 4 is a schematic diagram of a vehicle driving service processing device according to one or more embodiments of the present disclosure;

FIG. 5 is a schematic diagram of another vehicle driving service processing device provided by one or more embodiments of the present disclosure;

Fig. 6 is a schematic structural view of a vehicle driving service processing apparatus provided in one or more embodiments of the present specification;

Fig. 7 is a schematic structural view of another vehicle driving service processing apparatus provided in one or more embodiments of the present specification.

Detailed Description

In order to enable a person skilled in the art to better understand the technical solutions in one or more embodiments of the present specification, the technical solutions in one or more embodiments of the present specification will be clearly and completely described below with reference to the drawings in one or more embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one or more embodiments of the present disclosure without inventive effort, are intended to be within the scope of the present disclosure.

The embodiment of the vehicle driving service processing method provided in the specification comprises the following steps:

Referring to fig. 1, the vehicle driving service processing method provided in the present embodiment is applied to a user terminal, and specifically includes steps S102 to S108.

In step S102, the service subroutine of the application program invokes the near field communication interface to establish a near field communication connection with the target vehicle.

According to the vehicle driving service processing method, on the basis of performing driving mode registration based on the near field communication connection mode and the remote connection mode, the access prompt of the driving mode is displayed by detecting the near field communication connection mode or the remote connection mode of the target vehicle so as to prompt the user to enter the driving mode of the application program, and after the access prompt is triggered, a verification request is sent to the first server so as to perform idempotent verification on service data pushing based on the near field communication connection mode and the remote connection mode, service data pushing repetition caused by the service data pushing based on the near field communication connection mode and the remote connection mode is avoided through the idempotent verification of the service data pushing, and the service data pushed after verification is sent to the user terminal so as to display the pushed service data in the driving mode of the application program, so that driving service with better experience is provided for the user by means of the driving mode of the application program, and meanwhile, the access experience of the application program is improved.

The application program in this embodiment is running on a user terminal, and the application program is configured with a service subroutine, through which binding between a user and a vehicle service can be achieved, the bound vehicle is the target vehicle, the bound user is called a vehicle owner user, and the target vehicle is the target vehicle associated with the vehicle owner user under the service subroutine; in addition, the service subprogram can also realize the related services of opening, canceling, registering, entering, exiting and the like of the driving mode of the application program, and a server which cooperates with the service subprogram at a service side is called a first server.

The driving mode is a mode of providing a vehicle driving related service to a vehicle owner user of the driving target vehicle, for example, after entering the driving mode, providing the vehicle owner user of the driving target vehicle with the related service in the vehicle driving process of navigation, music, conversation and the like. The driving mode is configured for the application program, the application program provides driving related services in the application program after entering the driving mode, and in addition, the driving mode may also be configured for a service sub-program of the application program, or configured for a user terminal running the application program, and specific implementation processes and implementation process types configured for the application program are not described in detail herein.

In a specific implementation, the service sub-program of the application program establishes a near field communication connection with the target vehicle by calling a near field communication interface, where the near field communication connection is that between a user terminal and the target vehicle, and it is to be noted that, a near field communication component for establishing a near field communication connection between one side of the target vehicle and the user terminal refers to a near field communication component configured by the target vehicle or a near field communication component of an electronic device placed in the target vehicle, such as a bluetooth communication component of a bluetooth speaker placed in the target vehicle, and in this embodiment, whether a vehicle owner user carrying the user terminal is near the target vehicle is detected by whether the near field communication connection is established, that is, whether the vehicle owner user is in a "driving state" is detected.

In an optional implementation manner provided in this embodiment, after the service subroutine of the application program invokes the near field communication interface to establish a near field communication connection with the target vehicle, whether the near field communication component on the side of the target vehicle performs driving mode registration is detected by determining whether a driving mode registration record exists in the near field communication component that establishes the near field communication connection with the user terminal, if so, it is indicated that the near field communication component on the side of the target vehicle has performed driving mode registration, and the processing in the following step S104 is performed; if the near field communication module on the side of the target vehicle does not exist, the near field communication module on the side of the target vehicle does not perform driving mode registration, and the driving mode registration prompt of whether the near field communication module on the side of the target vehicle performs driving mode registration is displayed or not.

In a specific implementation process, the driving mode registration record is generated after the driving mode registration is performed, and this embodiment provides a registration manner based on two driving modes of near field communication connection and remote connection, and the following describes the registration process of the two driving modes respectively.

In a first alternative implementation provided in this embodiment, the driving mode registration based on the near field communication connection is implemented in the following manner:

After the service subprogram calls the near field communication interface to establish near field communication connection with a near field communication component of the target vehicle, saving a component identifier of the near field communication component, and uploading the component identifier to the first server so as to register a driving mode aiming at the near field communication component; correspondingly, after receiving the uploaded component identifier, the first server performs driving mode registration of the near field communication component based on the component identifier, and generates a driving mode registration record of the near field communication component.

In a second alternative implementation provided in this embodiment, the driving mode registration corresponding to the remote connection is performed in the following manner:

If a remote connection registration instruction submitted by the service subprogram is detected, generating a registration request carrying a user identifier and sending the registration request to the first server so as to register a driving mode aiming at a target vehicle bound by the user identifier; correspondingly, after receiving the registration request carrying the user identifier, the first server carries out remote connection driving mode registration for the target vehicle mapped by the user identifier, and generates a driving mode registration record for the remote connection.

It should be noted that, when the driving mode registration is performed, any one of the above two driving mode registration modes based on the near field communication connection and the remote connection may be used to perform the driving mode registration, and in addition, the two driving mode registration modes may be also used to perform the driving mode registration respectively. On the basis of the driving mode registration by adopting the two registration modes, the corresponding service data pushing can be performed after the driving mode registration is performed by adopting the two registration modes, namely: if the near field communication connection is detected to be established and the remote connection is detected to be also established, service data pushing is performed based on the near field communication connection and service data pushing is performed based on the remote connection, so that in order to avoid generating repeated service data pushing, a verification request is sent to the first server through the following step S106 to verify the service data pushing based on the near field communication connection and the remote connection, so that the repeated service data pushing is prevented from disturbing a user of a vehicle owner.

In this embodiment, on the basis of the application program configuring the service sub-program, in order to further improve the comprehensiveness of the service provided to the vehicle owner user in the driving mode, so as to improve the driving service experience of the vehicle owner user, a vehicle sub-program may be configured for the application program, and services related to the vehicle, such as vehicle condition data query access, are provided by the vehicle sub-program, so as to enrich service interaction in the vehicle driving process, where a server that cooperates with the vehicle sub-program on the service side is referred to as a second server. The vehicle subprogram comprises a vehicle enterprise applet provided by the application program, and the second server comprises a vehicle enterprise server provided by the vehicle enterprise of the target vehicle.

In a specific implementation, on the basis that the application program configures the service subprogram and the vehicle subprogram, in order to improve the perception of a vehicle owner user on a driving mode and further improve the interactivity in the process of accessing the driving mode, the embodiment also provides specific implementation of opening the driving mode, specifically, when an opening instruction submitted through a front end page of the service subprogram is detected, the vehicle subprogram of the application program is jumped to, after authorization processing is performed by the vehicle subprogram, the driving mode opening request is submitted to a second server, and after the driving mode opening request is received by the second server, the second server cooperates with the first server to perform driving mode opening.

Specifically, in order to ensure the safety in the driving mode opening process, identity verification is introduced in the driving mode opening process, and for this, in an alternative implementation provided by this embodiment, the driving mode opening is specifically implemented in the following manner:

(1) If an opening instruction submitted through a front-end page of the service subprogram is detected, jumping to a vehicle subprogram of the application program;

(2) The vehicle subprogram calls an authorization interface to carry out authorization processing and submits a driving mode opening request to a second server;

After receiving a driving mode opening request, the second server sends a token application to the first server, the first server generates a service token of the target vehicle according to the token application and returns the service token to the second server, and after obtaining the service token, the second server sends a user inquiry request carrying the service token to the first server, performs identity verification processing according to user identity information returned by the first server through identity information inquiry, and returns an identity verification result to the vehicle subprogram;

(3) Receiving an authentication result returned by the second server and returning the authentication result to the service subprogram;

(4) And the service subprogram synchronizes the identity verification result to the first server according to the returned identity verification result so as to conduct driving mode opening.

And after receiving the identity verification result synchronized by the service subprogram, the first server opens the driving mode of the application program if the identity verification result is that the identity verification passes.

Step S104, displaying the access prompt of the driving mode through the application program.

After the service subprogram of the application program invokes the near field communication interface to establish near field communication connection with the target vehicle, in this step, the application program displays the access prompt of the driving mode, for example, the access prompt of the driving mode is displayed in an application page of the application program in a waist-seal message prompt mode, or the access prompt of the driving mode is displayed in a message push mode, after the access prompt of the driving mode is displayed, if the access prompt is triggered, it indicates that a vehicle owner wants to enter the driving mode of the application program, and if the access prompt is not triggered, the vehicle owner does not need to process.

During the implementation, the display of the access prompt can be controlled through the state machine, so that the rationality of the access prompt display is improved, the trouble brought to a vehicle owner user by frequent prompt or repeated prompt is avoided, and the display of the access prompt controlled through the state machine specifically comprises the following steps:

Displaying the access prompt and recording the state of the access prompt;

If the state of the access prompt is not triggered, the access prompt is not processed;

if the state of the access prompt is that the prompt is deleted, displaying the access prompt according to a preset time interval;

And if the near field communication connection is detected to be disconnected, resetting the state of the access prompt recorded by the state machine, and after resetting the state, returning to execute the state operation of displaying the access prompt and recording the access prompt if the near field communication connection with the target vehicle is detected to be established again.

In addition to the above-mentioned presentation of the access prompt of the driving mode based on the establishment of the near field communication connection, in order to further improve the access convenience and flexibility of the driving mode, the presentation of the access prompt of the driving mode may be further performed based on remote connection, and optionally, the vehicle terminal of the target vehicle uploads the start instruction to the second server after detecting the start instruction of the target vehicle, the second server synchronizes the start instruction to the first server, and issues a prompt presentation command of the driving mode to the service subroutine via the first server, where the service subroutine presents the access prompt based on the prompt presentation command.

It should be noted that, the verification process performed after the access alert for the driving mode shown by the remote connection is triggered is similar to the verification process performed after the access alert for the driving mode shown by the near field communication connection is triggered, and the verification is performed by matching with the first server, specifically referring to the verification and service data display processes provided in the following steps S106 to S108.

And step S106, after the access prompt is triggered, a verification request is sent to the first server so as to verify the service data push based on the near field communication connection and remote connection.

Optionally, sending a verification request to the first server includes: submitting, by a controller of the service sub-program, an access instruction generated after the access reminder is triggered to a front-end page of the service sub-program, the front-end page generating the check request based on the access instruction and sending the check request to the first server; or submitting the verification request to the front-end page by the controller, and synchronizing the front-end page to the first server.

As described above, the driving mode registration includes two modes of driving mode registration based on the near field communication connection and driving mode registration based on the remote connection, and on the basis of performing driving mode registration by adopting the two modes, since the two modes can perform corresponding service data pushing, in order to avoid generating repeated service data pushing, it is necessary to check the service data pushing based on the near field communication connection and the remote connection, so as to avoid disturbing the user of the vehicle owner by the repeated service data pushing. Specifically, the service data pushing based on the near field communication connection is performed on the basis of detecting that the near field communication connection between the user terminal and the target vehicle is established, and the service data pushing based on the remote connection is performed on the basis of uploading a start command to the vehicle terminal of the target vehicle, optionally, if the driving mode registration is performed in a remote connection mode, uploading the start command of the target vehicle to the second server through the vehicle terminal of the target vehicle, and synchronizing the start command to the first server by the second server, wherein after receiving the start command, the first server also needs to verify the service data pushing based on the near field communication connection and the remote connection.

In an optional implementation manner provided in this embodiment, the checking, by the first server, service data push based on the near field communication connection and remote connection specifically includes: and performing idempotent verification on the service data pushing triggered by the near field communication connection and the service data pushing triggered by the remote connection in the driving mode.

The idempotent verification refers to performing idempotent control on service data pushing based on established near field communication connection and service data pushing based on remote connection after the vehicle is started, and aims to perform service data pushing in one mode after verification under the condition that both service data pushing based on near field communication connection and service data pushing based on remote connection are triggered, so that the repeated service data pushing is prevented from disturbing a vehicle owner user.

In the idempotent calibration process, the calibration process can be performed according to a pre-configured calibration rule, for example, the calibration process is performed according to a time priority rule, that is, the service data push with the previous trigger time is normally executed, the service data push with the subsequent trigger time is no longer executed, or the calibration process is performed according to a push priority rule, if the push priority of the near field communication connection mode is lower than the push priority of the remote connection mode, the service data push based on the near field communication connection is no longer executed, and the service data push based on the remote connection is normally executed.

And step S108, entering a driving mode of the application program, and updating application page display based on the service data of the driving mode pushed by the first server.

After the verification request is sent to the first server, the first server verifies the service data pushed to the user terminal and pushes the service data to the user terminal according to the verification result, then enters a driving mode of the application program, and updates application page display of the application program based on the service data of the driving mode pushed by the first server. In addition, the driving mode of the application program can be entered after the access prompt is triggered, and the application page display of the application program can be updated according to the service data determined after the verification.

In a specific implementation, on the basis of entering the driving mode of the application program, the data interaction processing can be implemented by collecting driving related data of a driving user of the target vehicle in the driving process and performing the data interaction processing with the first server based on the driving related data, and in an alternative implementation provided by this embodiment, the following manner is adopted:

Collecting driving interaction data of a driving user of the target vehicle and submitting the driving interaction data to the first server;

Receiving interaction response data of the driving interaction data issued by the first server;

For example, user characteristic data of a driving user is collected through a user terminal, the collected user characteristic data is uploaded to a first server for monitoring, whether the driving user is in a safe driving state or not is monitored, and if the driving user is in the safe driving state, the user characteristic data collection and the monitoring process are continued; and if the vehicle is in the unsafe driving state, feeding back a driving prompt to the user terminal.

In another optional implementation manner provided in this embodiment, the data interaction processing is implemented in the following manner:

Submitting a vehicle condition query request to the first server according to the acquired vehicle condition query instruction;

And receiving the vehicle condition data of the target vehicle, which is inquired and issued by the first server, and displaying the vehicle condition data through the service subprogram.

In this embodiment, the application program refers to a third party application program installed in the user terminal, and may be configured with other subroutines or functional modules besides a service subroutine, for example, a payment application configured with a main service subroutine, in order to avoid affecting normal use of the application program, an exit mechanism of a driving mode of the application program is further provided, and optionally, if it is detected that the near field communication connection is interrupted, a connection interruption reminder is displayed through the application program; and exiting the driving mode of the application program after the connection interruption reminding is triggered.

The following describes the vehicle driving service processing method provided in this embodiment further by taking an application of the vehicle driving service processing method provided in this embodiment to a vehicle driving scene as an example, and referring to fig. 2, the vehicle driving service processing method applied to the vehicle driving scene specifically includes the following steps.

In step S202, the service subroutine of the application program invokes the near field communication interface to establish a near field communication connection with the target vehicle.

Step S204, the access prompt of the driving mode is displayed through the application program.

In step S206, the controller of the service sub-program submits an access instruction generated after the access reminder is triggered to the front-end page of the service sub-program, and the front-end page generates a verification request based on the access instruction.

In step S208, the front page of the service subroutine sends a check request to the first server to perform idempotent checks on the service data push based on the near field communication connection and the remote connection.

Step S218, service data of the driving mode pushed by the first server is received.

Step S220, entering a driving mode of the application program, and updating application page display of the application program based on service data of the driving mode.

In step S222, if the near field communication connection is detected to be interrupted, a connection interruption reminder is displayed by the application program.

In step S224, the driving mode of the application program is exited after the connection interruption reminder is triggered.

Another embodiment of the vehicle driving service processing apparatus provided in the present specification is as follows:

In the above embodiment, a vehicle driving service processing method applied to a user terminal is provided, and in cooperation with the vehicle driving service processing method, a vehicle driving service processing method applied to a first server is also provided, and because the vehicle driving service processing method applied to the first server and the vehicle driving service processing method applied to the user terminal are mutually matched in the execution process, the description is relatively simple, and corresponding content can be found in the corresponding description of the embodiment of the vehicle driving service processing method applied to the user terminal provided above. The method embodiments described below are merely illustrative.

Referring to fig. 3, the vehicle driving service processing method provided in the present embodiment is applied to a first server, and the method specifically includes steps S302 to S306.

Step S302, a verification request of a driving mode of an application program submitted by a user terminal is received.

The application program of the embodiment is run on the user terminal, and is configured with a service subprogram, through which service binding between the user and the vehicle can be realized, the bound vehicle is called a target vehicle, and the bound user is called a vehicle owner user; in addition, the service subprogram can also realize the related services of opening, canceling, registering, entering, exiting and the like of the driving mode of the application program, and a server which cooperates with the service subprogram at a service side is called a first server.

In particular implementations, the verification request is generated by a service subroutine of the application. Optionally, the verification request is sent by a front-end page of the service sub-program, and the verification request is generated after the front-end page receives an access instruction of the service sub-program for the access prompt of the driving mode; or the front-end page of the service subprogram synchronizes after receiving the verification request sent by the controller of the service subprogram.

In this embodiment, two registration modes of driving modes are provided: the driving mode registration based on the near field communication connection and the remote connection driving mode registration can be adopted to perform driving mode registration in any one of the two driving mode registration modes based on the near field communication connection and the remote connection when the driving mode registration is performed, and in addition, the two driving mode registration modes can be respectively adopted to perform driving mode registration. On the basis of the driving mode registration by adopting the two registration modes, the corresponding service data pushing can be performed after the driving mode registration is performed by adopting the two registration modes, namely: if the establishment of the near field communication connection is detected and the establishment of the remote connection is detected, the service data push is performed based on the near field communication connection and the service data push is performed based on the remote connection, so that in order to avoid the repeated service data push, the user terminal makes a request for performing service data push verification by sending the verification request to the first server.

Specifically, in the first optional implementation manner provided in this embodiment, the driving mode registration based on the near field communication connection is implemented in the following manner:

receiving a component identifier of a near field communication component of the target vehicle uploaded by the user terminal;

And performing driving mode registration of the near field communication component based on the component identification, and generating a driving mode registration record of the near field communication component.

In a second optional implementation manner provided in this embodiment, the driving mode registration based on the near field communication connection is implemented in the following manner:

Receiving a registration request carrying a user identifier sent by the user terminal; the registration request is generated after a remote connection registration instruction submitted by the service subprogram is detected;

and performing remote connection driving mode registration for the target vehicle mapped by the user identification, and generating a driving mode registration record for the remote connection.

In a specific implementation, on the basis that the application program configures the service subprogram and the vehicle subprogram, in order to improve the perception of a vehicle owner user on a driving mode and further improve the interactivity in the access process of the driving mode, the embodiment further provides an implementation manner of opening the driving mode, and in an alternative implementation manner provided in the embodiment, the opening process of the driving mode specifically includes:

(1) Receiving a token application sent by a second server aiming at a driving mode opening request submitted by the user terminal;

(2) Generating a service token of the target vehicle and returning the service token to the second server;

(3) Receiving a user inquiry request carrying the service token sent by the second server and inquiring user identity information;

(4) Returning the queried user identity information to the second server to perform identity verification processing;

(5) And receiving the identity verification result synchronized by the service subprogram, and opening the driving mode of the application program.

Step S304, based on the verification request, verifying service data pushing based on near field communication connection and remote connection in the driving mode.

In an optional implementation manner provided in this embodiment, verifying based on service data push of the near field communication connection and the remote connection specifically includes: and performing idempotent verification on service data pushing triggered based on the near field communication connection and service data pushing triggered by the remote connection in the driving mode.

It should be noted that, in addition to the verification performed according to the verification request sent by the user terminal provided above, the above verification process may also be performed after the vehicle owner user detects the start of the target vehicle on the basis of the driving mode registration performed by the remote connection, and optionally, the vehicle machine terminal of the target vehicle associated with the service subroutine uploads the start instruction to the second server after detecting the start instruction of the target vehicle, and the second server synchronizes the start instruction to the first server to perform the verification.

Step S306, service data of the driving mode are pushed to the user terminal according to the verification result.

In a specific implementation, by collecting driving related data of a driving user of the target vehicle in a driving process and performing data interaction processing with the first server based on the driving related data, in an alternative implementation provided by this embodiment, the data interaction processing is implemented in the following manner:

Receiving driving interaction data of a driving user of the target vehicle submitted by the user terminal, and performing driving interaction processing based on the driving interaction data to obtain interaction response data of the driving interaction data;

Issuing interactive response data of the driving interactive data to the user terminal;

receiving a vehicle condition query request of the target vehicle submitted by the user terminal;

and inquiring vehicle condition data corresponding to the vehicle identifier at a second server based on the vehicle identifier carried by the vehicle condition inquiry request and issuing the vehicle condition data to the user terminal.

Step S210, a vehicle start command synchronized by the second server is received.

And the vehicle starting instruction is uploaded to the second server by the vehicle subprogram of the application program after the vehicle starting instruction is detected.

Step S212, a verification request of a driving mode of the application program submitted by the user terminal is received.

Wherein the verification request is generated by a service sub-program of the application program after establishing the near field communication connection with the target vehicle.

Step S214, based on the verification request, performing idempotent verification on the service data push based on the near field communication connection and the remote connection in the driving mode.

Step S216, service data of pushing driving modes to the user terminal is determined according to the verification result.

An embodiment of a vehicle driving service processing apparatus provided in the present specification is as follows:

In the above-described embodiments, a vehicle driving service processing method applied to a user terminal is provided, and correspondingly, a vehicle driving service processing apparatus applied to a user terminal is also provided, and the following description is made with reference to the accompanying drawings.

Referring to fig. 4, a schematic diagram of a vehicle driving service processing apparatus provided in the present embodiment is shown.

Since the apparatus embodiments correspond to the method embodiments, the description is relatively simple, and the relevant portions should be referred to the corresponding descriptions of the method embodiments provided above. The device embodiments described below are merely illustrative.

The embodiment provides a vehicle driving service processing device, which is operated on a user terminal, and the device comprises:

a near field communication connection establishment module 402 configured to invoke a near field communication interface by a service subroutine of the application program to establish a near field communication connection with the target vehicle;

An access reminder presentation module 404 configured to present access reminders for driving patterns via the application;

A check request sending module 406 configured to send a check request to the first server after the access alert is triggered, to check the service data push based on the near field communication connection and the remote connection;

The driving mode entering module 408 is configured to enter a driving mode of the application program and update an application page presentation based on the service data of the driving mode pushed by the first server.

in the above-described embodiments, a vehicle driving service processing method applied to a first server is provided, and a vehicle driving service processing apparatus operating on the first server is provided correspondingly, and is described below with reference to the accompanying drawings.

Referring to fig. 5, a schematic diagram of a vehicle driving service processing apparatus provided in the present embodiment is shown.

The present embodiment provides a vehicle driving service processing device, which operates on a first server, and includes:

a check request receiving module 502 configured to receive a check request of a driving mode of an application program submitted by a user terminal; the verification request is generated by a service subroutine of the application program;

A service data push verification module 504 configured to verify, based on the verification request, service data push based on near field communication connection and remote connection in the driving mode;

And a service data pushing module 506 configured to push the service data of the driving mode to the user terminal according to the verification result.

In response to the above-described vehicle driving service processing method applied to the user terminal, one or more embodiments of the present disclosure further provide a vehicle driving service processing device for executing the above-provided vehicle driving service processing method, and fig. 6 is a schematic structural diagram of a vehicle driving service processing device provided by one or more embodiments of the present disclosure, based on the same technical concept.

The vehicle driving service processing apparatus provided in the present embodiment includes:

As shown in fig. 6, the vehicle driving service processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 601 and a memory 602, where the memory 602 may store one or more storage applications or data. Wherein the memory 602 may be transient storage or persistent storage. The application programs stored in the memory 602 may include one or more modules (not shown), each of which may include a series of computer-executable instructions in the vehicle driving service processing device. Still further, the processor 601 may be arranged to communicate with the memory 602, executing a series of computer executable instructions in the memory 602 on the vehicle driving service processing device. The vehicle driving service processing device may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input/output interfaces 605, one or more keyboards 606, and the like.

In one particular embodiment, a vehicle driving service processing device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the vehicle driving service processing device, and configured to be executed by one or more processors, the one or more programs including computer-executable instructions for:

The service subprogram of the application program calls a near field communication interface to establish near field communication connection with the target vehicle;

Displaying an access prompt of a driving mode through the application program;

Sending a verification request to a first server after the access prompt is triggered so as to verify service data pushing based on the near field communication connection and remote connection;

and entering a driving mode of the application program, and updating application page display based on the service data of the driving mode pushed by the first server.

Another vehicle driving service processing apparatus embodiment provided in the present specification is as follows:

Corresponding to a vehicle driving service processing method applied to the first server described above, one or more embodiments of the present disclosure further provide another vehicle driving service processing apparatus for performing the vehicle driving service processing method provided above, based on the same technical concept, and fig. 7 is a schematic structural diagram of one or more embodiments of the present disclosure.

As shown in fig. 7, the vehicle driving service processing device may have a relatively large difference due to different configurations or performances, and may include one or more processors 701 and a memory 702, where the memory 702 may store one or more storage applications or data. Wherein the memory 702 may be transient storage or persistent storage. The application programs stored in the memory 702 may include one or more modules (not shown in the figures), each of which may include a series of computer-executable instructions in the vehicle driving service processing device. Still further, the processor 701 may be configured to communicate with the memory 702 and execute a series of computer executable instructions in the memory 702 on the vehicle driving service processing device. The vehicle driving service processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input/output interfaces 705, one or more keyboards 706, and the like.

receiving a verification request of a driving mode of an application program submitted by a user terminal; the verification request is generated by a service subroutine of the application program;

based on the verification request, verifying service data pushing based on near field communication connection and remote connection in the driving mode;

And pushing the service data of the driving mode to the user terminal according to the verification result.

An embodiment of a storage medium provided in the present specification is as follows:

corresponding to the above-described vehicle driving service processing method applied to the user terminal, one or more embodiments of the present specification further provide a storage medium based on the same technical concept.

The storage medium provided in this embodiment is configured to store computer executable instructions that, when executed by a processor, implement the following flow:

Displaying an access prompt of a driving mode through the application program;

It should be noted that, the embodiments of the storage medium in the present specification and the embodiments of the vehicle driving service processing method in the present specification are based on the same inventive concept, so that the specific implementation of the embodiments may refer to the implementation of the corresponding methods, and the repetition is omitted.

Another storage medium embodiment provided in this specification is as follows:

corresponding to the above-described vehicle driving service processing method applied to the first server, one or more embodiments of the present specification further provide a storage medium based on the same technical idea.

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

In the 30 s of the 20 th century, improvements to one technology could clearly be distinguished as improvements in hardware (e.g., improvements to circuit structures such as diodes, transistors, switches, etc.) or software (improvements to the process flow). However, with the development of technology, many improvements of the current method flows can be regarded as direct improvements of hardware circuit structures. Designers almost always obtain corresponding hardware circuit structures by programming improved method flows into hardware circuits. Therefore, an improvement of a method flow cannot be said to be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (e.g., field programmable gate array (Field Programmable GATE ARRAY, FPGA)) is an integrated circuit whose logic functions are determined by user programming of the device. A designer programs to "integrate" a digital system onto a PLD without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, such programming is mostly implemented with "logic compiler (logic compiler)" software, which is similar to the software compiler used in program development and writing, and the original code before being compiled is also written in a specific programming language, which is called hardware description language (Hardware Description Language, HDL), but HDL is not just one, but a plurality of kinds, such as ABEL(Advanced Boolean Expression Language)、AHDL(Altera Hardware Description Language)、Confluence、CUPL(Cornell University Programming Language)、HDCal、JHDL(Java Hardware Description Language)、Lava、Lola、MyHDL、PALASM、RHDL(Ruby Hardware Description Language), and VHDL (Very-High-SPEED INTEGRATED Circuit Hardware Description Language) and Verilog are currently most commonly used. It will also be apparent to those skilled in the art that a hardware circuit implementing the logic method flow can be readily obtained by merely slightly programming the method flow into an integrated circuit using several of the hardware description languages described above.

The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer readable medium storing computer readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, application SPECIFIC INTEGRATED Circuits (ASICs), programmable logic controllers, and embedded microcontrollers, examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, atmel AT91SAM, microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic of the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller in a pure computer readable program code, it is well possible to implement the same functionality by logically programming the method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Such a controller may thus be regarded as a kind of hardware component, and means for performing various functions included therein may also be regarded as structures within the hardware component. Or even means for achieving the various functions may be regarded as either software modules implementing the methods or structures within hardware components.

The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

For convenience of description, the above devices are described as being functionally divided into various units, respectively. Of course, the functions of each unit may be implemented in the same piece or pieces of software and/or hardware when implementing the embodiments of the present specification.

One skilled in the relevant art will recognize that one or more embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present description can take the form of a computer program product on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present description is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.

It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.

One or more embodiments of the present specification may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.

In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.

The foregoing description is by way of example only and is not intended to limit the present disclosure. Various modifications and changes may occur to those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. that fall within the spirit and principles of the present document are intended to be included within the scope of the claims of the present document.

Claims

1. A vehicle driving service processing method applied to a user terminal, the method comprising:

Displaying an access prompt of a driving mode through the application program;

entering a driving mode of the application program, and updating application page display based on service data of the driving mode pushed by the first server;

After detecting a starting instruction of the target vehicle, the vehicle-mounted terminal of the target vehicle uploads the starting instruction to a second server, and the second server synchronizes the starting instruction to the first server so as to perform the verification;

The verifying the service data push based on the near field communication connection and the remote connection comprises the following steps:

and performing idempotent verification on the service data pushing triggered by the near field communication connection and the service data pushing triggered by the remote connection in the driving mode.

2. The vehicle driving service processing method according to claim 1, the transmitting a verification request to the first server, comprising:

submitting, by a controller of the service sub-program, an access instruction generated after the access reminder is triggered to a front-end page of the service sub-program, the front-end page generating the check request based on the access instruction and sending the check request to the first server;

Or alternatively

Submitting, by the controller, the check request to the front-end page and synchronizing, by the front-end page, to the first server.

3. The vehicle driving service processing method according to claim 1, further comprising:

If the near field communication connection is detected to be interrupted, displaying a connection interruption prompt through the application program;

And exiting the driving mode of the application program after the connection interruption reminding is triggered.

4. The vehicle driving service processing method according to claim 1, further comprising:

And/or the number of the groups of groups,

5. The vehicle driving service processing method according to claim 1, further comprising:

If an opening instruction submitted through a front-end page of the service subprogram is detected, jumping to a vehicle subprogram of the application program;

the vehicle subprogram calls an authorization interface to carry out authorization processing and submits a driving mode opening request to a second server;

Receiving an authentication result returned by the second server and returning the authentication result to the service subprogram;

And the service subprogram synchronizes the identity verification result to the first server according to the returned identity verification result so as to conduct driving mode opening.

6. The vehicle driving service processing method according to claim 1, after the execution of the step of calling a near field communication interface to establish a near field communication connection with a target vehicle by a service subroutine of the application program, and before the execution of the step of presenting an access reminder of a driving pattern by the application program, further comprising:

Judging whether a driving mode registration record exists in a near field communication component which establishes the near field communication connection with the user terminal;

If yes, executing the access reminding step for displaying the driving mode through the application program.

7. The vehicle driving service processing method according to claim 1, further comprising:

After the service subprogram calls the near field communication interface to establish near field communication connection with a near field communication component of the target vehicle, the component identification of the near field communication component is saved, and the component identification is uploaded to the first server so as to register a driving mode aiming at the near field communication component.

8. The vehicle driving service processing method according to claim 1, further comprising:

If a remote connection registration instruction submitted by the service subprogram is detected, a registration request carrying a user identifier is generated and sent to the first server, so that driving mode registration is carried out for the target vehicle bound with the user identifier.

9. The vehicle driving service processing method according to claim 1, wherein the vehicle-mounted terminal of the target vehicle uploads the start-up instruction to a second server after detecting the start-up instruction of the target vehicle, the start-up instruction is synchronized by the second server to the first server, and a reminder presentation command of the driving mode is issued to the service subroutine through the first server, the service subroutine presenting the access reminder based on the reminder presentation command.

10. A vehicle driving service processing method applied to a first server, the method comprising:

pushing service data of the driving mode to the user terminal according to the verification result;

the method comprises the steps that after a vehicle machine terminal of a target vehicle associated with a service subprogram detects a starting instruction of the target vehicle, the starting instruction is uploaded to a second server, and the second server synchronizes the starting instruction to the first server so as to carry out verification;

the verifying the service data push based on the near field communication connection and the remote connection in the driving mode comprises the following steps:

and performing idempotent verification on service data pushing triggered based on the near field communication connection and service data pushing triggered by the remote connection in the driving mode.

11. The vehicle driving service processing method according to claim 10, the verification request is transmitted by a front-end page of the service subroutine, the verification request being generated after the front-end page receives an access instruction of the service subroutine for an access reminder of the driving mode;

Or alternatively

And the front-end page of the service subprogram synchronizes after receiving the verification request sent by the controller of the service subprogram.

12. The vehicle driving service processing method according to claim 10, further comprising:

And/or the number of the groups of groups,

13. The vehicle driving service processing method according to claim 10, further comprising:

receiving a token application sent by a second server aiming at a driving mode opening request submitted by the user terminal;

Generating a service token of the target vehicle and returning the service token to the second server;

Receiving a user inquiry request carrying the service token sent by the second server and inquiring user identity information;

Returning the queried user identity information to the second server to perform identity verification processing;

And receiving the identity verification result synchronized by the service subprogram, and opening the driving mode of the application program.

14. The vehicle driving service processing method according to claim 10, further comprising:

15. The vehicle driving service processing method according to claim 10, further comprising:

16. A vehicle driving service processing apparatus operating at a user terminal, the apparatus comprising:

the near field communication connection establishment module is configured to call a near field communication interface by a service subprogram of the application program to establish near field communication connection with the target vehicle;

the access prompt display module is configured to display the access prompt of the driving mode through the application program;

The verification request sending module is configured to send a verification request to the first server after the access prompt is triggered so as to verify service data pushing based on the near field communication connection and remote connection;

the driving mode entering module is configured to enter a driving mode of the application program and update application page display based on service data of the driving mode pushed by the first server;

17. A vehicle driving service processing apparatus operating on a first server, the apparatus comprising:

the verification request receiving module is configured to receive a verification request of a driving mode of an application program submitted by a user terminal; the verification request is generated by a service subroutine of the application program;

The service data pushing verification module is configured to verify service data pushing based on near field communication connection and remote connection in the driving mode based on the verification request;

the service data pushing module is configured to push the service data of the driving mode to the user terminal according to the verification result;

18. A vehicle driving service processing apparatus comprising:

A processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to:

Displaying an access prompt of a driving mode through the application program;

19. A vehicle driving service processing apparatus comprising:

The method comprises the steps that after a vehicle machine terminal of a target vehicle associated with a service subprogram detects a starting instruction of the target vehicle, the starting instruction is uploaded to a second server, and the second server synchronizes the starting instruction to a first server so as to carry out verification;

20. A storage medium storing computer-executable instructions that when executed by a processor implement the following:

Displaying an access prompt of a driving mode through the application program;

21. A storage medium storing computer-executable instructions that when executed by a processor implement the following: