Data transaction method and apparatus, terminal device, and storage medium

Abstract

The application is suitable for the field of communication technology, and provides a data transaction method and device, terminal equipment and storage medium. A service registration request sent by a roadside device is acquired, a service list is generated and stored, then a service use confirmation data frame sent by a vehicle terminal and a transaction data frame sent by a target roadside device are acquired, and then a target service used by the vehicle terminal is determined according to service use information and service production information contained in the data frame, and finally the target service cost is determined. Thus, by pre-generating a service list that can be provided by each roadside device, and when service production use data fed back by the vehicle terminal and the roadside device is acquired, the target service used by the vehicle terminal and the target service cost of the target service are acquired from the service list, to realize automatic calculation and payment of the service cost, thereby realizing automatic calculation and settlement of the cost when using the data service provided by the vehicle wireless communication system, and improving the convenience of transaction.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of communication, and particularly relates to a data transaction method and device, a terminal device and a storage medium. BACKGROUND

[0002] Vehicle wireless communication technology, that is, vehicle-to-external wireless information exchange technology, is a key technology of a future intelligent transportation system. The technology enables communication between a vehicle and a vehicle, a vehicle and a base station, and a base station and a base station, thereby obtaining real-time road conditions, road information, pedestrian information and a series of traffic information, improving driving safety, reducing congestion, improving traffic efficiency, providing vehicle-mounted entertainment information and the like.

[0003] In related technologies, vehicle wireless communication technology can realize communication between a vehicle and a roadside device. The roadside device can provide data services for a driving vehicle to realize different levels of automatic driving. The vehicle, as a user of the data services, should pay a certain fee to a data service provider. Therefore, how to realize data service transactions in a vehicle wireless communication system and improve the convenience of transactions is a problem that needs to be solved at present. SUMMARY

[0004] The embodiments of the application provide a data transaction method and device, a terminal device and a storage medium, which can solve the problem of how to realize data transactions between a vehicle and a roadside sensing device.

[0005] A first aspect of the embodiments of the application provides a data transaction method applied to a cloud platform in a vehicle wireless communication system. The vehicle wireless communication system further includes a vehicle terminal and a roadside device. The data transaction method includes the following steps.

[0006] Obtaining service registration requests sent by each roadside device, wherein the service registration request includes position information of the roadside device, a service type provided by the roadside device and a service fee;

[0007] Generating a service list according to each service registration request and storing the service list, wherein the service list includes service information corresponding to each roadside device;

[0008] Obtaining a service use confirmation data frame sent by the vehicle terminal and a transaction data frame corresponding to the service use confirmation data frame and sent by a target roadside device;

[0009] Determining a target service used by the vehicle terminal according to service use information contained in the service use confirmation data frame and service production information contained in the transaction data frame;

[0010] Determining a target service fee corresponding to the vehicle terminal according to a service fee of the target service.

[0011] Optionally, before the steps of obtaining the service usage confirmation data frame sent by the vehicle terminal and the transaction data frame corresponding to the service usage confirmation data frame sent by the target road-side device, the method further includes the following steps of:

[0012] obtaining a service acquisition request sent by the vehicle terminal, wherein the service acquisition request comprises the identifier of the vehicle terminal and the predicted driving path;

[0013] acquiring, according to the predicted driving path, the service information corresponding to the road-side device to be passed through from the service list and sending the service information to the vehicle terminal, so that the vehicle terminal performs the prepayment processing according to the service information corresponding to the road-side device to be passed through, wherein the road-side device to be passed through is the road-side device included in the predicted driving path;

[0014] obtaining a prepayment request sent by the vehicle terminal, wherein the prepayment request comprises the prepayment service and the payment account corresponding to the vehicle terminal;

[0015] determining the prepayment fee according to the service fee of the prepayment service, and performing the deduction processing on the payment account according to the prepayment fee;

[0016] after the step of determining the target service fee of the vehicle terminal according to the service fee of the target service, the method further includes the following steps of:

[0017] performing the settlement processing according to the prepayment fee and the target service fee.

[0018] Optionally, in the possible implementation manner of the first aspect, the prepayment request comprises the identifier of the vehicle terminal, and after the steps of determining the prepayment fee according to the service fee of the prepayment service, and performing the deduction processing on the payment account according to the prepayment fee, the method further includes the following steps of:

[0019] sending the decryption data of the road-side device corresponding to the prepayment service to the vehicle terminal according to the identifier of the vehicle terminal, so that the vehicle terminal performs the decryption processing on the real-time service data of the road-side device according to the decryption data when the real-time service data of the road-side device is received.

[0020] Optionally, in the possible implementation manner of the first aspect, the service registration request further comprises the identifier of the road-side device, the decryption data comprises the key data of the road-side device, the road-side device performs the encryption processing on the real-time service data through the key data in advance, and before the step of sending the decryption data of the road-side device corresponding to the prepayment service to the vehicle terminal according to the identifier of the vehicle terminal, so that the vehicle terminal performs the decryption processing on the real-time service data of the road-side device according to the decryption data when the real-time service data of the road-side device is received, the method further includes the following steps of:

[0021] generating the key data of each road-side device according to the preset key and the identifier of each road-side device.

[0022] sending the key data of each roadside device to each roadside device respectively;

[0023] sending the decryption data of the roadside device corresponding to the pre-paid service to the vehicle terminal according to the identification of the vehicle terminal, comprising:

[0024] sending the key data of the roadside device corresponding to the pre-paid service to the vehicle terminal according to the identification of the vehicle terminal.

[0025] Optionally, in a possible implementation manner of the first aspect, the decryption data comprises coordinate reverse deflection data of the roadside device, the roadside device performs encryption processing on real-time service data through coordinate reverse deflection data corresponding to coordinate deflection data in advance, and before the decryption data of the roadside device corresponding to the pre-paid service is sent to the vehicle terminal according to the identification of the vehicle terminal to enable the vehicle terminal to decrypt the real-time service data of the roadside device according to the decryption data before receiving the real-time service data of the roadside device, the method further comprises:

[0026] obtaining the coordinate deflection data sent by each roadside device, wherein the coordinate deflection data is generated by the roadside device according to its own position information;

[0027] generating the coordinate reverse deflection data of each roadside device according to the coordinate deflection data of each roadside device respectively;

[0028] sending the decryption data of the roadside device corresponding to the pre-paid service to the vehicle terminal according to the identification of the vehicle terminal, comprising:

[0029] sending the coordinate reverse deflection data of the roadside device corresponding to the pre-paid service to the vehicle terminal according to the identification of the vehicle terminal.

[0030] Optionally, in a possible implementation manner of the first aspect, the identification of the vehicle terminal is included in the pre-paid request, and before the pre-paid fee is determined according to the service fee of the pre-paid service and the payment account is deducted according to the pre-paid fee, the method further comprises:

[0031] obtaining the first identity authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal;

[0032] performing identity authentication on the vehicle terminal according to the identification of the vehicle terminal to determine a second identity authentication result of the cloud platform to the vehicle terminal;

[0033] determining that the first identity authentication result and the second identity authentication result are both successful.

[0034] Optionally, in a possible implementation manner of the first aspect, before the settlement processing is performed according to the pre-paid fee and the target service fee, the method further comprises:

[0035] obtaining a third identity authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal;

[0036] performing identity authentication on the vehicle terminal according to the identifier of the vehicle terminal to determine a fourth identity authentication result of the cloud platform to the vehicle terminal;

[0037] determining that the third identity authentication result and the fourth identity authentication result are both successful.

[0038] A second aspect of the embodiments of the application provides another data transaction method, applied to a vehicle terminal, comprising:

[0039] obtaining real-time service data sent by a roadside device, wherein the real-time service data comprises an identifier of the roadside device;

[0040] sending a service use confirmation data frame to the roadside device and the cloud platform according to the identifier of the roadside device, so that the cloud platform determines a target service charge according to the service use confirmation data frame, wherein the service use confirmation data frame comprises service use information.

[0041] Optionally, before the above-mentioned obtaining the real-time service data sent by the roadside device, the method further comprises:

[0042] sending a service acquisition request to the cloud platform, wherein the service acquisition request comprises an identifier of the vehicle terminal and a planned driving path;

[0043] obtaining service information corresponding to a roadside device to be passed through sent by the cloud platform, wherein the roadside device to be passed through is a roadside device included in the planned driving path, and the service information corresponding to the roadside device to be passed through is obtained by the cloud platform from a service list stored by itself according to the planned driving path;

[0044] displaying the service information corresponding to the roadside device to be passed through;

[0045] obtaining an operation instruction of the user to the service information corresponding to the roadside device to be passed through, and determining a prepayment service according to the operation instruction;

[0046] generating a prepayment request according to the prepayment service and sending the prepayment request to the cloud platform, wherein the prepayment request comprises the prepayment service and payment account information corresponding to the vehicle terminal.

[0047] Optionally, before the above-mentioned sending the service acquisition request to the cloud platform, the method further comprises:

[0048] obtaining destination information input by a user and current position information of a vehicle in which the vehicle terminal is located;

[0049] According to the destination information and the current position information, a predicted driving path is planned.

[0050] Optionally, before the prepayment request is generated according to the prepayment service and is sent to the cloud platform, the method further includes:

[0051] The cloud platform is authenticated to determine a first authentication result of the vehicle terminal to the cloud platform.

[0052] The prepayment request is generated according to the prepayment service and is sent to the cloud platform, and the prepayment request further includes the first authentication result.

