Cloud-technology-based service transaction method, transaction cloud platform, and related product

Abstract

The embodiments of the present application belong to the technical field of clouds. Disclosed are a cloud-technology-based service transaction method, a transaction cloud platform, and a related product. In the embodiments of the present application, a transaction cloud platform is provided between charge point providers and charge point subscribers. A plurality of charge point providers list charge points provided by themselves on the transaction cloud platform, and charge point subscribers subscribe to charge points required thereby on the transaction cloud platform according to requirements. During the use of charge points by users for charging, the transaction cloud platform calculates charge fees of the plurality of users with respect to the charge point subscribers, and charge fees of the charge point subscribers with respect to the plurality of charge point providers. By means of the service transaction method provided in the embodiments of the present application, a third-party charge platform can quickly establish its own charge network. In addition, the complexity of using charge point subscribers is reduced for users.

Description

Service transaction methods, transaction cloud platforms and related products based on cloud technology

[0001] This application claims priority to Chinese Patent Application No. 202411020374.X, filed on July 27, 2024, entitled "Service Transaction Method, Transaction Cloud Platform and Related Products Based on Cloud Technology", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of cloud technology, and in particular to a service transaction method, transaction cloud platform and related products based on cloud technology. Background Technology

[0003] Currently, for service providers such as charge point operators (CPOs), service subscribers such as third-party charging platforms can directly subscribe to charging stations from the CPO. This allows users registered on the third-party charging platform to use these charging stations to charge their vehicles. This is a business-to-consumer (B2C) service transaction model. However, this model requires third-party charging platforms to subscribe to charging stations separately from each CPO, hindering their ability to quickly establish their own charging networks. Furthermore, this model increases the complexity for users selecting the desired charging stations on third-party charging platforms. Summary of the Invention

[0004] This application provides a service transaction method, transaction cloud platform, and related products based on cloud technology, which can help third-party charging platforms quickly establish their own charging networks and reduce the complexity for users when using third-party charging platforms. The technical solution is as follows:

[0005] Firstly, a service transaction method based on cloud technology is provided. This method is applied to a transaction cloud platform, which is used by charging pile subscribers to subscribe to charging piles provided by multiple charging pile providers. Multiple users are registered in the charging pile subscribers, and multiple users can use the charging piles subscribed to by the charging pile subscribers for charging.

[0006] In this method, at least one charging pile listed by multiple charging pile providers on a transaction cloud platform is obtained; a charging pile subscription interface is displayed, which includes the charging piles listed by the multiple charging pile providers; in response to the operation of the charging pile subscriber on the charging pile subscription interface, at least one charging pile subscribed by the charging pile subscriber is determined, and the charging pile subscriber is instructed to display the subscribed charging pile to multiple users; in response to multiple users using the charging pile subscribed by the charging pile subscriber, the charging fees between the multiple users and the charging pile subscriber, as well as the charging fees between the charging pile subscriber and the multiple charging pile providers, are settled.

[0007] Since the transaction cloud platform lists charging piles provided by multiple charging pile providers, charging pile subscribers do not need to subscribe to charging piles individually from each provider. Therefore, through the service transaction method provided in this application embodiment, third-party charging platforms and other charging pile subscribers can quickly establish their own charging networks. Furthermore, because the transaction cloud platform lists charging piles provided by multiple charging pile providers, charging pile subscribers can compare the charging piles provided by multiple providers according to their own user needs to subscribe to suitable charging piles, thereby reducing the complexity for users when using charging pile subscriptions.

[0008] Based on the method provided in the first aspect, in one possible implementation, the multiple users include a target user who subscribes to a target charging pile using a charging pile subscriber, and the multiple charging pile providers include a first charging pile provider, which is the charging pile provider that provides the target charging pile.

[0009] In this scenario, the process of settling charging fees between multiple users and the charging pile subscriber in response to multiple users using charging piles subscribed by the charging pile subscriber can be as follows: obtain the usage details of the target user using the target charging pile from the first charging pile provider; send the usage details to the charging pile subscriber, instructing the charging pile subscriber to display the charging billing results to the target user based on the usage details, and use the charging billing results to instruct the target user to transact charging fees with the charging pile subscriber.

[0010] After a user uses a target charging station subscribed to by the charging station subscriber, the transaction cloud platform obtains the usage details of the target charging station from the charging station provider. The transaction cloud platform then returns the obtained usage details to the charging station subscriber, enabling the charging station subscriber to determine the fee that the user needs to pay to the charging station subscriber, i.e., the charging fee, based on the usage details and pre-configured billing rules.

[0011] Based on the method provided in the first aspect, in one possible implementation, the multiple charging pile providers include a second charging pile provider. In this scenario, the process of settling charging fees between the charging pile subscriber and the multiple charging pile providers in response to multiple users using charging piles subscribed to by the charging pile subscriber can be as follows: Summarize the total charging pile usage details between the charging pile subscriber and the second charging pile provider, whereby the total charging pile usage details include the sum of usage details of all users within the charging pile subscriber using charging piles provided by the second charging pile provider; display the total charging pile usage details; in response to confirmation operations by the charging pile subscriber and the second charging pile provider regarding the total charging pile usage details, generate a charging bill based on the total charging pile usage details; and, based on the charging bill, transact the charging fees between the transaction accounts of the charging pile subscriber and the second charging pile provider.

[0012] In this embodiment of the application, the charging pile subscriber and the charging pile provider settle charging fees through a transaction cloud platform.

[0013] Based on the method provided in the first aspect, in one possible implementation, in response to multiple users using charging piles subscribed by a charging pile subscriber, after settling the charging fees between the charging pile subscriber and multiple charging pile providers, a first transaction query interface is also displayed; in response to any operation of any of the multiple charging pile providers on the first transaction query interface, the transaction details of that charging pile provider are displayed.

[0014] The transaction details provided by the charging station provider typically include a breakdown of charging fees received by the provider over a specific period. Through this method, the transaction cloud platform can also provide charging station providers with an income query function.

[0015] Based on the method provided in the first aspect, in one possible implementation, after settling the charging fees between the charging pile subscriber and multiple charging pile providers in response to multiple users using charging piles subscribed by the charging pile subscriber, a second transaction query interface is also displayed; in response to the charging pile subscriber's operation on the second transaction query interface, the transaction details of the charging pile subscriber are displayed.

[0016] The transaction details for charging station subscribers can, for example, include a breakdown of charging fees paid by the subscriber to the charging station provider over a specific period. Through this method, the transaction cloud platform can also provide charging station subscribers with a payment inquiry function.

[0017] Based on the method provided in the first aspect, in one possible implementation, before acquiring at least one charging pile listed on the transaction cloud platform by multiple charging pile providers, a first set of interfaces configured on any one of the multiple charging pile providers is acquired. The first set of interfaces includes a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface. A first interface debugging interface is displayed based on the first interface set. The first interface debugging interface includes debugging options corresponding to each interface in the first interface set. In response to the operation of the charging pile provider on the first interface debugging interface, the interfaces in the first interface set are debugged so that the transaction cloud platform can interact with the charging pile provider through the interfaces in the first interface set.

[0018] For any charging station provider, there is at least one interface. Other devices can use this interface to perform functions such as charging station query, charging station start, charging station stop, and usage details query. For ease of explanation later, the at least one interface configured on the charging station provider will be collectively referred to as the first interface set. The first interface set includes the charging station query interface, charging station start interface, charging station stop interface, and usage details query interface.

[0019] In this scenario, before the charging pile provider uploads the charging pile to the trading cloud platform, the trading cloud platform also needs to debug the interfaces in the first interface set to ensure that the charging pile provider and the trading cloud platform can interact normally.

[0020] Based on the method provided in the first aspect, in one possible implementation, the trading cloud platform is configured with a second set of interfaces. This second set of interfaces includes a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface. In this scenario, before displaying the charging pile subscription interface, a second interface debugging interface is displayed. This interface includes each interface in the second set of interfaces and instructs the charging pile subscriber to debug the interfaces in the second set, enabling the charging pile subscriber to interact with the trading cloud platform through the interfaces in the second set.

[0021] To facilitate interaction between charging pile subscribers and the trading cloud platform, a second set of interfaces is configured on the trading cloud platform. This second set of interfaces includes a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface, so that charging pile subscribers can call the interfaces in the second set to interact with the trading cloud platform.

[0022] In this scenario, before subscribing to a charging pile on the trading cloud platform, the charging pile subscriber needs to debug the interfaces in the second interface set to ensure that the charging pile subscriber and the trading cloud platform can interact normally.

[0023] Based on the method provided in the first aspect, in one possible implementation, before multiple charging pile providers each list at least one charging pile on the transaction cloud platform, a first onboarding interface is displayed; in response to any operation of one of the multiple charging pile providers on the first onboarding interface, the charging pile provider is authenticated; after confirming that the charging pile provider has passed authentication, a first service agreement is displayed, which includes the fee settlement rules between the charging pile provider and the charging pile subscriber; in response to the charging pile provider's confirmation of the first service agreement, the transaction account of the charging pile provider is opened.

[0024] Any charging station provider can join the transaction cloud platform through the above methods.

[0025] Based on the method provided in the first aspect, in one possible implementation, a second entry interface is displayed before the charging pile subscription interface is displayed; in response to the charging pile subscriber's operation on the second entry interface, the charging pile subscriber is authenticated; after confirming that the charging pile subscriber has been authenticated, a second service agreement is displayed, which includes the fee settlement rules between the charging pile subscriber and each of the multiple charging pile providers; in response to the charging pile subscriber's confirmation operation of the second service agreement, the charging pile subscriber's transaction account is opened.

[0026] Through the above methods, charging pile subscribers can register on the transaction cloud platform.

[0027] Based on the method provided in the first aspect, in one possible implementation, the process of obtaining at least one charging pile listed by multiple charging pile providers on the transaction cloud platform can be as follows: displaying a charging pile registration interface; receiving an operation from any one of the multiple charging pile providers on the charging pile registration interface, and obtaining at least one charging pile registered by that charging pile provider; displaying a charging pile listing interface, which includes listing options corresponding to each of the at least one registered charging pile; receiving an operation from that charging pile provider on the charging pile listing interface, and displaying at least one charging pile listed by that charging pile provider.

[0028] When charging pile providers list their charging piles on the trading cloud platform, they can first register all or some of their own charging piles on the trading cloud platform, and then choose which charging piles to list on the trading cloud platform, that is, choose which charging piles subscribers can subscribe to.

[0029] Secondly, a transaction cloud platform is provided, which has the function of implementing the service transaction method based on cloud technology described in the first aspect. The transaction cloud platform includes at least one module for implementing the service transaction method based on cloud technology provided in the first aspect.

[0030] Thirdly, a computing device cluster is provided, including at least one computing device, each computing device including a processor and memory;

[0031] The processor of the at least one computing device is used to execute instructions stored in the memory of the at least one computing device, so that the cluster of computing devices executes the cloud-based service transaction method provided in the first aspect.

[0032] Fourthly, a computer program product containing instructions is provided, which, when executed by a cluster of computing devices, causes the cluster of computing devices to perform the cloud-based service transaction method provided in the first aspect.

[0033] Fifthly, a computer-readable storage medium is provided, including computer program instructions, which, when executed by a computing device cluster, enable the computing device cluster to perform the cloud-based service transaction method provided in the first aspect.

[0034] The technical effects achieved by the corresponding technical means in the second to fifth aspects mentioned above are similar, and will not be repeated here. Attached Figure Description

[0035] Figure 1 is a schematic diagram of a scenario of an operator-led mode, a car manufacturer-led mode, and a charging platform-led mode provided in the embodiments of this application;

[0036] Figure 2 is a schematic diagram of the architecture of a service transaction system provided in an embodiment of this application;

