Vehicle payment method based on v2x and device thereof

Abstract

Embodiments of the present application relate to a vehicle payment method based on V2X and a device thereof, the method is performed by a service request terminal, comprising: receiving service information broadcasted by a service providing terminal based on a Pc5 interface, the service information being related to services that can be provided by the service providing terminal; sending a service request for a first service to the service providing terminal based on the Pc5 interface, wherein the service request comprises payment account information of the service request terminal, and the first service is at least part of the services that can be provided by the service providing terminal; receiving payment completion information from a payment institution terminal based on a Uu interface. By using the present application, vehicle payment can be more convenient.

Description

Technical Field

[0001] This application relates to the field of intelligent driving technology, and in particular to a vehicle payment method and device based on V2X. Background Technology

[0002] Currently, drivers and passengers typically use third-party payment methods for vehicle-related expenses. For example, drivers can use mobile payment apps to pay for things like car washes, parking, and refueling. However, this method doesn't cover all vehicle-related scenarios, such as when the driver isn't in the vehicle (e.g., in driverless vehicles), when the driver is driving and it's inconvenient to pay manually, or when there's no mobile phone available for payment in the car. Therefore, there's a need for a more widely applicable vehicle payment method. Summary of the Invention

[0003] In view of this, a V2X-based vehicle payment method and device are proposed, which can complete vehicle payment more conveniently.

[0004] In related technologies, vehicle payment systems require specific equipment (e.g., OBU) and have short communication distances. The above technical solutions can only be implemented when the vehicle enters the feasible communication area, potentially leading to traffic congestion. In technologies employing third-party payment applications, payment actions (e.g., scanning) must be performed by either the service-providing terminal or the service-requesting terminal before the payment can be executed, which poses difficulties for vehicle occupants, especially drivers. Furthermore, in all these methods, the distance between the service-providing terminal and the service-requesting terminal must be within line of sight; otherwise, scanning cannot be performed, which is also inconvenient for vehicle occupants.

[0005] In a first aspect, embodiments of this application provide a V2X-based vehicle payment method, which is executed by a service requesting terminal. The method includes: receiving service information broadcast by a service providing terminal via a PC5 interface, the service information being related to services that the service providing terminal can provide; sending a service request for a first service to the service providing terminal via the PC5 interface, wherein the service request includes payment account information of the service requesting terminal, and the first service is at least a portion of the services that the service providing terminal can provide; and receiving payment completion information from a payment institution terminal via a Uu interface.

[0006] The method described can employ multiple communication methods during the payment process, particularly using a PC5 interface between the service provider and the service requester, and a Uu interface between the service provider terminal and the payment institution terminal. This improves communication time and cleverly utilizes communication methods from the Internet of Vehicles (IoV) field. Furthermore, the payment process of this vehicle payment method does not require manual operation by vehicle personnel or service personnel, and is not limited by the distance between them, thus making it portable and secure.

[0007] In one possible design, before sending the service request for the first service, the method further includes: sending a payment account request to the payment institution via the Uu interface; and receiving the payment account information from the payment institution's terminal via the Uu interface.

[0008] Since the service request terminal and the payment institution terminal are far apart (remote communication), the service request terminal can send a payment account request to the payment institution via the Uu interface and receive the payment account information of the service request terminal via the Uu interface.

[0009] In one possible design, the payment account information is the terminal identifier of the service requesting terminal, and the terminal identifier is bound to the payment account of the service requesting terminal.

[0010] To facilitate quick payments, the service request terminal can bind its terminal identifier to a payment account, thereby saving the step of requesting a payment account.

[0011] In one possible design, before sending the service request for the first service, the method further includes: receiving billing information from the service providing terminal via the PC5 interface regarding the service requesting terminal accepting the first service; and determining, based on the billing information, that the first service meets preset service limitation conditions.

[0012] In this way, service requesting users can customize service limitations according to their personal preferences, and the service requesting terminal can automatically filter the first service that meets the service limitations to determine the first service suitable for the service requesting user, thereby improving the user experience.

[0013] Secondly, embodiments of this application provide a V2X-based vehicle payment method, executed by a service providing terminal, comprising: broadcasting service information that the service providing terminal can provide via a PC5 interface, the service information being related to services that the service providing terminal can provide; receiving a service request for a first service from a service requesting terminal via a PC5 interface, wherein the service request includes payment account information of the service requesting terminal, and the first service is at least a portion of the services that the service providing terminal can provide; sending a payment request to a payment institution terminal via a Uu interface regarding payment by the service requesting terminal for the first service, wherein the payment request includes billing information for the first service and payment account information of the service requesting terminal; and receiving payment completion information from the payment institution terminal via a Uu interface, indicating that the service requesting terminal has performed payment for the first service.

[0014] The described method can employ multiple communication methods during the payment process, particularly using a PC5 interface between the service provider and the service requester, and a Uu interface between the service provider terminal and the payment institution terminal. This improves communication time and cleverly utilizes communication methods from the Internet of Vehicles (IoV) field. Furthermore, this vehicle payment method eliminates the need for manual operation by vehicle and service personnel, and is not limited by distance, thus offering portability and security. With the payment account information of the service requesting terminal known, the service provider terminal can send a payment request to the payment institution terminal, allowing the payment terminal to complete the payment operation based on both the service requesting terminal's and the service provider terminal's payment account information.

[0015] In one possible design, after receiving the payment completion information, the method further includes: sending feedback to the service requesting terminal via the Pc5 interface that the service requesting terminal has completed payment for the first service.

[0016] In practice, since the service provider terminal and the service requesting terminal are close to each other, after the service provider terminal receives the payment completion operation from the payment institution terminal, it can send payment completion information to the service requesting terminal based on Pc5, thereby realizing that both the service provider terminal and the service requesting terminal have been notified that the payment has been completed.

[0017] Thirdly, embodiments of this application provide a V2X-based vehicle payment method, executed by a service requesting terminal, comprising: receiving service information broadcast by a service providing terminal via a PC5 interface, the service information being related to services that the service providing terminal can provide; sending a service request for a first service to the service providing terminal via a PC5 interface, wherein the first service is at least a portion of the services that the service providing terminal can provide; receiving payment account information of the service providing terminal and billing information of the service requesting terminal for accepting the first service from the service providing terminal via a PC5 interface; and sending a payment request to a payment institution terminal via a Uu interface, wherein the payment request includes the payment account information of the service providing terminal and the billing information.