[0053] The prepayment request is generated according to the prepayment service and the first authentication result and is sent to the cloud platform, and the prepayment request further includes the first authentication result.

[0054] Optionally, before the service usage confirmation data frame is sent to the roadside device and the cloud platform according to the identification of the roadside device, the method further includes:

[0055] The decryption data corresponding to the roadside device sent by the cloud platform is acquired.

[0056] According to the decryption data, the real-time service data is decrypted to generate plaintext data corresponding to the real-time service data.

[0057] A third aspect of the embodiments of the present application provides another data transaction method, applied to a roadside device, and including:

[0058] A service registration request is sent to the cloud platform, and the service registration request includes the position information of the roadside device, the type of the service provided, and the service fee.

[0059] Real-time service data is sent to the vehicle terminal, and the real-time service data includes the identification of the roadside device.

[0060] A service usage confirmation data frame sent by the vehicle terminal is acquired.

[0061] According to the service usage information included in the service usage confirmation data frame, a transaction data frame corresponding to the service usage confirmation data frame is generated, and the transaction data frame includes service production information.

[0062] The transaction data frame is sent to the cloud platform, so that the cloud platform determines a target service fee according to the transaction data frame.

[0063] Optionally, before the real-time service data is sent to the vehicle terminal, the method further includes:

[0064] obtain the key data sent by the cloud platform;

[0065] encrypt the real-time service data according to the key data.

[0066] Optionally, before the real-time service data is sent to the vehicle terminal, the method further includes:

[0067] perform coordinate deflection processing on the location information to generate coordinate deflection data, and send the coordinate deflection data to the cloud platform;

[0068] encrypt the real-time service data according to the coordinate deflection data.

[0069] A fourth aspect of the embodiments of the present application provides a data transaction device applied to a cloud platform in a vehicle wireless communication system, the vehicle wireless communication system further including a vehicle terminal and a roadside device, and the data transaction device includes:

[0070] a first obtaining module, configured to obtain service registration requests sent by the roadside devices, wherein the service registration requests include location information of the roadside devices, service types provided by the roadside devices, and service fees;

[0071] a first generating module, configured to generate a service list according to the service registration requests and store the service list, wherein the service list includes service information corresponding to the roadside devices;

[0072] a second obtaining module, configured to obtain a service use confirmation data frame sent by the vehicle terminal and a transaction data frame corresponding to the service use confirmation data frame and sent by a target roadside device;

[0073] a first determining module, configured to determine a target service used by the vehicle terminal according to service use information included in the service use confirmation data frame and service production information included in the transaction data frame;

[0074] a second determining module, configured to determine a target service fee corresponding to the vehicle terminal according to the service fee of the target service.

[0075] A fifth aspect of the embodiments of the present application provides a data transaction device applied to a vehicle terminal, and the data transaction device includes:

[0076] a third obtaining module, configured to obtain real-time service data sent by the roadside device, wherein the real-time service data includes an identifier of the roadside device;

[0077] a first sending module, configured to send a service use confirmation data frame to the roadside device and the cloud platform according to the identifier of the roadside device, so that the cloud platform determines a target service fee according to the service use confirmation data frame, wherein the service use confirmation data frame includes service use information.

[0078] A sixth aspect of this application provides a data transaction device applied to roadside equipment, comprising:

[0079] The second sending module is used to send a service registration request to the cloud platform. The service registration request includes the location information of the roadside equipment, the type of service provided, and the service fee.

[0080] The third sending module is used to send real-time service data to the vehicle terminal, wherein the real-time service data includes the identifier of the roadside equipment.

[0081] The fourth acquisition module is used to acquire the service usage confirmation data frame sent by the vehicle terminal;

[0082] The second generation module is used to generate a transaction data frame corresponding to the service usage confirmation data frame based on the service usage information included in the service usage confirmation data frame, wherein the transaction data frame includes service production information.

[0083] The fourth sending module is used to send transaction data frames to the cloud platform so that the cloud platform can determine the target service fee based on the transaction data frames.

[0084] A seventh aspect of this application provides a terminal device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the data transaction method described in the first, second, or third aspects.

[0085] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the data transaction methods described in the first, second, or third aspects.

[0086] The fifth aspect of this application provides a computer program product that, when run on a terminal device, causes the terminal device to execute the data transaction methods described in the first, second, or third aspects.

[0087] The beneficial effects of this application's embodiments compared to the prior art are as follows: This application discloses a data transaction method, apparatus, terminal device, and storage medium. It can acquire service registration requests sent by various roadside devices, generate and store a service list based on these requests, then acquire service usage confirmation data frames sent by the vehicle terminal and transaction data frames sent by the target roadside device corresponding to the service usage confirmation data frames. Furthermore, based on the service usage information contained in the service usage confirmation data frames and the service production information contained in the transaction data frames, it determines the target service used by the vehicle terminal. Finally, it determines the target service fee corresponding to the vehicle terminal based on the service fee of the target service. Therefore, by pre-generating a service list that each roadside device can provide, and upon acquiring service production and usage data from the vehicle terminal and roadside devices, retrieving the target service used by the vehicle terminal and the target service fee from the service list, it achieves automatic calculation and payment of service fees. This realizes automatic fee calculation and settlement when using data services provided by the vehicle wireless communication system, improving the convenience of transactions. Attached Figure Description

[0088] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0089] Figure 1 This is a flowchart illustrating a data transaction method provided in Embodiment 1 of this application;

[0090] Figure 2 This is a schematic diagram of a vehicle driving path provided in Embodiment 1 of this application;

[0091] Figure 3 This is a flowchart illustrating a data transaction method provided in Embodiment 2 of this application;

[0092] Figure 4 This is a flowchart illustrating a data transaction method provided in Embodiment 3 of this application;

[0093] Figure 5 This is a signaling interaction diagram of a data transaction method provided in an embodiment of this application;

[0094] Figure 6 This is a schematic diagram of the structure of a data transaction device provided in Embodiment 4 of this application;

[0095] Figure 7 This is a schematic diagram of the structure of a data transaction device provided in Embodiment 5 of this application;

[0096] Figure 8 This is a schematic diagram of the structure of a data transaction device provided in Embodiment Six of this application;

[0097] Figure 9 This is a schematic diagram of the structure of a terminal device provided in Embodiment 7 of this application. Detailed Implementation

[0098] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0099] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0100] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0101] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0102] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0103] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0104] It should be understood that the sequence number of each step in this embodiment does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of this application embodiment.

[0105] In related technologies, vehicle wireless communication technology enables communication between vehicles and roadside equipment. Roadside equipment can provide data services to vehicles to achieve different levels of autonomous driving. As the user of data services, vehicles should pay a certain fee to the data service provider. Therefore, how to realize data service transactions in vehicle wireless communication systems and improve the convenience of transactions is an urgent problem to be solved.

[0106] In view of this, embodiments of this application provide a data transaction method, apparatus, terminal device, and storage medium. By pre-generating a list of services that each roadside device can provide, and upon obtaining service production and usage data fed back by the vehicle terminal and the roadside device, the method retrieves the target service used by the vehicle terminal and the target service fee from the service list to achieve automatic calculation and payment of service fees. This enables automatic fee calculation and settlement when using data services provided by the vehicle wireless communication system, thereby improving the convenience of transactions.

[0107] To illustrate the technical solution of this application, specific embodiments are described below.

[0108] Reference Figure 1 The diagram shows a flowchart of a data transaction method provided in Embodiment 1 of this application. The method is applied to a cloud platform in a vehicle wireless communication system, which also includes a vehicle terminal and roadside equipment.

[0109] The vehicle wireless communication system can be a V2X (Vehicle to X) system, a cellular communication-based system, an Enhanced Ultra High Throughput (EUHT) system, or an extended ETC communication technology system, etc., and this application does not limit this. The cloud platform, also known as a cloud computing platform, provides computing, networking, and storage capabilities based on hardware and software resources.

[0110] like Figure 1 As shown, this data transaction method may include the following steps:

[0111] Step 101: Obtain the service registration requests sent by each roadside device.

[0112] The service registration request may include the location information of the roadside equipment, the type of service provided, and the service fee.

[0113] In this embodiment, when a roadside device is powered on or started, it can send a service registration request to the corresponding cloud platform. The cloud platform can obtain service registration requests from all roadside devices under its management in real time, and manage the services provided by each roadside device based on the obtained service registration requests. It should be noted that each roadside device corresponds to a sensing range, and the roadside device can only provide services within its sensing range. Therefore, the location information of the roadside device can be the area covered by its service.

[0114] As one possible implementation, the services provided by roadside equipment may include perception data sharing services. Perception data sharing services can provide vehicle terminals with perception data of the surrounding environment within the service coverage area of ​​the roadside equipment, such as various types of perception data such as roads, obstacles, vehicles, and pedestrians, so that vehicles can achieve autonomous driving or assisted driving based on the perception data.

[0115] As another possible implementation, the types of services provided by roadside equipment may also include traffic violation detection services, traffic light reminder services, driving guidance services, etc., and this application embodiment does not limit this. For example, when roadside equipment provides a red-light violation detection service, the roadside equipment providing the red-light violation detection service is generally set up near traffic lights, and the red-light violation detection service can detect traffic participants who run red lights within the service coverage area of ​​the roadside equipment.

[0116] In the embodiments of this application, the location information and service types provided by roadside equipment are diverse, and the service fees corresponding to roadside equipment with different service types or different sensing ranges are also different. Generally speaking, the larger the service sensing range of a roadside equipment, the higher its corresponding service fee; the more complex the service information of a roadside equipment, the higher its corresponding service fee.