[0037] Figure 3 is a schematic diagram of the architecture of another service transaction system provided in an embodiment of this application;

[0038] Figure 4 is a schematic diagram of the architecture of another service transaction system provided in an embodiment of this application;

[0039] Figure 5 is a flowchart of a service transaction method based on cloud technology provided in an embodiment of this application;

[0040] Figure 6 is a flowchart of another service transaction method based on cloud technology provided in an embodiment of this application;

[0041] Figure 7 is a schematic diagram of a site registration interface provided in an embodiment of this application;

[0042] Figure 8 is a schematic diagram of a site racking interface provided in an embodiment of this application;

[0043] Figure 9 is a schematic diagram of a site de-shelving interface provided in an embodiment of this application;

[0044] Figure 10 is a schematic diagram of the process for a charging pile provider to join a transaction cloud platform according to an embodiment of this application;

[0045] Figure 11 is a schematic diagram of a first interface debugging interface provided in an embodiment of this application;

[0046] Figure 12 is a schematic diagram of the process of a charging pile provider joining the transaction cloud platform and debugging the interface according to an embodiment of this application;

[0047] Figure 13 is a schematic diagram of a site subscription request page provided in an embodiment of this application;

[0048] Figure 14 is a schematic diagram of a site subscription interface provided in an embodiment of this application;

[0049] Figure 15 is a schematic diagram of the process for a charging pile subscriber to join a transaction cloud platform according to an embodiment of this application;

[0050] Figure 16 is a schematic diagram of a second interface debugging interface provided in an embodiment of this application;

[0051] Figure 17 is a schematic diagram of the process of a charging pile subscriber joining the transaction cloud platform and debugging the interface provided in an embodiment of this application;

[0052] Figure 18 is a schematic diagram of a process for settling fees between a charging pile subscriber and a user, provided in an embodiment of this application.

[0053] Figure 19 is a schematic diagram of a process for settling fees between a charging pile subscriber and a charging pile provider according to an embodiment of this application;

[0054] Figure 20 is a schematic diagram of the structure of a transaction cloud platform provided in an embodiment of this application;

[0055] Figure 21 is a schematic diagram of the structure of a computing device provided in an embodiment of this application;

[0056] Figure 22 is a schematic diagram of the structure of a computing device cluster provided in an embodiment of this application;

[0057] Figure 23 is a schematic diagram of another computing device cluster provided in an embodiment of this application. Detailed Implementation

[0058] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the implementation methods of this application will be further described in detail below with reference to the accompanying drawings.

[0059] Before explaining the embodiments of this application, the technical terms and application scenarios involved in the embodiments of this application will be introduced first.

[0060] A service refers to the resources and capabilities that users obtain in a self-service, on-demand, and online manner. This includes Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and Software as a Service (SaaS). Services provide intangible value or benefits to users. For example, a service might be a charging station, which users use to charge their cars. Another example is shared transportation, such as shared bicycles or cars, which users use as a means of transportation.

[0061] Resources: refers to physical or logical things generated during the process of users purchasing and using services.

[0062] Service provider: refers to the operator or enterprise that owns the service. For example, if the service is charging piles, the service provider is also called a charging pile provider, which typically includes charging pile operators or car manufacturers that can provide charging piles. Similarly, if the service is car sharing, the service provider is also called a car sharing provider, which typically includes car sharing operators.

[0063] Service subscriber: This refers to a third-party platform or company that subscribes to a service from the service provider. For example, if the service is charging stations, the service subscriber is also called a charging station subscriber. Charging station subscribers typically include third-party charging platforms or car manufacturers that need to subscribe to charging stations. Similarly, if the service is car sharing, the service subscriber is also called a car sharing subscriber. Car sharing subscribers typically include third-party car sharing platforms.

[0064] User: Refers to an account registered with a service subscriber. After registering with a service subscriber, a user can use the services subscribed to by that service subscriber. For example, if the service subscriber is a third-party charging platform, the user can be understood as an account registered on that third-party charging platform, and the user can use the charging stations subscribed to by that third-party charging platform for charging.

[0065] The following example uses charging piles as an illustration to illustrate the application scenario of this application's embodiments. It should be noted that the service transaction method provided in this application's embodiments is not limited to the charging pile scenario; any service requiring transactions between users, service subscribers, and service providers can apply the service transaction method provided in this application's embodiments. Further examples will not be provided here.

[0066] Driven by a new round of technological revolution in vehicle electrification and intelligentization, electric vehicles are experiencing explosive growth. Electric vehicles not only possess advantages in power, quietness, and autonomous driving, but also offer economic advantages compared to gasoline-powered vehicles, thus gaining increasing acceptance from consumers. In this process, charging infrastructure has been given a new mission and a new positioning, becoming a key support for "new energy vehicles and new power systems." As a component of charging infrastructure, the charging network plays an increasingly important role in the development of electric vehicles. A charging network can be understood as a network composed of various charging stations provided to users.

[0067] With the development of electric vehicle energy storage technology, charging network operators all hope to provide high-quality charging stations to different users. Therefore, how to provide high-quality charging stations to users has become a new challenge.

[0068] The current operating models of charging networks mainly include: operator-led model, car manufacturer-led model, and charging platform-led model.

[0069] The operator-led model refers to a charging pile operator who is not only the investor, builder, operator and maintainer of charging piles, but also organizes the charging piles they produce into a charging network to directly provide charging piles for car owners.

[0070] The automaker-led model refers to electric vehicle companies forming a charging network by combining their own charging piles and / or those purchased from charging pile operators in order to gain control over the market and directly provide charging stations for car owners.

[0071] The charging platform-led model refers to a third-party charging platform that does not directly participate in the investment and construction of charging piles. Instead, it uses its own resource integration capabilities to connect the charging piles of major charging pile operators or car manufacturers to its own platform to form a charging network, thereby providing charging piles for users registered on the third-party charging platform.

[0072] Figure 1 is a schematic diagram illustrating three scenarios provided in this application: an operator-led mode, a vehicle manufacturer-led mode, and a charging platform-led mode. As shown in Figure 1, in the operator-led mode, the CPO can directly provide charging piles to vehicle owners for charging. In the vehicle manufacturer-led mode, the vehicle manufacturer can directly provide charging piles to vehicle owners for charging. In the charging platform-led mode, a third-party charging platform can integrate charging piles provided by various CPOs or vehicle manufacturers, and then provide charging piles to users registered on the third-party charging platform.

[0073] However, in operator-led or automaker-led models, the CPO or automaker needs to build their own charging stations to provide services to users, which is a capital-intensive operation, thus requiring significant financial strength and overall operational capabilities from the CPO or automaker. In contrast, in a charging platform-led model, a third-party charging platform can integrate charging stations from different CPOs or automakers to provide users with diverse charging options. Therefore, a charging platform-led operation model can achieve "interconnectivity" between the third-party charging platform and the CPO, providing users with a more convenient one-stop charging experience.

[0074] However, in the current charging platform-led operating model, third-party charging platforms need to subscribe to charging piles separately on each CPO, making it difficult for them to quickly establish their own charging networks. Furthermore, this model prevents third-party charging platforms from making direct horizontal comparisons of the charging piles offered by different CPOs. Consequently, when subscribing to charging piles, third-party charging platforms do not consider the needs of registered users on their platforms, thus increasing the complexity for users selecting the desired charging piles on these platforms.

[0075] Based on this, this application provides a service transaction method based on cloud technology. In this embodiment, a transaction cloud platform is added between charging pile providers and charging pile subscribers. The transaction cloud platform is used by charging pile subscribers to subscribe to charging piles provided by multiple charging pile providers. Multiple users are registered within each charging pile subscriber, and these users can use the subscribed charging piles for charging. Thus, multiple charging pile providers list their charging piles on the transaction cloud platform, and charging pile subscribers subscribe to the charging piles they need on the platform according to their requirements. Simultaneously, during the charging process, the transaction cloud platform settles the charging fees between the multiple users and the charging pile subscribers, as well as the charging fees between the charging pile subscribers and the multiple charging pile providers.

[0076] On the one hand, since the transaction cloud platform lists charging piles provided by multiple charging pile providers, charging pile subscribers do not need to subscribe to charging piles individually from each charging pile provider. Therefore, through the service transaction method provided in this application embodiment, third-party charging platforms can quickly establish their own charging networks.

[0077] On the other hand, since the trading cloud platform lists charging piles provided by multiple charging pile providers, charging pile subscribers can make horizontal comparisons of the charging piles provided by multiple charging pile providers according to their own user needs, so as to subscribe to suitable charging piles, thereby reducing the complexity for users when using charging pile subscribers.

[0078] The following provides an example of the service transaction system involved in the embodiments of this application.

[0079] Figure 2 is a schematic diagram of the architecture of a service transaction system provided in an embodiment of this application. As shown in Figure 2, the service transaction system includes multiple service providers 10, a transaction cloud platform 20, and at least one service subscriber 30. Figure 2 uses three service providers 10 and two service subscribers 30 as an example.

[0080] As shown in Figure 2, any service provider 10 lists its services on the transaction cloud platform 20. When any service subscriber 30 needs to subscribe to a service, the transaction cloud platform 20 displays the services listed by each service provider 10 to the service subscriber 30. The service subscriber 30 then subscribes to a service from the services listed by each service provider 10 based on its own needs. Users registered with the service subscriber 30 then use the services subscribed to by the service subscriber.

[0081] The service transaction system shown in Figure 2 can be applied between any service subscriber and service purchaser. This application embodiment does not limit the application scenario of the service transaction system shown in Figure 2.

[0082] The following example uses charging stations and shared vehicles as examples to illustrate the system shown in Figure 2.

[0083] Figure 3 is a schematic diagram of the architecture of another service transaction system provided in an embodiment of this application. As shown in Figure 3, the service provider 10 typically includes charging pile provider A, charging pile provider B, and charging pile provider C, and the service subscriber 30 typically includes charging pile subscriber A and charging pile subscriber B.

[0084] Among them, any one of the charging pile provider A, charging pile provider B, and charging pile provider C can be a CPO or a car manufacturer. Any one of the charging pile subscribers A and B can be a third-party charging platform or a car manufacturer.

[0085] It should be noted that the charging piles provided by the charging pile provider can be either manufactured by the provider itself or purchased from other companies. The charging pile provider retains ownership of the provided charging piles, including the right to operate and manage them. Only after a charging pile subscriber subscribes to a charging pile from the charging pile provider will the subscriber's users have the right to use that charging pile for charging.

[0086] As shown in Figure 3, charging pile providers A, B, and C list their charging piles on the trading cloud platform 20. Charging pile subscribers A and B then subscribe to the charging piles they need on the trading cloud platform 20. For example, they can subscribe to charging piles in a specific area or to charging piles that support supercharging.

[0087] Through the service transaction system shown in Figure 3, since the transaction cloud platform lists charging piles provided by multiple charging pile providers, charging pile subscribers do not need to subscribe to charging piles individually from each provider. Therefore, through the service transaction method provided in this application embodiment, third-party charging platforms and other charging pile subscribers can quickly establish their own charging networks. Furthermore, since the transaction cloud platform lists charging piles provided by multiple providers, charging pile subscribers can horizontally compare the charging piles provided by multiple providers according to their own user needs to subscribe to suitable charging piles, thereby reducing the complexity for users when using charging pile subscriptions.

[0088] In addition, through the service transaction system shown in Figure 3, charging pile providers can also attract more traffic through the transaction cloud platform, thereby attracting more users to use the charging piles provided by the charging pile providers.

