Batch migration method and system between single lamp controller platforms

Abstract

The invention discloses a batch migration method and system between single lamp controller platforms. The method comprises the following steps: importing a single lamp controller information list through a user front end; updating a filtering list cached by the system, and recording the state of the to-be-migrated single lamp controller; obtaining corresponding item information from the cache; issuing communication parameter configuration instructions to the single lamp controllers in batches; recording and storing an operation log; issuing query instructions in batches, monitoring, feeding back and comparing communication parameters; issuing a reset instruction when the comparison is consistent; and clearing the cache and feeding back a migration result. The system comprises a single-lamp controller migration module, a single-lamp controller information import module, a user project information management module, a cache management module, a log module and a communication interface module, supports data encryption transmission and dynamic retransmission strategies, and remarkably improves the migration efficiency of the single-lamp controller through modular design. And the data management capability and the operation transparency are enhanced.

Description

Technical Field

[0001] The present invention relates to the technical field of single lamp controller migration, and in particular to a method and system for batch migration of single lamp controllers between platforms. Background Art

[0002] When migrating existing single-lamp controllers to different management platforms, they usually rely on manual on-site operations, such as re-burning the program or reconfiguring communication parameters. This method is not only time-consuming and labor-intensive, but also prone to human error causing the device to malfunction. In addition, the existing migration method lacks batch processing capabilities, especially when there are a large number of single-lamp controllers. The manual operation efficiency is low and it is difficult to meet the rapid deployment requirements of large-scale intelligent lighting systems. Therefore, there is an urgent need for a technical solution that supports remote batch migration to improve the automation and efficiency of single-lamp controller migration. Summary of the invention

[0003] Technical purpose: In view of the shortcomings of the existing migration between single-lamp controller platforms, the present invention discloses a method and system for batch migration between single-lamp controller platforms. By introducing cache management, user and project information management, log recording, communication encryption and other functions, remote batch migration and status monitoring of single-lamp controllers are realized.

[0004] Technical solution: To achieve the above technical objectives, the present invention adopts the following technical solution: A method for batch migration of single lamp controllers between platforms, comprising the following steps: Obtain an information list of single lamp controllers to be migrated in batches, the information list including at least a unique identification serial number of each single lamp controller; Update the filter list in the system cache based on the single lamp controller information list. The filter list contains the single lamp controller serial number and its maximum number of times it is sent. The initial number of times it is sent is set to zero. Read the project information associated with each single lamp controller from the system cache. The project information includes project name, IP address or domain name, port, VPN, user name, password, network logo, SDK encryption configuration and automatic reset configuration; Loop through the single lamp controller information list and send communication parameter configuration instructions to each single lamp controller in turn. The communication parameters include IP address or domain name, port, VPN, user name, password, network logo and SDK encryption configuration; The operation information of each communication parameter configuration instruction is recorded in the log module. The operation information includes the user's IP address, operation type, operation result and the serial number of the single lamp controller, and the operation timestamp is stored in the database; After the communication parameter configuration command is issued, the system sends a batch of communication parameter query commands to all single lamp controllers in the single lamp controller information list, and monitors the single lamp controller feedback message pushed through the telecommunications IoT platform, parses the feedback content and obtains the actual communication parameters of the single lamp controller; Compare the actual communication parameters fed back by each single lamp controller with the configured communication parameters. If the communication parameters are inconsistent, resend the communication parameter configuration command to the single lamp controller until the maximum number of times is reached; if the communication parameters are consistent, mark the migration of the single lamp controller as successful; Send a reset command to the successfully migrated single lamp controller to restart the single lamp controller; After the migration is completed, the filter list in the cache is cleared, and the migration results are fed back to the front-end interface through Websocket for users to view.

[0005] The present invention also provides a system for batch migration between single lamp controller platforms, which is used to implement the above-mentioned method for batch migration between single lamp controller platforms, including: The single lamp controller migration module is used to obtain the information list of the single lamp controllers to be migrated, initialize the filter list in the system, and perform communication parameter configuration, feedback monitoring and status update in batches; Single lamp controller information import module, used to receive single lamp controller information from the user front end, including Excel batch import and single data manual entry, and perform data verification to ensure information integrity; User project information management module, including user management module and project management module. The user management module is used to manage system user information, including user account creation and role permission configuration; the project management module is used to create and manage project information, including project name, communication parameters, network logo, SDK encryption configuration and reset configuration, allowing users to create and edit project information, and automatically test communication parameter connectivity before starting a task; The cache management module is used to create and update the filter list, record the delivery progress information and maximum delivery times of each single lamp controller to the system cache, and clear the invalid data in the cache after the migration task is completed; The log module is used to record the user operation information and single lamp controller feedback information during the migration operation, including the issuance of communication parameters, the issuance of reset instructions, and the modification of project information. It also supports filtering and querying historical logs by operation type, user name, and single lamp controller serial number; The communication interface module is used to establish a connection with the telecommunications IoT platform, push communication parameter configuration instructions to the telecommunications IoT platform, and monitor the feedback message of the single lamp controller to obtain the actual communication parameters.