[0117] As one possible implementation, since the service information provided by roadside equipment may not be applicable to all types of vehicles, the service registration request may also include vehicle type information so that users can select the service provided by the corresponding roadside equipment based on the type of vehicle they are driving.

[0118] Step 102: Generate and store a service list based on each service registration request.

[0119] The service list includes service information for each roadside device.

[0120] In this embodiment, after the cloud platform receives the service registration request sent by the roadside device, it can generate a service list based on the roadside device location information, the type of service provided, and the service fee included in the service registration request and store it locally. When a vehicle uses the service provided by the roadside device, it can query the relevant service through the service list and calculate the fee.

[0121] Step 103: Obtain the service usage confirmation data frame sent by the vehicle terminal and the transaction data frame sent by the target roadside equipment corresponding to the service usage confirmation data frame.

[0122] A data frame is a protocol data unit at the data link layer, which can include three parts: a frame header, a data portion, and a frame trailer. The frame header and trailer contain necessary control information, such as synchronization information, address information, and error control information; the data portion includes information such as service confirmation success information, service usage information, service transaction success information, and service production information, etc.

[0123] In this embodiment, after a vehicle terminal uses a service provided by a roadside device, the vehicle terminal can send a service usage confirmation data frame to the cloud platform and the target roadside device providing the service. The cloud platform can then confirm the service information used by the vehicle terminal based on the service confirmation success information contained in the service usage confirmation data frame. After receiving the service usage confirmation data frame sent by the vehicle terminal, the target roadside device can generate a transaction data frame based on the service usage confirmation data frame and send it to the cloud platform. After obtaining the service usage confirmation data frame and the service transaction success information contained in the transaction data frame, the cloud platform can determine the service used by the vehicle terminal based on the service list and calculate the cost.

[0124] Furthermore, since the cloud platform contains a large amount of service information, to help users quickly filter out the roadside services they need and to allow users to choose whether or not to use related services according to their preferences, the expected roadside equipment and corresponding service information that the vehicle will pass through can be sent to the vehicle terminal based on the vehicle's expected travel route for the user to select, thereby further improving the convenience and flexibility of transactions. That is, in one possible implementation of this application, before step 103 above, the following may be included:

[0125] Obtain the service acquisition request sent by the vehicle terminal, wherein the service acquisition request includes the vehicle terminal's identifier and the expected driving route;

[0126] Based on the expected driving route, the service information corresponding to the expected roadside equipment is obtained from the service list and sent to the vehicle terminal so that the vehicle terminal can perform prepayment processing based on the service information corresponding to the expected roadside equipment. The expected roadside equipment refers to the roadside equipment included in the expected driving route.

[0127] Obtain the prepayment request sent by the vehicle terminal, wherein the prepayment request includes the prepayment service and the payment account corresponding to the vehicle terminal;

[0128] The prepaid fee is determined based on the service fee for the prepaid service, and the payment is deducted from the payment account based on the prepaid fee.

[0129] In this embodiment of the application, the service acquisition request includes the identifier of the vehicle terminal. Each vehicle terminal identifier is unique. Based on the vehicle terminal identifier, the service information corresponding to the expected roadside equipment is sent to the corresponding vehicle terminal, which can avoid sending service information incorrectly.

[0130] One possible implementation is to plan the expected driving route based on the vehicle's initial location and destination. After receiving a service request from the vehicle terminal, the cloud platform parses and processes the request to determine the vehicle terminal's identifier and the expected driving route. Based on the expected driving route and a locally stored service list, it identifies the roadside equipment expected to be passed along the route and retrieves information such as the service type and cost of each roadside equipment from the service list, sending this information to the vehicle terminal. This allows the user to select a prepaid service from the roadside equipment based on their needs. After the user selects a prepaid service through the vehicle terminal, the vehicle terminal generates a prepayment request and sends it to the cloud platform. The cloud platform then parses and processes this request to determine the selected prepaid service, calculates the service cost for each prepaid service from the service list, sums the costs of all prepaid services to determine the prepayment fee, and deducts the prepayment from the payment account accordingly.

[0131] Furthermore, each roadside device can send corresponding real-time service data externally. To ensure transaction security and prevent data theft or misuse, the data sent by the roadside devices can be encrypted. Therefore, after the cloud platform deducts the prepayment from the payment account corresponding to the vehicle terminal, it needs to promptly send the corresponding decrypted data to the vehicle terminal so that the vehicle terminal can decrypt the service data provided by the roadside terminal when using the corresponding service. In one possible implementation, the prepayment request may also include the vehicle terminal's identifier. After determining the prepayment fee based on the service fee of the prepaid service and deducting the payment from the payment account based on the prepayment fee, it may also include:

[0132] Based on the vehicle terminal's identifier, the decrypted data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal, so that when the vehicle terminal receives the real-time service data from the roadside equipment, it can decrypt the real-time service data according to the decrypted data.

[0133] As one possible implementation, the roadside equipment can pre-encrypt the real-time service data using key data. Correspondingly, the decrypted data includes the roadside equipment's key data, and the service registration request also includes the roadside equipment's identifier. Based on the vehicle terminal's identifier, the decrypted data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal. This allows the vehicle terminal to decrypt the real-time service data received from the roadside equipment, which can include:

[0134] Based on the preset key and the identifier of each roadside device, key data for each roadside device is generated respectively;

[0135] The key data of each roadside device is sent to each roadside device respectively.

[0136] Correspondingly, when the roadside equipment pre-encrypts the real-time service data using key data, the aforementioned sending of the decrypted data from the roadside equipment corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier may include:

[0137] Based on the vehicle terminal's identifier, the key data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal.

[0138] The preset key is a unique key for the cloud platform. Based on this preset key and the identifiers of each roadside device, the cloud platform uses encryption algorithms such as SM4 and SM2 to distribute the key data for each roadside device. Then, based on the vehicle terminal's identifier, the cloud platform sends the key data of the roadside device corresponding to the prepaid service to the vehicle terminal making the prepaid payment. This allows the vehicle terminal to receive the corresponding real-time service data when it enters the service coverage area of ​​the roadside device corresponding to the prepaid service, and decrypt it using the key data corresponding to that roadside device to obtain plaintext data for service use, thus improving transaction security.

[0139] As another possible implementation, the roadside equipment can pre-encrypt the real-time service data using coordinate deflection data. Correspondingly, the decrypted data includes the roadside equipment's coordinate inverse deflection data, with the coordinate deflection data corresponding to the coordinate inverse deflection data. Based on the vehicle terminal's identifier, the decrypted data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal. This allows the vehicle terminal, upon receiving the real-time service data from the roadside equipment, to perform decryption processing on the real-time service data before including:

[0140] Acquire coordinate deflection data sent by each roadside device, wherein the coordinate deflection data is generated by the roadside device based on its own position information;

[0141] Based on the coordinate deflection data of each roadside device, generate the coordinate reverse deflection data of each roadside device;

[0142] Correspondingly, when the roadside equipment pre-encrypts the real-time service data using coordinate deflection data, the aforementioned method of sending the decrypted data of the roadside equipment corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier includes:

[0143] Based on the vehicle terminal's identifier, the coordinate reverse deflection data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal.

[0144] Each roadside device can use its specific deflection encryption algorithm to perform coordinate deflection processing on its location information, allowing it to send real-time service data in the form of coordinate deflection. The cloud platform can obtain the coordinate deflection data of the roadside device and determine the corresponding inverse coordinate deflection data. This inverse coordinate deflection data can be in the form of a plug-in. When a vehicle terminal prepays for the roadside device, the cloud platform can send the inverse coordinate deflection data of the roadside device to the prepaid vehicle terminal in the form of a plug-in, based on the vehicle terminal's identifier. This allows the vehicle terminal to receive the corresponding real-time service data when it enters the service coverage area of ​​the roadside device corresponding to the prepaid service, and decrypt it according to the inverse coordinate deflection data to obtain plaintext data for service use, thus improving transaction security.

[0145] Furthermore, to ensure the security of prepayment, the vehicle terminal's authentication result with the cloud platform can be obtained and the vehicle terminal's identity can be authenticated before prepayment. Only when both parties are successfully authenticated can subsequent prepayment be processed. That is, in one possible implementation of this application embodiment, the prepayment request includes the vehicle terminal's identifier. Before determining the prepayment fee based on the service fee of the prepayment service and deducting the payment from the payment account based on the prepayment fee, the following may also be included:

[0146] Obtain the first identity authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal;

[0147] Based on the vehicle terminal's identifier, the vehicle terminal is authenticated to determine the cloud platform's second authentication result for the vehicle terminal;

[0148] Both the first and second identity authentication results are confirmed to be successful.

[0149] The identity authentication can be a conventional identity authentication method, such as the national cryptographic authentication method. This application does not restrict the identity authentication method.

[0150] Step 104: Determine the target service used by the vehicle terminal based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame.

[0151] In this embodiment, the cloud platform can determine the service usage of the vehicle terminal during its journey by using service usage information sent by the vehicle terminal, thereby determining whether the vehicle terminal has used a particular service. The cloud platform can also determine whether the roadside equipment has successfully sent its corresponding real-time service data by using service production information (identifying the service source) sent by the roadside equipment. By combining the service usage information and the service production information, the target service actually used by the vehicle terminal can be determined.

[0152] Step 105: Determine the target service fee corresponding to the vehicle terminal based on the service fee of the target service.