[0089] Optionally, as shown in Figure 3, charging pile subscriber B can also subscribe to charging piles directly from charging pile provider D. In this scenario, charging pile subscriber B can integrate the charging piles subscribed to on the transaction cloud platform and the charging piles subscribed to on the charging pile provider D and display them to the user, thus providing the user with more diversified charging pile resources.

[0090] Figure 4 is a schematic diagram of the architecture of another service transaction system provided in an embodiment of this application. As shown in Figure 4, service providers 10 typically include car-sharing provider A, car-sharing provider B, and car-sharing provider C, and service subscribers 30 typically include car-sharing subscriber A and car-sharing subscriber B. The shared vehicles can be shared transportation tools such as shared bicycles or shared cars.

[0091] In this context, any one of the car-sharing providers A, B, and C can be a car-sharing operator. Any one of the car-sharing subscribers A and B can be a third-party car-sharing platform.

[0092] As shown in Figure 4, shared car providers A, B, and C list their shared cars on the transaction cloud platform 20. Shared car subscribers A and B then subscribe to the shared cars they need on the transaction cloud platform 20. For example, they can subscribe to shared cars in a certain area or to a specific type of shared car (such as an electric motorcycle).

[0093] Through the service transaction system shown in Figure 4, since the transaction cloud platform lists shared vehicles provided by multiple shared vehicle providers, shared vehicle subscribers do not need to subscribe to shared vehicles separately from each shared vehicle provider. Therefore, through the service transaction method provided in this application embodiment, third-party shared vehicle platforms can quickly establish their own shared vehicle networks. Furthermore, since the transaction cloud platform lists shared vehicles provided by multiple shared vehicle providers, shared vehicle subscribers can horizontally compare the shared vehicles provided by multiple shared vehicle providers according to their own user needs to subscribe to suitable shared vehicles, thereby reducing the complexity for users when using shared vehicle subscriptions.

[0094] In addition, through the service transaction system shown in Figure 4, car-sharing providers can also attract more traffic through the transaction cloud platform, thereby attracting more users to use the car-sharing vehicles provided by the car-sharing providers.

[0095] The service transaction method provided in this application embodiment will be explained below. This method is applied to a transaction cloud platform, which is used by service subscribers to subscribe to services provided by multiple service providers. Multiple users are registered among the service subscribers, and these users can use the services subscribed to by the service subscribers.

[0096] Figure 5 is a flowchart of a service transaction method based on cloud technology provided in an embodiment of this application. As shown in Figure 5, the method includes the following steps.

[0097] Step 501: Obtain at least one service listed on the transaction cloud platform by multiple service providers.

[0098] Step 502: Display the service subscription interface, which includes services offered by multiple service providers.

[0099] Step 503: In response to the service subscriber's operation on the service subscription interface, determine at least one service subscribed by the service subscriber so that the service subscriber can display the subscribed service to multiple users.

[0100] Step 504: In response to multiple users using services subscribed by the service subscriber, settle the fees between the multiple users and the service subscriber, as well as the fees between the service subscriber and the multiple service providers.

[0101] In this embodiment, a transaction cloud platform is added between the service providers and service subscribers. The transaction cloud platform is used by the service subscriber to subscribe to services provided by multiple service providers. Each service subscriber has multiple registered users who can use the services they have subscribed to. Thus, multiple service providers list their services on the transaction cloud platform, and service subscribers subscribe to the services they need through the platform. During service usage, the transaction cloud platform settles the fees between the multiple users and the service subscribers, as well as the fees between the service subscribers and the multiple service providers.

[0102] On the one hand, since the trading cloud platform lists services from multiple service providers, service subscribers do not need to subscribe to services individually from each service provider. Accordingly, in scenarios where the service is a charging station, a third-party charging platform, as a service subscriber, can quickly establish its own charging network based on the charging stations provided by multiple CPOs listed on the trading cloud platform.

[0103] On the other hand, since the transaction cloud platform offers services from multiple service providers, service subscribers can compare the services offered by multiple service providers based on their own user needs to subscribe to the appropriate service, thereby reducing the complexity for users when using service subscribers.

[0104] In this application embodiment, the embodiment shown in Figure 5 can be applied to scenarios where the service is of any type. For example, it can be applied to scenarios where the service is for any entity, such as charging stations or shared vehicles. The embodiment shown in Figure 5 will be described below using charging stations as an example. When this application embodiment is applied to other service scenarios, the relevant content of the embodiment shown in Figure 6 below can also be referred to for implementation, and will not be described in detail thereafter.

[0105] Figure 6 is a flowchart of another service transaction method provided in an embodiment of this application. This method is applied to a transaction cloud platform, where a charging pile subscriber subscribes to charging piles provided by multiple charging pile providers. Multiple users are registered within the charging pile subscriber, and these users can use the charging piles subscribed to by the charging pile subscriber for charging. As shown in Figure 6, the method includes the following steps.

[0106] Step 601: Obtain at least one charging pile from each of the multiple charging pile providers listed on the transaction cloud platform.

[0107] In some embodiments, step 601 can be implemented as follows: displaying a charging pile registration interface; in response to an operation by any one of the multiple charging pile providers on the charging pile registration interface, obtaining at least one charging pile registered by that charging pile provider; displaying a charging pile listing interface, the charging pile listing interface including listing options corresponding to each of the at least one charging pile registered by the charging pile provider; in response to an operation by the charging pile provider on the charging pile listing interface, obtaining at least one charging pile listed by the charging pile provider.

[0108] When charging pile providers list their charging piles on the trading cloud platform, they can first register all or some of their own charging piles on the trading cloud platform, and then choose which charging piles to list on the trading cloud platform, that is, choose which charging piles the charging pile subscribers can subscribe to.

[0109] Registering charging stations on the trading cloud platform can be understood as the charging station provider reporting relevant information about the charging stations, such as the name, location, and specifications, to the platform. The specifications include parameters such as the main unit power, charging mode, and the power of each charging gun (one or more charging guns) within the charging station.

[0110] A charging station typically includes a main unit and one or more charging guns configured on that main unit. Users can use any of the charging guns to charge their vehicles. Examples of charging modes for charging stations include: liquid-cooled supercharging mode and normal charging mode. Liquid-cooled supercharging mode refers to a supercharging mode that uses liquid circulation cooling to cool the battery; supercharging mode can be understood as a fast charging mode. Normal charging mode can be understood as a charging mode with lower charging efficiency than supercharging mode.

[0111] For example, the charging pile registration interface includes a charging pile registration option, which can be an icon. When the charging pile provider triggers this registration option, the trading cloud platform displays the charging pile registration window. The charging pile provider can add relevant information for each charging pile to be registered in the registration window. The trading cloud platform saves this relevant information, thus completing the registration of the charging piles provided by the charging pile provider to the trading cloud platform.

[0112] After a charging station provider registers at least one charging station with the trading cloud platform, the platform can further display a charging station listing interface, which includes listing options corresponding to each of the at least one charging station. When a charging station provider triggers a listing option corresponding to a charging station, the trading cloud platform confirms that the charging station provider has listed the charging station.

[0113] Furthermore, to facilitate charging station providers in quickly viewing which charging stations have been listed on the listing interface, the trading cloud platform can also display the listing status of each charging station on the listing interface, including whether it is listed or not.

[0114] After a charging station provider registers at least one charging station with the trading cloud platform, the listing status of each charging station is "not listed". When the charging station provider triggers the listing option for a charging station, the trading cloud platform updates the listing status of the charging station to "listed" after confirming that the listing is successful.

[0115] When a charging pile provider triggers the option to list a charging pile, the transaction cloud platform can also review the relevant information of the charging pile, such as confirming whether the information of the charging pile registered by the charging pile provider is true. Only after the review is passed will the transaction cloud platform confirm that the charging pile has been successfully listed.

[0116] Based on this, when a charging pile provider triggers the listing option for a specific charging pile, the transaction cloud platform can also display a listing review prompt to indicate that the charging pile provider is currently reviewing the charging pile to be listed. An example of this listing review prompt could be: "Listing application submitted successfully; the platform will complete the review within 3 business days."

[0117] In addition, charging station providers typically set up multiple sites when deploying charging stations. Each site can be understood as a geographical location, and multiple charging stations are deployed at each site. The specifications of the multiple charging stations at the same site can be the same or different. In this scenario, the charging station registration interface can be called the site registration interface, and the charging station listing interface can be called the site listing interface.

[0118] Charging station providers can register stations (i.e., register charging stations) on the station registration interface, and similarly, list stations (i.e., list charging stations) on the station listing interface. It should be noted that when a charging provider lists a station, it means listing all charging stations within that station.

[0119] Figure 7 is a schematic diagram of a charging station registration interface provided in an embodiment of this application. The charging station provider is exemplified as a CPO. After the CPO logs into the transaction cloud platform, the platform displays the charging station registration interface shown in Figure 7. This interface includes a charging station registration option. When the CPO triggers this option, they can register their provided charging stations to the transaction cloud platform, that is, register the relevant information of the charging stations in the charging stations to the transaction cloud platform.

[0120] Figure 8 is a schematic diagram of a charging station listing interface provided in an embodiment of this application. As shown in Figure 8, after the CPO registers its own charging stations to the trading cloud platform, the trading cloud platform displays the charging station listing interface. The charging station listing interface includes relevant information for each registered charging station, such as the region where each charging station is located, the name of each charging station, the host power of the charging piles in each charging station, and the number of devices in each charging station, that is, the number of charging piles included in the charging station.

[0121] As shown in Figure 8, the site listing interface also includes listing options for each site, and the listing status for each site is "not listed". When the CPO clicks the listing option for a site, the trading cloud platform, after approving the site, will record that the site is the site listed by the CPO, that is, record that the charging piles in the site are the charging piles listed by the CPO, and update the status of the site to "listed".

[0122] Additionally, as shown in Figure 8, the charging pile deployment interface also includes a selection option corresponding to each site (represented by a box in Figure 8) and a batch deployment option. The CPO can select the selection options for multiple sites, and then trigger the batch deployment option, thus enabling batch deployment of sites.

[0123] Optionally, after displaying the charging pile registration interface, the transaction cloud platform, in response to any operation performed by any of the multiple charging pile providers on the registration interface, retrieves at least one charging pile registered by that provider and directly lists it as a charging pile. Correspondingly, the status of at least one charging pile registered by that provider is directly marked as listed. In this scenario, the charging pile provider does not need to specifically select which charging piles to list.

[0124] Furthermore, after listing charging piles on the trading cloud platform, the charging pile provider can selectively delist some charging piles. For example, if the charging pile provider detects a malfunction in a charging pile, it can delist that charging pile from the trading cloud platform. Based on this, in some embodiments, the trading cloud platform can also display a charging pile delisting interface, which includes delisting options for each of the at least one listed charging piles; in response to any operation by the charging pile provider on the charging pile delisting interface, one or more charging piles from the at least one listed charging piles can be delisted.

[0125] In this embodiment of the application, removing a charging pile from the platform can be understood as updating the status of the charging pile to "not listed". After the charging pile is removed from the platform, the transaction cloud platform will no longer display the charging pile to the charging pile subscribers. That is, the charging pile subscribers will not subscribe to the removed charging piles.

[0126] As can be seen from the foregoing, in some embodiments, the charging pile delisting interface can be the site delisting interface. The charging pile provider can delist a site using the site delisting interface, that is, delist all charging piles in that site. It should be noted that when the charging pile provider delists a site, it indicates that all charging piles in that site are being delisted.

[0127] Figure 9 is a schematic diagram of a charging station delisting interface provided in an embodiment of this application. After the CPO lists its own charging stations on the trading cloud platform, the trading cloud platform displays the charging station delisting interface shown in Figure 9. The charging station delisting interface includes relevant information for each charging station that has been listed, such as the region where each charging station is located, the name of each charging station, the main power of the charging piles in each charging station, and the number of charging piles included in each charging station.

