Multi-platform docking method and equipment for battery replacement service data, electronic equipment and medium

Abstract

The embodiment of the invention discloses a multi-platform docking method and device for power conversion service data, electronic equipment and a medium, and relates to the technical field of data docking, and the method comprises the steps: obtaining a plurality of pieces of to-be-docked power conversion service data, and determining service data docking information of each piece of to-be-docked power conversion service data, the business data docking information comprises at least one docking platform; obtaining platform configuration information of each docking platform in a pre-created docking platform library through each piece of service data docking information; according to the platform configuration information of each docking platform, protocol screening is carried out in a pre-created docking protocol management library, and a current docking protocol of each docking platform is matched; and through the current docking protocol of each docking platform, controlling a platform communication state with the docking platform so as to realize multi-platform docking of the power conversion service data.

Description

[0001] This application claims priority from the invention patent application filed with the China National Patent Office on December 29, 2023, with the application number 2023118671086 and the invention title "A Multi-Platform Docking Method, Device, and Medium for Battery-Swap Service Data", and the entire text of the above-mentioned Chinese patent application is incorporated herein by reference. Technical Field

[0002] This specification relates to the technical field of data docking, and particularly to a multi-platform docking method, device, electronic device, and medium for battery-swap service data. Background Art

[0003] As the scale of the battery-swap business gradually expands and in coordination with the development of the battery-swap business in various regions, the digital center of an enterprise needs to quickly cooperate with IT departments such as local official regulatory platforms and partner enterprise platforms for the docking of battery-swap service data. In the battery-swap business, data docking is an important link. Currently, there is no standard protocol for the battery-swap business, and data docking is usually carried out based on the charging interface specifications in the existing charging business standard protocol, combined with the local battery-swap business operation design for revision to design the battery-swap protocol.

[0004] Since there are significant differences between the charging business logic and the battery-swap business logic, it is usually necessary to conduct customized development based on the content of the customer interface. That is to say, the existing data docking methods usually require customized development for each customer's needs, with a long development cycle and high development costs. At the same time, due to frequent changes in requirements, developers need to continuously modify the code to adapt to new requirements, further increasing the development costs and operation and maintenance difficulties. In addition, the existing data docking methods usually lack unified standards and specifications, resulting in difficulties in data docking between different platforms. When problems occur in the docking, it affects the efficiency of problem troubleshooting. In summary, the existing data docking can only conduct customized development based on the interface content, with a large development workload, frequent changes in requirements, high demand docking costs, and high operation and maintenance difficulties after delivery. Summary of the Invention

[0005] One or more embodiments of this specification provide a multi-platform docking method, device, electronic device, and medium for battery-swap service data to solve the following technical problems: The existing data docking can only conduct customized development based on the interface content, with a large development workload, frequent changes in requirements, high demand docking costs, and high operation and maintenance difficulties after delivery.

[0006] One or more embodiments of this specification adopt the following technical solutions:

[0007] One or more embodiments of this specification provide a multi-platform docking method for swapping power service data. The method includes: obtaining a plurality of to-be-docked swapping power service data, and determining service data docking information for each to-be-docked swapping power service data, where the service data docking information includes at least one docking platform; through each piece of service data docking information, obtaining platform configuration information of each docking platform in a pre-created docking platform library; according to the platform configuration information of each docking platform, performing protocol screening in a pre-created docking protocol management library to match the current docking protocol of each docking platform; through the current docking protocol of each docking platform, controlling the platform communication state with the docking platform to achieve multi-platform docking of swapping power service data.

[0008] Through the above technical solution, through the pre-created docking platform library and docking protocol management library, the configuration information and docking protocols of docking platforms can be uniformly managed and standardized, reducing the differences and complexities between different platforms, and improving the efficiency and accuracy of data docking; by using the correct docking protocol and encryption technology, the security and integrity of data during transmission can be ensured, preventing data from being tampered with or stolen, and enhancing the security of data; by uniformly managing and maintaining the docking platform library and docking protocol management library, the workload of manual configuration and adjustment for different platforms can be reduced, the maintenance cost can be lowered, and the work efficiency can be improved; by using standard docking protocols and protocol text formats, new docking platforms and business data types can be easily extended, enhancing the scalability of the system; by using the correct docking protocol and data standard, the accuracy and consistency of data can be ensured, improving the quality and accuracy of data.

[0009] Further, when the platform communication state with the docking platform is a connected state, based on the platform configuration information of each docking platform, encapsulating each to-be-docked swapping power service data to generate corresponding encapsulated swapping power service data; according to the platform configuration information of each docking platform, pushing each encapsulated swapping power service data.

[0010] Through the above technical solution, when the platform communication status with the docking platform is in a connected state, by encapsulating each piece of business data for battery swapping to be docked based on the platform configuration information of each docking platform and pushing it using the matching docking protocol, the data transmission path and method can be optimized, the delay and loss during data transmission can be reduced, the data transmission efficiency can be improved, the data format and content can be ensured to match the requirements of the docking platform, the data compatibility can be enhanced, and the information transmission errors or failures caused by data format mismatch can be reduced; the encapsulated business data for battery swapping is more concise and standardized, reducing the redundancy and errors during data transmission, thereby improving the efficiency and accuracy of data transmission; the encapsulation process can encrypt or hide sensitive data, enhancing the security of the data during transmission and preventing unauthorized access and tampering; due to the different configuration information of each docking platform, customized data pushing for different platforms can be achieved through encapsulation to meet the specific business needs of each platform; by ensuring the accurate and efficient transmission of data to each docking platform, a smoother and more convenient service experience can be provided for users, enhancing user satisfaction.

