Charging data distribution method and device based on cloud service, and medium

Abstract

The invention discloses a charging data distribution method and device based on cloud service, and a medium, and relates to the technical field of new energy vehicles. The method comprises the following steps: configuring connection information of a battery charging and swapping enterprise terminal and a docking platform in a battery charging and swapping data distribution system, and configuring transmission information of the docking platform; wherein the transmission information comprises a required charging data type and a push interface; acquiring to-be-distributed data from a database corresponding to the charging and swapping enterprise terminal based on the required charging and swapping data type under the condition that the distribution demand is triggered, and assembling a to-be-sent message based on the connection information and the to-be-distributed data; and distributing the to-be-sent message to the docking platform based on the push interface. According to the method, the technical problem that when the number of platforms is too large, a battery charging and replacing enterprise needs to maintain a large number of systems, and a large amount of manpower and material resources are consumed is solved.

Description

[0001] This application claims priority based on the invention patent application filed with the China National Intellectual Property Administration on December 29, 2023, with the application number 2023118678507 and the invention title "A Method, Device, and Medium for Charging and Swapping Data Distribution Based on Cloud Services". The entire content of the above Chinese patent application is incorporated herein by reference. Technical Field

[0002] This application relates to the technical field of new energy vehicles, and particularly to a method, device, and medium for charging and swapping data distribution based on cloud services. Background Art

[0003] The China Charging Alliance has established a national monitoring platform for electric vehicle charging infrastructure, which aims to integrate the information resources of charging service platforms of different enterprises and cities, promote the interconnection and interoperability of different charging service platforms, and provide support for policy-making. The platform has achieved quasi-dynamic docking with enterprise-level platforms, and can query four-level menus online to display various static information of public charging piles and swapping stations.

[0004] To meet the data requirements of the platform, each charging and swapping enterprise reports data to the government platform or the host factory platform, providing information such as the location, current, and voltage of public charging piles and swapping stations. However, charging and swapping enterprises need to connect to numerous government platforms and host factory platforms, and the data communication protocols of each platform are different, resulting in the need for charging and swapping enterprises to customize a set of data distribution protocols for each platform. Therefore, when the number of platforms is too large, it will cause charging and swapping enterprises to need to maintain a large number of systems, consuming a large amount of manpower and material resources. Summary of the Invention

[0005] Embodiments of this application provide a method, device, and medium for charging and swapping data distribution based on cloud services to solve the following technical problem: when the number of platforms is too large, it will cause charging and swapping enterprises to need to maintain a large number of systems, consuming a large amount of manpower and material resources.

[0006] In a first aspect, embodiments of this application provide a method for charging and swapping data distribution based on cloud services, which is characterized in that it is applied to a charging and swapping data distribution system. The method includes: configuring the connection information between the charging and swapping enterprise side and the docking platform in the charging and swapping data distribution system, and configuring the transmission information of the docking platform; wherein, the transmission information includes the required charging and swapping data types and the push interface; in the case of triggering a distribution requirement, obtaining the data to be distributed from the database corresponding to the charging and swapping enterprise side based on the required charging and swapping data types, and assembling a message to be sent based on the connection information and the data to be distributed; and distributing the message to be sent to the docking platform based on the push interface.

[0007] A method for distributing charging and swapping data based on cloud services provided by an embodiment of the present application realizes the rapid distribution of charging and swapping data through cloud services, improving the efficiency of data transmission. Through cloud services, data encryption and backup can be achieved to ensure the security and integrity of data. According to actual requirements, the connection information and transmission information between the charging and swapping enterprise side and the docking platform can be flexibly configured to meet the data distribution requirements in different scenarios. The method for distributing charging and swapping data based on cloud services can provide high availability and fault tolerance, ensuring that data distribution can still proceed normally under various abnormal conditions. With the development of the charging and swapping business, the data volume may continuously increase, and the method for distributing charging and swapping data based on cloud services can easily expand servers and storage devices to meet the growing data processing requirements.

[0008] In an implementation manner of the present application, the connection information between the charging and swapping enterprise side and the docking platform is configured in the charging and swapping data distribution system, specifically including: generating a message key and a signature key when the docking authentication between the charging and swapping enterprise side and the docking platform is passed; sending the message key and the signature key to the charging and swapping enterprise side and the docking platform side for storage; preferably, the method further includes: obtaining the docking platform identifier and the docking platform key of the docking platform; wherein, the docking platform identifier and the docking platform key are assigned when the docking platform registers in the charging and swapping data distribution system; based on the docking platform identifier and the docking platform key, applying for the docking authentication between the charging and swapping enterprise side and the docking platform.

[0009] By obtaining the docking platform identifier and the docking platform key of the docking platform in the embodiment of the present application, the connection security between the charging and swapping enterprise side and the docking platform can be ensured. The identifier and the key are used to generate the message key and the signature key, which can guarantee the security and integrity of data transmission. Based on the docking platform identifier and the docking platform key, the charging and swapping enterprise side can apply for docking authentication. Only through docking authentication can a connection with the docking platform be established to ensure the legality and security of the connection between the charging and swapping enterprise side and the docking platform. The connection information between the charging and swapping enterprise side and the docking platform can be flexibly configured according to actual requirements. Different docking platforms may have different identifiers and keys, which can be configured according to actual situations to meet the connection requirements in different scenarios. By sending the message key and the signature key to the charging and swapping enterprise side and the docking platform side for storage, traceability and verification can be carried out when data transmission problems occur, ensuring the source and integrity of data. It can be easily extended to more charging and swapping enterprise sides and docking platforms, supporting more business requirements, and having good scalability.