[0153] The final target service fee needs to be determined by taking into account the actual usage of the service by the vehicle terminal.

[0154] Furthermore, due to various practical factors, vehicles may not necessarily travel along the planned route. Therefore, a final settlement is required after the trip ends. For services that have been prepaid but not actually used, a refund needs to be processed for the payment account. For services that have not been prepaid but have actually been used, the corresponding service fee needs to be deducted from the payment account. That is, as a possible implementation of this application embodiment, after step 105 above, it may also include:

[0155] Settlement is processed based on prepaid fees and target service fees.

[0156] For example, see Figure 2 This is a schematic diagram of a vehicle's travel path. The vehicle terminal's expected travel path A includes a first roadside device 1 and a second roadside device 2. The vehicle terminal selects the services corresponding to the first roadside device 1 and the second roadside device 2. However, if the vehicle actually travels along the travel path B, that is, the vehicle only passes through the service coverage area of ​​the first roadside device 1 and uses the service corresponding to the first roadside device 1, then during the settlement process, the prepaid fee corresponding to the second roadside device 2 needs to be refunded to the payment account.

[0157] Furthermore, to ensure the security of the settlement process, similar to prepayment, identity authentication can be performed on both the payer and the chargeer before settlement. Specifically, before the settlement process based on the prepayment fee and the target service fee, the following steps can be taken: obtaining the third-party authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal; authenticating the vehicle terminal based on its identifier to determine the fourth-party authentication result of the cloud platform; and confirming that both the third and fourth-party authentication results are successful. The specific details of the identity authentication can be found in the description of identity authentication in the prepayment section, and will not be repeated in this embodiment.

[0158] The data transaction method disclosed in the above embodiments of this application, applied to a cloud platform, can acquire service registration requests sent by various roadside devices, generate and store a service list based on each service registration request, then acquire service usage confirmation data frames sent by vehicle terminals and transaction data frames sent by target roadside devices corresponding to the service usage confirmation data frames, and further determine the target services used by the vehicle terminals based on the service usage information contained in the service usage confirmation data frames and the service production information contained in the transaction data frames, and finally determine the target service fee corresponding to the vehicle terminals based on the service fee of the target services. Thus, by pre-generating a service list that each roadside device can provide, and upon acquiring service production and usage data fed back by the vehicle terminals and roadside devices, retrieving the target services used by the vehicle terminals and the target service fees of the target services from the service list, automatic calculation and payment of service fees are achieved. This realizes automatic fee calculation and settlement when using data services provided by the vehicle wireless communication system, improving the convenience of transactions.

[0159] The following section uses the vehicle terminal side as an example to further explain the data transaction method provided in the embodiments of this application.

[0160] See Figure 3 The diagram illustrates a flowchart of a data transaction method provided in Embodiment 2 of this application. Figure 3 As shown, this data transaction method, applied to vehicle terminals, may include the following steps:

[0161] Step 301: Obtain real-time service data sent by the roadside equipment.

[0162] The real-time service data includes the identification of roadside equipment.

[0163] In this embodiment of the application, when the vehicle terminal enters the service coverage area corresponding to the roadside equipment, it can receive real-time service data sent by the roadside equipment via broadcast.

[0164] Furthermore, to ensure the timeliness of services provided by each roadside device, the vehicle terminal can obtain service information corresponding to each roadside device from the cloud platform upon startup. This allows users to choose whether to use the relevant services and make prepayments based on their preferences. As one possible implementation of this application, before step 301 above, the following steps may also be included:

[0165] Send a service request to the cloud platform, which includes the vehicle terminal's identifier and the expected driving route;

[0166] Obtain service information corresponding to the roadside equipment expected to be passed by, sent by the cloud platform. The roadside equipment expected to be passed by refers to the roadside equipment included in the expected driving path, and the service information corresponding to the roadside equipment expected to be passed by is obtained by the cloud platform from its own stored service list based on the expected driving path.

[0167] Displays service information for the roadside equipment expected to be encountered;

[0168] Obtain user operation instructions for the service information corresponding to the roadside equipment expected to pass by, and determine the prepaid service based on the operation instructions;

[0169] A prepaid request is generated based on the prepaid service and sent to the cloud platform. The prepaid request includes the prepaid service and the payment account information corresponding to the vehicle terminal.

[0170] The service request includes the vehicle terminal's identifier, which allows the cloud platform to send service information corresponding to the expected roadside equipment to the vehicle terminal based on the vehicle terminal's identifier, thus avoiding the missending of service information.

[0171] Furthermore, since the cloud platform needs to combine the predicted driving path to send the service information corresponding to the roadside equipment that the vehicle terminal is expected to pass through to the vehicle terminal for push to the user, the service acquisition request includes the predicted driving path. The predicted driving path can be generated by route planning based on the current location of the vehicle terminal and the destination information. That is, as a possible implementation of this application embodiment, before sending the service acquisition request to the cloud platform, it may include:

[0172] Obtain the destination information input by the user and the current location information of the vehicle where the vehicle terminal is located;

[0173] Route planning is performed based on destination and current location information to generate a predicted driving route.

[0174] Furthermore, to ensure the security of prepayment, identity authentication can be performed on the cloud platform before prepayment. Once authentication is successful, the prepayment request is sent to the cloud platform for subsequent prepayment. Specifically, in one possible implementation of this application embodiment, before generating and sending the prepayment request based on the prepayment service to the cloud platform, the process may further include: performing identity authentication on the cloud platform to determine the vehicle terminal's first identity authentication result with the cloud platform; the generation and sending of the prepayment request based on the prepayment service to the cloud platform may include: generating and sending the prepayment request based on the prepayment service and the first identity authentication result, wherein the prepayment request also includes the first identity authentication result. The specific content of the identity authentication can be found in the description of identity authentication in steps 103 and 105 of Embodiment 1 of this application, and will not be repeated in this embodiment.

[0175] Step 302: Based on the identification of the roadside equipment, send a service usage confirmation data frame to the roadside equipment and the cloud platform so that the cloud platform can determine the target service fee based on the service usage confirmation data frame.

[0176] The service usage confirmation data frame includes service usage information.

[0177] Furthermore, to ensure the security of data transactions between the vehicle terminal and the roadside equipment, and to prevent data theft or misuse, the roadside equipment needs to encrypt the real-time service data when sending it. This allows the vehicle terminal to decrypt the encrypted real-time service data using the decrypted data obtained after prepayment, thus obtaining the corresponding plaintext data. In one possible implementation of this application, before step 302, the following step is also included:

[0178] Obtain the decrypted data corresponding to the roadside equipment sent by the cloud platform;

[0179] Based on the decrypted data, the real-time service data is decrypted to generate the corresponding plaintext data.

[0180] As one possible implementation, roadside equipment can pre-encrypt real-time service data using key data. Correspondingly, the decryption data includes the key data of the roadside equipment. The key data for each roadside equipment is generated by the cloud platform based on a preset key and the identifier of each roadside equipment. The cloud platform sends the key data of each roadside equipment to the respective equipment, enabling them to encrypt the real-time service data using the corresponding key data. After prepayment, the vehicle terminal can obtain the decryption data from the roadside equipment corresponding to the prepaid service based on its identifier. It can then decrypt the corresponding real-time service data using this decryption data to obtain plaintext data for service use.

[0181] As another possible implementation, roadside equipment can pre-encrypt real-time service data using coordinate deflection data. Correspondingly, the decrypted data includes the roadside equipment's inverse coordinate deflection data, with the original coordinate deflection data and inverse coordinate deflection data being mutually exclusive. The coordinate deflection data for each roadside equipment is generated separately by processing its own location information using coordinate deflection data. Thus, the roadside equipment can encrypt the real-time service data based on the corresponding coordinate deflection data. After prepayment, the vehicle terminal can obtain the inverse coordinate deflection data of the roadside equipment corresponding to the prepaid service based on the vehicle terminal's identifier. This inverse coordinate deflection data is then used to decrypt the corresponding real-time service data, obtaining plaintext data for service use.

[0182] Other specific details of Embodiment 2 of this application can be found in the relevant content of the foregoing embodiments, and will not be repeated here.

[0183] The data transaction method disclosed in the above embodiments of this application is applied to a vehicle terminal. First, it acquires real-time service data sent by roadside equipment. Then, based on the identifier of the roadside equipment, it sends a service usage confirmation data frame to both the roadside equipment and the cloud platform, enabling the cloud platform to determine the target service fee based on the service usage confirmation data frame. Thus, by acquiring service data during vehicle operation to use the corresponding service, and by sending a service usage confirmation data frame to the roadside equipment and the cloud platform to determine the target service fee, automatic fee calculation and settlement are achieved when using data services provided by the vehicle wireless communication system, improving the convenience of transactions.

[0184] The following section uses roadside equipment as an example to further illustrate the data transaction method provided in this application embodiment.

[0185] See Figure 4 The diagram illustrates a flowchart of a data transaction method provided in Embodiment 3 of this application. Figure 4 As shown, this data transaction method, applied to roadside equipment, may include the following steps:

[0186] Step 401: Send a service registration request to the cloud platform.

[0187] The service registration request includes the location information of the roadside equipment, the type of service provided, and the service fee.

[0188] In this embodiment, after the roadside equipment starts operating, it needs to register the services it provides with the cloud platform so that the cloud platform can form a service list based on the service information registered by multiple different roadside equipment.

[0189] Step 402: Send real-time service data to the vehicle terminal.