[0011] Further, determining the business data docking information of each piece of the business data for battery swapping to be docked specifically includes: determining the business event attribute in the business data attribute of each piece of the business data for battery swapping to be docked; based on the business event attribute of the business data for battery swapping to be docked, performing push permission matching in the pre-constructed platform push configuration table to determine at least one docking platform with push permission corresponding to each piece of the business data for battery swapping to be docked.

[0012] Through the above technical solution, by determining the business event attribute in the business data attribute of each piece of the business data for battery swapping to be docked and matching the push permission in the pre-constructed platform push configuration table, the docking platforms with push permission can be quickly determined, thus realizing fast and accurate data docking and improving the business processing efficiency; by determining the business data docking information of each piece of the business data for battery swapping to be docked, the accuracy and integrity of the data can be ensured, data loss or damage can be avoided, and at the same time, the leakage of important data can be avoided, enabling each platform to obtain what it needs, which is conducive to ensuring the security of enterprise business data.

[0013] Further, before obtaining the platform configuration information of each of the docking platforms in the pre-created docking platform library through each of the business data docking information, the method further includes: obtaining the platform information of multiple platforms to be docked, where the platform information includes any one or more of a platform identifier, platform operator information, platform type, platform protocol information, and push event information; based on the platform information of each of the platforms to be docked, configuring each of the platforms to be docked to generate the platform configuration information of each docking platform; according to the pre-obtained push rules for swapping power business data, configuring the push information of each docking platform to construct a platform push configuration table, where the platform push configuration table includes multiple docking platforms and the push data event attributes corresponding to each docking platform; creating a docking platform library through the platform configuration information of each docking platform and the platform push configuration table.

[0014] Through the above technical solution, by obtaining the platform information of multiple platforms to be docked and configuring it to generate the platform configuration information of each docking platform, unified management and configuration of the docking platforms can be achieved, and configuration and management problems caused by differences between different platforms can be avoided; according to the pre-obtained push rules for swapping power business data, configuring the push information of each docking platform can construct a flexible platform push configuration table, which can adapt to different business requirements and data structures, and achieve flexible management and push of data; through the platform configuration information of each docking platform and the platform push configuration table, automated data push can be realized.

[0015] Further, based on the platform configuration information of each docking platform, encapsulating each of the to-be-docked swapping power business data to generate corresponding encapsulated swapping power business data, specifically including: determining the platform configuration information of each docking platform, where the platform configuration information includes the platform docking protocol and platform docking data standard of the docking platform; based on the platform configuration information of each docking platform, establishing a data standard mapping relationship between each of the to-be-docked swapping power business data and at least one platform docking data standard; encapsulating each of the to-be-docked swapping power business data according to the data standard mapping relationship between each of the to-be-docked swapping power business data and at least one platform docking data standard to generate the encapsulated swapping power business data corresponding to each docking platform.

[0016] Through the above technical solutions, by determining the platform configuration information of each docking platform, including the platform docking protocol and the platform docking data standard, it is possible to ensure data compatibility between different platforms, making it simpler and more efficient to transfer and exchange data between different platforms, and reducing the possibility of data conversion and conversion errors; by establishing a data standard mapping relationship between each piece of battery swapping service data to be docked and at least one platform docking data standard, it is possible to standardize and normalize the data to ensure the accuracy and consistency of the data, improve the readability and understandability of the data, and provide a more reliable basis for subsequent data analysis and decision-making; by encapsulating the battery swapping service data to be docked and generating the encapsulated battery swapping service data corresponding to each docking platform, the data processing efficiency can be greatly improved; the encapsulated data can be directly transmitted to the docking platform without additional format conversion and processing, reducing intermediate links and data processing time, and improving the data processing efficiency; by encapsulating the battery swapping service data, the data can be encrypted, backed up, and protected, thereby enhancing the security of the data, preventing data leakage, tampering, and damage, and ensuring the security of enterprise data.

[0017] Further, according to the platform configuration information of each of the docking platforms, push each of the encapsulated battery swapping service data, which specifically includes: according to the platform configuration information of each of the docking platforms, determine the operator processor corresponding to each of the docking platforms to determine the operator configuration information of each of the docking platforms; through each of the operator configuration information, push each of the encapsulated battery swapping service data according to the current docking protocol of each of the docking platforms.

[0018] Through the above technical solutions, through the corresponding operator processor and docking protocol, it is possible to ensure that data is transmitted in the most efficient manner, reduce delays and losses during data transmission, and improve the efficiency of data transmission; by uniformly managing and maintaining the docking protocol management library, it is possible to reduce the workload of manually configuring and adjusting different platforms, reduce the maintenance cost, and improve the work efficiency.

[0019] Further, after creating the docking platform library, the method further includes: monitoring the communication status of multiple docking platforms in the docking platform library, and obtaining the current communication status of each docking platform; through the current communication status of each docking platform, conduct interface problem troubleshooting.

[0020] Through the above technical solution, by monitoring the communication status of the docking platform in real time, connection problems can be discovered and solved in a timely manner, data loss or transmission delay caused by communication interruption can be avoided, the stability and reliability of data transmission can be improved, the accuracy and integrity of data can be ensured, and the reason for communication interruption can be quickly located through monitoring, and corresponding measures can be taken in a timely manner for repair, shortening the time for problem solving, reducing the impact on the business, and improving the availability and reliability of the system.

[0021] Further, before screening protocols in the pre-created docking protocol management library according to the platform configuration information of each said docking platform and matching the current docking protocol of each said docking platform, the method further includes: defining a plurality of docking protocols, generating the protocol text format of each said docking protocol, wherein the protocol text format includes the header information, message body and message end identifier of the protocol; creating a docking protocol management library according to the protocol text format of each said docking protocol.