[0010] In an implementation manner of the present application, the transmission information of the docking platform is configured, which specifically includes: determining the required charging and swapping data types of the docking platform, and based on the required charging and swapping data types, determining the corresponding charging and swapping station IDs. The required charging and swapping data types include charging and swapping data type information and charging and swapping station information; configuring the push interface of the docking platform; preferably, configuring the push interface of the docking platform specifically includes: determining any HTTP(S) interface as the push interface to be configured, and configuring the URL of the push interface to be configured; specifying that the push interface to be configured uses the HTTP(S) / POST method to transmit parameters, and defining the data format corresponding to the message to be sent as JSON.

[0011] In the embodiment of the present application, by determining the required charging and swapping data types of the docking platform and determining the corresponding charging and swapping station IDs based on these types, the standardization and consistency of the data are ensured, which helps to reduce errors and misunderstandings caused by inconsistent data formats or missing information. Configuring the push interface of the docking platform makes the data transmission interface clear and reduces the docking difficulty. For charging and swapping stations or other data sources, as long as the data is sent according to the predetermined interface and data format, it can ensure that the data is correctly received and processed. Preferably, the HTTP(S) / POST method is used to transmit parameters. This method is very common and efficient in network transmission. The POST method is particularly suitable for sending a large amount of data because it has no data length limit and can send the data included in the request body.

[0012] In an implementation manner of the present application, before obtaining the corresponding data to be distributed in the distribution database based on the required charging and swapping data types, the method further includes: connecting the corresponding charging and swapping station based on the charging and swapping station ID; obtaining the corresponding required charging and swapping data in the charging and swapping station based on the required charging and swapping data types, and sending the required charging and swapping data to the distribution database; performing standardization processing on the required charging and swapping data in the distribution database to obtain the corresponding data to be distributed.

[0013] In the embodiment of the present application, by directly connecting the charging and swapping station and obtaining the required charging and swapping data, this solution can ensure the timeliness and accuracy of the data. The data of the charging and swapping station is usually updated in real time, and such data can better reflect the current charging and swapping situation. By using the charging and swapping station ID to locate and connect the corresponding charging and swapping station, it can ensure that the data is obtained from the correct data source and guarantee the integrity of the data. By automatically connecting the charging and swapping station, obtaining data, sending it to the distribution database and performing standardization processing, the complexity and error rate of manual operations are greatly reduced, and the overall work efficiency is improved. Real-time, accurate, and complete charging and swapping data helps charging and swapping enterprises better understand the operation situation, so as to make more informed decisions, such as adjusting electricity prices, optimizing the charging and swapping layout, etc.

[0014] In an implementation manner of the present application, the charging and swapping data distribution system includes a configuration parsing engine, a data assembly engine, and a data forwarding engine. The method further includes: obtaining configuration information corresponding to the docking platform, where the configuration information includes connection information and transmission information; putting the configuration information into the configuration parsing engine for parsing to obtain the parsed configuration data; putting the parsed configuration data into the message queue to send the parsed configuration data to the data assembly engine through the message queue for data assembly; and / or obtaining the assembled message to be sent from the data assembly engine; putting the assembled message to be sent into the message queue to send the encapsulated message to be sent to the data forwarding engine through the message queue for data forwarding.

[0015] In the embodiment of the present application, by directly obtaining the required charging and swapping data from the charging and swapping station and sending it to the distribution database, the accuracy and real-time nature of the data can be ensured, and errors and distortions in data transmission are avoided. By performing standardized processing on the required charging and swapping data in the distribution database, the integrity and consistency of the data can be ensured, and problems such as inconsistent data formats or missing data are avoided. By directly connecting to the corresponding charging and swapping station and obtaining the required charging and swapping data, the intermediate links in data transmission can be reduced, and the efficiency of data acquisition and processing is improved. By performing standardized processing on the required charging and swapping data in the distribution database, data traceability and auditing can be conveniently carried out to ensure the source and reliability of the data. By connecting to the corresponding charging and swapping station based on the charging and swapping station id, the source and method of data acquisition can be flexibly adjusted according to actual needs to meet the data acquisition requirements in different scenarios.

[0016] In an implementation manner of the present application, based on the connection information and the data to be distributed, assemble the message to be sent, specifically including: constructing the message header of the message to be sent based on the preset message header definition rule; constructing the message body of the message to be sent based on the data to be distributed, and encrypting the message body based on the message key to obtain the message body to be assembled; assembling the message header and the message body to be assembled to obtain the message to be signed; signing the message to be signed based on the signature key to obtain the message to be sent; preferably, the message header includes: content type and authorization information, where the content type is used to identify the encoding method of the message body in the request, and the authorization information is used to indicate the operation authority of the docking platform.

[0017] In the embodiment of the present application, by constructing a message header and encrypting the message body with a message key, the security and integrity of the message can be ensured. The message header includes the content type and authorization information, which can ensure the legality of the source and destination of the message. By constructing the message header based on the preset message header definition rules, the standardization and normalization of the message header can be ensured, facilitating data interaction and integration between different systems. By encrypting the message body with the message key, the security of the data to be distributed can be protected, preventing the data from being tampered with or stolen during transmission. By signing the message to be signed, the integrity and authenticity of the message can be ensured, avoiding the forgery and tampering of the message.

