Battery replacement management method and battery replacement management system
By sending communication connection requests to the battery swap cloud platform in the battery swap control system and switching to the localized battery swap platform in the event of failure, the problem that the battery swap business process cannot be completed due to network instability or service abnormality is solved, and the stability and normal progress of the battery swap business process is achieved.
Patent Information
- Application Number
- CN202411843328.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-13
- Publication Date
- 2025-04-11
AI Technical Summary
When the existing battery swap platform interacts with the battery swap cloud platform, it is prone to problems such as network instability, service abnormalities and public cloud failures, resulting in the inability to complete the battery swap business process.
Provide a battery swap management method and system, by sending a communication connection request to the battery swap cloud platform in the battery swap control system, if successful, sending battery swap service data to obtain operation information; if the connection fails, switch to the localized battery swap platform, establishing a communication connection and sending battery swap service data to obtain operation information.
When the battery swap station control system and the battery swap cloud platform are abnormal, the normal operation of the battery swap business process is ensured, which improves the stability of the battery swap process.
Smart Images

Figure CN119814817A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of battery replacement technology, and in particular to a battery replacement management method and a battery replacement management system. Background Art
[0002] The mainstream battery swapping platforms on the market currently involve many systems, most of which include a battery swapping station control system deployed locally at the battery swapping station and a battery swapping cloud platform deployed in the cloud. When the driver drives the battery swapping vehicle into the battery swapping station to perform the battery swapping operation, he needs to rely on the interaction between the battery swapping station control system and the battery swapping cloud platform to complete the battery swapping process. However, since the battery swapping station control system needs to access the network across networks when interacting with the battery swapping cloud platform, network instability, abnormal battery swapping cloud platform services, public cloud failures, etc. often occur, resulting in the inability to complete the battery swapping business process. Summary of the invention
[0003] The purpose of this application is to provide a battery swap management method and a battery swap management system, which can ensure the normal progress of the battery swap business process when the interaction between the battery swap station control system and the battery swap cloud platform is abnormal.
[0004] To achieve the above objectives: In a first aspect, an embodiment of the present application provides a battery swap management method, which is applied to a battery swap station control system, and the method includes: Send a communication connection request to the battery swap cloud platform; If the communication connection is successful, the battery swapping service data is sent to the battery swapping cloud platform to obtain first battery swapping operation information for performing battery swapping for the battery swapping vehicle; If the communication connection fails, establish a communication connection with the localized battery swapping platform, and send the battery swapping service data to the localized battery swapping platform to obtain the second battery swapping operation information.
[0005] In one embodiment, the localized battery swap platform is deployed in the local network of the battery swap station, and the battery swap cloud platform is deployed on a remote server; the battery swap cloud platform includes a main battery swap cloud platform and a backup battery swap cloud platform, and the main battery swap cloud platform and the backup battery swap cloud platform are deployed on different servers; The sending of a communication connection request to the battery swap cloud platform includes: Sending a communication connection request to the main battery swap cloud platform; When the request fails, sending a communication connection request to the backup battery swap cloud platform; If the request fails again, it is determined that the communication connection has failed.
[0006] In a second aspect, an embodiment of the present application provides a battery swap management method, which is applied to a battery swap cloud platform, and the method includes: In response to a communication connection request sent by the battery swap station control system, establishing a communication connection with the battery swap station control system; In response to the battery swapping service data sent by the battery swapping station control system, sending first battery swapping operation information to control the battery swapping station control system to perform battery swapping for the battery swapping vehicle; Establish a communication connection with the localized battery swap platform and synchronize data.
[0007] In one embodiment, establishing a communication connection with a localized battery swap platform and performing data synchronization includes: In response to a request for obtaining full basic business data sent by a localized battery swap platform, authenticating the localized battery swap platform; When the authentication is successful, a list of basic business data types is sent to the localized battery swapping platform, so that the localized battery swapping platform obtains the full amount of basic business data according to the list of basic business data types.
[0008] In one embodiment, establishing a communication connection with a localized battery swap platform and performing data synchronization also includes: when basic business data changes, based on a preset communication protocol, sending the changed incremental basic business data to the localized battery swap platform.
[0009] In a third aspect, an embodiment of the present application provides a battery swap management method, which is applied to a localized battery swap platform, and the method includes: In response to a communication connection request of the battery swap station control system, establishing a communication connection with the battery swap station control system; In response to the battery swapping service data sent by the battery swapping station control system, second battery swapping operation information is sent to control the battery swapping station control system to perform battery swapping for the battery swapping vehicle; Establish a communication connection with the battery swap cloud platform and synchronize data.
[0010] In one embodiment, the method further comprises: Build localized battery swapping business logic based on the battery swapping operation process; According to the needs of battery swapping business, build the basic business data model of business objects and establish a local database; Among them, the business objects include battery swap stations, batteries, vehicles, drivers, enterprises and battery swap agreements.
[0011] In one embodiment, establishing a communication connection with the battery swap cloud platform and performing data synchronization includes: Sending a request to obtain full basic business data to the battery swap cloud platform; If the request is successful, receive the list of basic business data types returned by the battery swap cloud platform; Based on the basic business data type list, a paging acquisition request is sent to the battery swap cloud platform, wherein the paging acquisition request includes a specified data type and a paging parameter; Receive the paging data corresponding to the paging acquisition request returned by the battery swap cloud platform, and save it to the local database.
[0012] In one embodiment, establishing a communication connection with the battery swap cloud platform and performing data synchronization also includes: after the battery swap station control system swaps battery for the battery swap vehicle based on the second battery swap operation information, the local battery swap process data corresponding to the battery swap vehicle is reported to the battery swap cloud platform.
[0013] In a fourth aspect, an embodiment of the present application provides a battery swap management system, including a battery swap station control system, a battery swap cloud platform and a localized battery swap platform as described above.
[0014] The battery swap management method and battery swap management system provided in the embodiment of the present application send a communication connection request to the battery swap cloud platform; if the communication connection is successful, the battery swap service data is sent to the battery swap cloud platform to obtain the first battery swap operation information for battery swapping vehicles; if the communication connection fails, a communication connection is established with the localized battery swap platform, and the battery swap service data is sent to the localized battery swap platform to obtain the second battery swap operation information. In this way, when the battery swap station control system interacts abnormally with the battery swap cloud platform, it can switch to the localized battery swap platform to take over the battery swap service, ensuring the normal operation of the battery swap service process. BRIEF DESCRIPTION OF THE DRAWINGS
[0015] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.
[0016] Figure 1 Schematic diagram of the process of the battery replacement management method provided in the embodiment of the present application Figure 1 .
[0017] Figure 2 A timing diagram of the battery swap platform switching process provided in an embodiment of the present application.
[0018] Figure 3 Schematic diagram of the process of the battery replacement management method provided in the embodiment of the present application Figure 2 .
[0019] Figure 4 A timing diagram for sending incremental basic business data provided in an embodiment of the present application.
[0020] Figure 5 Schematic diagram of the process of the battery replacement management method provided in the embodiment of the present application Figure 3 .
[0021] Figure 6 A timing diagram for reporting local battery replacement data provided in an embodiment of the present application.
[0022] Figure 7 A schematic diagram of the structure of the data model provided in the embodiment of the present application.
[0023] Figure 8 A timing diagram for synchronization of full basic business data provided in an embodiment of the present application. DETAILED DESCRIPTION
[0024] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.
[0025] It should be noted that, in this article, the terms "include", "comprises" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "includes a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element. In addition, components, features, and elements with the same name in different embodiments of the present application may have the same meaning or different meanings, and their specific meanings need to be determined by their explanation in the specific embodiment or further combined with the context of the specific embodiment.
[0026] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in this article, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of this article, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein can be interpreted as "at the time of..." or "when..." or "in response to determination". Furthermore, as used in this article, the singular forms "one", "one" and "the" are intended to also include plural forms, unless there is an opposite indication in the context. It should be further understood that the terms "comprising", "including" indicate that there are described features, steps, operations, elements, components, projects, kinds, and / or groups, but do not exclude the existence, occurrence or addition of one or more other features, steps, operations, elements, components, projects, kinds, and / or groups. The terms "or" and "and / or" used herein are interpreted as inclusive, or mean any one or any combination. Thus, “A, B, or C” or “A, B and / or C” means “any of the following: A; B; C; A and B; A and C; B and C; A, B, and C.” An exception to this definition will occur only when a combination of elements, functions, steps, or operations are inherently mutually exclusive in some manner.
[0027] It should be understood that, although the various steps in the flowchart in the embodiment of the present application are displayed in sequence according to the indication of the arrows, these steps are not necessarily performed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and it can be performed in other orders. Moreover, at least a portion of the steps in the figure may include a plurality of sub-steps or a plurality of stages, and these sub-steps or stages are not necessarily performed at the same time, but can be performed at different times, and their execution order is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
[0028] It should be noted that, in this article, step codes such as S101, S102, etc. are used for the purpose of expressing the corresponding content more clearly and concisely, and do not constitute a substantial limitation on the sequence. When implementing the step, those skilled in the art may execute S102 first and then S101, etc., but these should all be within the scope of protection of this application.
[0029] It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.
[0030] In the subsequent description, the suffixes such as "module", "component" or "unit" used to represent elements are only used to facilitate the description of the present application, and have no specific meanings. Therefore, "module", "component" or "unit" can be used in a mixed manner.
[0031] See also Figure 1 , is a battery swap management method provided in an embodiment of the present application. The method can be executed by the battery swap management system provided in an embodiment of the present application. The system can be implemented in software and / or hardware. In this embodiment, the execution subject of the method is a battery swap station control system as an example. The battery swap management method provided in this embodiment includes the following steps: Step S110: Send a communication connection request to the battery swap cloud platform.
[0032] Specifically, the battery swap cloud platform is deployed in the cloud, which can usually provide flexible resource allocation and has strong scalability. Therefore, by default, the battery swap process and battery swap business data of the vehicle are managed by the battery swap cloud platform. Since the battery swap process of the vehicle, by default, needs to rely on the network communication between the battery swap station control system and the battery swap cloud platform, the configuration of the battery swap operation process by the battery swap station control system is completed through the interaction of the battery swap business data. Therefore, before the battery swap business data is interacted, the communication capability between the battery swap station control system and the battery swap cloud platform is generally detected and verified based on the established communication protocol. In one embodiment of the present application, the interactive heartbeat messages between the battery swap station control system and the battery swap cloud platform can be monitored in real time. When the heartbeat check has a 404 error or a timeout problem, it can be determined that there is a problem with the network connection between the battery swap station control system and the battery swap cloud platform, or it can be determined that the battery swap cloud platform is unavailable at this time. For example, the power swap station control system regularly initiates a ping request signal to the power swap cloud platform through the internally integrated cloud SDK. If the power swap station control system successfully establishes a communication connection with the power swap cloud platform, the power swap station control system will receive a pong response signal within the preset time. If the power swap station control system cannot establish a communication connection with the power swap cloud platform, the power swap station control system will return a 404 error or timeout prompt message to trigger a retry mechanism. Among them, PING (Packet Internet Groper) is used to test the network connection, and PONG (Packet Internet Groper Echo Reply) is the response message of PING.
[0033] Step S120: If the communication connection is successful, the battery swapping service data is sent to the battery swapping cloud platform to obtain the first battery swapping operation information for performing battery swapping for the battery swapping vehicle.
[0034] Specifically, when the driver drives the vehicle into the battery swap station for battery swap, he needs to send a battery swap request to the battery swap station control system through a preset request method, such as scanning the QR code of the battery swap station. After receiving the battery swap request, the battery swap station control system collects battery swap business data. The battery swap business data may include basic information of the battery swap vehicle and driver, battery information, battery swap requirements, etc., such as the model and license plate information of the battery swap vehicle, the identity information and contact information of the driver, the model and remaining power of the battery to be replaced, and the type of battery to be replaced, such as short-range battery and long-range battery. If the communication connection between the battery swap station control system and the battery swap cloud platform is normal, then after collecting the battery swap business data, the battery swap station control system needs to upload the battery swap business data to the battery swap cloud platform by default. The battery swap cloud platform authenticates the battery swap vehicle and the driver of the battery swap based on the uploaded battery swap business data, and determines whether the battery swap vehicle belongs to a battery swap model, whether the operating enterprise to which the battery swap vehicle belongs is a contracted cooperative enterprise, and whether the driver of the battery swap vehicle has been added to the blacklist of prohibited battery swaps. After the battery swap vehicle and the battery swap driver are successfully authenticated, a battery swap service order will be generated based on the battery swap service data, and the first battery swap operation information will be generated and sent to the corresponding battery swap station control system. The battery swap station control system will configure the corresponding battery swap operation process based on the first battery swap operation information, such as selecting the battery in the appropriate bin for replacement according to the type of battery to be replaced, placing the replaced battery with insufficient power in the appropriate bin for charging, and the order settlement method after the subsequent battery replacement is completed, etc.
[0035] Step S130: If the communication connection fails, establish a communication connection with the localized battery swapping platform, and send battery swapping service data to the localized battery swapping platform to obtain the second battery swapping operation information.
[0036] Specifically, if the communication connection between the battery swap station control system and the battery swap cloud platform is abnormal, the battery swap station control system will request to start the localized battery swap platform, and process the battery swap business data through the localized battery swap platform to generate the second battery swap operation information, so that the battery swap station control system can configure the battery swap operation process according to the second battery swap operation information. In one embodiment, the second battery swap operation information and the first battery swap operation information may be identical in content, for example, both contain an operation command for the battery swap station control system to perform a battery replacement. In other embodiments, the second battery swap operation information and the first battery swap operation information may not be exactly the same in content, for example, in addition to both containing the same operation command for the battery swap station control system to perform a battery replacement, since the localized battery swap station platform cannot access the external network, it is also impossible to complete the settlement of the battery swap business order through a third-party payment platform. Therefore, the second battery swap operation information and the first battery swap operation information may be different in the process management of order settlement. For example, the first battery swap operation information can support both online and offline payment methods, while the second battery swap operation information only supports offline payment, or supports drivers to reserve online payment information, such as bank card number, payment account number, etc. After the localized battery swap platform successfully establishes communication with the battery swap cloud platform, the battery swap cloud platform completes the payment of the order through a third-party platform based on the reserved payment information.
[0037] It should be noted that the localized battery swap platform is deployed in the local network of the battery swap station and is in the same network range as the battery swap station control system. Data interaction can be carried out directly through the local area network. The connection status is relatively stable. Even without the support of the battery swap cloud platform, it can also support the independent operation of the basic functions of the battery swap station, such as battery replacement operations and recording battery swap data.
[0038] The battery swap cloud platform is deployed on a remote server, and the battery swap station control system needs to access the battery swap cloud platform across the Internet, which is prone to disconnection or unstable signals. Therefore, in one embodiment of the present application, the battery swap cloud platform includes a main battery swap cloud platform and a backup battery swap cloud platform, and the main battery swap cloud platform and the backup battery swap cloud platform are deployed on different servers; sending a communication connection request to the battery swap cloud platform includes: sending a communication connection request to the main battery swap cloud platform; when the request fails, sending a communication connection request to the backup battery swap cloud platform; if the request fails again, it is determined that the communication connection has failed.
[0039] Figure 2 This is a timing diagram of the battery swap platform switching process provided in the embodiment of the present application. Figure 2 As shown, it is assumed that the main battery swap cloud platform is Figure 2 The cloud platform in the standby battery swapping cloud platform is Figure 2The disaster recovery cloud in the cloud SDK. First, the battery swap station control system actively initiates a ping connection request to the cloud platform through the cloud SDK. If a pong response signal is returned, the communication connection between the battery swap station control system and the cloud platform is successful. If a 404 error or timeout prompt message is returned, the communication connection between the battery swap station control system and the cloud platform fails, triggering the cloud SDK to initiate a ping connection request to the cloud platform again. If the request fails three times in a row, the cloud SDK is triggered to initiate a ping connection request to the disaster recovery cloud. The disaster recovery cloud is a backup of the cloud platform, which is used to take over the battery swap service when the cloud platform fails or is unavailable. It maintains the key data of the cloud platform and a copy of the battery swap service to ensure that the battery swap service can be seamlessly switched when the cloud platform fails. There can be multiple disaster recovery clouds, each of which can be deployed on different servers with different geographical locations, which can reduce the risk of single point failures. If the battery swap station control system successfully communicates with the disaster recovery cloud, a pong response signal is returned. If the communication connection fails, a 404 error or timeout prompt message is returned, and the retry mechanism is triggered. If the connection fails after three retries, a request is made to enable the localized battery swap platform, and a communication connection request is initiated to the localized battery swap platform, which will then take over the battery swap business process. The localized battery swap platform in the embodiment of the present application is deployed in the local network of the battery swap station and is in the same network range as the battery swap station control system, so cross-network access is not required. Therefore, the localized battery swap platform is more stable than the battery swap cloud platform. When the interaction between the battery swap station control system and the battery swap cloud platform is abnormal, the localized battery swap platform takes over the battery swap service by switching to the localized battery swap platform to complete the interaction of the battery swap business data, thereby ensuring the normal progress of the battery swap business process and improving the stability of the battery swap process.
[0040] See also Figure 3 , is a battery swap management method provided in an embodiment of the present application. The method can be executed by the battery swap management system provided in an embodiment of the present application. The system can be implemented in software and / or hardware. In this embodiment, the execution subject of the method is a battery swap cloud platform as an example. The battery swap management method provided in this embodiment includes the following steps: Step S210: In response to the communication connection request sent by the battery swap station control system, establish a communication connection with the battery swap station control system.
[0041] Step S220: In response to the battery swapping service data sent by the battery swapping station control system, first battery swapping operation information is sent to control the battery swapping station control system to perform battery swapping for the battery swapping vehicle.
[0042] Specifically, after receiving the communication connection request sent by the battery swap station control system, if the battery swap cloud platform and the battery swap station control system can establish a communication connection normally, the battery swap cloud platform can receive the battery swap business data sent by the battery swap station control system. At this time, the battery swap cloud platform can normally send the first battery swap operation information to control the battery swap station control system and complete the battery swap service for the battery swap vehicle.
[0043] Step S230: Establish a communication connection with the localized battery swap platform and synchronize data.
[0044] Specifically, in order to complete the battery swapping operation process by simulating station-cloud interaction through the localized battery swapping platform when a failure occurs on the battery swapping cloud platform, the battery swapping cloud platform needs to establish a communication connection with the localized battery swapping platform and synchronize the business data stored in the cloud with the localized battery swapping platform, so as to authenticate the battery swapping vehicle and the battery swapping driver when the vehicle is swapping batteries.
[0045] In one embodiment, data synchronization includes: responding to a request for obtaining the full amount of basic business data sent by the localized battery swap platform, authenticating the localized battery swap platform; if the authentication is successful, sending a list of basic business data types to the localized battery swap platform, so that the localized battery swap platform obtains the full amount of basic business data according to the list of basic business data types.
[0046] Specifically, when synchronizing data, the battery swap cloud platform will authenticate the localized battery swap platform that needs to synchronize data, for example, through AK (Access Key) and SK (Secret Key) to ensure that only authorized localized battery swap platforms can access and operate data. After successful authentication, the HTTPS protocol is used to encrypt and transmit the basic business data that needs to be synchronized to ensure the security of data during transmission. Full basic business data refers to the complete set of basic business information necessary for the battery swap process, which constitutes the basis for the operation of the battery swap business. Exemplarily, the full basic business data may include: vehicle information, such as vehicle ID, vehicle model, license plate number, etc.; vehicle-bound driver information, such as driver ID, name, contact information, account information, etc.; battery information, such as battery ID, model, capacity, health status, etc.; battery swap station information, such as battery swap station ID, geographic location, service capabilities, battery inventory, etc.; enterprise information, such as enterprise ID, name, contact information, service scope, etc. When the localized battery swap platform is initially established or initialized, it is necessary to obtain all necessary basic business data from the battery swap cloud platform to initialize the local database.
[0047] In one embodiment, when the basic business data changes, data synchronization also includes: based on a preset communication protocol, sending the changed incremental basic business data to a localized battery swap platform.
[0048] Figure 4 A timing diagram for the delivery of incremental basic business data provided in the embodiment of the present application. After the battery swap cloud platform synchronizes all basic business data, as the battery swap service proceeds, some basic business data will also change, for example, updates to the driver information bound to the vehicle, such as changes in contact information, account status updates, etc.; battery status updates, such as changes in battery health status, charging and discharging status, battery replacement records, etc.; battery swap station status updates, such as changes in battery inventory, changes in service capabilities, etc.; as well as newly added battery swap service companies, newly added battery swap vehicle models, etc. Figure 4 As shown in the figure, these changed incremental basic business data are sent in batches by the battery swap cloud platform to the localized battery swap platform based on the MQTT protocol. After receiving the incremental basic business data, the localized battery swap cloud platform will send a confirmation message to the battery swap cloud platform, indicating that the data has been successfully received. After confirming the receipt of the incremental basic business data, the localized battery swap platform will update the local database based on the incremental basic business data to ensure that the local data is synchronized with the cloud platform and to ensure the continuity of the battery swap business.
[0049] See also Figure 5 , is a battery swap management method provided in an embodiment of the present application. The method can be executed by the battery swap management system provided in an embodiment of the present application. The system can be implemented in software and / or hardware. In this embodiment, the execution subject of the method is a localized battery swap platform as an example. The battery swap management method provided in this embodiment includes the following steps: Step S310: In response to a communication connection request of the battery swap station control system, establish a communication connection with the battery swap station control system; Step S320: In response to the battery swapping service data sent by the battery swapping station control system, second battery swapping operation information is sent to control the battery swapping station control system to perform battery swapping for the battery swapping vehicle; Step S330: Establish a communication connection with the battery swap cloud platform and synchronize data.
[0050] Specifically, when the communication connection between the battery swap station control system and the battery swap cloud platform fails, it will switch to the localized battery swap platform, and the localized battery swap platform will cooperate with the battery swap station control system to complete the battery swap business process. After the battery swap station control system swaps the battery for the battery swap vehicle based on the second battery swap operation information, it is necessary to establish a communication connection with the battery swap cloud platform and perform data synchronization. In one embodiment, data synchronization includes: reporting the local battery swap process data corresponding to the battery swap vehicle to the battery swap cloud platform.
[0051] Figure 6 This is a timing diagram of local battery replacement data reporting provided in the embodiment of the present application. Figure 6As shown in the figure, after the battery swapping vehicle is replaced by the local battery swapping platform, the local battery swapping platform needs to actively report the local battery swapping process data to the battery swapping cloud platform based on the MQTT protocol. If the reporting request is successful, the battery swapping cloud platform will return a confirmation message to the local battery swapping platform and update the basic business data stored in the cloud to ensure that the battery swapping cloud platform synchronizes the changes in business data and ensures the continuity of the battery swapping business.
[0052] In one embodiment, when establishing a localized battery swap platform, it is necessary to build a localized battery swap business logic based on the battery swap operation process; build a basic business data model of business objects and establish a local database based on the battery swap business needs; wherein the business objects include battery swap stations, batteries, vehicles, drivers, enterprises, and battery swap agreements.
[0053] Specifically, when building a localized battery swap platform, since the battery swap cloud platform involves many systems, such as battery swap agreement services, order services, billing services, user driver services, vehicle services, battery services, etc., the localized battery swap platform can only run within a predetermined local area network. Therefore, it is impossible to deploy all systems to the localized battery swap platform, and it is necessary to simplify the systems involved in the battery swap cloud platform. First, it is necessary to identify all key system components involved in the battery swap cloud platform, such as battery swap agreement services, order services, billing services, user driver services, vehicle services, battery services, etc. Analyze the data dependencies between these system components, determine which data is necessary in the battery swap process, and then unify and abstract the data that is dependent on the battery swap process to create a common data model that can describe all key data in the battery swap process and reduce data dependency.
[0054] Figure 7 This is a schematic diagram of the structure of the data model provided in the embodiment of the present application. Figure 7As shown, the business object entities involved in the basic business data model defined in the embodiment of the present application include: battery swap stations, batteries, vehicles, drivers, enterprises, and battery swap agreements. Among them, the attributes defined in the data model of the battery swap station may include the battery swap station ID, supported battery swap models, etc.; the attributes defined in the data model of the battery may include the battery ID, battery model, battery capacity, battery health status, etc. in stock; the attributes defined in the data model of the vehicle may include the vehicle ID, model, license plate number, registration information, etc. that supports battery swap; the attributes defined in the data model of the driver may include the driver ID, driver's license information, contact information, and the battery swap classification list to which it belongs; the attributes defined in the data model of the enterprise may include the enterprise ID, name, contact information, etc. that provides battery swap services and signs contracts to enjoy battery swap services; the data model of the battery swap agreement defines the rules and standards for the battery swap process. By building a corresponding data model for each business object to support the battery swap business logic and data interaction during the battery swap process, the localized battery swap platform can operate independently.
[0055] In one embodiment of the present application, after the localized battery swap platform is successfully established, when data initialization is required, data synchronization is performed including: sending a request to obtain the full amount of basic business data to the battery swap cloud platform; if the request is successful, receiving a list of basic business data types returned by the battery swap cloud platform; based on the list of basic business data types, sending a paging acquisition request to the battery swap cloud platform, the paging acquisition request including specified data types and paging parameters; receiving paging data returned by the battery swap cloud platform corresponding to the paging acquisition request, and saving it to the local database.
[0056] Figure 8 This is a timing diagram of full basic business data synchronization provided by the embodiment of this application. Figure 8As shown, when the localized battery swap platform needs to obtain the full amount of basic business data from the battery swap cloud platform, it first initiates a request to the battery swap cloud platform to obtain a list of data types that need to be synchronized. If the request is successful, the cloud platform will return the list of basic business data types to the localized battery swap platform. Since the amount of full basic business data is generally large, the localized battery swap platform will obtain the full amount of basic business data from the cloud platform in batches according to the returned list of basic business data types, so as to reduce the load of a single data transmission and improve the stability of data transmission. When the localized battery swap platform performs batch pulling, it sends a paging acquisition request to the battery swap cloud platform. The paging acquisition request contains the data type that needs to be pulled this time, as well as the specified page number or offset. After receiving the paging acquisition request, the battery swap cloud platform queries the cloud database according to the specified data type and paging parameters and returns the corresponding paging data. After receiving the paging data, the localized battery swap platform performs necessary data processing, such as data verification, format conversion, etc., and then stores the processed data in the local database. The data is pulled in batches in a loop until a complete set of basic business data is obtained, so that the local database can support the smooth progress of the battery replacement process.
[0057] To summarize, the battery swap management method provided in the embodiments of the present application builds a localized battery swap platform locally at the battery swap station. When the interaction between the battery swap station control system and the battery swap cloud platform is abnormal, the method switches to the localized battery swap platform, and the localized battery swap platform takes over the battery swap business and interacts with the battery swap station control system for battery swap business data, thereby ensuring the normal progress of the battery swap business process and improving the stability of the battery swap process.
[0058] Based on the same inventive concept as the aforementioned embodiment, the embodiment of the present application also provides a battery swap management system, which includes a battery swap station control system, a battery swap cloud platform and a localized battery swap platform as described in the aforementioned embodiment. The detailed functional implementation of each of the above modules can refer to the introduction in the aforementioned method embodiment, which will not be repeated here. The battery swap management method as described above is realized through the collaboration between the above-mentioned battery swap management system and the modules arranged therein, which has exactly the same beneficial effects.
[0059] The technical features of the above-described embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above-described embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0060] In this document, the terms "comprises," "comprising," or any other variations thereof, are intended to cover a non-exclusive inclusion of elements other than those listed and may also include additional elements not expressly listed.
[0061] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.
Claims
1. A battery replacement management method, characterized in that: Applied to a battery swap station control system, the method comprises: Send a communication connection request to the battery swap cloud platform; If the communication connection is successful, the battery swapping service data is sent to the battery swapping cloud platform to obtain the first battery swapping operation information for performing battery swapping for the battery swapping vehicle; If the communication connection fails, establish a communication connection with the localized battery swapping platform, and send the battery swapping service data to the localized battery swapping platform to obtain the second battery swapping operation information.
2. The battery replacement management method according to claim 1, characterized in that: The localized battery swap platform is deployed in the local network of the battery swap station, and the battery swap cloud platform is deployed on a remote server; the battery swap cloud platform includes a main battery swap cloud platform and a backup battery swap cloud platform, and the main battery swap cloud platform and the backup battery swap cloud platform are deployed on different servers; The sending of a communication connection request to the battery swap cloud platform includes: Sending a communication connection request to the main battery swap cloud platform; When the request fails, sending a communication connection request to the backup battery swap cloud platform; If the request fails again, it is determined that the communication connection has failed.
3. A battery replacement management method, characterized in that: Applied to the battery swap cloud platform, the method includes: In response to a communication connection request sent by the battery swap station control system, establishing a communication connection with the battery swap station control system; In response to the battery swapping service data sent by the battery swapping station control system, first battery swapping operation information is sent to control the battery swapping station control system to perform battery swapping for the battery swapping vehicle; Establish a communication connection with the localized battery swap platform and synchronize data.
4. The battery replacement management method according to claim 3, characterized in that: The establishing of a communication connection with the localized battery swapping platform and performing data synchronization includes: In response to a request for obtaining full basic business data sent by a localized battery swap platform, authenticating the localized battery swap platform; When the authentication is successful, a list of basic business data types is sent to the localized battery swapping platform, so that the localized battery swapping platform obtains the full amount of basic business data according to the list of basic business data types.
5. The battery replacement management method according to claim 4, characterized in that: The establishing of a communication connection with the localized battery swapping platform and performing data synchronization also includes: When the basic business data changes, the changed incremental basic business data will be sent to the localized battery swap platform based on the preset communication protocol.
6. A battery replacement management method, characterized in that: Applied to a localized battery swap platform, the method includes: In response to a communication connection request of the battery swap station control system, establishing a communication connection with the battery swap station control system; In response to the battery swapping service data sent by the battery swapping station control system, second battery swapping operation information is sent to control the battery swapping station control system to perform battery swapping for the battery swapping vehicle; Establish a communication connection with the battery swap cloud platform and synchronize data.
7. The battery replacement management method according to claim 6, characterized in that: The method further comprises: Build localized battery swap business logic based on the battery swap operation process; According to the needs of battery swapping business, build the basic business data model of business objects and establish a local database; Among them, the business objects include battery swap stations, batteries, vehicles, drivers, enterprises and battery swap agreements.
8. The battery replacement management method according to claim 7, characterized in that: The establishing of a communication connection with the battery swap cloud platform and performing data synchronization includes: Sending a request to obtain full basic business data to the battery swap cloud platform; If the request is successful, receive the list of basic business data types returned by the battery swap cloud platform; Based on the basic business data type list, a paging acquisition request is sent to the battery swap cloud platform, wherein the paging acquisition request includes a specified data type and a paging parameter; Receive the paging data corresponding to the paging acquisition request returned by the battery swap cloud platform, and save it to the local database.
9. The battery replacement management method according to claim 6, characterized in that: The establishing of a communication connection with the battery swap cloud platform and performing data synchronization includes: After the battery swap station control system swaps battery for the battery swap vehicle based on the second battery swap operation information, the local battery swap process data corresponding to the battery swap vehicle is reported to the battery swap cloud platform.
10. A battery replacement management system, characterized in that: It includes the battery swap station control system as described in claim 1 or 2, the battery swap cloud platform as described in any one of claims 3 to 5, and the localized battery swap platform as described in any one of claims 6 to 9.