[0022] Through the above technical solution, by defining a plurality of docking protocols and generating the corresponding protocol text formats, the standardization and normalization of data docking can be achieved, ensuring that data transmission and exchange between different platforms follow unified standards and specifications; by using the docking protocol management library, the corresponding docking protocols can be quickly searched and obtained, avoiding the cumbersome process of manual configuration and search; at the same time, using the standard protocol text format for data encapsulation can reduce errors in data conversion and format conversion, improving the accuracy and efficiency of data transmission; the creation of the docking protocol management library provides flexibility for business growth and system upgrade. When new docking protocols need to be defined or existing docking protocols need to be updated, they can be conveniently added or modified without large-scale adjustment of the entire system; by using standard docking protocols and protocol text formats for data encapsulation, data can be encrypted, backed up and protected, thereby enhancing data security; by creating a docking protocol management library, unified management and maintenance of docking protocols can be realized, reducing the maintenance cost, reducing repetitive labor, and improving work efficiency.

[0023] Further, before matching the push permissions in the pre-constructed platform push configuration table, the method further includes: obtaining a plurality of event attributes of the current platform and the data push rules corresponding to each event attribute; performing push configuration on the platform basic data according to the data push rules corresponding to each event attribute, generating event push configuration information corresponding to each said platform basic data, wherein the event push configuration information includes the request interface information of the platform basic data, the event attribute type corresponding to the platform basic data, and the data push platform corresponding to the platform basic data; constructing a platform push configuration table through each said event push configuration information.

[0024] Through the above technical solution, the platform push configuration table can clearly display information such as the event attribute type, request interface information, and data push platform of each platform's basic data, which helps to better understand and track data during the data management and push process, improving the efficiency and accuracy of data management and push. According to the information in the platform push configuration table, the push target platform for data push can be automatically matched, which avoids the cumbersome and error-prone manual configuration and improves the data security of various battery swapping data.

[0025] One or more embodiments of this specification provide a multi-platform docking device for battery swapping service data. The device includes: an acquisition module, configured to acquire a plurality of battery swapping service data to be docked and determine the service data docking information of each battery swapping service data to be docked, where the service data docking information includes at least one docking platform; a configuration module, configured to obtain the platform configuration information of each docking platform in a pre-created docking platform library through each service data docking information; a protocol module, configured to perform protocol screening in a pre-created docking protocol management library according to the platform configuration information of each docking platform to match the current docking protocol of each docking platform; a docking module, configured to control the platform communication state between the battery swapping service data to be docked and the docking platform through the current docking protocol of each docking platform to achieve multi-platform docking of battery swapping service data.

[0026] One or more embodiments of this specification provide an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements the multi-platform docking method for battery swapping service data as described in any one of the above.

[0027] One or more embodiments of this specification provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the multi-platform docking method for battery swapping service data as described in any one of the above.

[0028] The above at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects: Through the above technical solutions, by means of the pre-created docking platform library and docking protocol management library, the configuration information and docking protocols of the docking platform can be uniformly managed and standardized, reducing the differences and complexities between different platforms, and improving the efficiency and accuracy of data docking; By using the correct docking protocol and encryption technology, the security and integrity of data during transmission can be ensured, preventing data from being tampered with or stolen, and enhancing data security; By uniformly managing and maintaining the docking platform library and docking protocol management library, the workload of manually configuring and adjusting different platforms can be reduced, the maintenance cost can be lowered, and the work efficiency can be improved; By using standard docking protocols and protocol text formats, new docking platforms and business data types can be easily extended, enhancing the scalability of the system; By using the correct docking protocol and data standard, the accuracy and consistency of data can be ensured, improving the quality and accuracy of data. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments recorded in this specification. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings. In the drawings:

[0030] Figure 1 It is a schematic flowchart of a multi-platform docking method for battery swapping service data provided by the embodiments of this specification;

[0031] Figure 2 It is a schematic structural diagram of an electronic device provided by the embodiments of this specification. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0032] In order to enable those skilled in the art to better understand the technical solutions in this specification, the following will clearly and completely describe the technical solutions in the embodiments of this specification with reference to the drawings in the embodiments of this specification. Obviously, the described embodiments are only some embodiments of this specification, rather than all embodiments. Based on the embodiments of this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of this specification.

[0033] As the scale of the battery swapping service gradually expands and in coordination with the implementation of the battery swapping service in various regions, the enterprise's digital center needs to quickly cooperate with the IT departments of official regulatory platforms and partner enterprise platforms in each region for data docking of the battery swapping service. In the battery swapping service, data docking is an important link. Currently, there is no standard protocol for the battery swapping service. The data docking is usually based on the charging interface specifications in the existing charging service standard protocol and is revised in combination with the local battery swapping service operation design for the battery swapping protocol design.

[0034] Due to the significant differences between the charging service logic and the battery swapping service logic, it is usually necessary to develop specifically according to the content of the customer interface. That is to say, the existing data docking methods usually require customized development for the needs of each customer, with a long development cycle and high development costs. At the same time, due to frequent changes in requirements, developers need to continuously modify the code to adapt to new requirements, further increasing the development costs and operation and maintenance difficulties. In addition, the existing data docking methods usually lack unified standards and specifications, resulting in difficulties in data docking between different platforms. When problems occur in the docking, it affects the efficiency of problem troubleshooting. In summary, the existing data docking can only be developed specifically according to the interface content, with a large development workload, frequent changes in requirements, high demand docking costs, and great operation and maintenance difficulties after delivery.

[0035] The embodiments of this specification provide a multi-platform docking method for battery swapping service data. It should be noted that the execution subject in the embodiments of this specification can be a platform server or any device with data processing capabilities. Figure 1 The following is a schematic flowchart of a multi-platform docking method for battery swapping service data provided by the embodiments of this specification, as Figure 1 shown, mainly including the following steps:

[0036] Step S101: Obtain multiple pieces of battery swapping service data to be docked and determine the service data docking information for each piece of battery swapping service data to be docked.

[0037] In an embodiment of this specification, the embodiments of this specification can be implemented through a forwarding platform. Through the forwarding platform and the enterprise server, multiple pieces of battery swapping service data to be docked are obtained. Here, the battery swapping service data includes the station-side data of the battery swapping station and the battery swapping vehicle data. And determine the service data docking information for each piece of battery swapping service data to be docked. Among them, the service data docking information includes at least one docking platform. Here, the docking platform can be an official regulatory platform or the enterprise platform of a partner enterprise.

[0038] Through the above technical solutions, by obtaining multiple data for the battery swapping service to be docked and determining the service data docking information for each data, the data docking work can be completed quickly and accurately, reducing manual operations and errors, and improving the service processing efficiency; by obtaining multiple data for the battery swapping service to be docked, the collaborative work between different service systems can be promoted.

[0039] Determining the service data docking information for each of the data for the battery swapping service to be docked specifically includes: determining the service event attribute in the service data attribute of each of the data for the battery swapping service to be docked; according to the service event attribute of the data for the battery swapping service to be docked, performing push permission matching in the pre-constructed platform push configuration table to determine at least one docking platform with push permission corresponding to each of the data for the battery swapping service to be docked.

[0040] In an embodiment of the present specification, obtaining the data for the battery swapping service to be docked includes the service event attribute in the service data attribute. These data can be obtained from different sources, such as databases, files, API interfaces, etc. For each data for the battery swapping service to be docked, its service event attribute is identified. The service event attribute here can refer to specific events or operations related to the battery swapping service, such as battery swapping requests, battery swapping completions, fault reports, etc., and the service event attribute can also be set according to the data source of the battery swapping data, such as battery pack data, battery swapping station data, etc. A platform push configuration table is pre-constructed, and this table contains the corresponding relationships between different platforms and different service event attributes. The platform here is the platform in the docking platform library, and the configuration table can be customized according to actual needs. For example, it can include information such as the name of the platform, push permission, push method, etc. According to the service event attribute of the data for the battery swapping service to be docked, the corresponding platform with push permission is searched for in the platform push configuration table. If a matching platform is found, it means that such data can be sent to this platform, that is, this platform can receive and process these data for the battery swapping service to be docked.

[0041] Through the above technical solutions, by determining the service event attribute in the service data attribute of each data for the battery swapping service to be docked and matching the push permission in the pre-constructed platform push configuration table, the docking platform with push permission can be quickly determined, thereby achieving fast and accurate data docking and improving the service processing efficiency; by determining the service data docking information for each data for the battery swapping service to be docked, the accuracy and integrity of the data can be ensured, data loss or damage can be avoided, and at the same time, the leakage of important data can be avoided, enabling each platform to obtain what it needs, which is conducive to ensuring the security of the enterprise's service data.

[0042] Before performing push permission matching in the pre-constructed platform push configuration table, the method further includes: obtaining multiple event attributes of the current platform and the data push rules corresponding to each event attribute; according to the data push rules corresponding to each event attribute, performing push configuration on the platform basic data to generate event push configuration information corresponding to each piece of the platform basic data, where the event push configuration information includes the request interface information of the platform basic data, the event attribute type corresponding to the platform basic data, and the data push platform corresponding to the platform basic data; constructing a platform push configuration table through each piece of the event push configuration information.

[0043] In one embodiment of the present specification, there are two ways to construct the platform push configuration table. The first way is as follows: First, obtain multiple event attributes of the current platform and the data push rules corresponding to each event attribute. The event attributes here refer to the event attributes of all battery swapping data (also known as platform basic data) of the battery swapping enterprise, and the data push rules corresponding to each event attribute refer to which platforms this event attribute can be pushed to. According to the data push rules corresponding to each event attribute, perform push configuration on the platform basic data to generate event push configuration information corresponding to each piece of the platform basic data. The event push configuration information includes the request interface information of the platform basic data, that is, how this platform basic data is obtained, and also includes the event attribute type corresponding to the platform basic data, that is, the event attribute type to which this platform basic data belongs, and also includes the data push platform corresponding to the platform basic data, that is, the platform to which such data can be pushed. Construct a platform push configuration table through each piece of the event push configuration information.

[0044] Through the above technical solution, the platform push configuration table can clearly display information such as the event attribute type, request interface information, and data push platform of each piece of the platform basic data, which helps to better understand and track data during the data management and push process, and improves the efficiency and accuracy of data management and push. According to the information in the platform push configuration table, the push target platform for data push can be automatically matched, which avoids the tediousness and error-proneness of manual configuration and improves the data security of various battery swapping data.

[0045] Step S102, through each business data docking information, obtain the platform configuration information of each docking platform in the pre-created docking platform library.

[0046] Before obtaining the platform configuration information of each of these docking platforms in the pre-created docking platform library through each of these business data docking information, the method further includes: obtaining the platform information of multiple platforms to be docked, where the platform information includes any one or more of platform identifier, platform operator information, platform type, platform protocol information, and push event information; configuring each of these platforms to be docked based on the platform information of each of these platforms to be docked, generating the platform configuration information of each docking platform; configuring the push information of each of these docking platforms according to the pre-obtained push rules for battery swapping service data, constructing a platform push configuration table, where the platform push configuration table includes multiple docking platforms and the push data event attributes corresponding to each docking platform; creating a docking platform library through the platform configuration information of each of these docking platforms and this platform push configuration table.