[0018] The method described can employ multiple communication methods during the payment process, particularly using a PC5 interface between the service provider and the service requester, and a Uu interface between the service provider terminal and the payment institution terminal. This improves communication time and cleverly utilizes communication methods from the Internet of Vehicles (IoV) field. Furthermore, this vehicle payment method eliminates the need for manual operation by vehicle personnel and service personnel, and does not limit the distance between them, thus making it portable and secure. The service request terminal can use different communication methods to send different requests to different entities (service provider terminal or payment institution terminal).

[0019] In one possible design, after the step of sending the payment request, the method further includes: receiving payment completion information from the payment institution terminal via the Uu interface, indicating that the service requesting terminal has performed payment for the first service.

[0020] In this method, since the service request terminal and the payment institution terminal are far apart (remote communication), payment completion information can be received from the payment institution terminal based on the Uu interface.

[0021] Fourthly, embodiments of this application provide a V2X-based vehicle payment method, executed by a service providing terminal, comprising: broadcasting service information that the service providing terminal can provide via a PC5 interface, the service information being related to services that the service providing terminal can provide; receiving a service request for a first service from a service requesting terminal via a PC5 interface, wherein the first service is at least a portion of the services that the service providing terminal can provide; sending payment account information of the service providing terminal and the service requesting terminal's acceptance of the first service to the service requesting terminal via a PC5 interface; and receiving payment completion information from a payment institution terminal via a Uu interface, indicating that the service requesting terminal has performed payment for the first service.

[0022] The method described can employ multiple communication methods during the payment process, particularly using a PC5 interface between the service provider and the service requester, and a Uu interface between the service provider terminal and the payment institution terminal. This improves communication time and cleverly utilizes communication methods from the Internet of Vehicles (IoV) field. Furthermore, this vehicle payment method eliminates the need for manual operation by vehicle and service personnel, and is not limited by distance, thus offering portability and security. With the payment account information of the service provider terminal already known, the service provider terminal can send billing information and payment account information to the service requester terminal, allowing the service requester terminal to use this information to send a payment request to the payment institution terminal.

[0023] In one possible design, after receiving payment completion information from the payment institution terminal via the Uu interface, indicating that the service requesting terminal has performed payment for the first service, the method further includes: sending the payment completion information to the service requesting terminal via the Pc5 interface.

[0024] In practice, since the service provider terminal and the service requesting terminal are close to each other, after the service provider terminal receives the payment completion operation from the payment institution terminal, it can send payment completion information to the service requesting terminal based on Pc5, thereby realizing that both the service provider terminal and the service requesting terminal have been notified that the payment has been completed.

[0025] Fifthly, embodiments of this application provide a V2X-based vehicle payment device, comprising: a first receiving module, configured to receive service information broadcast by a service providing terminal via a PC5 interface, the service information being related to services that the service providing terminal can provide; a first sending module, configured to send a service request for a first service to the service providing terminal via a PC5 interface, wherein the service request includes payment account information of the service requesting terminal, and the first service is at least a portion of the services that the service providing terminal can provide; and a second receiving module, configured to receive payment completion information from a payment institution terminal via a Uu interface.

[0026] In one possible design, the device further includes: a second sending module for sending a payment account request to the payment institution via a Uu interface; and a third receiving module for receiving the payment account information from the payment institution's terminal via a Uu interface.

[0027] In one possible design, the payment account information is the terminal identifier of the service requesting terminal, and the terminal identifier is bound to the payment account of the service requesting terminal.

[0028] In one possible design, the device further includes: a fourth receiving module, configured to receive billing information from the service providing terminal via a Pc5 interface regarding the service requesting terminal's acceptance of the first service; and a first determining module, configured to determine that the first service meets preset service limitation conditions.

[0029] Sixthly, embodiments of this application provide a V2X-based vehicle payment device, comprising: a broadcast module for broadcasting service information that the service providing terminal can provide via a PC5 interface, the service information being related to services that the service providing terminal can provide; a first receiving module for receiving a service request for a first service from a service requesting terminal via a PC5 interface, wherein the service request includes payment account information of the service requesting terminal, and the first service is at least a portion of the services that the service providing terminal can provide; a first sending module for sending a payment request to a payment institution terminal via a Uu interface regarding the service requesting terminal paying for the first service, wherein the payment request includes billing information for the first service and payment account information of the service requesting terminal; and a second receiving module for receiving payment completion information from the payment institution terminal via a Uu interface, indicating that the service requesting terminal has performed payment for the first service.

[0030] In one possible design, the device further includes a second sending module for sending the payment completion information to the service request terminal via a Pc5 interface.

[0031] In a seventh aspect, embodiments of this application provide a V2X-based vehicle payment device, comprising: a first receiving module, configured to receive service information broadcast by a service providing terminal via a PC5 interface, the service information being related to services that the service providing terminal can provide; a first sending module, configured to send a service request for a first service to the service providing terminal via a PC5 interface, wherein the first service is at least a portion of the services that the service providing terminal can provide; a second receiving module, configured to receive payment account information of the service providing terminal and billing information of the service requesting terminal accepting the first service from the service providing terminal via a PC5 interface; and a second sending module, configured to send a payment request to a payment institution terminal via a Uu interface, wherein the payment request includes the payment account information of the service providing terminal and the billing information of the service requesting terminal accepting the first service.

[0032] In one possible design, the device further includes a third receiving module, configured to receive from the payment institution terminal via a Uu interface an indication that the service requesting terminal has performed payment for the first service.

[0033] Eighthly, embodiments of this application provide a V2X-based vehicle payment device, comprising: a broadcast module for broadcasting service information that the service providing terminal can provide via a PC5 interface, the service information being related to services that the service providing terminal can provide; a first receiving module for receiving a service request for a first service from a service requesting terminal via a PC5 interface, wherein the first service is at least a portion of the services that the service providing terminal can provide; a first sending module for sending payment account information of the service providing terminal and the service requesting terminal's acceptance of the first service to the service requesting terminal via a PC5 interface; and a second receiving module for receiving payment completion information from a payment institution terminal via a Uu interface, indicating that the service requesting terminal has performed payment for the first service.

[0034] In one possible design, the device further includes a second sending module, configured to send feedback to the service requesting terminal via a Pc5 interface, indicating that the service requesting terminal has completed payment for the first service.

[0035] Ninthly, embodiments of this application provide an electronic terminal, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured to implement a method of any one of the first, second, third, or fourth aspects when executing the instructions.

[0036] In a tenth aspect, embodiments of this application provide a non-volatile computer-readable storage medium having computer program instructions stored thereon, characterized in that the computer program instructions, when executed by a processor, implement a method of any one of the possible designs of the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0037] In one aspect, embodiments of this application provide a computer program product, characterized in that it includes instructions that, when executed on a computer, cause the computer to perform any of the possible designs of the first aspect, the second aspect, the third aspect, or the fourth aspect.