[0190] The real-time service data includes the identification of roadside equipment.

[0191] In this embodiment, the roadside equipment can broadcast real-time service data at a certain frequency, so that when a vehicle enters the monitoring range of the roadside equipment, the vehicle terminal installed in the vehicle can obtain the real-time service data of the roadside equipment and use the corresponding service provided by the roadside equipment. The identifier of the roadside equipment is used to provide a basis for the subsequent transmission of service usage confirmation data frames by the vehicle terminal, avoiding the mistransmission of service usage confirmation data frames.

[0192] Furthermore, to ensure transaction security and prevent data theft or misuse, the roadside equipment can encrypt the real-time service data using key data distributed by the cloud platform before sending it. In one possible implementation of this application, before step 402, the following steps are also included:

[0193] Obtain the key data sent by the cloud platform;

[0194] The real-time service data is encrypted based on the key data.

[0195] The key data for roadside equipment is generated by the cloud platform based on a preset key and the roadside equipment's identifier. When the cloud platform sends key data, the roadside equipment uses this key data to encrypt the real-time service data. Correspondingly, after the vehicle terminal makes a prepayment, the cloud platform can send the roadside equipment's key data to the vehicle terminal based on the vehicle terminal's identifier. This allows the vehicle terminal to decrypt the real-time service data using the key data, obtaining plaintext data for service use.

[0196] Furthermore, the roadside equipment can also encrypt the real-time service data using coordinate deflection data. That is, as another possible implementation of this application embodiment, before step 402 above, it further includes:

[0197] The location information is processed by coordinate deflection to generate coordinate deflection data, which is then sent to the cloud platform.

[0198] The real-time service data is encrypted based on the coordinate deflection data.

[0199] Specifically, roadside equipment can generate coordinate deflection data by performing coordinate deflection processing on location information. The roadside equipment then uses this coordinate deflection data to encrypt real-time service data. Correspondingly, after the vehicle terminal makes a prepayment, the cloud platform generates corresponding inverse coordinate deflection data for the roadside equipment based on its coordinate deflection data. Then, based on the vehicle terminal's identifier, the cloud platform sends the inverse coordinate deflection data from the roadside equipment to the vehicle terminal, enabling the vehicle terminal to decrypt the real-time service data using the inverse coordinate deflection data to obtain plaintext data for service use.

[0200] Step 403: Obtain the service usage confirmation data frame sent by the vehicle terminal.

[0201] Step 404: Generate a transaction data frame corresponding to the service usage confirmation data frame based on the service usage information included in the service usage confirmation data frame.

[0202] The transaction data frame includes service production information.

[0203] Step 405: Send the transaction data frame to the cloud platform so that the cloud platform can determine the target service fee based on the transaction data frame.

[0204] Other specific details of Embodiment 3 of this application can be found in the relevant content of the foregoing embodiments, and will not be repeated here.

[0205] The data transaction method disclosed in the above embodiments of this application is applied to roadside equipment. First, a service registration request is sent to a cloud platform. Then, real-time service data is sent to the vehicle terminal. Next, a service usage confirmation data frame sent by the vehicle terminal is obtained. Then, based on the service usage information included in the service usage confirmation data frame, a transaction data frame corresponding to the service usage confirmation data frame is generated. Finally, the transaction data frame is sent to the cloud platform so that the cloud platform can determine the target service fee based on the transaction data frame. Therefore, by generating a transaction data frame upon obtaining the service usage confirmation data frame sent by the vehicle terminal and sending the transaction data frame to the cloud platform to determine the target service fee, automatic calculation and payment of service fees are achieved. This realizes automatic fee calculation and settlement when using data services provided by the vehicle wireless communication system, improving the convenience of transactions.

[0206] Figure 5 This is a signaling interaction diagram of a data transaction method provided in an embodiment of this application. Figure 5 As shown, this data transaction method may include the following steps:

[0207] Step 501: The roadside equipment sends a service registration request to the cloud platform.

[0208] The service request includes the vehicle terminal's identifier and the expected travel route.

[0209] Step 502: The cloud platform generates and stores a service list based on each service registration request.

[0210] Step 503: The roadside equipment sends real-time service data to the vehicle terminal.

[0211] The service list includes service information for each roadside device.

[0212] Step 504: The vehicle terminal sends a service usage confirmation data frame to the roadside equipment based on the identification of the roadside equipment.

[0213] The service usage confirmation data frame includes service usage information.

[0214] Step 505: The vehicle terminal sends a service usage confirmation data frame to the cloud platform.

[0215] Step 506: The roadside equipment generates a transaction data frame corresponding to the service usage confirmation data frame based on the service usage information included in the service usage confirmation data frame.

[0216] The transaction data frame includes service production information.

[0217] Step 507: The roadside equipment sends the transaction data frame to the cloud platform.

[0218] Step 508: The cloud platform determines the target service used by the vehicle terminal based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame.

[0219] Step 509: The cloud platform determines the target service fee corresponding to the vehicle terminal based on the service fee of the target service.

[0220] Through the above process, the cloud platform generates a list of services that each roadside device can provide. The vehicle terminal and the roadside device feed back service production and usage data to the cloud platform, so that the cloud platform can obtain the target services used by the vehicle terminal and the target service fees from the service list, so as to realize the automatic calculation and payment of service fees. This enables automatic fee calculation and settlement when using data services provided by the vehicle wireless communication system, improving the convenience of transactions.

[0221] See Figure 6 The diagram shows a schematic of a data transaction device according to Embodiment 4 of this application. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0222] This data trading device is applied to a cloud platform and may specifically include the following modules:

[0223] The first acquisition module 601 is used to acquire service registration requests sent by each roadside device, wherein the service registration request includes the location information of the roadside device, the type of service provided, and the service fee.

[0224] The first generation module 602 is used to generate and store a service list based on each service registration request, wherein the service list includes service information corresponding to each roadside device.

[0225] The second acquisition module 603 is used to acquire the service usage confirmation data frame sent by the vehicle terminal and the transaction data frame sent by the target roadside equipment corresponding to the service usage confirmation data frame.

[0226] The first determining module 604 is used to determine the target service used by the vehicle terminal based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame.

[0227] The second determining module 605 is used to determine the target service fee corresponding to the vehicle terminal based on the service fee of the target service.

[0228] The data transaction apparatus disclosed in the above embodiments of this application, applied to a cloud platform, can acquire service registration requests sent by various roadside devices, generate and store a service list based on each service registration request, then acquire service usage confirmation data frames sent by vehicle terminals and transaction data frames sent by target roadside devices corresponding to the service usage confirmation data frames. Furthermore, based on the service usage information contained in the service usage confirmation data frames and the service production information contained in the transaction data frames, the target service used by the vehicle terminal is determined. Finally, based on the service fee of the target service, the target service fee corresponding to the vehicle terminal is determined. Thus, by pre-generating a service list that each roadside device can provide, and upon acquiring service production and usage data fed back by the vehicle terminal and roadside devices, retrieving the target service used by the vehicle terminal and the target service fee from the service list, automatic calculation and payment of service fees are achieved. This enables automatic fee calculation and settlement when using data services provided by the vehicle wireless communication system, improving the convenience of transactions.

[0229] In one possible implementation of Embodiment 4 of this application, the data transaction device may further include the following module, applied before acquiring the service usage confirmation data frame sent by the vehicle terminal and the transaction data frame corresponding to the service usage confirmation data frame sent by the target roadside equipment:

[0230] The fifth acquisition module is used to acquire service acquisition requests sent by the vehicle terminal.

[0231] The service request includes the vehicle terminal's identifier and the expected travel route.

[0232] The fifth sending module is used to obtain the service information corresponding to the roadside equipment expected to be passed from the service list according to the expected driving route and send it to the vehicle terminal so that the vehicle terminal can perform prepayment processing according to the service information corresponding to the roadside equipment expected to be passed.

[0233] The roadside equipment that is expected to be passed through refers to the roadside equipment included in the expected travel route.

[0234] The sixth acquisition module is used to acquire prepayment requests sent by the vehicle terminal.

[0235] The prepaid request includes the prepaid service and the payment account corresponding to the vehicle terminal.

[0236] The deduction processing module is used to determine the prepaid fee based on the service fee of the prepaid service, and to deduct the prepaid fee from the payment account accordingly.

[0237] In one possible implementation of Embodiment 4 of this application, the data transaction device may further include the following module, which is used after determining the target service fee corresponding to the vehicle terminal based on the service fee of the target service:

[0238] The settlement module is used to process settlements based on prepaid fees and target service fees.

[0239] In one possible implementation of Embodiment 4 of this application, the prepayment request includes the identifier of the vehicle terminal. The data transaction device may further include the following module, which is used to determine the prepayment fee based on the service fee of the prepayment service, and then deduct the prepayment from the payment account based on the prepayment fee:

[0240] The decryption processing module is used to send the decrypted data of the roadside equipment corresponding to the prepaid service to the vehicle terminal according to the vehicle terminal's identifier, so that when the vehicle terminal receives the real-time service data from the roadside equipment, it can decrypt the real-time service data according to the decrypted data.

[0241] In one possible implementation of Embodiment 4 of this application, the service registration request further includes the identifier of the roadside device, and the decryption data includes the key data of the roadside device. The roadside device pre-encrypts the real-time service data using the key data. The aforementioned data transaction device may further include the following module, which is used to send the decryption data of the roadside device corresponding to the prepaid service to the vehicle terminal according to the identifier of the vehicle terminal, so that the vehicle terminal can perform decryption processing on the real-time service data based on the decryption data when receiving the real-time service data from the roadside device:

[0242] The third generation module is used to generate key data for each roadside device based on the preset key and the identifier of each roadside device.

[0243] The sixth sending module is used to send the key data of each roadside device to each roadside device respectively.

[0244] As one possible implementation, the above-mentioned decryption processing module may include the following sub-modules:

[0245] The first sending submodule is used to send the key data of the roadside equipment corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier.

[0246] In one possible implementation of Embodiment 4 of this application, the decrypted data includes coordinate inversion data of the roadside equipment. The roadside equipment pre-encrypts the real-time service data using the coordinate inversion data corresponding to the coordinate inversion data. The aforementioned data transaction device may further include the following module, which is used to send the decrypted data of the roadside equipment corresponding to the prepaid service to the vehicle terminal according to the vehicle terminal's identifier, so that the vehicle terminal, upon receiving the real-time service data from the roadside equipment, can perform decryption processing on the real-time service data based on the decrypted data before doing so:

[0247] The seventh acquisition module is used to acquire coordinate deflection data sent by each roadside device.

[0248] Among them, the coordinate deflection data is generated by the roadside equipment based on its own position information.

[0249] The fourth generation module is used to generate the coordinate reverse deflection data of each roadside device based on the coordinate deflection data of each roadside device.

[0250] As one possible implementation, the above decryption processing module may include the following sub-modules:

[0251] The second sending submodule is used to send the coordinate reverse deflection data of the roadside equipment corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier.

[0252] In one possible implementation of Embodiment 4 of this application, the prepayment request includes the identifier of the vehicle terminal. The data transaction device may further include the following module, which is used to determine the prepayment fee based on the service fee of the prepayment service and to deduct the payment from the payment account based on the prepayment fee:

[0253] The eighth acquisition module is used to acquire the first identity authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal.

[0254] The first authentication module is used to authenticate the vehicle terminal based on its identifier, so as to determine the result of the cloud platform's second authentication of the vehicle terminal.

[0255] The third determination module is used to confirm that both the first and second identity authentication results are successful.

[0256] In one possible implementation of Embodiment 4 of this application, the data transaction device may further include the following module, used before settlement processing based on prepaid fees and target service fees:

[0257] The ninth acquisition module is used to acquire the third-party authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal.

[0258] The second authentication module is used to authenticate the vehicle terminal based on its identifier, so as to determine the result of the cloud platform's fourth authentication of the vehicle terminal.

[0259] The fourth determination module is used to confirm that both the third-party authentication result and the fourth-party authentication result are successful.

[0260] The data transaction device provided in this application embodiment can be applied in the aforementioned method embodiment one. For details, please refer to the description of the above method embodiment one, which will not be repeated here.

[0261] See Figure 7 The diagram shows a schematic of a data transaction device provided in Embodiment 5 of this application. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0262] This data transaction device is applied to vehicle terminals and may specifically include the following modules:

[0263] The third acquisition module 701 is used to acquire real-time service data sent by the roadside equipment, wherein the real-time service data includes the identifier of the roadside equipment.

[0264] The first sending module 702 is used to send a service usage confirmation data frame to the roadside equipment and the cloud platform according to the identification of the roadside equipment, so that the cloud platform can determine the target service fee based on the service usage confirmation data frame.

[0265] The service usage confirmation data frame includes service usage information.

[0266] The data transaction device disclosed in the above embodiments of this application is applied to a vehicle terminal. First, it acquires real-time service data sent by roadside equipment. Then, based on the identifier of the roadside equipment, it sends a service usage confirmation data frame to both the roadside equipment and the cloud platform, enabling the cloud platform to determine the target service fee based on the service usage confirmation data frame. Thus, by acquiring service data during vehicle operation to use the corresponding service, and by sending a service usage confirmation data frame to the roadside equipment and the cloud platform to determine the target service fee, automatic fee calculation and settlement are achieved when using data services provided by the vehicle wireless communication system, improving the convenience of transactions.

[0267] In one possible implementation of Embodiment 5 of this application, the data transaction device may further include the following module, which is used before acquiring real-time service data sent by the roadside equipment:

[0268] The seventh sending module is used to send service acquisition requests to the cloud platform.

[0269] The service request includes the vehicle terminal's identifier and the expected travel route.

[0270] The tenth acquisition module is used to acquire service information corresponding to the expected roadside equipment sent by the cloud platform.

[0271] The roadside equipment to be passed is the roadside equipment included in the expected travel route. The service information corresponding to the roadside equipment to be passed is obtained by the cloud platform from its own stored service list based on the expected travel route.

[0272] The display module is used to display service information corresponding to the roadside equipment that is expected to pass by.

[0273] The fifth determination module is used to obtain the user's operation instructions for the service information corresponding to the roadside equipment expected to pass by, and to determine the prepaid service based on the operation instructions.

[0274] The eighth sending module is used to generate a prepaid request based on the prepaid service and send it to the cloud platform.

[0275] The prepaid request includes the prepaid service and the payment account information corresponding to the vehicle terminal.

[0276] In one possible implementation of Embodiment 5 of this application, the data transaction device may further include the following module, which is used before sending a service acquisition request to the cloud platform:

[0277] The eleventh acquisition module is used to acquire the destination information input by the user and the current location information of the vehicle where the vehicle terminal is located.

[0278] The fifth generation module is used to perform route planning based on destination information and current location information to generate the expected driving route.

[0279] In one possible implementation of Embodiment 5 of this application, the data transaction device may further include the following module, which is used before generating a prepaid request based on the prepaid service and sending it to the cloud platform:

[0280] The sixth determination module is used to perform identity authentication on the cloud platform to determine the first identity authentication result of the vehicle terminal on the cloud platform;

[0281] Correspondingly, the eighth sending module mentioned above may specifically include the following sub-modules:

[0282] The generation submodule is used to generate a prepaid request based on the prepaid service and the first identity authentication result and send it to the cloud platform. The prepaid request also includes the first identity authentication result.

[0283] In one possible implementation of Embodiment 5 of this application, the data transaction device may further include the following module, which is used to send a service usage confirmation data frame to the roadside equipment and the cloud platform based on the identifier of the roadside equipment, so that the cloud platform can determine the target service fee based on the service usage confirmation data frame:

[0284] The twelfth acquisition module is used to acquire the decrypted data corresponding to the roadside equipment sent by the cloud platform.

[0285] The sixth generation module is used to decrypt the real-time service data based on the decrypted data to generate the plaintext data corresponding to the real-time service data.

[0286] The data transaction device provided in this application embodiment can be applied in the aforementioned method embodiment two. For details, please refer to the description of the above method embodiment two, which will not be repeated here.

[0287] See Figure 8 The diagram shows a schematic of a data transaction device provided in Embodiment Six of this application. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0288] This data trading device is used in roadside equipment and may specifically include the following modules:

[0289] The second sending module 801 is used to send a service registration request to the cloud platform.

[0290] The service registration request includes the location information of the roadside equipment, the type of service provided, and the service fee.

[0291] The third sending module 802 is used to send real-time service data to the vehicle terminal.

[0292] The real-time service data includes the identification of roadside equipment.

[0293] The fourth acquisition module 803 is used to acquire the service usage confirmation data frame sent by the vehicle terminal.

[0294] The second generation module 804 is used to generate a transaction data frame corresponding to the service usage confirmation data frame based on the service usage information included in the service usage confirmation data frame.

[0295] The transaction data frame includes service production information.

[0296] The fourth sending module 805 is used to send the transaction data frame to the cloud platform so that the cloud platform can determine the target service fee based on the transaction data frame.

[0297] The data transaction device disclosed in the above embodiments of this application is applied to roadside equipment. First, it sends a service registration request to a cloud platform. Then, it sends real-time service data to the vehicle terminal. Next, it obtains a service usage confirmation data frame sent by the vehicle terminal. Then, based on the service usage information included in the service usage confirmation data frame, it generates a transaction data frame corresponding to the service usage confirmation data frame. Finally, it sends the transaction data frame to the cloud platform so that the cloud platform can determine the target service fee based on the transaction data frame. Thus, by generating a transaction data frame upon obtaining the service usage confirmation data frame sent by the vehicle terminal and sending the transaction data frame to the cloud platform to determine the target service fee, it achieves automatic calculation and payment of service fees. This realizes automatic fee calculation and settlement when using data services provided by the vehicle wireless communication system, improving the convenience of transactions.

[0298] In one possible implementation of Embodiment Six of this application, the data transaction device may further include the following module, which is used before sending real-time service data to the vehicle terminal:

[0299] The thirteenth acquisition module is used to acquire the key data sent by the cloud platform.

[0300] The first encryption module is used to encrypt real-time service data based on key data.

[0301] In one possible implementation of Embodiment Six of this application, the data transaction device may further include the following module, which is used before sending real-time service data to the vehicle terminal:

[0302] The seventh generation module is used to perform coordinate deflection processing on the location information to generate coordinate deflection data, which is then sent to the cloud platform.

[0303] The second encryption module is used to encrypt real-time service data based on coordinate deflection data.

[0304] The data transaction device provided in this application embodiment can be applied in the aforementioned method embodiment three. For details, please refer to the description of the above method embodiment three, which will not be repeated here.