[0006] Beneficial effects: The method and system for batch migration between single lamp controller platforms provided by the present invention have the following beneficial effects: The present invention can support remote automated migration of a large number of single-lamp controllers by introducing a single-lamp controller information import module, a cache management module and a batch operation mechanism, thereby avoiding the low efficiency of manual on-site operations in traditional solutions and greatly improving operational efficiency.

[0007] The present invention uses a dynamic retransmission strategy and introduces a cache management module to enable the system to adjust the operation process in real time according to the network status or feedback information from the single lamp controller, and realize automatic retry and interval optimization when the communication parameter configuration fails. Compared with the fixed retry method, the migration success rate and system robustness in complex scenarios are improved.

[0008] The user and project information management module of the present invention realizes flexible configuration of user permissions and efficient management of project information. The log module supports multi-condition query, ensures the traceability of operations and transparency of task results. The communication encryption mechanism ensures the security and consistency of data during transmission, effectively prevents data leakage and tampering, and meets the requirements for data security. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art are briefly introduced below.

[0010] Figure 1 A flow chart of a method for batch migration of single lamp controllers between platforms of the present invention; Figure 2 This is an application scenario diagram of the method and system for batch migration between single lamp controller platforms of the present invention; Figure 3 The software architecture diagram of the batch migration method between single lamp controller platforms of the present invention; Figure 4 This is a flow chart of information entry for a single lamp controller of the present invention; Figure 5 It is a schematic diagram of the batch migration system between single lamp controller platforms of the present invention. DETAILED DESCRIPTION

[0011] The present invention will be described more clearly and completely below by way of a preferred embodiment in conjunction with the accompanying drawings, but the present invention is not limited to the scope of the embodiment.

[0012] like Figure 1 As shown, a method for batch migration of single lamp controllers between platforms includes the following steps: S101, obtaining an information list of single lamp controllers to be migrated in batches, the information list including at least a unique identification serial number of each single lamp controller; In one embodiment, the information list of single lamp controllers to be migrated in batches is imported into the system by the user through different projects. This process specifically includes: Single lamp controller information import, that is, single lamp controller data is imported into the system background individually or in batches and loaded into the memory; Single lamp controller information verification, that is, reviewing the single lamp controller serial number according to the system verification rules. The verification principle is that the serial number of the single lamp controller must comply with the verification rules and must be unique in the platform input data and the data input in this batch. The same serial number cannot appear in the data source. The verification rule is that the serial number of the single lamp controller must be 12 digits without letters. Persistence of single lamp controller information means that after all verifications are passed, the source data is updated and the verified single lamp controller information in the memory is stored in the database; The import result of the single-lamp controller is displayed, that is, the system feeds back the incorrect single-lamp controller information to the front end according to the verification rules. Specifically, when an error is found during the single-lamp controller information verification, the data is quickly rolled back, and the error information is sent to the front end through Websocket to remind the user to check. After the user manually determines, the data is reprocessed and imported again until all verifications pass.

[0013] S102. Update the filter list in the system cache based on the single lamp controller information list. The filter list includes the serial number of the single lamp controller and its maximum number of issuance times. The initial number of issuance times is set to zero. The initial state of the system cache is an empty list. The user selects the single lamp controller information list that needs to issue batch instructions in the front-end interface. The front-end interface filters the single lamp controller according to its online status, and the data is transmitted to the background service through the interface.

[0014] S103, reading the project information associated with each single lamp controller from the system cache, the project information including the project name, IP address or domain name, port, VPN, user name, password, network logo, SDK encryption configuration and automatic reset configuration; In a specific embodiment, project information is entered and managed by the user and included in the user project information management module; the password is encrypted using crypto; the network logo includes automatic search for the public network, General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), EVDO (Evolution Data only, EV-DO), 4G, 5G, NarrowBand-Internet of Things (NB-IOT), WiFi and RJ-45; the SDK encryption configuration indicates whether the single-lamp controller message is SDK encrypted; automatic reset indicates whether the reset command is automatically sent after the communication parameters are successfully sent, and the project information and the serial number of the single-lamp controller are in a one-to-many relationship.