[0038] These and other aspects of this application will become more apparent in the description of the following embodiments(s). Attached Figure Description

[0039] The accompanying drawings, which are included in and form part of this specification, illustrate exemplary embodiments, features, and aspects of this application together with the specification and serve to explain the principles of this application.

[0040] Figure 1 This diagram illustrates an application scenario of vehicle payment according to an embodiment of this application.

[0041] Figure 2 This diagram illustrates a communication scenario of a vehicle payment system according to an embodiment of this application.

[0042] Figure 3 A diagram showing a vehicle payment device for performing vehicle payment according to an embodiment of this application;

[0043] Figure 4 A diagram illustrating the execution of a vehicle payment system according to an embodiment of this application;

[0044] Figure 5 A diagram illustrating the execution of a vehicle payment system according to another embodiment of this application;

[0045] Figure 6 A diagram illustrating the execution of a vehicle payment system according to another embodiment of this application;

[0046] Figure 7 A block diagram of a vehicle payment device according to another embodiment of this application is shown;

[0047] Figure 8 A block diagram of a vehicle payment device according to another embodiment of this application is shown;

[0048] Figure 9 A block diagram of a vehicle payment device according to another embodiment of this application is shown;

[0049] Figure 10 A block diagram of a vehicle payment device according to another embodiment of this application is shown. Detailed Implementation

[0050] Various exemplary embodiments, features, and aspects of this application will now be described in detail with reference to the accompanying drawings. The same reference numerals in the drawings denote elements that have the same or similar functions. Although various aspects of the embodiments are shown in the drawings, they are not necessarily drawn to scale unless specifically indicated otherwise.

[0051] In this application embodiment, " / " can indicate that the related objects are in an "or" relationship. For example, A / B can represent A or B. "And / or" can be used to describe three relationships between related objects. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. A and B can be singular or plural. To facilitate the description of the technical solutions in this application embodiment, the terms "first" and "second" can be used to distinguish technical features with the same or similar functions. These terms do not limit the quantity or execution order, and they are not necessarily different. In this application embodiment, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary" or "for example" should not be construed as being better or more advantageous than other embodiments or design solutions. The use of "exemplary" or "for example" is intended to present related concepts in a specific manner for ease of understanding.

[0052] Furthermore, to better illustrate this application, numerous specific details are provided in the following detailed embodiments. Those skilled in the art should understand that this application can be implemented without certain specific details. In some instances, methods, means, components, and circuits well-known to those skilled in the art have not been described in detail in order to highlight the main points of this application.

[0053] To better describe the technical solution of this application, the following will refer to Figure 1 Describe the vehicle payment scenario. Figure 1 This diagram illustrates an application scenario for vehicle payment according to an embodiment of this application.

[0054] A driver operates vehicle 110, which can perform vehicle-to-vehicle (V2V) communication with vehicle 120, or vehicle-to-infrastructure (V2I) communication with roadside infrastructure 130. In practice, to enable V2I communication with roadside infrastructure 130, a roadside unit (RSU) can be embedded within the roadside infrastructure; therefore, roadside infrastructure 130 can be referred to as RSU 130. Alternatively, vehicle 110 can perform vehicle-to-pedestrian (V2P) communication with pedestrian 140. Furthermore, vehicle 110 can also perform vehicle-to-network (V2N) communication with communication network 150 to obtain timely traffic information or billing information. These communication methods can be collectively referred to as V2X communication (where X represents anything).

[0055] like Figure 1 As shown, after the driver pays the relevant fees for vehicle 110, RSU 130 can receive an instruction from communication network 150 to allow vehicle 110 to pass, and open the gate of RSU 130 to allow vehicle 110 to pass through RSU 130 and drive.

[0056] Existing technologies require either the service-providing terminal or the service-requesting terminal to perform a payment action (e.g., scanning a QR code) before payment can be executed, which is inconvenient for vehicle occupants, especially drivers. Furthermore, in these methods, the distance between the service-providing terminal and the service-requesting terminal must be within line of sight; otherwise, scanning cannot be performed, which is also inconvenient for vehicle occupants.

[0057] Based on this, this application provides a V2X-based vehicle payment method. This method eliminates the need for manual operation by vehicle and service personnel, and is not limited by the distance between them, thus offering portability and security. To better understand the application scenarios of this application, the following will refer to... Figure 2 and Figure 3 The communication scenario of a vehicle payment system according to an embodiment of this application and a vehicle payment device for vehicle payment are described.

[0058] Figure 2 This diagram illustrates a communication scenario of a vehicle payment system according to an embodiment of this application. Figure 2 As shown, the communication system includes a base station 210 and various terminal devices 220 to 250. For ease of understanding, terminal devices 220 and 250 are vehicles, and terminal device 240 is a mobile terminal (e.g., a mobile phone) held by a user. In implementation, the types and number of terminal devices can be... Figure 4 This application does not limit the types or quantities produced, whether more or less.

[0059] As an example, this communication system is based on V2X. Within this system, based on the different communication interfaces, it can be divided into direct communication and cellular communication.

[0060] Cellular communication is a Uu-based communication method. In this method, any communication command sent by either party must first pass through the base station before being processed and forwarded by subsequent nodes; direct dialogue is not possible. Figure 2 As shown, the vehicle 220 and the mobile terminal 240 can use cellular communication via base station 210.

[0061] Direct communication is a communication method based on the PC5 interface. In this method, neighboring terminals are allowed to establish a direct link, and data transmission no longer passes through a base station relay. In other words, in this communication method, both parties can directly execute data transmission after using the base station to transmit signaling. Figure 4 As shown, vehicle 220 and RSU 230, as well as vehicle 220 and vehicle 250, directly transmit data to each other while using base station 210 to transmit signaling to each other.

[0062] Corresponding to the exemplary embodiments of this application, each terminal device in the vehicle payment system can adopt different communication methods according to payment needs. As an example, at the payment site (e.g., when a vehicle needs to pay for cleaning), since the distance between the two parties is relatively short, a direct communication method (based on the PC5 interface) can be used. When data transmission involving the payment institution's terminal requires remote transmission, a cellular communication method (based on the Uu interface) can be used.

[0063] Figure 3 This diagram illustrates a vehicle payment device for performing vehicle payments according to an embodiment of this application. The device can be any of the above-described devices or devices within those devices. The device can be a chip system. In this embodiment, the chip system can be composed of chips or may include chips and other discrete components. Device 300 includes at least one processor 320 for implementing the functions of the vehicle payment device in the method provided in this embodiment. Exemplarily, the processor 320 can generate payment information, etc., as detailed in the method examples, and will not be repeated here.