[0018] In one implementation manner of the present application, based on the signature key, sign the message to be signed to obtain the message to be sent, specifically including: determining the parameters to be signed; performing a hash operation on the parameters to be signed based on the hash function preset on the charging and swapping enterprise side to generate a message digest; encrypting the message digest with the signature key to generate a digital signature; assembling the parameters to be signed, the digital signature and the message to be signed to obtain the message to be sent; preferably, the parameters to be signed include at least one of the charging and swapping enterprise identifier and the increment sequence; the increment sequence is used to represent the number of times the distribution requirement is triggered.

[0019] In the embodiment of the present application, by encrypting the message digest with the signature key, the integrity and authenticity of the message can be ensured, preventing the message from being tampered with or forged during transmission. The digital signature can be used to verify the source and identity of the message, ensuring that the message is sent by the legal charging and swapping enterprise side, improving the security and credibility of the message. By introducing the increment sequence, the uniqueness and order of each distribution request can be ensured, preventing the occurrence of duplicate requests, and improving the accuracy and efficiency of data distribution. By performing a hash operation using the hash function preset on the charging and swapping enterprise side, the irreversibility and randomness of the message digest can be ensured, enhancing the security of the data.

[0020] In one implementation manner of the present application, after distributing the message to be sent to the docking platform based on the push interface, the method further includes: the docking platform performs a hash operation on the parameters to be signed in the message to be sent based on the preset hash function to generate a message digest to be compared; comparing the message digest with the message digest to be compared, and when it is determined that the message digest is the same as the message digest to be compared, encrypting the message body with the message key to obtain the data to be distributed.

[0021] In the embodiment of the present application, the docking platform performs a hash operation on the signature parameter to be sent in the received message to be sent, and compares it with the message digest to be compared generated by the preset hash function. If the two are the same, it indicates that the message to be sent has not been tampered with during the transmission process, ensuring the integrity of the data. By comparing the message digest with the message digest to be compared, the docking platform can prevent duplicate processing of the same data, improving the processing efficiency and accuracy. When the docking platform determines that the message digest is the same as the message digest to be compared, it encrypts the message body using the message key, further enhancing the security of the data.

[0022] In a second aspect, the embodiment of the present application provides a method for distributing charging and swapping data based on cloud services, which is characterized in that it is applied to a charging and swapping data distribution system. The method includes: configuring the connection information between the charging and swapping enterprise side and the docking platform in the charging and swapping data distribution system, and configuring the transmission information of the docking platform; wherein, the transmission information includes the required charging and swapping data types and the push interface; in the case of triggering a distribution requirement, based on the required charging and swapping data types, obtain the corresponding data to be distributed in the distribution database, and assemble the message to be sent based on the connection information; based on the push interface, distribute the message to be sent to the docking platform.

[0023] In an implementation manner of the present application, configuring the connection information between the charging and swapping enterprise side and the docking platform in the charging and swapping data distribution system specifically includes: the charging and swapping enterprise side obtains the docking platform identifier and the docking platform key of the docking platform; wherein, the docking platform identifier and the docking platform key are allocated when the docking platform registers in the charging and swapping data distribution system; based on the docking platform identifier and the docking platform key, apply for docking authentication; in the case of successful docking authentication, generate a message key and a signature key, and send the message key and the signature key to the charging and swapping enterprise side and the docking platform side for storage.

[0024] In an implementation manner of the present application, configuring the transmission information of the docking platform specifically includes: determining the required charging and swapping data types of the docking platform, and based on the required charging and swapping data types, determining the corresponding charging and swapping station id; configuring the push interface of the docking platform.

[0025] In an implementation manner of the present application, configuring the push interface of the docking platform specifically includes: determining any HTTP(S) interface as the push interface to be configured, and configuring the URL of the push interface to be configured; specifying that the push interface to be configured uses the HTTP(S) / POST method to transmit parameters, and defining the data format corresponding to the message to be sent as JSON.

[0026] In one implementation manner of the present application, before obtaining the corresponding data to be distributed in the distribution database based on the required charging and swapping data type, the method further includes: connecting to the corresponding charging and swapping station based on the charging and swapping station ID; obtaining the corresponding required charging and swapping data in the charging and swapping station based on the required charging and swapping data type, and sending the required charging and swapping data to the distribution database; performing standardization processing on the required charging and swapping data in the distribution database to obtain the corresponding data to be distributed.

[0027] In one implementation manner of the present application, assembling the message to be sent based on the connection information specifically includes: constructing the message header of the message to be sent based on the preset message header definition rule; wherein, the message header includes: content type and authorization information; the content type includes data format and encoding method; constructing the message body of the message to be sent based on the data to be distributed, and encrypting the message body based on the message key to obtain the message body to be assembled; assembling the message header and the message body to be assembled to obtain the message to be signed; signing the message to be signed based on the signature key to obtain the message to be sent.

[0028] In one implementation manner of the present application, signing the message to be signed based on the signature key to obtain the message to be sent specifically includes: determining the signature parameters; wherein, the signature parameters include: charging and swapping enterprise identifier, self-increasing sequence; the self-increasing sequence is used to represent the number of times the distribution requirement is triggered; performing a hash operation on the signature parameters based on the hash function preset at the charging and swapping enterprise side to generate a message digest; encrypting the message digest through the signature key to generate a digital signature; assembling the signature parameters, the digital signature and the message to be signed to obtain the message to be sent.

[0029] In one implementation manner of the present application, after distributing the message to be sent to the docking platform based on the push interface, the method further includes: the docking platform performing a hash operation on the signature parameters in the message to be sent based on the preset hash function to generate a message digest to be compared; comparing the message digest with the message digest to be compared, and when it is determined that the message digest is the same as the message digest to be compared, encrypting the message body based on the message key to obtain the data to be distributed.