[0128] As shown in Figure 9, the listing interface for each marketplace also includes a delisting option for each marketplace that has been listed, and the listing status for each marketplace is "listed". When the CPO triggers the delisting option for a marketplace, the trading cloud platform will record that marketplace as the marketplace delisted by the CPO and update the status of that marketplace to "not listed".

[0129] For other content in the interface shown in Figure 9, please refer to the foregoing embodiments, which will not be repeated here.

[0130] In addition, before listing charging piles on the trading cloud platform, charging pile providers need to first register on the trading cloud platform. In some embodiments, the registration of charging pile providers on the cloud platform can be implemented as follows: displaying a first registration interface; authenticating the charging pile provider in response to any operation of the charging pile provider on the first registration interface; after confirming that the charging pile provider has been authenticated, displaying a first service agreement, which includes the fee settlement rules between the charging pile provider and the charging pile subscriber; and opening the trading account of the charging pile provider in response to the charging pile provider's confirmation of the first service agreement.

[0131] In this embodiment, charging pile providers can complete their onboarding on the transaction cloud platform through authentication, signing a service agreement, and opening a transaction account. This process is easy to implement.

[0132] The first entry interface example includes a company information input window, through which charging pile providers can upload their own company-related information to the transaction cloud platform, such as the name of the charging pile provider and the company code of the charging pile provider.

[0133] Certifying a charging station provider can be understood as verifying the company information of the charging station provider to confirm the authenticity of the information uploaded by the provider. If the uploaded company information is confirmed to be authentic, the charging station provider is deemed to have passed the certification process.

[0134] The first service agreement includes the fee settlement rules between the charging station provider and the charging station subscriber. For example, it specifies the fee the charging station subscriber needs to pay the charging station provider for each unit of time a user uses the charging station. It also specifies the frequency of fee settlement between the charging station subscriber and the charging station provider, for example, once a day or once every two days.

[0135] Optionally, the first service agreement may also include other content. For example, it may include the obligations and rights that the charging station provider needs to fulfill in the process of providing the charging station, or it may include the responsibilities that the charging station provider needs to bear in the event of an accident. This application embodiment does not limit the content of the first service agreement.

[0136] When displaying the first service agreement, the transaction cloud platform can also display a confirmation option for the first service agreement. When it detects that the charging pile provider has triggered the confirmation option for the first service agreement, that is, when it detects that the charging pile provider has confirmed the first service agreement, it indicates that the charging pile provider agrees to the first service agreement, and therefore the transaction account of the charging pile provider can continue to be opened.

[0137] An example of how to activate the transaction account of the charging pile provider can be as follows: The transaction cloud platform notifies the transaction system to activate the transaction account of the charging pile provider. After the transaction system completes the activation of the transaction account, it returns a successful activation message to the transaction cloud platform, which carries the transaction account of the charging pile provider.

[0138] For example, the transaction system is a payment system. Correspondingly, the charging pile provider's transaction account can be understood as its receiving account. In this scenario, the transaction cloud platform can notify the payment system to open the charging pile provider's receiving account. After completing the opening of the receiving account, the payment system returns a successful opening message to the transaction cloud platform, which carries the charging pile provider's receiving account information.

[0139] Figure 10 is a schematic diagram of the process for a charging pile provider to join a transaction cloud platform according to an embodiment of this application. As shown in Figure 10, the charging pile provider completes the process of joining the transaction cloud platform through three steps: enterprise real-name authentication, signing a service agreement, and opening a payment account.

[0140] In Figure 10, the trading cloud platform can also be referred to as the "SuperCharge Alliance," and joining the trading cloud platform is called joining the SuperCharge Alliance.

[0141] It should be noted that Figure 10 is used to illustrate the steps for charging pile providers to join the trading cloud platform. Optionally, charging pile providers can join the trading cloud platform through more or fewer steps, which will not be illustrated here.

[0142] In addition, each charging station provider is equipped with at least one interface, through which other devices can perform functions such as charging station query, charging station start, charging station stop, and usage details query. For ease of explanation later, the at least one interface configured on the charging station provider will be collectively referred to as the first interface set, which includes the charging station query interface, charging station start interface, charging station stop interface, and usage details query interface.

[0143] In this scenario, before the charging pile provider uploads the charging pile to the trading cloud platform, the trading cloud platform also needs to debug the interfaces in the first interface set to ensure that the charging pile provider and the trading cloud platform can interact normally.

[0144] Based on this, in some embodiments, the implementation of the transaction cloud platform debugging the interfaces in the first interface set can be as follows: obtain the first interface set configured on any one of the multiple charging pile providers, the first interface set including a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface; display the first interface debugging interface, the first interface debugging interface including debugging options corresponding to each interface in the first interface set; respond to the operation of the charging pile provider on the first interface debugging interface, debug the interfaces in the first interface set, so that the transaction cloud platform can interact with the charging pile provider through the interfaces in the first interface set.

[0145] For any charging pile provider, the transaction cloud platform can debug the interface on the charging pile provider in the above manner.

[0146] One way to obtain the first set of interfaces configured on any one of the multiple charging pile providers is as follows: the charging pile provider publishes the parameter information of each interface in the first set of interfaces to the transaction cloud platform, and the transaction cloud platform obtains the parameter information of each interface in the first set of interfaces, that is, obtains the first set of interfaces configured on the charging pile provider.

[0147] The parameter information for each interface indicates the basic format of the request message that the transaction cloud platform needs to send when calling that interface. For example, the name of each parameter, the description of each parameter, and the value of each parameter included in the request message.

[0148] When the charging pile provider triggers the debugging option of a certain interface on the first interface debugging interface, the transaction cloud platform generates a request message for calling the interface based on the parameter information of the interface, and sends the request message to the charging pile provider. When the charging pile provider receives the request message, it calls the interface to generate a response message for the request message, and returns the response message to the transaction cloud platform. When the transaction cloud platform receives the response message, it confirms that the interface debugging is successful.

[0149] For example, when a charging pile provider triggers the commissioning option corresponding to the charging pile query interface, the transaction cloud platform generates a charging pile query request message based on the parameter information of the charging pile query interface and sends this message to the charging pile provider. Upon receiving the charging pile query request message, the charging pile provider invokes the charging pile query interface to query the charging piles according to the request message and returns the query results to the transaction cloud platform in a charging pile query response message. Upon receiving the response message, the transaction cloud platform confirms that the charging pile query interface commissioning was successful.

[0150] Figure 11 is a schematic diagram of a first interface debugging interface provided in an embodiment of this application. The first interface debugging interface includes debugging options corresponding to the charging pile query interface, charging pile start interface, charging pile stop interface, and usage details query interface in the first interface set. Figure 11 only illustrates the debugging options corresponding to the charging pile query interface.

[0151] For any interface in the first interface set, the first interface debugging interface also includes the parameter information of that interface. Figure 11 shows the parameter information of the charging pile query interface. When the charging pile provider triggers the debugging option of a certain interface, the transaction cloud platform debugs the function of that interface.

[0152] Additionally, as shown in Figure 11, the first interface debugging interface also includes an input window corresponding to the production interface address. This input window is used to input the address of the interface to be debugged. Thus, when the transaction cloud platform debugs this interface, it can send the generated request message to this address, thereby enabling the invocation of the interface.

[0153] The following provides examples of the parameter information for the charging pile query interface, charging pile start interface, charging pile stop interface, and usage details query interface.

[0154] Table 1 is a schematic illustration of the parameter information of a charging pile query interface provided in an embodiment of this application.

[0155] The parameter "ServiceType" indicates the type of service implemented by the corresponding interface. For example, in the scenario where the service is a charging pile, the value of the service type can be: batteryRecharge.

[0156] The parameter "LastQueryTime" indicates the time of the most recent query for charging stations. If the request message includes this field, the charging station provider only needs to query charging stations added between the last query time and the current time. If the request message does not include this field, the charging station provider needs to query all charging stations it provides.

[0157] Since charging station providers may offer a large number of charging stations, the information for all these stations may not be contained within a single charging station query response message. Therefore, charging station providers can record the information of their charging stations in pages, with each page containing information for a subset of charging stations, and each page being carried by a separate charging station query response message. In this scenario, when returning a charging station query response message, the charging station provider can use the parameter "PageNo" to indicate the total number of charging station query response messages returned in the current period, and the parameter "PageSize" to indicate how many charging station information is carried in each charging station query response message.

[0158] The parameter "ServiceItemNumber" is used to indicate the serial number of the charging station found in the query.

[0159] In the charging pile query request message sent by the transaction cloud platform, the values ​​of the parameters “PageNo”, “PageSize” and “ServiceItemNumber” can be empty. The values ​​of these parameters are updated by the charging pile provider according to the query results and then returned in the charging pile query response message.

[0160] Table 1

[0161] Table 2 is a schematic diagram illustrating the parameter information of a charging pile start-up interface provided in an embodiment of this application. Table 3 is a schematic diagram illustrating the parameter information of a charging pile stop-up interface provided in an embodiment of this application. The parameter information in Tables 2 and 3 is basically the same. The following explanation uses Table 2 as an example. The parameters already explained in Table 1 will not be repeated here.

[0162] The parameter "activity" is used to identify the interface. It's important to note that if the service provider configures different addresses for different interfaces, this parameter does not need to be included in the request message. However, if the same address is configured for different interfaces, this parameter must be included in the request message to distinguish which interface is being called.

[0163] The parameter "timeStamp" indicates the timestamp when the current request was initiated, which can be Coordinated Universal Time (UTC).

[0164] The parameter "businessId" indicates the request identifier for the current request. Each request has a unique request identifier. The parameter "orderId" indicates basic information about the current order, such as information about the user using the charging station.

[0165] The parameter "Startmode" indicates how the user requests to use the charging station. For example, it indicates a user request to use the charging station if the user scans the QR code corresponding to the charging station. Alternatively, it indicates a user request to use the charging station if the user plugs the charging station into their vehicle for charging.

[0166] The parameter "ServiceLimit" indicates the usage restrictions of the charging station. For example, the user may have set the charging time to 2 hours or the total charging cost to 10 yuan.

[0167] Table 2

[0168] Table 3

[0169] Table 4 is a schematic diagram illustrating the parameter information of a charging pile usage details query interface provided in an embodiment of this application. Related parameter descriptions can be found in Tables 2 and 3, and will not be repeated here.

[0170] Table 4

[0171] It should be noted that Tables 1 to 4 are illustrative examples of parameter information for the interfaces provided by the charging pile provider to the transaction cloud platform. This application does not limit the types and number of interfaces provided by the charging pile provider. These will not be illustrated further here.

[0172] The following example, using Figure 12, illustrates the process of any charging pile provider joining the transaction cloud platform and debugging its interface.

[0173] As shown in Figure 12, the charging pile provider, such as a CPO or a car manufacturer, first reports its relevant information to the transaction cloud platform. The transaction cloud platform then authenticates the charging pile provider. After successful authentication, the transaction cloud platform displays a successful authentication notification to the charging pile provider. Next, the transaction cloud platform displays the first service agreement. After confirming the first service agreement, the charging pile provider sends an account activation request to the payment system, instructing the payment system to activate the corresponding receiving account for the charging pile provider. After successfully activating the corresponding receiving account for the charging pile provider, the payment system returns the receiving account to the transaction cloud platform. The transaction cloud platform records the receiving account and simultaneously returns it to the charging pile provider to indicate successful account activation.

[0174] Afterwards, the transaction cloud platform can further debug the interfaces in the first set of interfaces configured on the charging pile provider. After debugging each interface and confirming that the interface is functioning normally, the transaction cloud platform can also display a successful interface debugging prompt to the charging pile provider.