[0064] Device 300 may further include at least one memory 330 for storing program instructions and / or data. The memory 330 is coupled to the processor 320. The coupling in this embodiment is an indirect coupling or communication connection between devices, units, or modules, and may be electrical, mechanical, or other forms, for information exchange between devices, units, or modules. The processor 320 may operate in conjunction with the memory 330. The processor 320 may execute program instructions stored in the memory 330. At least one of the at least one memories may be included in the processor.

[0065] Device 300 may further include a communication interface 310 for communicating with other devices via a transmission medium, thereby enabling the devices in device 300 to communicate with other devices. For example, the communication interface 310 may be a PC5 interface performing direct communication or a Uu interface performing cellular communication. For example, the other device may be a terminal. Processor 320 utilizes the communication interface 310 to send and receive data and to implement... Figure 4 to Figure 6 The method performed by the above device in the corresponding embodiment.

[0066] This application embodiment does not limit the specific connection medium between the communication interface 310, processor 320, and memory 330. This application embodiment... Figure 3 The memory 330, processor 320, and communication interface 310 are connected via a bus 340. Figure 3 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 3 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0067] In the embodiments of this application, the processor may be a general-purpose processor, a digital information processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or executed by a combination of hardware and software modules within the processor.

[0068] In the embodiments of this application, the memory can be non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM). Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. The memory in the embodiments of this application can also be a circuit or any other device capable of implementing storage functions, used to store program instructions and / or data.

[0069] The following will refer to Figure 4 to Figure 6 The specific description illustrates a vehicle payment system performing a vehicle payment according to an embodiment of this application.

[0070] like Figure 4As shown, the vehicle payment system may include a payment institution terminal 41, a service provider terminal 42, and a vehicle 43. The payment institution terminal 41 refers to a payment institution authorized to operate on the accounts of the service request terminal and / or the service provider terminal. For example, the payment institution terminal 41 may provide corresponding accounts to the service request terminal 42 and / or the service provider terminal 43 based on their identification information, which indicates unique identity information for these terminals. For instance, the payment institution terminal may assign a corresponding account based on the business license of a gas station; or, for another example, the payment institution terminal 41 may assign a corresponding account to the vehicle driven by the driver based on the driver's license provided by the driver.