[0047] In one embodiment of this specification, the construction of the platform push configuration table can also be achieved by constructing a docking platform library. Obtain the platform information of multiple platforms to be docked, where the platform information includes any one or more of platform identifier, platform operator information, platform type, platform protocol information, and push event information, and specifically may include information such as operator platform name, operator ID, operator external ID, platform type, protocol selection, region selection, protocol type, initialization vector, key, query token party civilization, retry count, request URL, message key key, signature key, etc. Configure each of these platforms to be docked according to the above platform information of each of these platforms to be docked, generating the platform configuration information of each docking platform. Configure the push information of each docking platform according to the pre-obtained push rules for battery swapping service data to construct a platform push configuration table, where the platform push configuration table includes multiple docking platforms and the push data event attributes corresponding to each docking platform; create a docking platform library through the platform configuration information of each docking platform and this platform push configuration table.

[0048] Through the above technical solutions, by obtaining the platform information of multiple platforms to be docked and configuring them to generate the platform configuration information of each docking platform, unified management and configuration of the docking platforms can be realized, and configuration and management problems caused by differences between different platforms can be avoided; by configuring the push information of each docking platform according to the pre-obtained push rules for battery swapping service data, a flexible platform push configuration table can be constructed, which can adapt to different business requirements and data structures, realizing flexible management and pushing of data; through the platform configuration information of each docking platform and this platform push configuration table, automated data pushing can be realized.

[0049] In one embodiment of the present specification, through at least one docking platform in each business data docking information, in the pre-created docking platform library, the platform configuration information of each docking platform can be obtained in the form of a platform identifier. By means of the pre-created docking platform library and the platform configuration information, the data docking process can be simplified. There is no need to manually configure the parameters and information of each docking platform. Only the corresponding platform configuration information can be obtained through the platform identifier, so as to quickly and accurately complete the data docking work.

[0050] After creating the docking platform library, the method further includes: monitoring the communication status of multiple docking platforms in the docking platform library, obtaining the current communication status of each docking platform; and troubleshooting interface problems based on the current communication status of each docking platform.

[0051] In one embodiment of the present specification, a professional monitoring tool or service is used to monitor the communication status of multiple docking platforms in the docking platform library. It should be noted that the communication status here refers to the communication connection status between the docking platform and the enterprise platform. The current communication status of each docking platform is obtained, and the current communication status includes a connected state and a disconnected state. The connected state indicates that the connection between the docking platform and the enterprise platform is active and data transmission is normal; the disconnected state indicates that the connection between the docking platform and the enterprise platform is interrupted and data transmission stops. Interface problems are troubleshot based on the current communication status of each docking platform. When the communication status of a certain docking platform shows a disconnected state, interface problem troubleshooting is required. Check the relevant logs and error messages to determine that the reason for the disconnection may be a network problem, a server problem, a configuration problem, or other reasons. According to the troubleshooting results, corresponding measures are taken for repair, such as restarting the service, adjusting configuration parameters, contacting the administrator, etc.

[0052] Through the above technical solution, by monitoring the communication status of the docking platform in real time, connection problems can be discovered and solved in a timely manner, avoiding data loss or transmission delay caused by communication interruption, improving the stability and reliability of data transmission, ensuring the accuracy and integrity of data. Through monitoring, the reason for the communication interruption can be quickly located, and corresponding measures can be taken for repair in a timely manner, shortening the time to solve the problem, reducing the impact on the business, and improving the availability and reliability of the system.

[0053] Step S103, according to the platform configuration information of each docking platform, perform protocol screening in the pre-created docking protocol management library to match the current docking protocol of each docking platform.

[0054] Before screening protocols in the pre-created docking protocol management library according to the platform configuration information of each such docking platform and matching the current docking protocol of each such docking platform, the method further includes: defining a plurality of docking protocols, generating the protocol text format of each such docking protocol, where the protocol text format includes the header information, message body, and message end identifier of the protocol; creating a docking protocol management library according to the protocol text format of each such docking protocol.

[0055] In an embodiment of the present specification, determine the protocol types to be docked, such as HTTP, HTTPS, TCP, UDP, etc. For each protocol, define its header information, message body, and message end identifier. The header information should include information such as the protocol version, message type, and message length. The message body should include specific business data, and the message end identifier is used to identify the end of the message. According to the defined docking protocols, generate the protocol text format of each docking protocol, including combining the header information, message body, and message end identifier in a specified format to form a complete protocol text, ensuring that the generated protocol text format meets the requirements of the docking protocol and is easy to read and understand. Create a dedicated docking protocol management library for storing and managing all defined docking protocols. In the management library, create an entry for each docking protocol, including information such as the protocol name, version, and protocol text format. Interfaces or tools can also be provided to quickly search for and obtain the corresponding docking protocol when needed.

[0056] As business requirements change and docking platforms develop, the docking protocols may change. Therefore, it is necessary to regularly update and maintain the docking protocol management library. When a new docking protocol needs to be defined, define it according to the above steps and add it to the management library. When an existing docking protocol needs to be modified or updated, timely update the corresponding protocol text format and the entry in the management library. When performing data docking, select the corresponding docking protocol as needed and obtain the corresponding protocol text format from the docking protocol management library. When encapsulating the business data to be docked for battery swapping, use the protocol text format of the selected docking protocol for encapsulation. For the docking protocols that have been used, monitor and maintain them regularly to ensure their normal operation and correct data transmission.