[0305] Figure 9 This is a schematic diagram of the terminal device provided in Embodiment 7 of this application. Figure 9 As shown, the terminal device 900 of this embodiment includes: at least one processor 910 ( Figure 9 (Only one is shown in the diagram) a processor, a memory 920, and a computer program 921 stored in the memory 920 and executable on the at least one processor 910, wherein the processor 910 executes the computer program 921 to implement the steps in the above-described data transaction method embodiments.

[0306] The terminal device 900 can be a desktop computer, laptop, handheld computer, cloud server, or other computing device. This terminal device may include, but is not limited to, a processor 910 and a memory 920. Those skilled in the art will understand that... Figure 9 This is merely an example of terminal device 900 and does not constitute a limitation on terminal device 900. It may include more or fewer components than shown in the figure, or combine certain components, or different components, such as input / output devices, network access devices, etc.

[0307] The processor 910 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0308] In some embodiments, the memory 920 may be an internal storage unit of the terminal device 900, such as a hard disk or memory of the terminal device 900. In other embodiments, the memory 920 may be an external storage device of the terminal device 900, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device 900. Furthermore, the memory 920 may include both internal and external storage units of the terminal device 900. The memory 920 is used to store the operating system, applications, boot loader, data, and other programs, such as the program code of the computer program. The memory 920 can also be used to temporarily store data that has been output or will be output.

[0309] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0310] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0311] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0312] In the embodiments provided in this application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0313] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0314] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0315] If the integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc. It should be noted that the content included in the computer-readable medium can be appropriately added or removed according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable media do not include electrical carrier signals and telecommunication signals.

[0316] The implementation of all or part of the processes in the methods of the above embodiments can also be accomplished by a computer program product. When the computer program product is run on a terminal device, the terminal device can implement the steps in the various method embodiments described above.

[0317] The embodiments described above are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A data transaction method, characterized in that, A cloud platform applied to a vehicle wireless communication system, wherein the vehicle wireless communication system further includes vehicle terminals and roadside equipment, and the data transaction method includes: Obtain service registration requests sent by each of the roadside devices, wherein the service registration requests include the location information of the roadside devices, the type of service provided, and the service fee; Based on each of the service registration requests, a service list is generated and stored, wherein the service list includes service information corresponding to each of the roadside devices; Obtain the service acquisition request sent by the vehicle terminal, wherein the service acquisition request includes the vehicle terminal's identifier and the expected driving route; According to the expected driving route, the service information corresponding to the expected roadside equipment is obtained from the service list and sent to the vehicle terminal, so that the vehicle terminal can perform prepayment processing according to the service information corresponding to the expected roadside equipment. The expected roadside equipment is the roadside equipment included in the expected driving route. Obtain the prepayment request sent by the vehicle terminal, wherein the prepayment request includes the prepayment service and the payment account corresponding to the vehicle terminal; Based on the service fee of the prepaid service, determine the prepaid fee, and deduct the payment from the payment account according to the prepaid fee; Obtain the service usage confirmation data frame sent by the vehicle terminal and the transaction data frame sent by the target roadside device corresponding to the service usage confirmation data frame; Based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame, the target service used by the vehicle terminal is determined. The target service fee corresponding to the vehicle terminal is determined based on the service fee of the target service. Settlement is processed based on the prepaid fees and the target service fees.

2. The data transaction method as described in claim 1, characterized in that, The prepaid request includes the identifier of the vehicle terminal. After determining the prepaid fee based on the service fee of the prepaid service and deducting the payment from the payment account based on the prepaid fee, the process further includes: Based on the identifier of the vehicle terminal, the decrypted data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal, so that when the vehicle terminal receives the real-time service data of the roadside equipment, it can decrypt the real-time service data according to the decrypted data.

3. The data transaction method as described in claim 2, characterized in that, The service registration request also includes the identifier of the roadside device, and the decryption data includes the key data of the roadside device. The roadside device pre-encrypts the real-time service data using the key data. The step of sending the decryption data of the roadside device corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier, so that the vehicle terminal, upon receiving the real-time service data from the roadside device, decrypts the real-time service data based on the decryption data before performing the decryption process, further includes: Based on the preset key and the identifier of each roadside device, key data for each roadside device is generated respectively; The key data of each of the roadside devices is sent to each of the roadside devices respectively; The step of sending decrypted data of the roadside equipment corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier includes: Based on the vehicle terminal's identifier, the key data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal.

4. The data transaction method as described in claim 2, characterized in that, The decrypted data includes the coordinate inverse deflection data of the roadside equipment. The roadside equipment pre-encrypts the real-time service data using the coordinate deflection data corresponding to the coordinate inverse deflection data. The step of sending the decrypted data of the roadside equipment corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier, so that the vehicle terminal, upon receiving the real-time service data from the roadside equipment, decrypts the real-time service data based on the decrypted data before performing the decryption process, further includes: The coordinate deflection data sent by each of the roadside devices is obtained, wherein the coordinate deflection data is generated by the roadside device based on its own position information; Based on the coordinate deflection data of each roadside device, coordinate reverse deflection data of each roadside device is generated respectively; The step of sending decrypted data of the roadside equipment corresponding to the prepaid service to the vehicle terminal based on the vehicle terminal's identifier includes: Based on the vehicle terminal's identifier, the coordinate reverse deflection data of the roadside equipment corresponding to the prepaid service is sent to the vehicle terminal.

5. The data transaction method as described in claim 1, characterized in that, The prepaid request includes the identifier of the vehicle terminal. Before determining the prepaid fee based on the service fee of the prepaid service and deducting the payment from the payment account based on the prepaid fee, the process further includes: Obtain the first identity authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal; Based on the identifier of the vehicle terminal, the vehicle terminal is authenticated to determine the second authentication result of the vehicle terminal by the cloud platform; It is confirmed that both the first and second identity authentication results are successful.

6. The data transaction method as described in claim 5, characterized in that, Before performing the settlement process based on the prepaid fee and the target service fee, the method further includes: Obtain the third-party authentication result of the vehicle terminal to the cloud platform sent by the vehicle terminal; Based on the identifier of the vehicle terminal, the vehicle terminal is authenticated to determine the fourth authentication result of the vehicle terminal by the cloud platform; It is confirmed that both the third and fourth identity authentication results are successful.

7. A data transaction method, characterized in that, A vehicle terminal used in a vehicle wireless communication system, the vehicle wireless communication system further including a cloud platform and roadside equipment, the data transaction method including: Acquire real-time service data sent by roadside equipment, wherein the real-time service data includes the identifier of the roadside equipment; Based on the identifier of the roadside equipment, a service usage confirmation data frame is sent to the roadside equipment and the cloud platform, so that the cloud platform can determine the target service fee based on the service usage confirmation data frame, wherein the service usage confirmation data frame includes service usage information; The cloud platform performs settlement processing through the following steps: The cloud platform obtains service registration requests sent by each roadside device, wherein the service registration request includes the location information of the roadside device, the type of service provided, and the service fee; the cloud platform generates and stores a service list based on each service registration request, wherein the service list includes service information corresponding to each roadside device; the cloud platform obtains service acquisition requests sent by the vehicle terminal, wherein the service acquisition request includes the vehicle terminal's identifier and the expected travel route; the cloud platform, based on the expected travel route, retrieves the service information corresponding to the expected roadside devices from the service list and sends it to the vehicle terminal, so that the vehicle terminal can perform prepayment processing based on the service information corresponding to the expected roadside devices, wherein the expected roadside devices are those included in the expected travel route. The process includes: the roadside equipment; the cloud platform acquiring a prepayment request sent by the vehicle terminal, wherein the prepayment request includes a prepayment service and a payment account corresponding to the vehicle terminal; the cloud platform determining a prepayment fee based on the service fee of the prepayment service, and deducting the prepayment fee from the payment account; the cloud platform acquiring a service usage confirmation data frame sent by the vehicle terminal and a transaction data frame sent by the target roadside equipment corresponding to the service usage confirmation data frame; the cloud platform determining the target service used by the vehicle terminal based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame; the cloud platform determining the target service fee corresponding to the vehicle terminal based on the service fee of the target service; and the cloud platform performing settlement processing based on the prepayment fee and the target service fee.

8. The data transaction method as described in claim 7, characterized in that, Before acquiring the real-time service data sent by the roadside equipment, the method further includes: Send a service acquisition request to the cloud platform, wherein the service acquisition request includes the identifier of the vehicle terminal and the expected driving route; The cloud platform obtains service information corresponding to the roadside devices expected to be passed through, wherein the roadside devices expected to be passed through are the roadside devices included in the expected driving path, and the service information corresponding to the roadside devices expected to be passed through is obtained by the cloud platform from its own stored service list according to the expected driving path. Display the service information corresponding to the roadside equipment that is expected to pass by; Obtain the user's operation instructions for the service information corresponding to the roadside equipment expected to be passed, and determine the prepaid service based on the operation instructions; A prepayment request is generated based on the prepayment service and sent to the cloud platform, wherein the prepayment request includes the prepayment service and the payment account information corresponding to the vehicle terminal.

9. The method as described in claim 8, characterized in that, Before sending the service acquisition request to the cloud platform, the method further includes: Obtain the destination information input by the user and the current location information of the vehicle where the vehicle terminal is located; Based on the destination information and the current location information, route planning is performed to generate the expected driving route.

10. The method as described in claim 8, characterized in that, Before generating a prepaid request based on the prepaid service and sending it to the cloud platform, the process also includes: The cloud platform is used to authenticate the vehicle terminal's identity, thereby determining the vehicle terminal's first authentication result with the cloud platform. The step of generating a prepaid request based on the prepaid service and sending it to the cloud platform includes: The prepaid request is generated based on the prepaid service and the first identity authentication result and sent to the cloud platform. The prepaid request also includes the first identity authentication result.