[0030] In a third aspect, an embodiment of the present application further provides a cloud service-based charging and swapping data distribution system, characterized in that the system includes: a configuration module, an assembly module, and a distribution module; the configuration module is used to configure the connection information between the charging and swapping enterprise side and the docking platform, and configure the transmission information of the docking platform; wherein, the transmission information includes the required charging and swapping data types and push interfaces; the assembly module is used to, when a distribution requirement is triggered, obtain the data to be distributed from the database corresponding to the charging and swapping enterprise side based on the required charging and swapping data types, and assemble the message to be sent based on the connection information and the data to be distributed; the distribution module is used to distribute the message to be sent to the docking platform based on the push interface.

[0031] In a fourth aspect, an embodiment of the present application further provides a non-volatile computer storage medium for cloud service-based charging and swapping data distribution, storing computer-executable instructions capable of implementing the cloud service-based charging and swapping data distribution method as described in any one of the above.

[0032] A cloud service-based charging and swapping data distribution method, device, and medium provided by an embodiment of the present application, through operations such as data encryption and signature verification, avoid the possibility that the cloud forwarding service is exposed on the public network and the plaintext information is stolen by others. The cloud forwarding service is easy to maintain. The forwarding system will not become bloated as the number of docking platforms increases, and will not consume a large amount of manpower, material resources, and financial resources. Through the functional aggregation and implementation of key core services, the number of systems can be greatly reduced, facilitating maintenance. For data, customized processing can be performed. Through the function of page configuration, for different protocols and different data information contents, data can be automatically assembled according to the required configuration rules, thereby realizing customized processing of data. The data processing ability is greatly improved. Because the core services of the system have clear divisions of labor and high functional aggregation. For example, the data assembly service is only responsible for assembling data; the data sending service is only responsible for sending data. Thus, the use efficiency of resources is greatly improved, and the ability to process data is significantly improved. Hundreds of millions of data can be assembled / sent per day. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] The drawings described herein are used to provide a further understanding of the present application, and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application, and do not constitute an improper limitation to the present application. In the drawings:

[0034] Figure 1 It is a flowchart of a cloud service-based charging and swapping data distribution method provided by an embodiment of the present application;

[0035] Figure 2 It is a schematic internal structure diagram of a cloud service-based charging and swapping data distribution system provided by an embodiment of the present application;

[0036] Figure 3Schematic structural diagram of a charging and swapping data distribution system of the present application;

[0037] Figure 4 Another flowchart of a charging and swapping data distribution method based on cloud service provided by an embodiment of the present application. Specific implementation manners

[0038] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with specific embodiments of the present application and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the protection scope of the present application.

[0039] The China Electric Vehicle Charging Infrastructure Promotion Alliance (hereinafter referred to as the "China Charging Alliance"), as the national industry organization for charging and swapping infrastructure, together with the China Automobile Industry Association, built and launched the National Electric Vehicle Charging Infrastructure Monitoring Platform (hereinafter referred to as the "National Charging and Swapping Facility Monitoring Platform") in 2019. The National Charging and Swapping Facility Monitoring Platform aims to establish an interconnection mechanism, unify the information exchange protocol, effectively integrate the information resources of charging service platforms of different enterprises and different cities, promote the interconnection of different charging service platforms, and provide support for formulating and implementing fiscal, taxation, supervision and other policies.

[0040] The National Charging and Swapping Facility Monitoring Platform has basically achieved quasi-dynamic docking (monthly) with enterprise-level platforms, and has online query of 4-level menus such as the whole country, provincial and municipal levels, enterprise lists, pile stations, etc., and displays various static information such as the quantity, type, power, provinces and cities, operators of public charging piles and swapping stations. In order to meet various data requirements of the National Charging and Swapping Facility Monitoring Platform, each charging and swapping enterprise will report its own charging and swapping data to the government monitoring platform at all levels (hereinafter referred to as the "government platform") or the platform of automobile manufacturers (hereinafter referred to as the "host factory platform"), providing information such as the location information, current, voltage, standards of public charging piles and swapping stations, effectively supporting the data statistics work of charging and swapping facilities, and providing information services for the government and the industry.

[0041] At present, for charging and swapping enterprises, they need to connect to a large number of government platforms and OEM platforms. Moreover, since each government platform and OEM platform has a certain degree of autonomy in formulating data communication protocols. Therefore, charging and swapping enterprises need to customize one set of data distribution protocols after another for government platforms and OEM platforms at all levels to meet the normal communication of various types of data. For the current situation, the general solution for charging and swapping enterprises to collect data is to set up a separate distribution system for each platform, and one distribution system only serves a certain platform. The biggest drawback of this solution is that when the number of connected platforms is too large, charging and swapping enterprises need to maintain dozens of systems, and the manpower and material resources consumed increase linearly with the number of connected platforms.

[0042] The embodiment of the present application provides a cloud service-based charging and swapping data distribution method, device and medium to solve the following technical problems: when the number of platforms is too large, it will cause charging and swapping enterprises to need to maintain a large number of systems and consume a large amount of manpower and material resources.

[0043] The technical solution proposed by the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

[0044] Figure 1 It is a flowchart of a cloud service-based charging and swapping data distribution method provided by the embodiment of the present application. As Figure 1 shown, a cloud service-based charging and swapping data distribution method provided by the embodiment of the present application is applied to a charging and swapping data distribution system, and specifically includes the following steps:

[0045] Step 101: Configure the connection information between the charging and swapping enterprise side and the connected platform in the charging and swapping data distribution system, and configure the transmission information of the connected platform.