[0057] Through the above technical solution, by defining multiple docking protocols and generating corresponding protocol text formats, the standardization and normalization of data docking can be achieved, ensuring that data transmission and exchange between different platforms follow unified standards and specifications; by using a docking protocol management library, the corresponding docking protocols can be quickly searched and obtained, avoiding the cumbersome process of manual configuration and search; at the same time, using a standard protocol text format for data encapsulation can reduce errors in data conversion and format conversion, improving the accuracy and efficiency of data transmission; the creation of the docking protocol management library provides flexibility for business growth and system upgrade. When new docking protocols need to be defined or existing docking protocols need to be updated, they can be conveniently added or modified without large-scale adjustment of the entire system; by using standard docking protocols and protocol text formats for data encapsulation, data can be encrypted, backed up, and protected, thus enhancing data security; by creating a docking protocol management library, unified management and maintenance of docking protocols can be achieved, reducing maintenance costs, reducing repetitive labor, and improving work efficiency.

[0058] In an embodiment of this specification, for each docking platform, a docking protocol matching the platform configuration information is screened in the docking protocol management library. Matching can be performed according to information such as the docking protocol and data standard of the platform to determine the docking protocol for each docking platform.

[0059] Step S104, through the current docking protocol of each docking platform, control the platform communication status with the docking platform to achieve multi-platform docking of battery swapping service data.

[0060] The method further includes: when the platform communication status with the docking platform is in a connected state, based on the platform configuration information of each such docking platform, encapsulate each piece of battery swapping service data to be docked to generate corresponding encapsulated battery swapping service data; push each piece of encapsulated battery swapping service data according to the platform configuration information of each such docking platform.

[0061] In one embodiment of the present specification, when the platform communication status with the docking platform is in a connected state, according to the platform configuration information of each docking platform and in accordance with the data standard of each docking platform, each piece of undocked battery swapping service data is encapsulated to generate corresponding encapsulated battery swapping service data. According to the platform configuration information of each docking platform, each piece of the encapsulated battery swapping service data is pushed. By encapsulating each piece of undocked battery swapping service data in accordance with the data standard of each docking platform, the standardization and normalization of data can be ensured, which helps to improve the consistency and readability of data; by encapsulating the battery swapping service data, the data can be cleaned, verified, and standardized, thereby improving the quality and accuracy of the data and avoiding subsequent business problems caused by data quality issues; in addition, by encapsulating the battery swapping service data, the data can be encrypted, backed up, and protected, thereby enhancing the security of the data, preventing data leakage, tampering, and damage, and ensuring the integrity and confidentiality of the data.

[0062] Based on the platform configuration information of each docking platform, each piece of undocked battery swapping service data is encapsulated to generate corresponding encapsulated battery swapping service data, which specifically includes: determining the platform configuration information of each docking platform, where the platform configuration information includes the platform docking protocol and the platform docking data standard of the docking platform; based on the platform configuration information of each docking platform, establishing a data standard mapping relationship between each piece of undocked battery swapping service data and at least one platform docking data standard; and encapsulating each piece of undocked battery swapping service data in accordance with the data standard mapping relationship between each piece of undocked battery swapping service data and at least one platform docking data standard to generate the encapsulated battery swapping service data corresponding to each docking platform.

[0063] In one embodiment of the present specification, the platform docking protocol and the platform docking data standard in the platform configuration information of each docking platform are obtained. The service data docking information of each piece of undocked battery swapping service data includes at least one docking platform. According to the platform configuration information of the docking platform, at least one data standard of each piece of undocked battery swapping service data is determined, and for each piece of undocked battery swapping service data, a data standard mapping relationship with the platform docking data standard is established. The data standard mapping relationship can be a one-to-one or one-to-many relationship, specifically depending on the business requirements and platform docking requirements. Each piece of undocked battery swapping service data is encapsulated in accordance with the data standard mapping relationship between each piece of undocked battery swapping service data and at least one platform docking data standard to generate the encapsulated battery swapping service data corresponding to each docking platform. The encapsulation process includes format conversion, data cleaning, verification, and standardization processing of the undocked battery swapping service data in accordance with the platform docking data standard. The encapsulated data should meet the requirements of the platform docking protocol and data standard so as to be correctly transmitted and parsed.

[0064] In one embodiment of this specification, the encapsulation timing process is as follows: First, through the method entry, obtain the platforms to which this message needs to be pushed, and determine the platform identification ID. Obtain the configuration information of the platform based on the platform ID, so as to obtain the configured JSON data through the configuration information of the platform. According to the configuration information of the platform, obtain specific JSON data. These data are usually dynamically generated and will vary according to the needs of the platform. After that, encapsulate the data through reflection, encapsulate it into a Map instead of a DTO, and choose to use Map (a collection of key-value pairs) as the structure for data transmission, rather than specifically defining a DTO class. Obtain the values in the battery swapping record DTO and return them. Through reflection, extract the required field values from the battery swapping record DTO and store them as key-value pairs in the Map. Execute cross-message value acquisition, obtain values from multiple different messages or packets, traverse these packets to extract the required data, and add it to the Map. Process the data format according to the configuration information of the platform, obtain the data type format configuration of each field in Redis, obtain the data type processor. The data types here include integers, decimals, strings, and dates. Use the template method to return the specific implementations of each subclass. According to the data type configuration in Redis, use the corresponding processors (such as integer processors, decimal processors, etc.) to process the data in the Map. After processing, convert the processed Map into JSON format, usually using libraries such as Jackson or Gson to complete. Finally, the JSON data can be pushed to the target platform.