[0071] The payment institution terminal 41 can be a third-party payment application, and the application may have a pre-bound payment account (e.g., a bank account) or a backend server for the payment account (e.g., a bank's backend server). The terminal service provider terminal 42 refers to a merchant providing services to the service request terminal, such as a gas station, car wash, or highway entrance. The service request terminal 43 refers to a device that performs payment operations on vehicle-related fees. In this application, the service request terminal 43 can indicate a vehicle, or it can indicate a hardware device (e.g., a chip) capable of performing communication methods based on a PC5 interface and a Uu interface, or an apparatus including such a hardware device.

[0072] like Figure 4 As shown, in step S4010, the service providing terminal 42 can periodically broadcast the service information it provides based on the PC5 interface. This service information is related to the services that the service providing terminal can provide, and includes, but is not limited to, the service content and pricing information, such as car wash service and a charge of 20 yuan per wash. In the case of multiple service providing terminals and each providing different services, the same vehicle may receive service information for different services from different service providing terminals. For example, the same vehicle 43 may receive information about highway toll services and toll fees, parking services and parking fees, and refueling services and refueling fees.

[0073] In this scenario, since the communication coverage area of ​​the PC5-based communication method is very small, the service provider terminal can be determined by the vehicle's location. Specifically, since different service providers 42 serve different areas, the service provider 42 providing services to the vehicle 43 can be determined by the location where the vehicle 43 is parked. For example, the service provider providing refueling services and the service provider providing parking services are located in different areas, and the service provider providing services to the vehicle can be determined by the final parking location of the vehicle 43. Furthermore, if the vehicle 43 can receive billing information from multiple service providers at the same parking location, vehicle occupants (e.g., the driver or passengers) can use input devices on the vehicle 43 (e.g., touch screens or buttons) to determine the service provider terminal.

[0074] Following the above method, after determining the service provider terminal 42, vehicle 43 can send a service request for the first service to the service provider terminal 42 via the Pc5 interface in step S4020.

[0075] In an optional embodiment, before sending a service request to the service provider terminal 42, vehicle 43 may receive billing information from the service provider terminal 42 regarding services received by vehicle 43. Based on the billing information, vehicle 43 can determine the first service it will receive.

[0076] Specifically, the vehicle 43 can be pre-set with service limitations. These limitations can be a minimum amount for each service, a limit on the service provider, or a payment cap for a particular payment method. For example, a vehicle user can limit the car wash fee to no more than 40 yuan, or only use the payment method of this exemplary embodiment for services with a payment amount of 50 yuan or less, or pre-set a preferred refueling brand. In implementation, the vehicle 43 can determine whether the service meets the service limitations. If not, it exits the payment process or notifies the user. If it does, subsequent steps can be executed. Furthermore, the service limitations can also be a pre-set selection method by the vehicle user. For example, the service limitations could be the lowest-priced option. For instance, if a car wash offers multiple services, the service limitations could be the lowest-priced option, allowing the vehicle to determine, based on the billing information, which service meets the pre-set service limitations.

[0077] In step S4020, vehicle 43 may send a service request for the first service to service provider terminal 42 via the Pc5 interface, wherein the service request may include a vehicle identifier for identifying vehicle 43. In step S4030, after receiving the service request, service provider terminal 42 requests payment account information from payment institution terminal 43 via the Uu interface. In implementation, the payment account information may be account information obtained by service provider terminal 42 after registering with payment institution terminal 43.

[0078] Upon receiving the request, payment institution terminal 43 determines the payment account information of service provider terminal 42. In practice, payment institution terminal 43 can generate or search for payment account information corresponding to service provider terminal 42 based on the identification information of service provider terminal 42. In step S4040, payment institution terminal 41 sends the payment account information to service provider terminal 42.

[0079] In step S4050, the service providing terminal 42 may send the billing information of the service request terminal for accepting the first service and the payment account information of the service providing terminal 42 to the vehicle 43 via the Pc5 interface.

[0080] After receiving the bill information and the payment account information of the service provider terminal 42, in step S4060, vehicle 43 sends a payment request for the first service to payment institution terminal 41 via the Uu interface, wherein the payment request includes the bill information and the payment account information of the service provider terminal 42.

[0081] After receiving the payment request, the payment institution terminal 41 determines the payment information for this payment based on the billing information, wherein the payment information includes the payment account information of the service provider terminal 42, the payment account information of the vehicle 43, and the billing information of the first service.

[0082] The payment institution terminal 41 uses the payment information to complete the payment operation, that is, the payment account of the service provider terminal 42 accepts the payment from the payment account of the vehicle 43.

[0083] After payment is completed, in step S4070, the payment institution terminal 41 sends payment completion information to the vehicle 43 via the Uu interface, indicating that the vehicle 43 has completed payment for the first service.

[0084] In step S4080, the payment institution terminal 41 may also send the payment completion information to the service provider terminal 42 via the Uu interface.

[0085] In an optional implementation, vehicle 43 can also report to service provider terminal 42 via the PC5 interface that vehicle 43 has completed payment for the first service. Upon receiving the feedback from vehicle 43, service provider terminal 42 provides the first service to vehicle 43.

[0086] In addition, the vehicle payment system can also adopt, for example Figure 5 The operation is shown. The vehicle payment system may include a payment institution terminal 51, a service provider terminal 52, and a vehicle 53.

[0087] The payment institution terminal 51 refers to a payment institution authorized to operate on the accounts of service request terminals and / or service provider terminals. As an example, the payment institution terminal 51 can provide corresponding accounts to service request terminals 52 and / or service provider terminals 53 based on their identification information, which indicates unique identity information for these terminals. For instance, the payment institution terminal can assign a corresponding account based on the business license of a gas station; or, for another example, the payment institution terminal 51 can assign a corresponding account to a vehicle driven by a driver based on the driver's license provided by the driver.

[0088] The payment institution terminal 51 can be a third-party payment application, and the application may have a pre-bound payment account (e.g., a bank account) or a backend server for the payment account (e.g., a bank's backend server). The terminal service provider terminal 52 refers to a merchant providing services to the service request terminal, such as a gas station, car wash, or highway entrance. The service request terminal 53 refers to a device that performs payment operations on vehicle-related fees. In this application, the service request terminal 53 can indicate a vehicle, or it can indicate a hardware device (e.g., a chip) capable of performing communication methods based on a PC5 interface and a Uu interface, or an apparatus including such a hardware device.

[0089] like Figure 5 As shown, in step S5010, service provider terminal 52 can periodically broadcast its service information via the PC5 interface. This service information is related to the services the service provider terminal can offer, and includes, but is not limited to, the service content and pricing information, such as car wash service and a charge of 20 yuan per wash. In the presence of multiple service provider terminals, each offering different services, the same vehicle may receive service information for different services from different service provider terminals. For example, the same vehicle 53 may receive information about highway toll services and toll fees, parking services and parking fees, and refueling services and refueling fees.

[0090] In this scenario, since the communication coverage area of ​​the PC5-based communication method is small, the service provider terminal can be determined by the vehicle's location. Specifically, since different service providers 52 serve different areas, the service provider 52 providing services to the vehicle 53 can be determined by the location where the vehicle 53 is parked. For example, the service provider providing refueling services and the service provider providing parking services are located in different areas, and the service provider providing services to the vehicle can be determined by the final parking location of the vehicle 53. Furthermore, if the vehicle 53 receives billing information from multiple service providers at the same parking location, vehicle occupants (e.g., the driver or passengers) can use input devices on the vehicle 53 (e.g., touchscreen displays or buttons) to determine the service provider terminal.

[0091] Following the above method, after determining the service provider terminal 52, vehicle 53 can send a service request for the service to the service provider terminal 52 via the Pc5 interface in step S5020.

[0092] In an optional embodiment, before sending a service request to the service provider terminal 52, vehicle 53 may receive billing information from the service provider terminal 52 regarding services received by vehicle 53. Based on the billing information, vehicle 53 can determine the first service.

[0093] Specifically, the vehicle 53 can be pre-set with service restrictions. These restrictions can be limits on the amount for each service, limits on the service providers, or limits on the payment amount for a particular payment method. For example, a vehicle user can limit the car wash fee to no more than 40 yuan, or the vehicle user can only use the payment method of this exemplary embodiment for services with a payment amount of 50 yuan or less, or the vehicle user can pre-set a selected refueling brand. In implementation, the vehicle 53 can determine whether the service meets the service restrictions. If not, it exits the payment process or notifies the user. If the service meets the restrictions, subsequent steps can be executed.

[0094] Furthermore, the service restriction conditions can also be a selection method pre-set by the vehicle user. For example, the service restriction condition can be the lowest price selection method. For instance, when the same car wash offers multiple car wash services, the service restriction condition can be the lowest price selection method, allowing the vehicle to determine the service that meets the service restriction conditions based on the service restriction conditions and billing information.

[0095] A service request is sent to the service provider terminal 52 via the PC5 interface. This service request may include the vehicle's payment account information. Therefore, the vehicle 53 needs to determine its corresponding payment account.Figure 5 As shown, vehicle 53 requests payment account information from payment institution terminal 51 via the Uu interface. In practice, when requesting payment account information from payment institution terminal 51, vehicle 53 can send its vehicle identifier to payment institution terminal 51. Payment institution terminal 51 can then use the vehicle identifier to determine or generate payment account information for vehicle 53. Subsequently, payment institution terminal 51 can send the payment account information to vehicle 53 via the Uu interface.

[0096] Furthermore, as another example, vehicle 53 can send an account binding request to the payment institution terminal 51 via the Uu interface. This request may include a terminal identifier (e.g., a vehicle identifier) ​​as payment account information. Upon receiving the request, payment institution terminal 51 can determine the payment account corresponding to vehicle 53 based on the terminal identifier. Subsequently, payment institution 51 can bind the terminal identifier to the payment account. In this way, vehicle 53 can provide the terminal identifier (also referred to as payment account information) to service provider terminal 52.

[0097] After receiving the service request, the service provider terminal 52 can determine that the vehicle 53 accepts the billing information of the first service, and in step S5030, sends the billing information to the vehicle 53 based on the Pc5 interface.

[0098] In step S5040, the service provider terminal 52 may send a payment request for the vehicle 53 to pay for the first service to the payment institution terminal via the Uu interface. The payment request includes billing information and payment account information of the vehicle 53.

[0099] Upon receiving the payment request, payment institution terminal 51 determines the payment information, which includes the payment account information of service provider terminal 52, the payment account information of vehicle 53, and the billing information of the first service. As an example, payment institution terminal 51 can generate / determine the payment account information corresponding to service provider terminal 52 based on the identification information of service provider terminal 52.

[0100] The payment institution terminal 51 uses the payment information to complete the payment operation, that is, the payment account of the service provider terminal 52 accepts the payment from the payment account of the vehicle 52.

[0101] After payment is completed, in step S5050, the payment institution terminal 51 sends payment completion information indicating that payment has been made for the first service to the service provider terminal 52 via the Uu interface.

[0102] In step S5060, the payment institution terminal 51 may also send the payment completion information to the service provider terminal 52 via the Uu interface.

[0103] In an optional implementation, the service provider terminal 52 sends a notification to the vehicle 53 via the PC5 interface that the vehicle 53 has completed payment and provides the first service to the vehicle 53.

[0104] from Figure 4 and Figure 5 In terms of operation, after receiving a service request from vehicle 43 or 53, service provider terminal 41 or 51 can, according to its settings, choose to have vehicle 43 or 53 or service provider terminal 42 or 52 apply for payment account information from the payment institution terminal, and then obtain the corresponding payment account information from the payment institution terminal. In implementation, after vehicle 43 or 53 obtains the payment account information, service provider terminal 42 or 52 can initiate a payment request to the payment institution terminal upon receiving the payment account information from vehicle 43 or 53, and the payment terminal will execute the payment operation. In another implementation, after service provider terminal 42 or 52 obtains the payment account information, vehicle 43 or 53 can initiate a payment request to the payment institution terminal upon receiving the payment account information and billing information from service provider terminal 42 or 52, and the payment terminal will execute the payment operation.

[0105] In implementation, to increase payment convenience, vehicle 43 or 53 in the vehicle payment system can adopt, for example... Figure 6 The operation is shown. The vehicle payment system may include a payment institution terminal 61, a service provider terminal 62, and a vehicle 63.

[0106] In step S6010, vehicle 63 may send an account binding request to the payment institution terminal via the Uu interface. The request may include the vehicle identifier (i.e., the terminal identifier) ​​of vehicle 63. The vehicle identifier is not limited to the Vehicle Identification Number (VIN), which is equivalent to the vehicle's "ID card".

[0107] Upon receiving the request, payment institution terminal 61 can assign a payment account to vehicle 63 via the Uu interface and store the account corresponding to the vehicle identifier of vehicle 63. Subsequently, payment institution terminal 81 can send the payment account to vehicle 83. As an example, vehicle 63 can send either only the payment account or the vehicle identifier corresponding to the payment account to the service provider terminal each time a payment request is made via the Pc5 interface.

[0108] Furthermore, the vehicle payment system may also include a payment application terminal 34, which can indicate a terminal device (e.g., a mobile phone) with a payment application. In implementation, the payment application account of the payment application terminal 34 can be bound to the vehicle's vehicle identifier, meaning that each payment application account can be used to pay for the fees incurred by the vehicle.

[0109] To this end, the payment application terminal 34 can send an account binding request to the payment institution terminal 61. This request includes the payment application's payment account and vehicle identifier, both sent to the payment institution terminal 61. The payment institution terminal 61 can then bind the payment account to the vehicle identifier. For security, the payment institution terminal 61 can send random verification information (e.g., a random verification code) to the vehicle. Subsequently, the vehicle 63 can...

[0110] It is understood that, in order to achieve the aforementioned functions, the terminals and other devices described above include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in a hardware-driven or software-driven manner 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 the embodiments of this application.

[0111] This application embodiment can divide the aforementioned terminal, etc., into functional modules according to the above method examples. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0112] When dividing each function into modules according to its corresponding function. Figure 7 to Figure 10 The structural block diagrams of the V2X-based vehicle payment devices involved in the above embodiments are shown respectively.

[0113] like Figure 7 The vehicle payment device 700 may include a first receiving module 710, a first sending module 720, and a second receiving module 730.

[0114] The first receiving module 710 is used to receive service information broadcast by the service providing terminal based on the PC5 interface. The service information is related to the services that the service providing terminal can provide.

[0115] The first sending module 720 is used to send a service request for a first service to the service providing terminal via the PC5 interface, wherein the service request includes the payment account information of the service requesting terminal, and the first service is a service that at least some of the service providing terminals can provide.

[0116] The second receiving module 730 is used to receive payment completion information from the payment institution's terminal via the Uu interface.

[0117] Optionally, the vehicle payment device 700 further includes: a second sending module for sending a payment account request to the payment institution via a Uu interface; and a third receiving module for receiving the payment account information from the payment institution's terminal via a Uu interface.

[0118] Optionally, the payment account information is the terminal identifier of the service requesting terminal, and the terminal identifier is bound to the payment account of the service requesting terminal.

[0119] Optionally, the vehicle payment device 700 further includes: a fourth receiving module, configured to receive billing information from the service providing terminal via a PC5 interface regarding the service requesting terminal accepting the first service; and a first determining module, configured to determine, based on the billing information, that the first service meets preset service limitation conditions.

[0120] like Figure 8 As shown, the vehicle payment device 800 may include a broadcast module 810, a first receiving module 820, a first sending module 830, and a second receiving module 840.

[0121] The broadcast module 810 is used to broadcast service information that the service providing terminal can provide based on the Pc5 interface, and the service information is related to the services that the service providing terminal can provide.

[0122] The first receiving module 820 is used to receive a service request for a first service from a service requesting terminal via a PC5 interface, wherein the service request includes payment account information of the service requesting terminal, and the first service is a service that at least some of the service providing terminals can provide.

[0123] The first sending module 830 is used to send a payment request to the payment institution terminal via the Uu interface regarding the service request terminal paying for the first service, wherein the payment request includes the billing information of the first service and the payment account information of the service request terminal;

[0124] The second receiving module 840 is used to receive payment completion information from the payment institution terminal via the Uu interface, indicating that the service request terminal has executed payment for the first service.

[0125] Optionally, the vehicle payment device 800 further includes: a second sending module, used to send feedback to the service request terminal via the PC5 interface that the service request terminal has completed payment for the first service.

[0126] like Figure 9As shown, the vehicle payment device 900 may include a first receiving module 910, a first sending module 920, a second receiving module 930, and a second sending module 940.

[0127] The first receiving module 910 is used to receive service information broadcast by the service providing terminal based on the PC5 interface. The service information is related to the services that the service providing terminal can provide.

[0128] The first sending module 920 is used to send a service request for a first service to the service providing terminal via the PC5 interface, wherein the first service is a service that at least some of the service providing terminals can provide.

[0129] The second receiving module 930 is used to receive, via the PC5 interface, the payment account information of the service providing terminal and the billing information of the service requesting terminal for accepting the first service.

[0130] The second sending module 940 is used to send a payment request to the payment institution terminal via the Uu interface, wherein the payment request includes the payment account information and the billing information of the service providing terminal.

[0131] Optionally, the vehicle payment device 900 further includes: a third receiving module, configured to receive payment completion information from the payment institution terminal via a Uu interface, indicating that the service request terminal has performed payment for the first service.

[0132] like Figure 10 As shown, the vehicle payment device 1000 may include a broadcast module 1010, a first receiving module 1020, a first sending module 1030, and a second receiving module 1040.

[0133] The broadcast module 1010 is used to broadcast service information that the service providing terminal can provide based on the PC5 interface, and the service information is related to the services that the service providing terminal can provide.

[0134] The first receiving module 1020 is used to receive a service request for a first service from a service request terminal via a PC5 interface, wherein the first service is a service that at least some of the service providing terminals can provide.

[0135] The first sending module 1030 is used to send the payment account information of the service providing terminal and the acceptance of the first service by the service requesting terminal to the service requesting terminal via the PC5 interface.

[0136] The second receiving module 1040 is used to receive payment completion information from the payment institution terminal via the Uu interface, indicating that the service request terminal has performed payment for the first service.

[0137] Optionally, the vehicle payment device 1000 further includes a second sending module, used to send feedback to the service request terminal via a PC5 interface that the service request terminal has completed payment for the first service.

[0138] Computer-readable storage media can be tangible devices capable of holding and storing instructions for use by an instruction execution device. Computer-readable storage media can be, for example—but not limited to—electrical storage devices, magnetic storage devices, optical storage devices, electromagnetic storage devices, semiconductor storage devices, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of computer-readable storage media include: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), electrically programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), compact disc read-only memory (CD-ROM), digital video disc (DVD), memory sticks, floppy disks, mechanical encoding devices, such as punch cards or recessed protrusions storing instructions thereon, and any suitable combination of the foregoing.