[0175] Step 602: Display the charging pile subscription interface, which includes charging piles listed by multiple charging pile providers.

[0176] After multiple charging pile providers list their charging piles through step 601, any charging pile subscriber can subscribe to the charging piles listed by multiple charging pile providers through the charging pile subscription interface displayed on the transaction cloud platform. Therefore, the charging pile subscriber does not need to interact with each charging pile provider individually.

[0177] In some embodiments, after a charging pile subscriber logs into the transaction cloud platform, the transaction cloud platform can display a charging pile subscription request page. In response to the charging pile subscriber's operation on the charging pile subscription request page, the transaction cloud platform confirms that the charging pile subscriber has initiated a charging pile subscription request, and then displays the charging pile subscription interface.

[0178] For example, in a scenario where charging pile providers deploy charging piles by listing them at service stations, the charging pile subscription request page can also be called a service station subscription request page. In this scenario, in response to the charging pile subscriber's action on this service station subscription request page, the transaction cloud platform confirms that the charging pile subscriber has initiated a service station subscription request, and then displays the service station subscription interface. The service station subscription interface includes multiple service stations listed by different charging pile providers, allowing charging pile subscribers to subscribe to charging piles by subscribing to service stations.

[0179] Figure 13 is a schematic diagram of a charging station subscription request interface provided in an embodiment of this application. As shown in Figure 13, the charging station subscription request interface includes a "Charging Station Subscription" option. When the confirmation operation of the charging pile subscriber to the "Charging Station Subscription" option is detected, the transaction cloud platform confirms that the charging pile subscriber has initiated a charging station subscription request, and then displays the charging station subscription interface shown in Figure 14.

[0180] As shown in Figure 14, the charging station subscription interface includes information sections corresponding to multiple charging station providers. These sections include the name of the respective charging station provider, such as XX Power Grid Co., Ltd., XX Charging Technology Co., Ltd., or XX New Energy Co., Ltd. The information sections also include information about the charging stations provided by each provider, such as the total number of stations, the service protocols supported by the provider, the name of each station, the location of each station, the number of charging stations in each station, the charging mode of each station, the main power of the charging station, and the maximum power of a single charging gun. For example, a charging station can be configured with one or more charging guns, and the maximum power of a single charging gun is the highest power among all the charging guns corresponding to that charging station.

[0181] Charging station subscribers can view information about the charging stations at a given charging station displayed on the station subscription interface. They can then filter which stations they need to subscribe to based on their requirements.

[0182] It should be noted that Figure 14 is an example diagram of a station subscription interface, and the embodiments of this application do not limit the content and form of the station subscription interface.

[0183] Step 603: In response to the charging pile subscriber's operation on the charging pile subscription interface, determine at least one charging pile subscribed by the charging pile subscriber, and instruct the charging pile subscriber to display the subscribed charging pile to multiple users.

[0184] In some embodiments, the charging station subscription interface includes a subscription option corresponding to each charging station. When a charging station subscriber selects the subscription option corresponding to a charging station, it is confirmed that the charging station subscriber has subscribed to that charging station.

[0185] For example, in a scenario where the charging pile subscription interface is a site subscription interface, as shown in Figure 14, the site subscription interface can include a subscription option corresponding to each charging pile provider. In this scenario, when a charging pile subscriber selects a subscription option, it is confirmed that the charging pile subscriber has subscribed to all charging piles in all sites provided by the charging pile provider corresponding to that subscription option. Optionally, the site subscription interface can include a subscription option corresponding to each site. In this scenario, when a charging pile subscriber selects a subscription option, it is confirmed that the charging pile subscriber has subscribed to all charging piles in all sites corresponding to that subscription option. This approach provides more flexibility for charging pile subscribers when subscribing to charging piles.

[0186] After the charging pile subscriber subscribes to a charging pile through steps 602 and 603, the charging pile will display relevant information about the subscribed charging pile to the user after the user logs in to the charging pile subscriber, so that the user can choose to use the subscribed charging pile.

[0187] In addition, before subscribing to charging piles on the trading cloud platform, charging pile subscribers need to first register on the trading cloud platform. In some embodiments, the registration of charging pile subscribers on the cloud platform can be implemented as follows: displaying a second registration interface; authenticating the charging pile subscriber in response to the charging pile subscriber's operation on the second registration interface; after confirming that the charging pile subscriber's authentication is successful, displaying a second service agreement, which is used to indicate the fee settlement rules between the charging pile subscriber and each of the multiple charging pile providers; and opening the charging pile subscriber's payment account in response to the charging pile subscriber's confirmation operation of the second service agreement.

[0188] In this embodiment, charging pile subscribers can complete their onboarding on the transaction cloud platform through authentication, signing a service agreement, and opening a payment account. This process is easy to implement.

[0189] The second entry interface example includes a company information input window, through which charging pile subscribers can upload their company-related information to the transaction cloud platform, such as the name of the charging pile subscriber and the company code of the charging pile subscriber.

[0190] Authenticating a charging station subscriber can be understood as verifying the company information of the subscriber to confirm the authenticity of the information uploaded by the subscriber. If the uploaded company information is confirmed to be authentic, the subscriber's authentication is deemed successful.

[0191] The second service agreement includes the fee settlement rules between the charging station subscriber and any charging station provider. For example, it specifies the fee the charging station subscriber needs to pay to the charging station provider when a user uses the charging station for a given period of time. It also specifies the frequency of fee settlement between the charging station subscriber and the service provider, such as once a day or once every two days.

[0192] Optionally, the second service agreement may also include other content. For example, it may include the obligations and rights that users on the charging station subscription platform must fulfill and enjoy when using the charging station, or it may include the responsibilities that the charging station subscription platform must bear in the event of an accident. This application embodiment does not limit the content of the second service agreement.

[0193] The method for opening a transaction account for the charging station subscriber can be found in the relevant content on opening a transaction account for the charging station provider, and will not be repeated here.

[0194] Figure 15 is a schematic diagram of the process for a charging pile subscriber to join the transaction cloud platform according to an embodiment of this application. As shown in Figure 15, the charging pile subscriber completes the process of joining the transaction cloud platform, that is, joining the Supercharging Alliance, through three steps: enterprise real-name authentication, signing a service agreement, and opening a payment account.

[0195] It should be noted that Figure 15 is used to illustrate the steps for charging pile subscribers to join the trading cloud platform. Optionally, charging pile subscribers can join the trading cloud platform through more or fewer steps, which will not be illustrated here.

[0196] In addition, to facilitate interaction between charging pile subscribers and the trading cloud platform, a second set of interfaces is configured on the trading cloud platform. The second set of interfaces includes a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface, so that charging pile subscribers can call the interfaces in the second set of interfaces to interact with the trading cloud platform.

[0197] In this scenario, before subscribing to a charging pile on the trading cloud platform, the charging pile subscriber needs to debug the interfaces in the second interface set to ensure that the charging pile subscriber and the trading cloud platform can interact normally.

[0198] Based on this, in some embodiments, the charging pile subscriber can debug the interfaces in the second interface set by displaying a second interface debugging interface on the transaction cloud platform, which includes each interface in the second interface set, and instructing the charging pile subscriber to debug the interfaces in the second interface set so that the charging pile subscriber can interact with the transaction cloud platform through the interfaces in the second interface set.

[0199] For any charging pile subscriber, the interface testing with the transaction cloud platform can be completed using the above method. Since the transaction cloud platform is configured with a unified set of second interfaces, the charging pile subscriber only needs to interact with the transaction cloud platform according to this unified set of second interfaces to realize functions such as querying, starting, and stopping charging piles at the charging pile provider's location.

[0200] The second interface debugging interface also displays parameter information for each interface.

[0201] The parameter information for each interface indicates the basic format of the request message that the charging pile subscriber needs to send when calling the interface. For example, the name of each parameter, the description of each parameter, and the value of each parameter included in the request message.

[0202] For any interface in the second set of interfaces, the implementation method by which the transaction cloud platform instructs the charging pile subscriber to debug the interface can be as follows: The charging pile subscriber generates a request message for calling the interface based on the parameter information of the interface, and sends the request message to the transaction cloud platform. When the transaction cloud platform receives the request message, it calls the interface to generate a response message for the request message, and returns the response message to the charging pile subscriber. The charging pile subscriber can then confirm that the interface debugging is successful.

[0203] Figure 16 is a schematic diagram of a second interface debugging interface provided in an embodiment of this application. As shown in Figure 16, the second interface debugging interface includes parameter information for each interface in the second interface set.

[0204] It should be noted that the second interface debugging interface shown in Figure 16 does not have debugging options for each interface. The transaction cloud platform only needs to display the parameter information of each interface in the second interface set to the charging pile subscriber, and the charging pile subscriber can debug the interface according to the interface parameter information.

[0205] For an explanation of the parameter information of the interfaces in the second interface set, please refer to the interfaces in the first interface set shown in Tables 1 to 4 above, which will not be repeated here.

[0206] In addition, after subscribing to a charging station, the transaction cloud platform can notify the charging station subscriber to pre-charge their account so that they can later pay the charging station provider from the pre-charged amount. Pre-charging means that the charging station subscriber tops up their transaction account before the user uses the charging station. Optionally, after subscribing to a charging station, the transaction cloud platform may not notify the charging station subscriber to pre-charge, but instead notify them to pay the charging station provider when settling the charging fees. This application embodiment does not limit this approach.

[0207] The following example, using Figure 17, illustrates the process of charging pile subscribers joining the transaction cloud platform and debugging its interfaces. As shown in Figure 17, the charging pile subscriber, such as a third-party charging platform or a car manufacturer, first reports its relevant information to the transaction cloud platform. The transaction cloud platform then authenticates the charging pile subscriber. After successful authentication, the transaction cloud platform displays a success message to the charging pile subscriber. Next, the transaction cloud platform displays the second service agreement. After confirming the second service agreement, the charging pile subscriber sends an account activation request to the payment system, instructing the payment system to activate the corresponding payment account. Once the payment system has activated the charging pile subscriber's payment account, it returns the payment account to the transaction cloud platform. The transaction cloud platform records the payment account and simultaneously returns the subscription account to the charging pile subscriber, indicating successful payment account activation.

[0208] Subsequently, the transaction cloud platform can further trigger the charging pile subscriber to debug the interfaces in the second set of interfaces configured on the transaction cloud platform. After receiving the request message sent by the charging pile subscriber during the debugging process, the transaction cloud platform generates a response message to be returned to the charging pile subscriber based on the request message, indicating that the interface debugging was successful.

[0209] Then, the charging pile subscriber can subscribe to the service through the transaction cloud platform. After confirming the subscription, the transaction cloud platform can also send a successful subscription notification to the charging pile subscriber. Afterwards, the charging pile subscriber can also pre-charge their payment account in the payment system through the transaction cloud platform. After confirming the successful pre-charge, the payment system can also send a successful pre-charge notification to the charging pile subscriber through the transaction cloud platform.

[0210] Step 604: In response to multiple users using charging piles subscribed to by the charging pile subscriber, settle the charging fees between the multiple users and the charging pile subscriber, as well as the charging fees between the charging pile subscriber and the multiple charging pile providers.

[0211] In some embodiments, the multiple users include a target user who uses a target charging pile subscribed to by a charging pile subscriber. The multiple charging pile providers include a first charging pile provider, which provides the target charging pile. In this scenario, in response to multiple users using charging piles subscribed to by the charging pile subscriber, the method for settling the charging fees between the multiple users and the charging pile subscriber includes: obtaining the usage details of the target user using the target charging pile from the first charging pile provider; sending the usage details to the charging pile subscriber so that the charging pile subscriber displays the charging pile billing results to the target user based on the usage details, and the charging pile billing results are used to instruct the target user to transact charging fees with the charging pile subscriber.