[0046] In an embodiment of the present application, to implement the cloud service-based charging and swapping data distribution method, first configure the connection information between the charging and swapping enterprise side and the connected platform in the charging and swapping data distribution system.

[0047] Specifically, when the docking authentication between the charging and swapping enterprise side and the connected platform is passed, generate a message key and a signature key; send the message key and the signature key to the charging and swapping enterprise side and the connected platform side for storage; preferably, the method further includes: obtaining the connected platform identifier and the connected platform key of the connected platform; wherein, the connected platform identifier and the connected platform key are allocated when the connected platform registers in the charging and swapping data distribution system; based on the connected platform identifier and the connected platform key, apply for the docking authentication between the charging and swapping enterprise side and the connected platform.

[0048] In one embodiment, to implement the charging and swapping data distribution method based on cloud services, it is first necessary to accurately configure the connection information between the charging and swapping enterprise side and the docking platform in the charging and swapping data distribution system, which is a key step to ensure that data can be safely and accurately distributed from the charging and swapping enterprise side to the docking platform. During implementation, first, the docking authentication between the charging and swapping enterprise side and the docking platform is performed to confirm the identities of both parties and establish a secure data transmission channel. When the docking authentication is passed, the system generates a pair of keys, namely the message key and the signature key. This pair of keys will play an encryption and verification role in the subsequent data transmission process to ensure the security and integrity of the data. After generating the keys, the system sends the message key and the signature key to the charging and swapping enterprise side and the docking platform side for storage respectively. In this way, in the subsequent data transmission, both parties can use these keys to encrypt and decrypt the data, as well as verify the authenticity and integrity of the data.

[0049] In addition, this embodiment also provides a preferred method to obtain the docking platform identifier and the docking platform key of the docking platform. These two parameters are assigned by the system when the docking platform registers in the charging and swapping data distribution system and have uniqueness and security. Through these two parameters, the identity of the docking platform can be further confirmed and the security of data transmission can be enhanced. After obtaining the docking platform identifier and the docking platform key, the charging and swapping enterprise side will apply for docking authentication with the docking platform based on these two parameters to reconfirm the identities and connection information of both parties before data transmission, ensuring that the data can be accurately transmitted to the target platform.

[0050] In one embodiment of the present application, it is also necessary to configure the transmission information of the docking platform in the charging and swapping data distribution system. It should be noted that the transmission information includes the required charging and swapping data types and the push interface.

[0051] Specifically, determine the required charging and swapping data types of the docking platform, and based on the required charging and swapping data types, determine the corresponding charging and swapping station IDs. The required charging and swapping data types include charging and swapping data type information and charging and swapping station information; configure the push interface of the docking platform; preferably, configure the push interface of the docking platform, specifically including: determine any HTTP(S) interface as the push interface to be configured, and configure the URL of the push interface to be configured; specify that the push interface to be configured uses the HTTP(S) / POST method to transmit parameters, and define the data format of the message to be sent as JSON.

[0052] In one embodiment, the transmission information of the docking platform determines the effectiveness and accuracy of data distribution. First, it is necessary to clarify the specific types of charging and swapping data required by the docking platform. This involves detailed communication with the docking platform to understand its business requirements and data usage scenarios. After determining the required data types, the system will further determine the corresponding charging and swapping station IDs based on this information. This is because different charging and swapping stations may provide different types of data, so it is necessary to ensure that the selected charging and swapping station can provide the data types required by the docking platform. The required charging and swapping data types not only include charging and swapping data type information but also charging and swapping station information. This design is to clearly identify the source and type of data during data transmission, facilitating the docking platform to correctly process and analyze the data. Next is to configure the push interface of the docking platform. The push interface is the key channel for data to be transmitted from the charging and swapping data distribution system to the docking platform, so its configuration must be accurate. In this embodiment, we preferably select the HTTP(S) interface as the push interface because the HTTP(S) protocol has a wide application foundation and good compatibility. When configuring specifically, first determine an available HTTP(S) interface as the push interface to be configured. Then, configure a unique URL for this interface, and this URL will be used as the target address for data pushing. At the same time, specify that the interface uses the HTTP(S) / POST method to transmit parameters because the POST method can carry more data and is relatively more secure. Finally, to ensure the standardization and consistency of data, it is also necessary to define the data format of the message to be sent as JSON. The JSON format has the characteristics of being concise, easy to read, and easy to parse, and is very suitable for the transmission and exchange of network data.

[0053] Step 102: In the case of triggering a distribution requirement, obtain the data to be distributed from the corresponding database at the charging and swapping enterprise end based on the required charging and swapping data types, and assemble the message to be sent based on the connection information and the data to be distributed.

[0054] In one embodiment of the present application, before obtaining the corresponding data to be distributed in the distribution database based on the required charging and swapping data types, the method further includes: connecting to the corresponding charging and swapping station based on the charging and swapping station ID; obtaining the required charging and swapping data in the charging and swapping station based on the required charging and swapping data types, and sending the required charging and swapping data to the distribution database; performing standardization processing on the required charging and swapping data in the distribution database to obtain the corresponding data to be distributed.

[0055] It should be noted that the interface for connecting to the corresponding charging and swapping station in the present application is also the HTTP(S) interface.

[0056] In one embodiment of the present application, in the case of triggering a distribution requirement, the data to be distributed is obtained from the corresponding database at the charging and swapping enterprise end based on the required charging and swapping data type.

[0057] Further, a message to be sent is assembled based on the connection information and the data to be distributed.