[0065] Through the above technical solutions, by determining the platform configuration information of each docking platform, including the platform docking protocol and the platform docking data standard, it is possible to ensure data compatibility between different platforms, making the transmission and exchange of data between different platforms simpler and more efficient, and reducing the possibility of data conversion and conversion errors; by establishing a data standard mapping relationship between each battery swapping service data to be docked and at least one platform docking data standard, it is possible to standardize and normalize the data to ensure the accuracy and consistency of the data, improve the readability and comprehensibility of the data, and provide a more reliable basis for subsequent data analysis and decision-making; by encapsulating the battery swapping service data to be docked and generating the encapsulated battery swapping service data corresponding to each docking platform, the data processing efficiency can be greatly improved; the encapsulated data can be directly transmitted to the docking platform without additional format conversion and processing, reducing intermediate links and data processing time, and improving the data processing efficiency; by encapsulating the battery swapping service data, the data can be encrypted, backed up, and protected, thereby enhancing the security of the data, preventing data leakage, tampering, and damage, and ensuring the security of enterprise data.

[0066] Push each piece of encapsulated battery swapping service data according to the platform configuration information of each docking platform, specifically including: determine the operator processor corresponding to each docking platform according to the platform configuration information of each docking platform to determine the operator configuration information of each docking platform; push each piece of encapsulated battery swapping service data according to each operator configuration information and the current docking protocol of each docking platform.

[0067] In an embodiment of the present specification, determining the operator processor corresponding to each docking platform according to the platform configuration information of each docking platform to determine the operator configuration information of each docking platform includes, but is not limited to, processor model, communication protocol, port number, data transmission rate, etc. Push each piece of encapsulated battery swapping service data according to the current docking protocol and operator configuration information of each docking platform. Monitor the pushing process to ensure that the data can be correctly transmitted to the docking platform. Optimize and adjust the pushing process according to business requirements and platform docking requirements to improve the efficiency and accuracy of data transmission.

[0068] In an embodiment of the present specification, execute the send message logic. First, obtain the operator processor and return the configuration information of the operator processor. Then obtain the send request processor and return it. Execute an HTTP request through the configuration information of the send request processor and the operator processor and return the request result. Obtain the request result processor and return the result processor. Process the request result through the result processor and return whether the request result is successful. When the returned result is a failure, determine that the data push fails, and trigger a re-push event when determining that the data push fails.

[0069] Through the above technical solutions, through the corresponding operator processor and docking protocol, it can ensure that data is transmitted in the most efficient way, reduce the delay and loss in the data transmission process, and improve the efficiency of data transmission; by uniformly managing and maintaining the docking protocol management library, it can reduce the workload of manual configuration and adjustment for different platforms, reduce the maintenance cost, and improve the work efficiency.

[0070] The above at least one technical solution adopted in the embodiments of this specification can achieve the following beneficial effects: Through the above technical solutions, by means of the pre-created docking platform library and docking protocol management library, the configuration information and docking protocols of the docking platforms can be uniformly managed and standardized, reducing the differences and complexities between different platforms, and improving the efficiency and accuracy of data docking; By encapsulating each piece of battery swapping service data to be docked based on the platform configuration information of each docking platform and pushing it using the matching docking protocol, the data transmission path and method can be optimized, reducing delays and losses during data transmission and improving the efficiency of data transmission; By using the correct docking protocol and encryption technology, the security and integrity of data during transmission can be ensured, preventing data from being tampered with or stolen, and enhancing data security; By uniformly managing and maintaining the docking platform library and docking protocol management library, the workload of manually configuring and adjusting different platforms can be reduced, the maintenance cost can be lowered, and the work efficiency can be improved; By using standard docking protocols and protocol text formats, new docking platforms and business data types can be easily extended, enhancing the scalability of the system; By using the correct docking protocol and data standard, the accuracy and consistency of data can be ensured, improving the quality and accuracy of data.

[0071] One or more embodiments of this specification provide a multi-platform docking device for battery swapping service data. The device includes: an acquisition module, configured to acquire multiple pieces of battery swapping service data to be docked and determine the service data docking information of each piece of the battery swapping service data to be docked, where the service data docking information includes at least one docking platform; a configuration module, configured to obtain the platform configuration information of each docking platform in the pre-created docking platform library through each piece of the service data docking information; a protocol module, configured to perform protocol screening in the pre-created docking protocol management library according to the platform configuration information of each docking platform and match the current docking protocol of each docking platform; a docking module, configured to control the platform communication state between the battery swapping service data to be docked and the docking platform through the current docking protocol of each docking platform, so as to achieve multi-platform docking of battery swapping service data.

[0072] One or more embodiments of this specification provide an electronic device Figure 2 which is a schematic structural diagram of an electronic device provided for the embodiments of this specification. As Figure 2 shown, it includes a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, it implements the multi-platform docking method for battery swapping service data in any of the above embodiments.

[0073] One or more embodiments of the present specification provide a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the multi-platform docking method for battery replacement service data in any of the above embodiments.

[0074] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. The key point of each embodiment is to illustrate the differences from other embodiments. In particular, for the embodiments of the device, equipment, and non-volatile computer storage medium, 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.

[0075] The above describes specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be executed in a different order from that in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In certain embodiments, multi-tasking and parallel processing are also possible or may be advantageous.

[0076] The devices and media provided by the embodiments of this specification correspond one-to-one with the methods. Therefore, the devices and media also have beneficial technical effects similar to those of their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be elaborated here.

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

[0078] This specification is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of this specification. 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, so that the instructions executed by the processor of the computer or other programmable data processing devices generate for implementing in the process Figure 1 one process or multiple processes and / or blocksFigure 1 a device for the functions specified in one or more boxes

[0079] 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 produce a manufactured article including an instruction device that implements the functions specified in one Figure 1 one process or more processes and / or boxes Figure 1 a box or more boxes

[0080] 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 produce a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one Figure 1 one process or more processes and / or boxes Figure 1 a box or more boxes

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

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