[0212] After a user uses a target charging station subscribed to by the charging station subscriber, the transaction cloud platform obtains the usage details of the target charging station from the charging station provider. The transaction cloud platform then returns the obtained usage details to the charging station subscriber, enabling the charging station subscriber to determine the fee that the user needs to pay to the charging station subscriber, i.e., the charging fee, based on the usage details and pre-configured billing rules.

[0213] The usage details typically include basic information about the target charging station, such as start and end times. In this scenario, the charging station subscriber can calculate the battery level based on the target charging station's basic information, start and end times, and then determine the charging fee that the user needs to pay to the charging station subscriber based on the battery level and pre-configured billing rules.

[0214] Optionally, the usage details can directly include the electricity consumed by the user during the use of the target charging station. In this scenario, the charging station subscriber can directly determine the charging fee that the user needs to pay to the charging station subscriber based on the electricity consumption and pre-configured billing rules.

[0215] The embodiments of this application do not limit the information included in the usage details, and will not be illustrated in detail here.

[0216] Furthermore, this application embodiment does not limit the billing rules configured at the service subscriber's location.

[0217] Furthermore, there are multiple ways for users to pay charging fees to the charging station subscriber, and this application embodiment does not limit this.

[0218] Furthermore, since the charging station subscriber only subscribes to the charging stations and does not directly own them, before a user can use the target charging station at the subscriber's location, the subscriber needs to trigger a service activation request for the target charging station. The subscriber responds to this request by generating a charging station activation request message and sending it to the transaction cloud platform. The transaction cloud platform then forwards this message to the primary charging station provider offering the target charging station. Upon receiving the activation request message, the primary charging station provider activates the charging function of the target charging station, enabling the user to use it for charging.

[0219] When the transaction cloud platform receives a charging pile start request message, it calls its own charging pile start interface to forward the message to the first charging pile provider. Upon receiving the request, the first charging pile provider calls its own charging pile start interface to initiate the charging function of the target charging pile.

[0220] Optionally, after activating the charging function of the target charging pile, the first charging pile provider can also return a charging pile activation response message to the transaction cloud platform. This message indicates that the charging function of the target charging pile has been activated. Upon receiving this message, the transaction cloud platform forwards it to the charging pile subscribers, who can then display it to inform users that the charging function of the target charging pile has been activated.

[0221] Additionally, after a user has finished charging at the target charging station, they can trigger a service stop request for the target charging station at the charging station subscriber's location. The charging station subscriber responds to this request by generating a charging station stop request message and sending it to the transaction cloud platform. The transaction cloud platform then forwards this message to the primary charging station provider offering the target charging station. Upon receiving this stop request message, the primary charging station provider stops the charging function of the target charging station, preventing the user from continuing to use it.

[0222] When the transaction cloud platform receives a charging pile stop request message, it calls its own charging pile stop interface to forward the message to the first charging pile provider. Upon receiving the stop request message, the first charging pile provider calls its own charging pile stop interface to stop the charging function of the target charging pile.

[0223] Alternatively, the method for a user to trigger a service stop request for a target charging station at the charging station subscriber's location can be as follows: After the user starts charging at the target charging station, the charging station subscriber displays a charging progress interface to the user, which includes a stop charging option. When the user triggers this stop charging option, a service stop request for the target charging station is detected. Alternatively, if the current charging stop conditions are met, a service stop request for the target charging station is considered detected. These charging stop conditions are those set by the user when starting the target charging station.

[0224] Optionally, after charging at the target charging station, the user can choose to directly unplug the charging cable between the target charging station and the vehicle. In this scenario, the first charging station provider will detect that the target charging station has stopped charging. At this time, the first charging station provider can also generate a service stop notification message and send the service stop notification message to the charging station subscriber through the transaction cloud platform, so that the charging station subscriber can be informed in a timely manner that the user has stopped using the target charging station.

[0225] Optionally, after a user has started charging at the target charging station, the first charging station provider can proactively terminate the charging function of the target charging station. For example, the first charging station provider may detect a malfunction in the target charging station. In this scenario, the first charging station provider can also generate a service stop notification message and send it to the charging station subscribers through the transaction cloud platform, so that the subscribers' users can be promptly informed that the charging function of the target charging station has been terminated.

[0226] In addition, after a user charges at a target charging station, the first charging station provider will record the start and end times of the target charging station's use, so that the user can subsequently return the usage details of the target charging station to the service subscriber through the transaction cloud platform based on the recorded information.

[0227] Furthermore, after determining that the target charging pile is no longer in use, the first charging pile provider can proactively send the usage details of the target charging pile to the service subscriber through the transaction cloud platform. Optionally, the first charging pile provider can also send the usage details of the target charging pile to the service subscriber through the transaction cloud platform after receiving a detail query request from the charging pile subscriber. This embodiment of the application does not limit this.

[0228] Figure 18 is a schematic diagram of a process for settling fees between a charging pile subscriber and a user, provided in an embodiment of this application.

[0229] As shown in Figure 18, the charging pile subscriber is exemplified by a third-party charging platform. After a user activates a charging pile on the third-party charging platform, the platform sends a charging pile activation request message to the charging pile operator providing that pile via a transaction cloud platform. Upon receiving this message, the operator activates the charging pile's charging function and sends a charging pile activation response message back to the third-party platform via the transaction cloud platform. When the user confirms they are no longer using the charging pile, the platform sends a charging pile deactivation request message to the operator via the transaction cloud platform. Upon receiving this message, the operator deactivates the charging pile's charging function and sends a charging pile deactivation response message back to the third-party platform via the transaction cloud platform.

[0230] Simultaneously, the charging station operator reports the usage details of the charging station to the third-party charging platform through the transaction cloud platform. After receiving the usage details, the third-party charging platform returns a detail confirmation message to the charging station operator through the transaction cloud platform. This confirmation message indicates that the third-party charging platform has received the usage details.

[0231] The third-party charging platform confirms the charging fee based on the usage details and displays the charging fee to the user to instruct the user to pay the charging fee to the third-party charging platform.

[0232] In addition, in this embodiment of the application, the service subscriber and the service provider also settle charging fees through a transaction cloud platform.

[0233] Based on this, in some embodiments, the multiple charging pile providers include a second charging pile provider. In this scenario, in response to multiple users using charging piles subscribed to by the charging pile subscriber, the settlement of charging fees between the charging pile subscriber and the multiple charging pile providers can be implemented as follows: Summarize the total charging pile usage details between the charging pile subscriber and the second charging pile provider, where the total charging pile usage details include the sum of usage details of all users in the charging pile subscriber using charging piles provided by the second charging pile provider; display the total charging pile usage details; in response to the confirmation operation of the charging pile subscriber and the second charging pile provider on the total charging pile usage details, generate a charging bill based on the total charging pile usage details; and based on the charging bill, transact the charging fees between the charging pile subscriber's payment account and the second charging pile provider's receiving account.

[0234] For example, the implementation of summarizing the total charging pile usage details between the charging pile subscriber and the second charging pile provider can be as follows: determine the time of the most recent summary of the total charging pile usage details between the charging pile subscriber and the second charging pile provider, then record the time period between that time and the current time, query the usage details of all users in the charging pile subscriber using the charging piles provided by the second charging pile provider within that time period, and use the sum of the queried usage details as the total charging pile usage details for this summary.

[0235] Displaying the total usage details of charging piles can be understood as follows: the transaction cloud platform displays the total usage details of charging piles to both the charging pile subscriber and the charging pile provider, so that the charging pile subscriber and the charging pile provider can confirm whether the summarized total usage details of charging piles are correct.

[0236] For example, after the transaction cloud platform displays the total usage details of the charging piles to the charging pile subscribers, it also displays a confirmation option for the total usage details of the charging piles. When it is detected that the charging pile subscribers have triggered the confirmation option, it is confirmed that the charging pile subscribers have confirmed the total usage details of the charging piles.

[0237] For example, after the transaction cloud platform displays the total usage details of the charging piles to the second charging pile provider, it also displays a confirmation option for the total usage details of the charging piles. When it detects that the second charging pile provider has triggered the confirmation option, it confirms that the second charging pile provider has confirmed the total usage details of the charging piles.

[0238] Alternatively, the method for generating a charging bill based on the total usage details of the charging pile can be as follows: Settle the fees for the total usage details of the charging pile according to the fee settlement rules indicated in the first and second service agreements to obtain the charging bill. This application does not limit the implementation method of fee settlement in its embodiments.

[0239] Optionally, in other embodiments, in response to multiple users using charging piles subscribed by a charging pile subscriber, the settlement of charging fees between the charging pile subscriber and multiple charging pile providers can be implemented as follows: aggregating the total charging pile usage details between the charging pile subscriber and the second charging pile provider, the total charging pile usage details including the sum of usage details of all users in the charging pile subscriber using charging piles provided by the second charging pile provider; generating a charging bill based on the total charging pile usage details; and transacting the charging fees between the charging pile subscriber's payment account and the second charging pile provider's receiving account based on the charging bill.

[0240] In this scenario, there is no need for the charging station subscriber and the second charging station provider to confirm the total usage details of the charging station.

[0241] In addition, in response to multiple users using charging piles subscribed by a charging pile subscriber, after settling the fees between the charging pile subscriber and multiple charging pile providers, the transaction cloud platform can also display the first transaction query interface; in response to any operation of any charging pile provider among the multiple charging pile providers on the first transaction query interface, the transaction details of that charging pile provider will be displayed.

[0242] The transaction details provided by the charging station provider typically include a breakdown of charging fees received by the provider over a specific period. Through this method, the transaction cloud platform can also provide charging station providers with an income query function.

[0243] In addition, in response to multiple users using charging piles subscribed by a charging pile subscriber, after settling the fees between the charging pile subscriber and multiple charging pile providers, the transaction cloud platform can also display a second transaction query interface; in response to the charging pile subscriber's operation on the second transaction query interface, the transaction details of the charging pile subscriber are displayed.

[0244] The transaction details of a charging station subscriber may, for example, include a breakdown of the charging fees paid by the subscriber to the charging station provider within a certain period. Through this method, the transaction cloud platform can also provide charging station subscribers with a payment inquiry function.

[0245] In addition, the transaction cloud platform can also provide other functions for charging pile subscribers and charging pile providers, such as intelligent data analysis and operational data display. These will not be elaborated on here.

[0246] Figure 19 is a schematic diagram illustrating the settlement process between a charging pile subscriber and a charging pile provider according to an embodiment of this application. As shown in Figure 19, after the transaction cloud platform summarizes the total usage details, it displays these details to both the charging pile subscriber and the charging pile provider for their confirmation. Then, the transaction cloud platform generates a charging bill and notifies the payment system to transfer funds between the charging pile subscriber and the charging pile provider based on the bill, i.e., to process the charging fees.

[0247] In addition, the transaction cloud platform also provides payment inquiry functions for charging pile subscribers and revenue inquiry functions for charging pile providers. Further details are omitted.

[0248] In summary, since the transaction cloud platform lists charging piles provided by multiple charging pile providers, charging pile subscribers do not need to subscribe to charging piles individually from each provider. Therefore, through the service transaction method provided in this application embodiment, third-party charging platforms and other charging pile subscribers can quickly establish their own charging networks. Furthermore, because the transaction cloud platform lists charging piles provided by multiple providers, charging pile subscribers can compare the charging piles provided by multiple providers according to their own user needs to subscribe to suitable charging piles, thereby reducing the complexity for users when using charging pile subscriptions.