11. The data transaction method as described in any one of claims 7-10, characterized in that, Before sending a service usage confirmation data frame to the roadside device and the cloud platform based on the identifier of the roadside device, so that the cloud platform can determine the target service fee based on the service usage confirmation data frame, the method further includes: Obtain the decrypted data corresponding to the roadside device sent by the cloud platform; Based on the decrypted data, the real-time service data is decrypted to generate plaintext data corresponding to the real-time service data.

12. A data transaction method, characterized in that, A roadside device used in a vehicle wireless communication system, wherein the vehicle wireless communication system further includes a cloud platform and vehicle terminals, and the data transaction method includes: Send a service registration request to the cloud platform, wherein the service registration request includes the location information of the roadside equipment, the type of service provided, and the service fee; Send real-time service data to the vehicle terminal, wherein the real-time service data includes the identifier of the roadside equipment; Obtain the service usage confirmation data frame sent by the vehicle terminal; Based on the service usage information included in the service usage confirmation data frame, a transaction data frame corresponding to the service usage confirmation data frame is generated, wherein the transaction data frame includes service production information; The transaction data frame is sent to the cloud platform so that the cloud platform can determine the target service fee based on the transaction data frame; The cloud platform performs settlement processing through the following steps: The cloud platform obtains service registration requests sent by each roadside device, wherein the service registration request includes the location information of the roadside device, the type of service provided, and the service fee; the cloud platform generates and stores a service list based on each service registration request, wherein the service list includes service information corresponding to each roadside device; the cloud platform obtains service acquisition requests sent by the vehicle terminal, wherein the service acquisition request includes the vehicle terminal's identifier and the expected travel route; the cloud platform, based on the expected travel route, retrieves the service information corresponding to the expected roadside devices from the service list and sends it to the vehicle terminal, so that the vehicle terminal can perform prepayment processing based on the service information corresponding to the expected roadside devices, wherein the expected roadside devices are those included in the expected travel route. The process includes: the roadside equipment; the cloud platform acquiring a prepayment request sent by the vehicle terminal, wherein the prepayment request includes a prepayment service and a payment account corresponding to the vehicle terminal; the cloud platform determining a prepayment fee based on the service fee of the prepayment service, and deducting the prepayment fee from the payment account; the cloud platform acquiring a service usage confirmation data frame sent by the vehicle terminal and a transaction data frame sent by the target roadside equipment corresponding to the service usage confirmation data frame; the cloud platform determining the target service used by the vehicle terminal based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame; the cloud platform determining the target service fee corresponding to the vehicle terminal based on the service fee of the target service; and the cloud platform performing settlement processing based on the prepayment fee and the target service fee.

13. The method as described in claim 12, characterized in that, Before sending real-time service data to the vehicle terminal, the method further includes: Obtain the key data sent by the cloud platform; The real-time service data is encrypted using the key data.

14. The method as described in claim 12, characterized in that, Before sending real-time service data to the vehicle terminal, the method further includes: The location information is subjected to coordinate deflection processing to generate coordinate deflection data, which is then sent to the cloud platform. The real-time service data is encrypted based on the coordinate deflection data.

15. A data transaction device, characterized in that, A cloud platform for use in vehicle wireless communication systems, wherein the vehicle wireless communication system further includes vehicle terminals and roadside equipment, and the data transaction device includes: The first acquisition module is used to acquire service registration requests sent by each of the roadside devices, wherein the service registration request includes the location information of the roadside device, the type of service provided, and the service fee; The first generation module is used to generate and store a service list based on each of the service registration requests, wherein the service list includes service information corresponding to each of the roadside devices; The fifth acquisition module is used to acquire service acquisition requests sent by the vehicle terminal, wherein the service acquisition request includes the vehicle terminal's identifier and the expected driving route; The fifth sending module is used to obtain the service information corresponding to the roadside equipment to be passed from the service list according to the expected driving route and send it to the vehicle terminal so that the vehicle terminal can perform prepayment processing according to the service information corresponding to the roadside equipment to be passed. The roadside equipment to be passed is the roadside equipment included in the expected driving route. The sixth acquisition module is used to acquire the prepayment request sent by the vehicle terminal, wherein the prepayment request includes the prepayment service and the payment account corresponding to the vehicle terminal. The deduction processing module is used to determine the prepaid fee based on the service fee of the prepaid service, and to deduct the prepaid fee from the payment account accordingly. The second acquisition module is used to acquire the service usage confirmation data frame sent by the vehicle terminal and the transaction data frame sent by the target roadside device corresponding to the service usage confirmation data frame. The first determining module is used to determine the target service that the vehicle terminal has used based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame. The second determining module is used to determine the target service fee corresponding to the vehicle terminal based on the service fee of the target service. The settlement module is used to process settlements based on prepaid fees and target service fees.

16. A data transaction device, characterized in that, A vehicle terminal used in a vehicle wireless communication system, the vehicle wireless communication system further including a cloud platform and roadside equipment, the data transaction device comprising: The third acquisition module is used to acquire real-time service data sent by the roadside equipment, wherein the real-time service data includes the identifier of the roadside equipment; The first sending module is used to send a service usage confirmation data frame to the roadside device and the cloud platform according to the identifier of the roadside device, so that the cloud platform can determine the target service fee according to the service usage confirmation data frame, wherein the service usage confirmation data frame includes service usage information; The cloud platform performs settlement processing through the following steps: The cloud platform obtains service registration requests sent by each roadside device, wherein the service registration request includes the location information of the roadside device, the type of service provided, and the service fee; the cloud platform generates and stores a service list based on each service registration request, wherein the service list includes service information corresponding to each roadside device; the cloud platform obtains service acquisition requests sent by the vehicle terminal, wherein the service acquisition request includes the vehicle terminal's identifier and the expected travel route; the cloud platform, based on the expected travel route, retrieves the service information corresponding to the expected roadside devices from the service list and sends it to the vehicle terminal, so that the vehicle terminal can perform prepayment processing based on the service information corresponding to the expected roadside devices, wherein the expected roadside devices are those included in the expected travel route. The process includes: the roadside equipment; the cloud platform acquiring a prepayment request sent by the vehicle terminal, wherein the prepayment request includes a prepayment service and a payment account corresponding to the vehicle terminal; the cloud platform determining a prepayment fee based on the service fee of the prepayment service, and deducting the prepayment fee from the payment account; the cloud platform acquiring a service usage confirmation data frame sent by the vehicle terminal and a transaction data frame sent by the target roadside equipment corresponding to the service usage confirmation data frame; the cloud platform determining the target service used by the vehicle terminal based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame; the cloud platform determining the target service fee corresponding to the vehicle terminal based on the service fee of the target service; and the cloud platform performing settlement processing based on the prepayment fee and the target service fee.

17. A data transaction device, characterized in that, A roadside device used in a vehicle wireless communication system, wherein the vehicle wireless communication system further includes a cloud platform and a vehicle terminal, and the data transaction device includes: The second sending module is used to send a service registration request to the cloud platform, wherein the service registration request includes the location information of the roadside equipment, the type of service provided, and the service fee; The third sending module is used to send real-time service data to the vehicle terminal, wherein the real-time service data includes the identifier of the roadside equipment; The fourth acquisition module is used to acquire the service usage confirmation data frame sent by the vehicle terminal; The second generation module is used to generate a transaction data frame corresponding to the service usage confirmation data frame based on the service usage information included in the service usage confirmation data frame, wherein the transaction data frame includes service production information. The fourth sending module is used to send the transaction data frame to the cloud platform so that the cloud platform can determine the target service fee based on the transaction data frame; The cloud platform performs settlement processing through the following steps: The cloud platform obtains service registration requests sent by each roadside device, wherein the service registration request includes the location information of the roadside device, the type of service provided, and the service fee; the cloud platform generates and stores a service list based on each service registration request, wherein the service list includes service information corresponding to each roadside device; the cloud platform obtains service acquisition requests sent by the vehicle terminal, wherein the service acquisition request includes the vehicle terminal's identifier and the expected travel route; the cloud platform, based on the expected travel route, retrieves the service information corresponding to the expected roadside devices from the service list and sends it to the vehicle terminal, so that the vehicle terminal can perform prepayment processing based on the service information corresponding to the expected roadside devices, wherein the expected roadside devices are those included in the expected travel route. The process includes: the roadside equipment; the cloud platform acquiring a prepayment request sent by the vehicle terminal, wherein the prepayment request includes a prepayment service and a payment account corresponding to the vehicle terminal; the cloud platform determining a prepayment fee based on the service fee of the prepayment service, and deducting the prepayment fee from the payment account; the cloud platform acquiring a service usage confirmation data frame sent by the vehicle terminal and a transaction data frame sent by the target roadside equipment corresponding to the service usage confirmation data frame; the cloud platform determining the target service used by the vehicle terminal based on the service usage information contained in the service usage confirmation data frame and the service production information contained in the transaction data frame; the cloud platform determining the target service fee corresponding to the vehicle terminal based on the service fee of the target service; and the cloud platform performing settlement processing based on the prepayment fee and the target service fee.

18. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1-7, or the method as described in any one of claims 7-11, or the method as described in any one of claims 12-14.

19. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-6, or the method as described in any one of claims 7-11, or the method as described in any one of claims 12-14.

Images