[0139] The computer-readable program instructions or code described herein can be downloaded from computer-readable storage media to various computing / processing devices, or downloaded via a network, such as the Internet, local area network, wide area network, and / or wireless network, to an external computer or external storage device. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards them to the computer-readable storage media in the respective computing / processing device.

[0140] The computer program instructions used to perform the operations of this application may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Smalltalk, C++, etc., and conventional procedural programming languages ​​such as "C" or similar languages. The computer-readable program instructions may be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer may be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or may be connected to an external computer (e.g., via the Internet using an Internet service provider). In some embodiments, electronic circuits, such as programmable logic circuits, field-programmable gate arrays (FPGAs), or programmable logic arrays (PLAs), are personalized by utilizing state information from computer-readable program instructions. These electronic circuits can execute computer-readable program instructions to implement various aspects of this application.

[0141] Various aspects of this application are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0142] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processor of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner; thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0143] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0144] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction containing one or more executable instructions for implementing a specified logical function. In some alternative implementations, the functions marked in the blocks may occur in a different order than those shown in the drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved.

[0145] It should also be noted that each block in the block diagram and / or flowchart, as well as combinations of blocks in the block diagram and / or flowchart, can be implemented using hardware (such as circuits or ASICs (Application Specific Integrated Circuits)) that performs the corresponding function or action, or using a combination of hardware and software, such as firmware.