[0249] Figure 20 is a schematic diagram of a transaction cloud platform provided in an embodiment of this application. The transaction cloud platform is used for charging pile subscribers to subscribe to charging piles provided by multiple charging pile providers. Multiple users are registered in the charging pile subscribers, and multiple users can use the charging piles subscribed to by the charging pile subscribers for charging. As shown in Figure 20, the transaction cloud platform 2000 includes the following modules.

[0250] The first acquisition module 2001 is used to acquire at least one charging pile listed on the transaction cloud platform by multiple charging pile providers; the specific implementation method can be referred to step 601 in the embodiment of Figure 6.

[0251] The first display module 2002 is used to display the charging pile subscription interface, which includes charging piles uploaded by multiple charging pile providers; the specific implementation method can be referred to step 602 in the embodiment of Figure 6.

[0252] The first determining module 2003 is used to respond to the operation of the charging pile subscriber on the charging pile subscription interface, determine at least one charging pile subscribed by the charging pile subscriber, and instruct the charging pile subscriber to display the subscribed charging pile to multiple users; the specific implementation method can be referred to step 603 in the embodiment of Figure 6.

[0253] The settlement module 2004 is used to settle the charging fees between multiple users and the charging pile subscriber, as well as the charging fees between the charging pile subscriber and multiple charging pile providers, in response to multiple users using charging piles subscribed by the charging pile subscriber. For a specific implementation, please refer to step 604 in the embodiment shown in Figure 6.

[0254] Optionally, the multiple users include the target user, who uses the target charging pile subscribed by the charging pile subscriber, and the multiple charging pile providers include the first charging pile provider, which is the charging pile provider that provides the target charging pile.

[0255] The settlement module is used for:

[0256] Obtain the usage details of the target user's use of the target charging station from the first charging station provider;

[0257] The usage details will be sent to the charging station subscriber, instructing the charging station subscriber to display the charging billing results to the target user based on the usage details. The charging billing results will be used to instruct the target user to transact charging fees with the charging station subscriber.

[0258] Optionally, the multiple charging station providers may include a second charging station provider;

[0259] The settlement module is used for:

[0260] The total charging pile usage details between the charging pile subscriber and the second charging pile provider are summarized. The total charging pile usage details include the sum of the usage details of all users in the charging pile subscriber using the charging piles provided by the second charging pile provider.

[0261] Displays a complete list of charging station usage details;

[0262] In response to the confirmation of total charging pile usage details by the charging pile subscriber and the second charging pile provider, a charging bill is generated based on the total charging pile usage details.

[0263] According to the charging bill, the charging fee is traded between the transaction account of the charging station subscriber and the transaction account of the second charging station provider.

[0264] Optionally, the trading cloud platform also includes a second display module for:

[0265] Display the first transaction query interface;

[0266] In response to any operation performed by any of the multiple charging pile providers on the first transaction query interface, the transaction details of any charging pile provider are displayed.

[0267] Optionally, the trading cloud platform also includes a third display module for:

[0268] Display the second transaction query interface;

[0269] In response to the charging pile subscriber's actions on the second transaction query interface, the charging pile subscriber's transaction details are displayed.

[0270] Optionally, the trading cloud platform may also include:

[0271] The second acquisition module is used to acquire the first set of interfaces configured on any one of the multiple charging pile providers. The first set of interfaces includes a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface.

[0272] The fourth display module is used to display the first interface debugging interface based on the first interface set. The first interface debugging interface includes debugging options corresponding to each interface in the first interface set.

[0273] The commissioning module is used to respond to the operation of any charging pile provider on the first interface commissioning interface, and to commission the interfaces in the first interface set so that the transaction cloud platform can interact with any charging pile provider through the interfaces in the first interface set.

[0274] Optionally, the transaction cloud platform is configured with a second set of interfaces, which includes a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface.

[0275] The trading cloud platform also includes:

[0276] The fifth display module is used to display the second interface debugging interface, which includes each interface in the second interface set and instructs the charging pile subscriber to debug the interfaces in the second interface set so that the charging pile subscriber can interact with the transaction cloud platform through the interfaces in the second interface set.

[0277] Optionally, the transaction cloud platform also includes a first onboarding module for:

[0278] The first login screen is displayed;

[0279] In response to any operation performed by any of the multiple charging pile providers on the first entry interface, authenticate any of the charging pile providers;

[0280] After confirming that any charging pile provider has passed the authentication, the first service agreement is displayed, which includes the fee settlement rules between any charging pile provider and the charging pile subscriber.

[0281] In response to any charging station provider's confirmation of the first service agreement, the transaction account of any charging station provider shall be activated.

[0282] Optionally, the transaction cloud platform also includes a second onboarding module for:

[0283] The second entry interface is displayed;

[0284] In response to the charging pile subscriber's operation on the second entry interface, authenticate the charging pile subscriber;

[0285] After confirming the charging pile subscriber's authentication, the second service agreement is displayed, which includes the fee settlement rules between the charging pile subscriber and each of the multiple charging pile providers.

[0286] In response to the charging pile subscriber's confirmation of the second service agreement, the charging pile subscriber's transaction account is activated.

[0287] Optionally, the first acquisition module is used for:

[0288] Display the charging station registration interface;

[0289] Receive operations from any one of the multiple charging pile providers on the charging pile registration interface, and obtain at least one charging pile registered by any one of the charging pile providers;

[0290] The charging pile listing interface is displayed, which includes listing options for each charging pile among at least one registered charging pile.

[0291] Receive operations from any charging pile provider on the charging pile listing interface and display at least one charging pile listed by any charging pile provider.

[0292] The first acquisition module 2001, the first display module 2002, the first determination module 2003, and the settlement module 2004 can all be implemented in software or in hardware. For example, the implementation of the first acquisition module 2001 will be described below. Similarly, the implementation of the first display module 2002, the first determination module 2003, and the settlement module 2004 can all refer to the implementation of the first acquisition module 2001.

[0293] As an example of a software functional unit, the first acquisition module 2001 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, and a container. Further, the aforementioned computing instance may be one or more. For example, the first acquisition module 2001 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed in the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed in the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0294] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

[0295] As an example of a hardware functional unit, the first acquisition module 2001 may include at least one computing device, such as a server. Alternatively, the first acquisition module 2001 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be implemented using a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0296] The multiple computing devices included in the first acquisition module 2001 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in the first acquisition module 2001 can be distributed in the same Availability Zone (AZ) or in different AZs. Likewise, the multiple computing devices included in the first acquisition module 2001 can be distributed in the same Virtual Private Cloud (VPC) or in multiple VPCs. These multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0297] It should be noted that, in other embodiments, the first acquisition module 2001 can be used to execute any step in the service transaction method based on cloud technology, the first display module 2002 can be used to execute any step in the service transaction method based on cloud technology, the first determination module 2003 can be used to execute any step in the service transaction method based on cloud technology, and the settlement module 2004 can be used to execute any step in the service transaction method based on cloud technology. The steps implemented by the first acquisition module 2001, the first display module 2002, the first determination module 2003, and the settlement module 2004 can be specified as needed. By implementing different steps in the service transaction method based on cloud technology through the first acquisition module 2001, the first display module 2002, the first determination module 2003, and the settlement module 2004, all functions of the transaction cloud platform can be realized.

[0298] This application also provides a computing device 2100. As shown in FIG21, the computing device 2100 includes: a bus 2102, a processor 2104, a memory 2106, and a communication interface 2108. The processor 2104, the memory 2106, and the communication interface 2108 communicate with each other via the bus 2102. The computing device 2100 may be a server or a terminal device. It should be understood that this application does not limit the number of processors and memories in the computing device 2100.

[0299] Bus 2102 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, only one line is used in Figure 21, but this does not imply that there is only one bus or one type of bus. Bus 2102 can include pathways for transmitting information between various components of computing device 2100 (e.g., memory 2106, processor 2104, communication interface 2108).

[0300] Processor 2104 may include any one or more processors such as a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP).

[0301] The memory 2106 may include volatile memory, such as random access memory (RAM). The processor 2104 may also include non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid state drive (SSD).

[0302] The memory 2106 stores executable program code, and the processor 2104 executes this executable program code to implement the functions of the aforementioned first acquisition module 2001, first display module 2002, first determination module 2003, and settlement module 2004, thereby realizing the service transaction method based on cloud technology. That is, the memory 2106 stores instructions for executing the service transaction method based on cloud technology.

[0303] Alternatively, the memory 2106 may store executable code, which the processor 2104 executes to implement the functions of the aforementioned transaction cloud platform, thereby realizing a service transaction method based on cloud technology. That is, the memory 2106 stores instructions for executing the service transaction method based on cloud technology.

[0304] The communication interface 2108 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the computing device 2100 and other devices or communication networks.

[0305] This application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0306] As shown in Figure 22, the computing device cluster includes at least one computing device 2100. The memory 2106 of one or more computing devices 2100 in the computing device cluster may store the same instructions for executing cloud-based service transaction methods.

[0307] In some possible implementations, the memory 2106 of one or more computing devices 2100 in the computing device cluster may also store partial instructions for executing cloud-based service transaction methods. In other words, a combination of one or more computing devices 2100 can jointly execute instructions for executing cloud-based service transaction methods.

[0308] It should be noted that the memory 2106 in different computing devices 2100 within the computing device cluster can store different instructions, which are used to execute certain functions of the transaction cloud platform. That is, the instructions stored in the memory 2106 of different computing devices 2100 can implement the functions of one or more modules among the first acquisition module 2001, the first display module 2002, the first determination module 2003, and the settlement module 2004.

[0309] In some possible implementations, one or more computing devices in a computing device cluster can be connected via a network. This network can be a wide area network (WAN) or a local area network (LAN), etc. Figure 23 illustrates one possible implementation. As shown in Figure 23, two computing devices 2100A and 2100B are connected via a network. Specifically, they are connected to the network through communication interfaces in each computing device. In this type of possible implementation, the memory 2106 in computing device 2100A stores instructions for executing the functions of the first acquisition module 2001, the first display module 2002, and the first determination module 2003. Simultaneously, the memory 2106 in computing device 2100B stores instructions for executing the functions of the settlement module 2004.

[0310] It should be understood that the functions of computing device 2100A shown in Figure 23 can also be performed by multiple computing devices 2100. Similarly, the functions of computing device 2100B can also be performed by multiple computing devices 2100.

[0311] This application also provides a computer program product containing instructions. The computer program product may be a software or program product containing instructions, capable of running on a computing device or stored on any usable medium. When the computer program product runs on at least one computing device, it causes the at least one computing device to execute a cloud-based service transaction method.

[0312] This application also provides a computer-readable storage medium. The computer-readable storage medium can be any available medium that a computing device can store, or a data storage device such as a data center that includes one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive). The computer-readable storage medium includes instructions that instruct a computing device to execute a cloud-based service transaction method.

[0313] In this application, the term "at least one" refers to one or more, and "multiple" refers to two or more. Unless otherwise stated, the symbol " / " generally signifies "or," for example, A / B can mean A or B. The term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Furthermore, for clarity, the terms "first," "second," and "third" are used in this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," and "third" do not limit the quantity or order of execution.

[0314] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. 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. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the protection scope of the technical solutions of the embodiments of this application.

Claims

1. A service transaction method based on cloud technology, characterized in that, The method is applied to a transaction cloud platform for a charging pile subscriber to subscribe to charging piles provided by a plurality of charging pile providers, a plurality of users are registered in the charging pile subscriber, and the plurality of users can charge using the charging piles subscribed by the charging pile subscriber; the method comprises: obtaining at least one charging pile respectively put on the transaction cloud platform by the plurality of charging pile providers; displaying a charging pile subscription interface, the charging pile subscription interface comprising charging piles respectively put on by the plurality of charging pile providers; in response to an operation of the charging pile subscriber on the charging pile subscription interface, determining at least one charging pile subscribed by the charging pile subscriber, and instructing the charging pile subscriber to display the subscribed charging pile to the plurality of users; in response to the plurality of users using the charging piles subscribed by the charging pile subscriber, settling charging fees between the plurality of users and the charging pile subscriber, and charging fees between the charging pile subscriber and the plurality of charging pile providers.