[0058] Specifically, based on the predefined message header definition rules, the message header of the message to be sent is constructed; based on the data to be distributed, the message body of the message to be sent is constructed, and the message body is encrypted based on the message key to obtain the message body to be assembled; the message header and the message body to be assembled are assembled to obtain the message to be signed; based on the signature key, the message to be signed is signed to obtain the message to be sent; preferably, the message header includes: content type and authorization information, the content type is used to identify the encoding method of the message body in the request, and the authorization information is used to indicate the operation authority of the docking platform.

[0059] In one embodiment, based on the predefined message header definition rules, the message header of the message to be sent is constructed: the charging and swapping enterprise end constructs the message header of the message to be sent according to the predefined message header definition rules. The message header includes content type and authorization information. The content type includes data format and encoding method. In this embodiment, the data format is JSON and the encoding method is UTF-8. Based on the data to be distributed, the message body of the message to be sent is constructed: the charging and swapping enterprise end uses the standardized data to be distributed as the message body to construct the message body of the message to be sent. Encrypt the message body based on the message key: the charging and swapping enterprise end uses the stored message key to encrypt the message body to obtain the message body to be assembled. Assemble the message header and the message body to be assembled: the charging and swapping enterprise end assembles the constructed message header and the message body to be assembled to form the message to be signed. Sign the message to be signed based on the signature key: the charging and swapping enterprise end uses the stored signature key to sign the message to be signed to increase the integrity and authenticity of the message.

[0060] In one embodiment of the present application, signing the message to be signed based on the signature key to obtain the message to be sent specifically includes: determining the parameters to be signed; performing a hash operation on the parameters to be signed based on the hash function pre-set at the charging and swapping enterprise end to generate a message digest; encrypting the message digest with the signature key to generate a digital signature; assembling the parameters to be signed, the digital signature and the message to be signed to obtain the message to be sent; preferably, the parameters to be signed include at least one of: the charging and swapping enterprise identifier, the self-incrementing sequence; the self-incrementing sequence is used to represent the number of times the distribution requirement is triggered.

[0061] In one embodiment, the parameters to be signed are determined: The charging and swapping enterprise terminal determines the parameters to be signed, including the charging and swapping enterprise identifier and an increment sequence. The increment sequence is used to represent the number of times the distribution requirement is triggered and will increase each time a distribution request is made. Based on the hash function pre - placed in the charging and swapping enterprise terminal, a hash operation is performed on the parameters to be signed: The charging and swapping enterprise terminal uses the pre - placed hash function to perform a hash operation on the parameters to be signed to generate a message digest. The hash function is used to ensure the uniqueness and immutability of the message. The message digest is encrypted with the signature key: The charging and swapping enterprise terminal uses the stored signature key to encrypt the message digest to generate a digital signature. The digital signature is used to ensure the integrity and authenticity of the message. The parameters to be signed, the digital signature, and the message to be signed are assembled: The charging and swapping enterprise terminal assembles the parameters to be signed, the digital signature, and the message to be signed to form a message to be sent. In this way, the message to be sent contains information such as the charging and swapping enterprise identifier, the increment sequence, and the digital signature.

[0062] Step 103: Based on the push interface, the message to be sent is distributed to the docking platform.

[0063] In one embodiment of the present application, after signing the message to be signed with the signature key to obtain the message to be sent, based on the push interface, the message to be sent is distributed to the docking platform.

[0064] In one embodiment of the present application, after distributing the message to be sent to the docking platform based on the push interface, the method further includes: The docking platform performs a hash operation on the parameters to be signed in the message to be sent based on the pre - placed hash function to generate a message digest to be compared; The message digest is compared with the message digest to be compared, and when it is determined that the message digest is the same as the message digest to be compared, the message body is encrypted based on the message key to obtain the data to be distributed.

[0065] In one embodiment of the present application, the charging and swapping data distribution system includes a configuration parsing engine, a data assembly engine, and a data forwarding engine. The method further includes: Obtaining the configuration information corresponding to the docking platform, where the configuration information includes connection information and transmission information; Putting the configuration information into the configuration parsing engine for parsing to obtain the parsed configuration data; Putting the parsed configuration data into the message queue to send the parsed configuration data to the data assembly engine through the message queue for data assembly; and / or, Obtaining the assembled message to be sent from the data assembly engine; Putting the assembled message to be sent into the message queue to send the encapsulated message to be sent to the data forwarding engine through the message queue for data forwarding.

[0066] As Figure 3 shown, Figure 3 It is a schematic structural diagram of a charging and swapping data distribution system of the present application.

[0067] Figure 4 Another flowchart of the charging and swapping data distribution method based on cloud service provided by the embodiment of the present application. As Figure 4 shown, another charging and swapping data distribution method based on cloud service provided by the embodiment of the present application is applied to the charging and swapping data distribution system, and specifically includes the following steps:

[0068] Step 401, configure the connection information between the charging and swapping enterprise terminal and the docking platform in the charging and swapping data distribution system, and configure the transmission information of the docking platform.

[0069] Among them, the transmission information includes the required charging and swapping data types and the push interface.

[0070] Step 402, in the case of triggering the distribution requirement, based on the required charging and swapping data types, obtain the corresponding data to be distributed in the distribution database, and assemble the message to be sent based on the connection information.

[0071] Step 403, distribute the message to be sent to the docking platform based on the push interface.

[0072] In an embodiment of the present application, configuring the connection information between the charging and swapping enterprise terminal and the docking platform in the charging and swapping data distribution system specifically includes: the charging and swapping enterprise terminal obtains the docking platform identifier and the docking platform key of the docking platform; among them, the docking platform identifier and the docking platform key are assigned when the docking platform registers in the charging and swapping data distribution system; based on the docking platform identifier and the docking platform key, apply for docking authentication; in the case of successful docking authentication, generate a message key and a signature key, and send the message key and the signature key to the charging and swapping enterprise terminal and the docking platform terminal for storage.