[0015] S104, loop through the single lamp controller information list, and send communication parameter configuration instructions to each single lamp controller in turn, where the communication parameters include IP address or domain name, port, VPN, user name, password, network logo, and SDK encryption configuration; In one embodiment, when issuing communication parameter configuration instructions, the system generates encrypted messages from the communication parameters. The encryption method is symmetric encryption, involving the Advanced Encryption Standard (AES) and the Tiny Encryption Algorithm (TEA). A connection is established with the telecommunications Internet of Things platform through the Netty service to push the encrypted message.

[0016] In one embodiment, the communication parameters are created by the user in the system and associated with the project information, and the connectivity test of the target address can be performed after the communication parameters are created. The principle of the connectivity test is that the system generates a random test serial number and generates a heartbeat query message according to the incoming SDK encryption type, and sends the information as a buffer to the target address through the writeAndFlush method of the User Datagram Protocol (UDP) through the copiedBuffer method of the Netty service; the system client receives the ChannelHandlerContext object passed in by SimpleChannelInboundHandler through the channelRead0 method of the Netty service and processes it; after confirming that the serial number and encryption method of the parsed heartbeat packet are consistent with the push message, it is pushed to the user who initiated the test at the front desk through the Websocekt service to inform him that the test is successful; the client waits for 10 seconds to receive the response message from the server, then exits and releases resources.

[0017] S105. Record the operation information of each communication parameter configuration instruction issued to the log module. The operation information includes the user's IP address, operation type, operation result and serial number of the single lamp controller, and store the operation timestamp in the database; the user IP is the IP address of the logged-in user, which is recorded by the front end and transmitted to the back end after the user logs in; there are four types of operation types, namely login operation, configuration parameters, parameter issuance and reset operation. Users can obtain the operation records in the system through the log module, including the issuance records of the single lamp controller, for traceability.

[0018] S106. After the communication parameter configuration instruction is issued, the system sends a batch of instructions to query the communication parameters to all single lamp controllers in the single lamp controller information list, and monitors the feedback message pushed by the single lamp controller through the telecommunications Internet of Things platform, parses the feedback content and obtains the actual communication parameters of the single lamp controller; Specifically, after receiving the message, the telecommunications Internet of Things platform sends it to the processing unit of the single-lamp controller through the nearest base station. After receiving the message information, the single-lamp controller parses and runs the instruction, and sends the result of the operation to the nearest base station. The base station sends the instruction to the telecommunications Internet of Things platform, which is further processed and displayed in the system front end.

[0019] In one embodiment, multi-threading technology is used to reduce the background operation load when parsing messages in batches.

[0020] S107, comparing the actual communication parameters fed back by each single lamp controller with the configured communication parameters, if the communication parameters are inconsistent, re-issuing the communication parameter configuration instruction to the single lamp controller until the maximum number of issuances is reached; if the communication parameters are consistent, marking the migration of the single lamp controller as successful; S108, issuing a reset command to the successfully migrated single lamp controller to complete the restart of the single lamp controller; In one embodiment, the reset instruction is an optional item, which is selected in the project information. If the reset instruction is not selected for the project, it will not be issued, and will be manually issued after all the items are issued.

[0021] S109. After the migration is completed, the filter list in the cache is cleared, and the migration result is fed back to the front-end interface through Websocket for the user to view.

[0022] Users can observe the modification of communication parameters of single-lamp controllers in real time through the interface. Subsequently, they only need to filter out the single-lamp controllers that failed to migrate and re-issue instructions to advance the process.

[0023] like Figure 2 The following is an application scenario of a specific embodiment of the present invention. The data flow process in this scenario is as follows: The system generates an encrypted message with the communication parameters and pushes it to the telecommunications IoT platform. After receiving the data, the telecommunications IoT platform pushes it to the base station closest to the single-lamp controller. The base station sends the information by broadcasting. After receiving the encrypted message sent by the base station, the single-lamp controller parses and executes the message content. After the execution is completed, the current communication parameters are encrypted into a message and actively reported to the base station. The base station pushes the data to the telecommunications IoT platform. The system monitors the encrypted message pushed by the telecommunications IoT platform, then decrypts the encrypted message information and displays it to the terminal platform for users to view.