2. The method of claim 1, wherein, The plurality of users comprises a target user, the target user uses a target charging pile subscribed by the charging pile subscriber, and the plurality of charging pile providers comprises a first charging pile provider, the first charging pile provider being a charging pile provider providing the target charging pile; The response to the plurality of users using the charging piles subscribed by the charging pile subscriber to settle the charging fees between the plurality of users and the charging pile subscriber comprises: obtaining a use detail of the target user using the target charging pile from the first charging pile provider; sending the use detail to the charging pile subscriber, instructing the charging pile subscriber to display a charging billing result to the target user according to the use detail, the charging billing result being used to instruct the target user to transact charging fees with the charging pile subscriber.

3. The method of claim 1 or 2, wherein, The plurality of charging pile providers comprises a second charging pile provider; The response to the plurality of users using the charging piles subscribed by the charging pile subscriber to settle the charging fees between the charging pile subscriber and the plurality of charging pile providers comprises: summarizing a total use detail of charging piles between the charging pile subscriber and the second charging pile provider, the total use detail comprising a sum of use details of all users of the charging pile subscriber using charging piles provided by the second charging pile provider; displaying the total use detail of charging piles; in response to a confirmation operation of the charging pile subscriber and the second charging pile provider on the total use detail of charging piles, generating a charging bill according to the total use detail of charging piles; according to the charging bill, transacting charging fees between a transaction account of the charging pile subscriber and a transaction account of the second charging pile provider.

4. The method according to any one of claims 1 to 3, characterized in that, After the response to the plurality of users using the charging piles subscribed by the charging pile subscriber to settle the charging fees between the charging pile subscriber and the plurality of charging pile providers, the method further comprises: displaying a first transaction query interface; In response to an operation of any charging pile provider in the plurality of charging pile providers on the first transaction query interface, transaction details of the any charging pile provider are displayed.

5. The method according to any one of claims 1 to 4, characterized in that, After the settlement of the charging fees between the charging pile subscription party and the plurality of charging pile providers in response to the plurality of users using the charging piles subscribed by the charging pile subscription party, the method further comprises: displaying a second transaction query interface; In response to an operation of the charging pile subscription party on the second transaction query interface, transaction details of the charging pile subscription party are displayed.

6. The method of any one of claims 1-5, wherein, Before the acquisition of the at least one charging pile respectively put on the transaction cloud platform by the plurality of charging pile providers, the method further comprises: acquiring a first interface set configured by any charging pile provider in the plurality of charging pile providers, the first interface set comprising a charging pile query interface, a charging pile start interface, a charging pile stop interface and a use details query interface; displaying a first interface test interface based on the first interface set, the first interface test interface comprising a test option corresponding to each interface in the first interface set; In response to an operation of the any charging pile provider on the first interface test interface, the interfaces in the first interface set are tested to enable the transaction cloud platform to interact with the any charging pile provider through the interfaces in the first interface set.

7. The method of any one of claims 1-6, wherein, The transaction cloud platform is configured with a second interface set, the second interface set comprising a charging pile query interface, a charging pile start interface, a charging pile stop interface and a use details query interface; Before the display of the charging pile subscription interface, the method further comprises: displaying a second interface test interface, the second interface test interface comprising each interface in the second interface set and instructing the charging pile subscription party to test the interfaces in the second interface set to enable the charging pile subscription party to interact with the transaction cloud platform through the interfaces in the second interface set.

8. The method of any one of claims 1-7, wherein, Before the acquisition of the at least one charging pile respectively put on the transaction cloud platform by the plurality of charging pile providers, the method further comprises: displaying a first entry interface; In response to an operation of any charging pile provider in the plurality of charging pile providers on the first entry interface, the any charging pile provider is authenticated; After confirming that the any charging pile provider passes the authentication, a first service agreement is displayed, the first service agreement comprising a fee settlement rule between the any charging pile provider and the charging pile subscription party; In response to a confirmation operation of the any charging pile provider on the first service agreement, a transaction account of the any charging pile provider is opened.

9. The method of any one of claims 1-8, wherein, Before the display of the charging pile subscription interface, the method further comprises: displaying a second entry interface; In response to an operation of the charging pile subscription party on the second entry interface, the charging pile subscription party is authenticated; After confirming that the charging pile subscription party passes the authentication, a second service agreement is displayed, the second service agreement comprising a fee settlement rule between the charging pile subscription party and each charging pile provider in the plurality of charging pile providers; In response to a confirmation operation of the charging pile subscriber to the second service agreement, a transaction account of the charging pile subscriber is opened.

10. The method of any one of claims 1-9, wherein, The acquiring the at least one charging pile respectively provided by the plurality of charging pile providers in the transaction cloud platform comprises: displaying a charging pile registration interface; receiving an operation of any charging pile provider of the plurality of charging pile providers on the charging pile registration interface, and acquiring at least one charging pile registered by the any charging pile provider; displaying a charging pile listing interface, the charging pile listing interface comprising a listing option corresponding to each charging pile of the registered at least one charging pile; receiving an operation of the any charging pile provider on the charging pile listing interface, and displaying at least one charging pile listed by the any charging pile provider.

11. A transaction cloud platform, characterized by, The transaction cloud platform is used for a charging pile subscriber to subscribe to charging piles provided by a plurality of charging pile providers, a plurality of users are registered in the charging pile subscriber, and the plurality of users can charge using the charging piles subscribed by the charging pile subscriber; the transaction cloud platform comprises: a first acquiring module, configured to acquire at least one charging pile respectively provided by the plurality of charging pile providers in the transaction cloud platform; a first displaying module, configured to display a charging pile subscription interface, the charging pile subscription interface comprising charging piles respectively listed by the plurality of charging pile providers; a first determining module, configured to determine at least one charging pile subscribed by the charging pile subscriber in response to an operation of the charging pile subscriber on the charging pile subscription interface, and instruct the charging pile subscriber to display the subscribed charging piles to the plurality of users; a settlement module, configured to settle charging fees between the plurality of users and the charging pile subscriber, and charging fees between the charging pile subscriber and the plurality of charging pile providers in response to the plurality of users using the charging piles subscribed by the charging pile subscriber.

12. The transaction cloud platform of claim 11, wherein, The plurality of users comprises a target user, the target user uses a target charging pile subscribed by the charging pile subscriber, and the plurality of charging pile providers comprises a first charging pile provider, the first charging pile provider being a charging pile provider providing the target charging pile; the settlement module is configured to: acquire a use detail of the target user using the target charging pile from the first charging pile provider; send the use detail to the charging pile subscriber, instruct the charging pile subscriber to display a charging billing result to the target user according to the use detail, the charging billing result being used to instruct the target user to transact charging fees with the charging pile subscriber.

13. The transaction cloud platform of claim 11 or 12, wherein, The plurality of charging pile providers comprises a second charging pile provider; the settlement module is configured to: aggregate a total use detail of charging piles between the charging pile subscriber and the second charging pile provider, the total use detail comprising a sum of use details of charging piles provided by the second charging pile provider used by all users in the charging pile subscriber; display the total use detail of charging piles; in response to a confirmation operation of the charging pile subscriber and the second charging pile provider to the total use detail of charging piles, generate a charging bill according to the total use detail of charging piles; and the settlement module is configured to: aggregate a total use detail of charging piles between the charging pile subscriber and the second charging pile provider, the total use detail comprising a sum of use details of charging piles provided by the second charging pile provider used by all users in the charging pile subscriber; display the total use detail of charging piles; in response to a confirmation operation of the charging pile subscriber and the second charging pile provider to the total use detail of charging piles, generate a charging bill according to the total use detail of charging piles. According to the charging bill, the charging fee is traded between the transaction account of the charging pile subscriber and the transaction account of the second charging pile provider.

14. The transaction cloud platform of any of claims 11-13, wherein, The transaction cloud platform further comprises a second display module, configured to: display a first transaction query interface; in response to the operation of any charging pile provider in the plurality of charging pile providers on the first transaction query interface, display the transaction details of the any charging pile provider.

15. The transaction cloud platform of any of claims 11-14, wherein, The transaction cloud platform further comprises a third display module, configured to: display a second transaction query interface; in response to the operation of the charging pile subscriber on the second transaction query interface, display the transaction details of the charging pile subscriber.

16. The transaction cloud platform of any one of claims 11-15, wherein, The transaction cloud platform further comprises: a second acquisition module, configured to acquire a first interface set configured on any charging pile provider in the plurality of charging pile providers, the first interface set comprising a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface; a fourth display module, configured to display a first interface test interface based on the first interface set, the first interface test interface comprising a test option corresponding to each interface in the first interface set; a test module, configured to, in response to the operation of the any charging pile provider on the first interface test interface, test the interfaces in the first interface set, so that the transaction cloud platform can interact with the any charging pile provider through the interfaces in the first interface set.

17. The transaction cloud platform of any of claims 11-16, wherein, The transaction cloud platform is configured with a second interface set, the second interface set comprising a charging pile query interface, a charging pile start interface, a charging pile stop interface, and a usage details query interface; The transaction cloud platform further comprises: a fifth display module, configured to display a second interface test interface, the second interface test interface comprising each interface in the second interface set and instructing the charging pile subscriber to test the interfaces in the second interface set, so that the charging pile subscriber can interact with the transaction cloud platform through the interfaces in the second interface set.

18. The transaction cloud platform of any of claims 11-17, wherein, The transaction cloud platform further comprises a first entry module, configured to: display a first entry interface; in response to the operation of the any charging pile provider in the plurality of charging pile providers on the first entry interface, authenticate the any charging pile provider; after confirming that the authentication of the any charging pile provider is passed, display a first service agreement, the first service agreement comprising a fee settlement rule between the any charging pile provider and the charging pile subscriber; in response to the confirmation operation of the any charging pile provider on the first service agreement, open a transaction account of the any charging pile provider.

19. The transaction cloud platform of any of claims 11-18, wherein, The transaction cloud platform further comprises a second entry module, configured to: display a second entry interface; in response to the operation of the charging pile subscriber on the second entry interface, authenticate the charging pile subscriber; after confirming that the authentication of the charging pile subscriber is passed, display a second service agreement, the second service agreement comprising a fee settlement rule between the charging pile subscriber and each charging pile provider in the plurality of charging pile providers. In response to the charging pile subscriber confirming the second service agreement, a transaction account of the charging pile subscriber is opened.

20. The transaction cloud platform of any of claims 11-19, wherein, The first obtaining module is configured to: display a charging pile registration interface; receive an operation of any charging pile provider in the plurality of charging pile providers on the charging pile registration interface, and obtain at least one charging pile registered by the any charging pile provider; display a charging pile listing interface, the charging pile listing interface comprising a listing option corresponding to each charging pile in the at least one registered charging pile; receive an operation of the any charging pile provider on the charging pile listing interface, and display at least one charging pile listed by the any charging pile provider.

21. A cluster of computing devices, characterized in that, comprise at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device, so that the computing device cluster executes the method as claimed in any one of claims 1-10.

22. A computer program product comprising instructions, wherein: When the instructions are executed by the computing device cluster, the computing device cluster executes the method as claimed in any one of claims 1-10.

23. A computer-readable storage medium, characterized in that, comprise computer program instructions, when the computer program instructions are executed by the computing device cluster, the computing device cluster executes the method as claimed in any one of claims 1-10.

Images