[0073] In an embodiment of the present application, configuring the transmission information of the docking platform specifically includes: determining the required charging and swapping data types of the docking platform, and determining the corresponding charging and swapping station id based on the required charging and swapping data types; configuring the push interface of the docking platform.

[0074] In an embodiment of the present application, configuring the push interface of the docking platform specifically includes: determining any HTTP(S) interface as the push interface to be configured, and configuring the URL of the push interface to be configured; specifying that the push interface to be configured uses the HTTP(S) / POST method to transmit parameters, and defining the data format of the message to be sent as JSON.

[0075] In one embodiment of the present application, before obtaining the corresponding data to be distributed in the distribution database based on the required charging and swapping data type, the method further includes: connecting to the corresponding charging and swapping station based on the charging and swapping station ID; obtaining the corresponding required charging and swapping data in the charging and swapping station based on the required charging and swapping data type, and sending the required charging and swapping data to the distribution database; performing standardization processing on the required charging and swapping data in the distribution database to obtain the corresponding data to be distributed.

[0076] In one embodiment of the present application, assembling the message to be sent based on the connection information specifically includes: constructing the message header of the message to be sent based on the preset message header definition rule; wherein, the message header includes: content type and authorization information; the content type includes data format and encoding method; constructing the message body of the message to be sent based on the data to be distributed, and encrypting the message body based on the message key to obtain the message body to be assembled; assembling the message header and the message body to be assembled to obtain the message to be signed; signing the message to be signed based on the signature key to obtain the message to be sent.

[0077] In one embodiment of the present application, signing the message to be signed based on the signature key to obtain the message to be sent specifically includes: determining the signature parameters; wherein, the signature parameters include: charging and swapping enterprise identifier, self-incrementing sequence; the self-incrementing sequence is used to represent the number of times the distribution requirement is triggered; performing a hash operation on the signature parameters based on the hash function preset at the charging and swapping enterprise side to generate a message digest; encrypting the message digest through the signature key to generate a digital signature; assembling the signature parameters, the digital signature and the message to be signed to obtain the message to be sent.

[0078] In one embodiment of the present application, after distributing the message to be sent to the docking platform based on the push interface, the method further includes: the docking platform performing a hash operation on the signature parameters in the message to be sent based on the preset hash function to generate a message digest to be compared; comparing the message digest with the message digest to be compared, and when it is determined that the message digest is the same as the message digest to be compared, encrypting the message body based on the message key to obtain the data to be distributed.

[0079] The above is the method embodiment proposed by the present application. Based on the same inventive concept, the embodiment of the present application also provides a cloud service-based charging and swapping data distribution system, and its structure is as Figure 2 shown.

[0080] Figure 2 FIG. is the internal structure schematic diagram of a cloud service-based charging and swapping data distribution system provided by the embodiment of the present application. As Figure 2 shown, the system 200 includes: a configuration module 201, an assembly module 202, and a distribution module 203;

[0081] A configuration module 201, configured to configure connection information between the charging and swapping enterprise side and the docking platform, and configure transmission information of the docking platform; wherein, the transmission information includes the required charging and swapping data types and push interfaces;

[0082] An assembly module 202, configured to, in case of a triggered distribution requirement, obtain data to be distributed from the database corresponding to the charging and swapping enterprise side based on the required charging and swapping data types, and assemble a message to be sent based on the connection information and the data to be distributed;

[0083] A distribution module 203, configured to distribute the message to be sent to the docking platform based on the push interface.

[0084] Some embodiments of the present application provide a non-volatile computer storage medium corresponding to Figure 1 for charging and swapping data distribution based on cloud services, storing computer-executable instructions, and the computer-executable instructions are set as:

[0085] Configure connection information between the charging and swapping enterprise side and the docking platform in the charging and swapping data distribution system, and configure transmission information of the docking platform; wherein, the transmission information includes the required charging and swapping data types and push interfaces;

[0086] In case of a triggered distribution requirement, obtain data to be distributed from the database corresponding to the charging and swapping enterprise side based on the required charging and swapping data types, and assemble a message to be sent based on the connection information and the data to be distributed;

[0087] Based on the push interface, distribute the message to be sent to the docking platform.

[0088] Each embodiment in the present application is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the embodiments of the Internet of Things devices and media, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments.

[0089] The systems and media provided by the embodiments of the present application correspond one-to-one with the methods. Therefore, the systems and media also have beneficial technical effects similar to those of the corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the systems and media are not repeated here.

[0090] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) that contain computer-usable program code.

[0091] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, as well as the combination of flows and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, such that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one or more flows and / or Figure 1 blocks or multiple blocks.

[0092] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, such that the instructions stored in the computer-readable memory generate a manufactured article including instruction means that implement the functions specified in Figure 1 one or more flows and / or Figure 1 blocks or multiple blocks.

[0093] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one or more flows and / or Figure 1 blocks or multiple blocks.

[0094] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0095] The memory may include non-permanent memory in the computer-readable medium, random access memory (RAM), and / or non-volatile memory in the form of, for example, read-only memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.