[0146] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple instances. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0147] The various embodiments of this application have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A V2X-based vehicle payment method, wherein the method is executed by a service request terminal, characterized in that, include: The service information is received via a PC5 interface from a service-providing terminal. The service information is related to the service provided by the service-providing terminal. The service-providing terminal is determined from multiple service-providing terminals providing different services based on the location of the service-requesting terminal. Based on the PC5 interface, receive billing information from the service providing terminal regarding the service requesting terminal accepting the first service; Based on the billing information, it is determined that the first service meets the preset service limitation conditions; A service request for a first service is sent to the service provider terminal via the PC5 interface, wherein the service request includes the payment account information of the service requesting terminal, and the first service is a service provided by at least some of the service provider terminals. Receive payment completion information from the payment institution's terminal via the Uu interface.

2. The method as described in claim 1, characterized in that, Before sending the service request for the first service, the method further includes: Send a payment account request to the payment institution via the Uu interface; The payment account information is received from the payment institution's terminal via the Uu interface.

3. The method as described in claim 1, characterized in that, The payment account information is the terminal identifier of the service requesting terminal, and the terminal identifier is bound to the payment account of the service requesting terminal.

4. A V2X-based vehicle payment method, wherein the method is executed by a service-providing terminal, corresponding to the V2X-based vehicle payment method executed by a service-requesting terminal as described in claim 1, characterized in that... include: Broadcast service information based on the PC5 interface, wherein the service information is related to the service provided by the service providing terminal, and the service providing terminal is determined from multiple service providing terminals providing different services based on the location of the service requesting terminal; The billing information for the first service received by the service requesting terminal is sent to the service requesting terminal via the PC5 interface. A service request for a first service is received from a service requesting terminal via a PC5 interface, wherein the service request includes the payment account information of the service requesting terminal, and the first service is a service provided by at least some of the service providing terminals. A payment request is sent to the payment institution's terminal via the Uu interface, requesting payment for the first service by the service requesting terminal. The payment request includes billing information for the first service received by the service requesting terminal and payment account information of the service requesting terminal. Based on the Uu interface, the system receives payment completion information from the payment institution's terminal, indicating that the service requesting terminal has executed payment for the first service.

5. The method as described in claim 4, characterized in that, After receiving the payment completion information, the method further includes: The system uses the PC5 interface to send a message to the service requesting terminal, indicating that the service requesting terminal has completed payment for the first service.

6. A V2X-based vehicle payment method, wherein the method is executed by a service request terminal, characterized in that, include: The service information is received via a PC5 interface from a service-providing terminal. The service information is related to the service provided by the service-providing terminal. The service-providing terminal is determined from multiple service-providing terminals providing different services based on the location of the service-requesting terminal. Based on the PC5 interface, receive billing information from the service providing terminal regarding the service requesting terminal accepting the first service; Based on the billing information, it is determined that the first service meets the preset service limitation conditions; A service request for a first service is sent to the service provider terminal via the PC5 interface, wherein the first service is a service provided by at least some of the service provider terminals. Based on the PC5 interface, the payment account information of the service provider terminal and the billing information of the service requesting terminal for accepting the first service are received from the service provider terminal. A payment request is sent to the payment institution's terminal via the Uu interface, wherein the payment request includes the payment account information and the billing information of the service provider terminal.