[0024] like Figure 3 The software architecture diagram of the batch migration method between single lamp controller platforms of the present invention is shown. There is a front-end UI interface for users to operate with a browser. The software system is deployed on an Apache server, and the back-end performs data persistence and acquisition through a database.

[0025] The user selects the single lamp controllers that need to be migrated in batches through the front-end interface, and transmits the data to the back-end through the back-end interface for processing; after the processing is completed, the data is persisted through the back-end database, and the migration status and instruction issuance time of the single lamp controller in the background data are updated; when the system is initialized, the corresponding project information is obtained from the database and loaded into the cache for use.

[0026] like Figure 4The figure shows the flow chart of single lamp controller information entry of the present invention. The single lamp controller information is entered by the user through the front-end UI interface, which is divided into Excel batch import and single manual entry. After entry, the system performs verification. After all verifications pass, the single lamp controller information is synchronized to the system database for persistence. If the verification fails, it is fed back to the user through the front-end UI interface, and waits for manual processing before being imported into the system again.

[0027] like Figure 5 As shown, the present invention also provides a system for batch migration between single lamp controller platforms, which is used to implement the above-mentioned method for batch migration between single lamp controller platforms, including: The single lamp controller migration module is used to obtain the information list of the single lamp controllers to be migrated, initialize the filter list in the system, and perform communication parameter configuration, feedback monitoring and status update in batches; The single-lamp controller information import module is used to receive single-lamp controller information from the user front end, including Excel batch import and manual entry of single data, and perform data verification to ensure information integrity; the single-lamp controller information import module includes single-lamp controller information import, single-lamp controller information verification, single-lamp controller information persistence, and display of single-lamp controller information import results.

[0028] User project information management module, including user management module and project management module. The user management module is used to manage system user information, including user account creation and role permission configuration; the project management module is used to create and manage project information, including project name, communication parameters, network logo, SDK encryption configuration and reset configuration, allowing users to create and edit project information, and automatically test communication parameter connectivity before starting a task; In one embodiment, the user management module includes a role permission allocation function, and the roles include ordinary users and administrators. Ordinary users can only view and manage the projects they created, and administrators can edit all user information and project information.

[0029] The cache management module is used to create and update the filter list, record the delivery progress information and maximum delivery times of each single lamp controller to the system cache, and clear the invalid data in the cache after the migration task is completed; The log module is used to record user operation information and single lamp controller feedback information during the migration operation, including the issuance of communication parameters, the issuance of reset instructions, and the modification of project information. It also supports filtering and querying historical logs by operation type, user name, and single lamp controller serial number; In one embodiment, the log module includes a recording module and a query module; the recording module is used to record the user's operations in the system and the feedback information of the single-lamp controller; the query module is used to query the historical log according to the filtering conditions, and the filtering conditions include the operation type, user name and the serial number of the single-lamp controller.

[0030] The communication interface module is used to establish a connection with the telecommunications IoT platform, push communication parameter configuration instructions to the telecommunications IoT platform, and monitor the feedback message of the single lamp controller to obtain the actual communication parameters.

[0031] The present invention also provides a single lamp controller capable of modifying communication parameters, comprising: An acquisition module, used to acquire messages pushed by the base station; A storage module, used for storing communication parameters; The processing module parses the message into communication parameters and runs it on its own program to modify its own communication parameters; The sending module encrypts the current communication parameters to generate a message and sends it to the telecommunications Internet of Things platform.

[0032] The above is only a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A method for batch migration of single lamp controllers between platforms, characterized in that: The following steps are involved: Obtain an information list of single lamp controllers to be migrated in batches, the information list including at least a unique identification serial number of each single lamp controller; Based on the single lamp controller information list, the filter list in the system cache is updated. The filter list contains the serial number of the single lamp controller and its maximum number of times of sending. The initial number of times of sending is set to zero. Read the project information associated with each single lamp controller from the system cache. The project information includes project name, IP address or domain name, port, VPN, user name, password, network logo, SDK encryption configuration and automatic reset configuration; Loop through the single lamp controller information list and send communication parameter configuration instructions to each single lamp controller in turn. The communication parameters include IP address or domain name, port, VPN, user name, password, network logo and SDK encryption configuration; The operation information of each communication parameter configuration instruction is recorded in the log module. The operation information includes the user's IP address, operation type, operation result and the serial number of the single lamp controller, and the operation timestamp is stored in the database; After the communication parameter configuration command is issued, the system sends a batch of communication parameter query commands to all single lamp controllers in the single lamp controller information list, and monitors the single lamp controller feedback message pushed through the telecommunications IoT platform, parses the feedback content and obtains the actual communication parameters of the single lamp controller; Compare the actual communication parameters fed back by each single lamp controller with the configured communication parameters. If the communication parameters are inconsistent, resend the communication parameter configuration command to the single lamp controller until the maximum number of times is reached; If the communication parameters are consistent, the migration of the single lamp controller is marked as successful; Send a reset command to the successfully migrated single lamp controller to restart the single lamp controller; After the migration is completed, the filter list in the cache is cleared, and the migration results are fed back to the front-end interface through Websocket for users to view.