[0096] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0097] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0098] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A method for distributing charging and swapping data based on cloud services, characterized in that, Applied to a charging and swapping data distribution system, the method includes: Configuring the connection information between the charging and swapping enterprise terminal and the docking platform in the charging and swapping data distribution system, and configuring the transmission information of the docking platform; wherein, the transmission information includes the required charging and swapping data types and the push interface; In the case of triggering a distribution requirement, obtaining the data to be distributed from the database corresponding to the charging and swapping enterprise terminal based on the required charging and swapping data types, and assembling the message to be sent based on the connection information and the data to be distributed; Based on the push interface, distributing the message to be sent to the docking platform.

2. The method for distributing charging and swapping data based on cloud service according to claim 1, wherein Configuring the connection information between the charging and swapping enterprise terminal and the docking platform in the charging and swapping data distribution system specifically includes: Generating a message key and a signature key in the case of successful docking authentication between the charging and swapping enterprise terminal and the docking platform; Sending the message key and the signature key to the charging and swapping enterprise terminal and the docking platform terminal for storage; Preferably, the method further includes: Obtaining the docking platform identifier and the docking platform key of the docking platform; wherein, the docking platform identifier and the docking platform key are assigned when the docking platform registers in the charging and swapping data distribution system; Applying for docking authentication between the charging and swapping enterprise terminal and the docking platform based on the docking platform identifier and the docking platform key.

3. A method for distributing charging and swapping data based on cloud services according to claim 1, characterized in that, Configuring the transmission information of the docking platform specifically includes: Determining the required charging and swapping data types of the docking platform, and based on the required charging and swapping data types, determining the corresponding charging and swapping station id, where the required charging and swapping data types include charging and swapping data type information and charging and swapping station information; Configuring the push interface of the docking platform; Preferably, configuring the push interface of the docking platform specifically includes: Determining any HTTP(S) interface as the push interface to be configured, and configuring the URL of the push interface to be configured; Specifying that the push interface to be configured uses the HTTP(S) / POST method to transmit parameters, and defining the data format corresponding to the message to be sent as JSON.

4. A method for distributing charging and swapping data based on cloud services according to claim 3, characterized in that Before obtaining the corresponding data to be distributed in the distribution database based on the required charging and swapping data types, the method further includes: Connecting to the corresponding charging and swapping station based on the charging and swapping station id; Obtaining the required charging and swapping data in the charging and swapping station based on the required charging and swapping data types, and sending the required charging and swapping data to the distribution database; Performing standardization processing on the required charging and swapping data in the distribution database to obtain the corresponding data to be distributed.

5. A method for distributing charging and swapping data based on cloud services according to claim 1, characterized in that, The charging and swapping data distribution system includes a configuration parsing engine, a data assembly engine, and a data forwarding engine, and the method further includes: Obtaining the configuration information corresponding to the docking platform, where the configuration information includes the connection information and the transmission information; Putting the configuration information into the configuration parsing engine for parsing to obtain the parsed configuration data; Putting the parsed configuration data into the message queue to send the parsed configuration data to the data assembly engine through the message queue for data assembly; And / or Obtaining the assembled message to be sent from the data assembly engine; Put the assembled message to be sent into the message queue, and send the encapsulated message to be sent to the data forwarding engine through the message queue for data forwarding.

6. The method for distributing charging and swapping data based on cloud service according to claim 2, wherein, Assemble the message to be sent based on the connection information and the data to be distributed, specifically including: Construct the message header of the message to be sent based on the preset message header definition rules; Construct the message body of the message to be sent based on the data to be distributed, and encrypt the message body based on the message key to obtain the message body to be assembled; Assemble the message header and the message body to be assembled to obtain the message to be signed; Sign the message to be signed based on the signature key to obtain the message to be sent; Preferably, the message header includes: content type and authorization information. The content type is used to identify the encoding method of the message body in the request, and the authorization information is used to indicate the operation permissions of the docking platform.

7. A method for distributing charging and swapping data based on cloud services according to claim 6, characterized in that, Sign the message to be signed based on the signature key to obtain the message to be sent, specifically including: Determine the parameters to be signed; Perform a hash operation on the parameters to be signed based on the hash function preset on the charging and swapping enterprise side to generate a message digest; Encrypt the message digest with the signature key to generate a digital signature; Assemble the parameters to be signed, the digital signature and the message to be signed to obtain the message to be sent; Preferably, the parameters to be signed include at least one of the charging and swapping enterprise identifier and the increment sequence; the increment sequence is used to represent the triggering times of the distribution requirements.

8. A method for distributing charging and swapping data based on cloud services according to claim 7, characterized in that After distributing the message to be sent to the docking platform based on the push interface, the method further includes: The docking platform performs a hash operation on the parameters to be signed in the message to be sent based on the preset hash function to generate a message digest to be compared; Compare the message digest with the message digest to be compared, and when it is determined that the message digest is the same as the message digest to be compared, encrypt the message body based on the message key to obtain the data to be distributed.

9. A charging and swapping data distribution system based on cloud services, characterized in that, The system includes: a configuration module, an assembly module, and a distribution module; The configuration module is used to configure the connection information between the charging and swapping enterprise side and the docking platform, and configure the transmission information of the docking platform; wherein, the transmission information includes the required charging and swapping data types and push interfaces; The assembly module is used to obtain the data to be distributed from the database corresponding to the charging and swapping enterprise side based on the required charging and swapping data types when a distribution requirement is triggered, and assemble the message to be sent based on the connection information and the data to be distributed; The distribution module is used to distribute the message to be sent to the docking platform based on the push interface.

10. A non-volatile computer storage medium for charging and swapping data distribution based on cloud services, storing computer-executable instructions, characterized in that, The computer-executable instructions can implement a method for distributing charging and swapping data based on cloud services as described in any one of claims 1-8.

Images