7. The method as described in claim 6, characterized in that, After sending the payment request, the method further includes: Based on the Uu interface, the system receives payment completion information from the payment institution's terminal, indicating that the service requesting terminal has executed payment for the first service.

8. A V2X-based vehicle payment method, wherein the method is executed by a service-providing terminal, corresponding to the V2X-based vehicle payment method executed by a service-requesting terminal as described in claim 6, characterized in that... include: Broadcast service information based on the PC5 interface, wherein the service information is related to the service provided by the service providing terminal, and the service providing terminal is determined from multiple service providing terminals providing different services based on the location of the service requesting terminal; The billing information for the first service received by the service requesting terminal is sent to the service requesting terminal via the PC5 interface. Based on the PC5 interface, a service request for a first service is received from a service request terminal, wherein the first service is a service provided by at least some of the service providing terminals; Based on the PC5 interface, the payment account information of the service providing terminal and the billing information of the service requesting terminal for accepting the first service are sent to the service requesting terminal. Based on the Uu interface, payment completion information is received from the payment institution terminal, indicating that the service request terminal has executed payment for the first service.

9. The method as described in claim 8, characterized in that, After receiving the payment completion information, the method further includes: Based on the PC5 interface, feedback is sent to the service requesting terminal that the service requesting terminal has completed payment for the first service.

10. A V2X-based vehicle payment device, applied to a service request terminal, characterized in that, include: The first receiving module is used to receive service information broadcast by a service providing terminal based on the PC5 interface. The service information is related to the service provided by the service providing terminal. The service providing terminal is determined from multiple service providing terminals providing different services based on the location of the service requesting terminal. The first sending module is configured to send a service request for a first service to the service providing terminal via the PC5 interface, wherein the service request includes the payment account information of the service requesting terminal, and the first service is a service provided by at least some of the service providing terminals. The second receiving module is used to receive payment completion information from the payment institution's terminal via the Uu interface; The fourth receiving module is used to receive billing information from the service providing terminal regarding the service requesting terminal accepting the first service via the Pc5 interface; The first determining module is used to determine, based on the billing information, that the first service meets preset service limitation conditions.

11. The device as claimed in claim 10, characterized in that, The device also includes: The second sending module is used to send a payment account request to the payment institution based on the Uu interface; The third receiving module is used to receive the payment account information from the payment institution's terminal via the Uu interface.

12. The device as claimed in claim 10, characterized in that, The payment account information is the terminal identifier of the service requesting terminal, and the terminal identifier is bound to the payment account of the service requesting terminal.

13. A V2X-based vehicle payment device, applied to a service providing terminal, corresponding to the V2X-based vehicle payment device applied to a service requesting terminal as described in claim 10, characterized in that, include: The broadcast module is used to broadcast service information based on the PC5 interface. The service information is related to the service provided by the service providing terminal, which is determined from multiple service providing terminals providing different services based on the location of the service requesting terminal. The first receiving module is configured to receive a service request for a first service from a service requesting terminal via a PC5 interface, wherein the service request includes payment account information of the service requesting terminal, and the first service is a service provided by at least some of the service providing terminals. The first sending module is used to send a payment request to the payment institution terminal via the Uu interface regarding the service request terminal paying for the first service, wherein the payment request includes the billing information of the first service and the payment account information of the service request terminal; The second receiving module is used to receive payment completion information from the payment institution terminal via the Uu interface, indicating that the service request terminal has executed payment for the first service; The third sending module is used to send the billing information of the service requesting terminal for receiving the first service to the service requesting terminal via the PC5 interface.

14. The device as claimed in claim 13, characterized in that, The device also includes: The second sending module is used to send feedback to the service requesting terminal via the Pc5 interface that the service requesting terminal has completed payment for the first service.

15. A V2X-based vehicle payment device, applied to a service request terminal, characterized in that, include: The first receiving module is used to receive service information broadcast by a service providing terminal based on the PC5 interface. The service information is related to the service provided by the service providing terminal. The service providing terminal is determined from multiple service providing terminals providing different services based on the location of the service requesting terminal. The first sending module is configured to send a service request for a first service to the service providing terminal via the Pc5 interface, wherein the first service is a service provided by at least some of the service providing terminals; The second receiving module is used to receive, via the PC5 interface, the payment account information of the service providing terminal and the billing information of the service requesting terminal for accepting the first service. The second sending module is used to send a payment request to the payment institution terminal via the Uu interface, wherein the payment request includes the payment account information of the service provider terminal and the billing information; The fourth receiving module is also configured to receive billing information from the service providing terminal regarding the service requesting terminal accepting the first service via the Pc5 interface; The first determining module is used to determine, based on the billing information, that the first service meets preset service limitation conditions.

16. The device as claimed in claim 15, characterized in that, The device also includes: The third receiving module is used to receive payment completion information from the payment institution terminal via the Uu interface, indicating that the service request terminal has executed payment for the first service.

17. A V2X-based vehicle payment device, applied to a service providing terminal, corresponding to the V2X-based vehicle payment device applied to a service requesting terminal as described in claim 15, characterized in that, include: The broadcast module is used to broadcast service information based on the PC5 interface. The service information is related to the service provided by the service providing terminal, which is determined from multiple service providing terminals providing different services based on the location of the service requesting terminal. The first receiving module is configured to receive a service request for a first service from a service request terminal via a Pc5 interface, wherein the first service is a service provided by at least some of the service providing terminals; The first sending module is used to send the payment account information of the service providing terminal and the service requesting terminal's acceptance of the first service to the service requesting terminal via the PC5 interface. The second receiving module is used to receive payment completion information from the payment institution terminal via the Uu interface, indicating that the service request terminal has performed payment for the first service; The third sending module is used to send the billing information of the service requesting terminal for receiving the first service to the service requesting terminal via the PC5 interface.

18. The device as claimed in claim 17, characterized in that, The device also includes: The second sending module is used to send feedback to the service requesting terminal via the PC5 interface, indicating that the service requesting terminal has completed payment for the first service.

19. An electronic terminal, characterized in that, include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the method of any one of claims 1 to 3, the method of any one of claims 4 to 5, the method of any one of claims 6 to 7, or the method of any one of claims 8 to 9 when executing the instructions.

20. A computer-readable storage medium having computer program instructions stored thereon, characterized in that, When the computer program instructions are executed by the processor, they implement the method according to any one of claims 1 to 3, the method according to any one of claims 4 to 5, the method according to any one of claims 6 to 7, or the method according to any one of claims 8 to 9.

21. A computer program product, characterized in that, Includes instructions that, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 3, the method of any one of claims 4 to 5, the method of any one of claims 6 to 7, or the method of any one of claims 8 to 9.

Images