2. The method for batch migration of single lamp controllers between platforms according to claim 1, characterized in that: The information list of single lamp controllers to be migrated in batches is imported into the system by the user through different projects. This process specifically includes: Single lamp controller information import, that is, single lamp controller data is imported into the system background individually or in batches and loaded into the memory; Single lamp controller information verification, that is, reviewing the serial number of the single lamp controller according to the system verification rules. The verification principle is that the serial number of the single lamp controller must comply with the verification rules and be unique in the platform input data and the data input in this batch. The same serial number cannot appear in the data source; Persistence of single lamp controller information means that after all verifications are passed, the source data is updated and the verified single lamp controller information in the memory is stored in the database; Display the single lamp controller import results, that is, the system will feed back the incorrect single lamp controller information to the front end according to the verification rules.

3. The method for batch migration of single lamp controllers between platforms according to claim 2, characterized in that: The verification rule means that the serial number of a single lamp controller is 12 digits pure numbers without letters.

4. The method for batch migration of single lamp controllers between platforms according to claim 1, characterized in that: The communication parameters are created by the user in the system and associated with the project information, and the connectivity test of the target address is performed after the communication parameters are created.

5. The method for batch migration of single lamp controllers between platforms according to claim 1, characterized in that: When issuing communication parameter configuration instructions, the system generates encrypted messages from the communication parameters, establishes a connection with the telecommunications IoT platform through the Netty service, and pushes the encrypted messages.

6. A system for batch migration between single lamp controller platforms, used to implement a method for batch migration between single lamp controller platforms as claimed in any one of claims 1 to 5, characterized in that: include: The single lamp controller migration module is used to obtain the information list of the single lamp controllers to be migrated, initialize the filter list in the system, and perform communication parameter configuration, feedback monitoring and status update in batches; Single lamp controller information import module, used to receive single lamp controller information from the user front end, including Excel batch import and single data manual entry, and perform data verification to ensure information integrity; User project information management module, including user management module and project management module. The user management module is used to manage system user information, including user account creation and role permission configuration; the project management module is used to create and manage project information, including project name, communication parameters, network logo, SDK encryption configuration and reset configuration, allowing users to create and edit project information, and automatically test communication parameter connectivity before starting a task; The cache management module is used to create and update the filter list, record the delivery progress information and maximum delivery times of each single lamp controller to the system cache, and clear the invalid data in the cache after the migration task is completed; The log module is used to record the user operation information and single lamp controller feedback information during the migration operation, including the issuance of communication parameters, the issuance of reset instructions, and the modification of project information. It also supports filtering and querying historical logs by operation type, user name, and single lamp controller serial number; The communication interface module is used to establish a connection with the telecommunications IoT platform, push communication parameter configuration instructions to the telecommunications IoT platform, and monitor the feedback message of the single lamp controller to obtain the actual communication parameters.

7. The system for batch migration of single lamp controllers between platforms according to claim 6, characterized in that: The single-lamp controller information import module includes single-lamp controller information import, single-lamp controller information verification, single-lamp controller information persistence, and display of single-lamp controller information import results.

8. The system for batch migration of single lamp controllers between platforms according to claim 6, characterized in that: The log module includes a recording module and a query module; the recording module is used to record the user's operations in the system and the feedback information of the single-lamp controller; the query module is used to query the historical log according to the filtering conditions, and the filtering conditions include the operation type, user name and the serial number of the single-lamp controller.

9. The system for batch migration of single lamp controllers between platforms according to claim 6, characterized in that: The user management module includes the role permission allocation function. The roles include ordinary users and administrators. Ordinary users can only view and manage the projects they created, while administrators can edit all user information and project information.

Images