[0083] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can store information by any method or technology. The 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassette tapes, magnetic disk storage, or other magnetic storage devices, or any other non-transmission media that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0084] It should also be noted that the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, such that a process, method, article or apparatus that includes a series of elements not only includes those elements but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or apparatus. Without further limitation, an element defined by the phrase "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0085] The above description is only for one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, various changes and modifications can be made to one or more embodiments of this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of one or more embodiments of this specification shall be included within the scope of the claims of this specification.

Claims

1. A multi-platform docking method for battery swapping service data, characterized in that The method includes: Obtaining a plurality of to-be-docked battery swapping service data, and determining service data docking information for each to-be-docked battery swapping service data, where the service data docking information includes at least one docking platform; Through each service data docking information, obtaining platform configuration information of each docking platform in a pre-created docking platform library; According to the platform configuration information of each docking platform, performing protocol screening in a pre-created docking protocol management library to match the current docking protocol of each docking platform; Controlling the platform communication status with each docking platform through the current docking protocol of each docking platform to achieve multi-platform docking of battery swapping service data.

2. The multi-platform docking method for battery swapping service data according to claim 1, wherein, The method further includes: When the platform communication status with the docking platform is a connected state, encapsulating each to-be-docked battery swapping service data based on the platform configuration information of each docking platform to generate corresponding encapsulated battery swapping service data; Pushing each encapsulated battery swapping service data according to the platform configuration information of each docking platform.

3. The multi-platform docking method for battery swapping service data according to claim 1, wherein Determining the service data docking information for each to-be-docked battery swapping service data specifically includes: Determining the service event attribute in the service data attribute of each to-be-docked battery swapping service data; Performing push permission matching in a pre-constructed platform push configuration table according to the service event attribute of the to-be-docked battery swapping service data to determine at least one docking platform with push permission corresponding to each to-be-docked battery swapping service data.

4. A multi-platform docking method for battery swapping service data according to claim 1, characterized in that, Before obtaining the platform configuration information of each docking platform in a pre-created docking platform library through each service data docking information, the method further includes: Obtaining platform information of a plurality of to-be-docked platforms, where the platform information includes any one or more of platform identification, platform operator information, platform type, platform protocol information, and push event information; Configuring each to-be-docked platform based on the platform information of each to-be-docked platform to generate platform configuration information of each docking platform; Configuring the push information of each docking platform according to a pre-obtained battery swapping service data push rule, and constructing a platform push configuration table, where the platform push configuration table includes a plurality of docking platforms and push data event attributes corresponding to each docking platform; Creating a docking platform library through the platform configuration information of each docking platform and the platform push configuration table.

5. The multi-platform docking method for battery swapping service data according to claim 2, wherein Encapsulating each to-be-docked battery swapping service data based on the platform configuration information of each docking platform to generate corresponding encapsulated battery swapping service data specifically includes: Determining the platform configuration information of each docking platform, where the platform configuration information includes the platform docking protocol and platform docking data standard of the docking platform; Establishing a data standard mapping relationship between each to-be-docked battery swapping service data and at least one platform docking data standard based on the platform configuration information of each docking platform; Encapsulate each of the to-be-docked battery swapping service data according to the data standard mapping relationship between each of the to-be-docked battery swapping service data and at least one platform docking data standard, so as to generate the encapsulated battery swapping service data corresponding to each docking platform.

6. A multi-platform docking method for battery swapping service data according to claim 2, characterized in that Push each of the encapsulated battery swapping service data according to the platform configuration information of each docking platform, specifically including: Determine the operator processor corresponding to each docking platform according to the platform configuration information of each docking platform, so as to determine the operator configuration information of each docking platform; Push each of the encapsulated battery swapping service data through each of the operator configuration information according to the current docking protocol of each docking platform.

7. A multi-platform docking method for battery swapping service data according to claim 4, characterized in that, After creating the docking platform library, the method further includes: Monitor the communication status of multiple docking platforms in the docking platform library, and obtain the current communication status of each docking platform; Perform interface problem troubleshooting through the current communication status of each docking platform.

8. A multi-platform docking method for battery swapping service data according to claim 1, characterized in that Before screening protocols in the pre-created docking protocol management library according to the platform configuration information of each docking platform and matching the current docking protocol of each docking platform, the method further includes: Define multiple docking protocols, and generate the protocol text format of each docking protocol, where the protocol text format includes the header information, message body, and message end identifier of the protocol; Create a docking protocol management library according to the protocol text format of each docking protocol.

9. A multi-platform docking method for battery swapping service data according to claim 3, characterized in that, Before matching the push permissions in the pre-constructed platform push configuration table, the method further includes: Obtain multiple event attributes of the current platform and the data push rules corresponding to each event attribute; Perform push configuration on the platform basic data according to the data push rules corresponding to each event attribute, and generate the event push configuration information corresponding to each platform basic data, where the event push configuration information includes the request interface information of the platform basic data, the event attribute type corresponding to the platform basic data, and the data push platform corresponding to the platform basic data; Construct a platform push configuration table through each of the event push configuration information.

10. A multi-platform docking device for battery swapping service data, characterized in that, The device includes: An acquisition module, configured to acquire multiple to-be-docked battery swapping service data, and determine the service data docking information of each to-be-docked battery swapping service data, where the service data docking information includes at least one docking platform; A configuration module, configured to obtain the platform configuration information of each docking platform in the pre-created docking platform library through each of the service data docking information; A protocol module, configured to screen protocols in the pre-created docking protocol management library according to the platform configuration information of each docking platform, and match the current docking protocol of each docking platform; A docking module, configured to control the platform communication status between the to-be-docked battery swapping service data and the docking platform through the current docking protocol of each docking platform, so as to implement multi-platform docking of battery swapping service data.

11. An electronic device, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the multi-platform docking method of the battery swapping service data according to any one of claims 1-9.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the multi-platform docking method for battery swapping service data as described in any one of claims 1-9.

Images