Intelligent cloud box device management and remote operation and maintenance method and system

Abstract

The application relates to the technical field of device management and control, and discloses an intelligent cloud box device management and remote operation and maintenance method and system.The method comprises the following steps: generating a dynamic identity code by hashing a cloud box hardware serial number, a firmware version and a registration timestamp, and generating a device instance identifier by indexing; generating a session key based on the instance identifier operation, and building a bidirectional encrypted communication channel; receiving device parameters through the encrypted channel, screening out a non-zero differential parameter sequence through time sequence difference; quantizing a parameter change amplitude and marking in stages, and forming a global event queue by removing duplicates and rearranging; analyzing operation and maintenance instructions in the queue, splitting fields and detecting mutual exclusion locks, and generating a conflict detection flag; when there is no conflict, encapsulating the instruction frame and encrypting and issuing the same, and updating a device operation snapshot according to a device receipt; and the application can improve the efficiency of intelligent cloud box device management and remote operation and maintenance.

Description

Technical Field

[0001] This invention relates to the field of equipment management technology, and in particular to a method and system for intelligent cloud box equipment management and remote operation and maintenance. Background Technology

[0002] Most existing smart cloud box operation and maintenance management solutions use fixed device identifiers to bind devices. This fixed device identity information makes them vulnerable to impersonation and access fraud. Communication links lack customized encryption mechanisms, and the operational data transmitted back by the devices is susceptible to leakage and tampering during transmission. All device operating parameters are directly uploaded to the server for storage and parsing, resulting in massive amounts of redundant parameters continuously consuming storage resources. Parameter anomaly identification lacks quantitative and tiered logic, fault data filtering and processing are time-consuming, and device status monitoring consumes a high amount of computing power.

[0003] The existing operation and maintenance (O&M) command delivery process lacks lock conflict verification for operation commands. This can easily lead to resource contention during concurrent multi-task O&M operations, causing command delivery failures, inconsistent device snapshot updates, and insufficient stability in remote O&M command execution. Furthermore, it makes it difficult to guarantee O&M processing efficiency in scenarios with centralized management of large numbers of cloud boxes. Therefore, improving the secure access capabilities and remote O&M processing efficiency of smart cloud box devices has become an urgent problem to be solved. Summary of the Invention

[0004] This invention provides a method and system for managing and remotely maintaining intelligent cloud box devices to solve the problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides a method for intelligent cloud box device management and remote operation and maintenance, comprising: 1. A method for managing and remotely maintaining a smart cloud box device, characterized in that the method includes: D1. Perform a hash operation on the device hardware serial number, firmware version number and first registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and use the dynamic device identity code as an index to generate the device instance identifier of the smart cloud box. D2. Based on the device instance identifier, generate session key data for the smart cloud box, and use the session key data to encrypt the communication link to establish a two-way encrypted channel for the smart cloud box. D3. Receive the return operation parameter vector of the smart cloud box through the bidirectional encrypted channel, and perform time-series differential comparison on the received vector to obtain the non-zero differential parameter sequence of the return operation parameter vector. D4. Map the intensity level of the non-zero difference parameter sequence to obtain the level label of the difference parameter sequence, and obtain the global event queue of the smart cloud box according to the association between the level label and the device instance identifier. D5. Parse the operation and maintenance instructions of the global event queue to obtain the opcode and operand of the operation and maintenance instructions, and perform mutual exclusion lock status bit detection on the opcode and operand to obtain the lock conflict detection flag bit of the operation and maintenance instructions. D6. Based on the lock conflict detection flag, obtain the native instruction frame data packet of the smart cloud box, and update the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet.

[0006] In a preferred embodiment, the step of performing a hash operation on the device hardware serial number, firmware version number, and first registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and using the dynamic device identity code as an index to generate a device instance identifier for the smart cloud box, includes: Obtain the device hardware serial number, firmware version number, and first registration timestamp of the smart cloud box; The device hardware serial number and the firmware version number are concatenated bit by bit to obtain the original registration certificate string of the smart cloud box; Based on the first registration timestamp, the original registration credential string is cyclically shifted and obfuscated to obtain the obfuscated registration data block of the smart cloud box; The identity fields of the obfuscated registration data block are aggregated to obtain the dynamic device identity code of the smart cloud box; The device identity code is bound to the dynamic device identity code to obtain the device instance identifier of the smart cloud box.

[0007] In a preferred embodiment, the step of generating session key data for the smart cloud box based on the device instance identifier, and using the session key data to encrypt the communication link to establish a two-way encrypted channel for the smart cloud box, includes: The device instance identifier and the first registration timestamp are byte-interleaved and mixed to obtain the hybrid credential data of the smart cloud box; Based on the low-order byte of the dynamic device identity code, the hybrid credential data is rearranged in reverse byte order to obtain the rearranged credential data of the smart cloud box. The session key data of the smart cloud box is obtained by performing nonlinear perturbation deduction on the rearranged credential data; Based on the session key data, the smart cloud box is encrypted to obtain a two-way encrypted channel for the smart cloud box.

[0008] In a preferred embodiment, the step of receiving the return operation parameter vector from the smart cloud box through the bidirectional encrypted channel, and performing a time-series differential comparison on the received vector to obtain the non-zero differential parameter sequence of the return operation parameter vector, includes: The encrypted data stream from the smart cloud box is received through the bidirectional encrypted channel. The encrypted data stream is validated by an integrity verification field to obtain the return operation parameter vector of the smart cloud box; Based on the device instance identifier, the previously stored operating parameter vector is retrieved as the parameter reference vector of the smart cloud box, and the difference between the returned operating parameter vector and the parameter reference vector is extracted to obtain the differential parameter sequence of the returned operating parameter vector. The differential parameter sequence is subjected to zero-value compression to obtain the non-zero differential parameter sequence of the returned running parameter vector.

[0009] In a preferred embodiment, the step of mapping the non-zero difference parameter sequence to intensity levels to obtain level labels for the difference parameter sequence, and obtaining the global event queue of the smart cloud box based on the association between the level labels and the device instance identifier, includes: Based on the device instance identifier, the dynamic device identity code, and the first registration timestamp, calculate the change amplitude value of the non-zero difference parameter sequence; The change amplitude value is matched with the preset intensity level numerical range to obtain the parameter change intensity level of the non-zero difference parameter sequence; Based on the intensity level of the parameter change and the device instance identifier, a temporary event record for the smart cloud box is generated. The temporary event record includes the device instance identifier, intensity level, and timestamp. The temporary event records are subjected to time repeatability determination to obtain the repeatability flag bit of the temporary event records; Based on the repetition flag, the temporary event records are screened and the retained temporary event records are used as the global event queue of the smart cloud box.

[0010] In a preferred embodiment, the formula for calculating the change amplitude value is as follows: ; in, The first of the non-zero difference parameter sequences Each change range value, The first in the non-zero difference parameter sequence One non-zero difference value, The low-order byte that identifies the device instance. This refers to the low-order byte of the dynamic device identification code. The least significant byte of the initial registration timestamp. This is a bitwise XOR operation.

[0011] In a preferred embodiment, parsing the operation and maintenance instructions of the global event queue to obtain the opcode and operands of the operation and maintenance instructions, and performing mutex lock status bit detection on the opcode and operands to obtain the lock conflict detection flag of the operation and maintenance instructions, includes: The protocol header of the operation and maintenance instruction data in the global event queue is decomposed to obtain the opcode and operands of the operation and maintenance instruction data; The opcode is split into high and low bytes to obtain the high byte and low byte of the opcode, and the high byte is used as the resource type index and the low byte is used as the resource instance index. Based on the resource type index and the resource instance index, the resource locator data of the operation and maintenance instruction is determined; Based on the resource locator data, obtain the lock status flag of the operation and maintenance instruction, wherein the lock status flag includes a read lock flag and a write lock flag; The lock status flag and the opcode are used to determine a conflict. If the write lock flag is locked and the opcode indicates a write operation, it is determined to be a conflict. Otherwise, it is determined to be a non-conflict, and the lock conflict detection flag of the operation and maintenance instruction is obtained.

[0012] In a preferred embodiment, the step of obtaining the lock status flag of the operation and maintenance instruction based on the resource locator data, wherein the lock status flag includes a read lock flag and a write lock flag, including: Based on the resource locator data, the lock status data array of the operation and maintenance instruction is bit-width aligned and addressed to obtain the lock byte address data of the operation and maintenance instruction; Based on the lock byte address data, the corresponding lock state byte data is read from the lock state data array; Based on the low-order bits in the resource locator data, determine the starting bit position of the maintenance instruction within the lock status byte data; Starting from the starting position, the read lock status bit data and write lock status bit data are extracted sequentially to obtain the lock status flag of the operation and maintenance instruction.

[0013] In a preferred embodiment, the step of obtaining the native instruction frame data packet of the smart cloud box based on the lock conflict detection flag, and updating the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet, includes: When the lock conflict detection flag indicates no conflict, the operation code and operands of the operation and maintenance instruction are encapsulated into the native instruction frame of the smart cloud box. The native instruction frame is sent to the smart cloud box through the bidirectional encrypted channel, and the execution confirmation frame returned by the smart cloud box is received. Update the running status snapshot corresponding to the device instance identifier based on the execution result code in the execution confirmation frame.

[0014] To address the aforementioned problems, the present invention also provides an intelligent cloud box device management and remote operation and maintenance system, the system comprising: The device dynamic identity generation module is used to perform hash calculation on the device hardware serial number, firmware version number and first registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and use the dynamic device identity code as an index to generate the device instance identifier of the smart cloud box. A two-way encrypted channel construction module is used to generate session key data for the smart cloud box based on the device instance identifier, and use the session key data to encrypt the communication link to establish a two-way encrypted channel for the smart cloud box. The parameter timing difference extraction module is used to receive the return operation parameter vector of the smart cloud box through the bidirectional encrypted channel, and perform timing difference comparison on the received vector to obtain the non-zero difference parameter sequence of the return operation parameter vector. The hierarchical event queue collection module is used to perform intensity level mapping on the non-zero difference parameter sequence to obtain the level label of the difference parameter sequence, and obtain the global event queue of the smart cloud box according to the association relationship between the level label and the device instance identifier. The operation and maintenance instruction lock conflict verification module is used to parse the operation and maintenance instructions in the global event queue, obtain the opcode and operand of the operation and maintenance instructions, and perform mutual exclusion lock status bit detection on the opcode and operand to obtain the lock conflict detection flag bit of the operation and maintenance instructions. The status snapshot update module is used to obtain the native instruction frame data packet of the smart cloud box based on the lock conflict detection flag, and update the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet.

[0015] Compared with the prior art, the present invention has the following beneficial effects: 1. This invention generates a dynamic device identity code using the hardware serial number, firmware version, and registration timestamp. This code, combined with multi-round data obfuscation and byte interleaving operations, constructs a dedicated session key. A bidirectional encrypted communication link is then established based on this key, achieving encrypted protection of communication data from the device access source. The encrypted channel ensures secure transmission of device operating parameters, guaranteeing the security and integrity of data interaction throughout the entire lifecycle of the smart cloud box. Simultaneously, it filters non-zero parameter data through time-series differential filtering, quantifies parameter variation amplitude using a custom formula, and classifies fault severity levels. This streamlines invalid monitoring data, reduces cloud data storage and computational overhead, and significantly improves the processing efficiency of device operating status monitoring.

[0016] 2. This invention adds a resource bit addressing and mutex lock conflict detection mechanism to the operation and maintenance commands, accurately identifies resource occupation conflicts for command reading and writing, avoids the problem of device command disorder caused by the concurrent issuance of multiple commands, and remotely issues and executes conflict-free commands after encapsulation, and updates the device operation status snapshot in real time based on the device feedback results, so as to realize the standardized issuance, execution and status synchronization of operation and maintenance commands, systematically implement remote automated operation and maintenance, and continuously optimize the execution efficiency of batch management and remote operation and maintenance of smart cloud boxes. Attached Figure Description

[0017] Figure 1 This is a flowchart illustrating a method for managing and remotely maintaining an intelligent cloud box device according to an embodiment of the present invention. Figure 2 A functional module diagram of an intelligent cloud box device management and remote operation and maintenance system provided in an embodiment of the present invention; The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0018] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0019] This application provides a method for managing and remotely maintaining smart cloud box devices. The executing entity of this method includes, but is not limited to, at least one of the following electronic devices that can be configured to execute the method provided in this application: a server, a terminal, etc. In other words, the method for managing and remotely maintaining smart cloud box devices can be executed by software or hardware installed on a terminal device or a server device. The server includes, but is not limited to, a single server, a server cluster, a cloud server, or a cloud server cluster. The server can be an independent server or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms.

[0020] Reference Figure 1 The diagram shown is a flowchart illustrating a method for managing and remotely maintaining a smart cloud box device according to an embodiment of the present invention. In this embodiment, the method for managing and remotely maintaining a smart cloud box device includes: D1. Perform a hash operation on the device hardware serial number, firmware version number and first registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and use the dynamic device identity code as an index to generate the device instance identifier of the smart cloud box. In this embodiment of the invention, the step of performing a hash operation on the device hardware serial number, firmware version number, and first registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and using the dynamic device identity code as an index to generate the device instance identifier of the smart cloud box, includes: Obtain the device hardware serial number, firmware version number, and first registration timestamp of the smart cloud box; The device hardware serial number and the firmware version number are concatenated bit by bit to obtain the original registration certificate string of the smart cloud box; Based on the first registration timestamp, the original registration credential string is cyclically shifted and obfuscated to obtain the obfuscated registration data block of the smart cloud box; The identity fields of the obfuscated registration data block are aggregated to obtain the dynamic device identity code of the smart cloud box; The device identity code is bound to the dynamic device identity code to obtain the device instance identifier of the smart cloud box.

[0021] The device's hardware serial number is permanently embedded in the main control storage chip of the smart cloud box. It is burned into the device at the factory and cannot be modified or replaced later. This single code uniquely binds to a single physical smart cloud box hardware unit. The firmware version number corresponds to the unique code of the firmware program currently installed and running on the smart cloud box. Each firmware version iteration generates a new version code to distinguish differences in program content. The first registration timestamp is the time sequence data uniformly recorded and stored by the platform at the moment when the smart cloud box first connects to the operation and maintenance service platform and completes the registration handshake interaction. The device hardware serial number, firmware version number, and first registration timestamp are all stored in binary big-endian format and are directly retrieved from the local storage area of ​​the smart cloud box and the platform's registration database. The original data content is completely retained without any deletion or modification, thus forming all the original basic data required for the subsequent generation of the identity code.

[0022] After extracting the complete binary bit sequence of the device hardware serial number and the complete binary bit sequence of the firmware version number, the original bit arrangement order of the two sets of data is kept constant. The complete bit content of the firmware version number is concatenated to the end of the bit content of the device hardware serial number to achieve a fixed bit-by-bit concatenation operation with the beginning and end connected. No extra padding bits are inserted or the original valid bits are removed. After concatenation, the complete binary string is integrated to form a continuous and uninterrupted complete binary string. The complete binary string obtained by integration is the original registration certificate string.

[0023] A fixed eight bits are selected as the uniform number of cyclic shift bits. Based on the first registration timestamp that has been collected, the shift reference is locked. A uniform left cyclic shift operation is performed on the original registration certificate string. The eight bits of data overflowing from the front of the original registration certificate string are filled into the empty bit positions at the end of the entire data string in the original order. After a single complete shift operation, the bit arrangement pattern inside the original registration certificate string is fixed and scrambled, and all original bit data is completely preserved without loss. The continuous binary data formed after this standardized shift and obfuscation process is the obfuscated registration data block.

[0024] The identity field aggregation defines three fixed categories of extracted fields: the hardware identity field corresponding to the hardware serial number, the firmware identifier field corresponding to the firmware version number, and the network access registration feature field corresponding to the first registration timestamp. All bit content corresponding to these three predetermined identity fields is precisely extracted from the obfuscated registration data block. Reserved padding bits that do not serve an identity identification function are removed. The selected bits of the three categories are then integrated and spliced ​​into a complete feature data stream according to their original order in the obfuscated registration data block. A complete hash operation is performed on the integrated feature data stream, and the SM3 national cryptographic hash algorithm is used to generate a fixed-length identifier data that uniquely corresponds to a single smart cloud box. This unique identifier data, produced by field aggregation and hash operation, is the dynamic device identity code.

[0025] The identity binding process executes a platform index solidification association operation, setting the generated dynamic device identity code as a unique index identifier. Within the platform's device file storage partition, this index identifier is locked one-to-one with the currently collected hardware serial number, firmware version information, and initial registration file information. Once the binding relationship is entered into the platform's device ledger, it cannot be arbitrarily released or changed, ensuring that one dynamic device identity code can only match all the registration file information corresponding to one smart cloud box. After the binding process is completed, a globally unique identification code is generated that is exclusive to the corresponding smart cloud box. This globally unique identification code is the device instance identifier.

[0026] The beneficial effect is that by relying on the unique hardware serial number, firmware version number and first registration timestamp of the device, multi-source data is spliced, shifted and obfuscated and fields are collected to generate a dynamic device identity code. Unlike the traditional fixed device ID, it can avoid the risk of counterfeit access caused by static device identification. By binding the dynamic identity code to generate a device instance identifier, the identity of a single smart cloud box device is globally uniquely bound, which improves the security of identity verification from the source of device registration and access, and provides a reliable identity index basis for subsequent session key generation and device data differentiation and management.

[0027] D2. Based on the device instance identifier, generate session key data for the smart cloud box, and use the session key data to encrypt the communication link to establish a two-way encrypted channel for the smart cloud box. In this embodiment of the invention, the step of generating session key data for the smart cloud box based on the device instance identifier, and using the session key data to encrypt the communication link to establish a two-way encrypted channel for the smart cloud box, includes: The device instance identifier and the first registration timestamp are byte-interleaved and mixed to obtain the hybrid credential data of the smart cloud box; Based on the low-order byte of the dynamic device identity code, the hybrid credential data is rearranged in reverse byte order to obtain the rearranged credential data of the smart cloud box. The session key data of the smart cloud box is obtained by performing nonlinear perturbation deduction on the rearranged credential data; Based on the session key data, the smart cloud box is encrypted to obtain a two-way encrypted channel for the smart cloud box.

[0028] The complete binary byte sequence corresponding to the device instance identifier and the complete binary byte sequence corresponding to the first registration timestamp are extracted. The byte interleaving and mixing adopts a fixed processing rule of alternating single bytes. The single byte is taken out from the device instance identifier byte sequence in turn, and then the single byte is taken out from the first registration timestamp byte sequence in a loop to complete the interleaving arrangement. After any set of original data bytes is completely consumed, the remaining bytes are uniformly continued at the end of the combined data. The storage content of the single byte and the value of the byte itself are not changed throughout the process. After the fixed alternating interleaving arrangement, they are integrated to form a continuous and complete byte combination data. The complete data formed after the byte interleaving and mixing process is the mixed voucher data.

[0029] The last eight consecutive bytes of the dynamic device identification code are uniformly and fixedly extracted as the low-order bytes for subsequent processing. Using these fixed eight bytes as the reference for arrangement, the byte reordering operation is carried out. Starting from the last storage byte of the mixed voucher data, the original byte arrangement positions are reversed one by one from back to front. The bytes that were originally at the back are moved to the storage positions at the front, and the bytes that were originally at the front are sequentially extended to the storage positions at the back. After all the bytes have been rearranged, the total number of bytes is kept exactly the same as the number of bytes in the original mixed voucher data without any increase or decrease. After the entire string of bytes is reversed, a new byte string is generated. The byte data obtained after the reordering is the rearranged voucher data.

[0030] The nonlinear perturbation deduction adopts a standardized processing method of fixed segmented misalignment replacement. The rearranged voucher data is evenly divided into three equal-length byte segments. The first segment byte and the second segment byte are selected to perform a fixed position byte content swap operation. The middle segment byte is changed sequentially according to the rule of fixed single-byte offset. After all segment replacement and position offset operations are completed, no additional bytes are added or deleted. After the fixed misalignment replacement processing, the original key data with the unique corresponding attribute of the device is obtained. The data finally formed after the nonlinear perturbation deduction processing is the session key data.

[0031] Based on the generated session key data, AES symmetric encryption is used to complete the overall encryption process across the entire link. The overall encryption of the entire link covers all communication data in the uplink and downlink transmission links between the smart cloud box and the operation and maintenance server. Uplink messages from the device to the platform to upload operating parameters and downlink messages from the platform to the device to issue operation and maintenance instructions are all included in the encryption coverage. The complete payload data inside the message and the control field in the message header are uniformly protected by the same session key. The communication interaction between the two ends follows the same set of encryption and decryption rules throughout the entire process. After the encryption deployment is implemented, bidirectional full-link encrypted data transmission is realized. Based on this encryption mode, a dedicated communication link capable of bidirectional secure data interaction is built. The communication link built according to the established encryption rules is the bidirectional encrypted channel.

[0032] The beneficial effects are that a unique session key is generated by interleaving device instance identifiers, first registration timestamp bytes, reversing the low-order bytes of dynamic device identity codes, and performing multi-layer operations with nonlinear perturbation. The key is deeply bound to the information of a single cloud box device, effectively avoiding the problem of key homogenization. Based on this key, a two-way encrypted channel is built to achieve full-link encryption protection for device uplink and downlink communication messages, preventing the theft and tampering of transmitted data, and improving the transmission security level of data interaction between the smart cloud box and the operation and maintenance platform.

[0033] D3. Receive the return operation parameter vector of the smart cloud box through the bidirectional encrypted channel, and perform time-series differential comparison on the received vector to obtain the non-zero differential parameter sequence of the return operation parameter vector. In this embodiment of the invention, the step of receiving the return operation parameter vector from the smart cloud box through the bidirectional encrypted channel, and performing a time-series differential comparison on the received vector to obtain the non-zero differential parameter sequence of the return operation parameter vector, includes: The encrypted data stream from the smart cloud box is received through the bidirectional encrypted channel. The encrypted data stream is validated by an integrity verification field to obtain the return operation parameter vector of the smart cloud box; Based on the device instance identifier, the previously stored operating parameter vector is retrieved as the parameter reference vector of the smart cloud box, and the difference between the returned operating parameter vector and the parameter reference vector is extracted to obtain the differential parameter sequence of the returned operating parameter vector. The differential parameter sequence is subjected to zero-value compression to obtain the non-zero differential parameter sequence of the returned running parameter vector.

[0034] The operation and maintenance server continuously monitors the data transmission port of the two-way encrypted channel. All the running data generated by the smart cloud box is packaged into an encrypted data stream and then transmitted unidirectionally to the operation and maintenance server through the established two-way encrypted channel. The server continuously captures the continuously transmitted data at the channel port, fully collects the encrypted content sent by the corresponding smart cloud box, and completes the full collection of the encrypted content.

[0035] The encrypted data stream contains a dedicated verification field. This solution uniformly uses the SHA verification method to complete the integrity verification field verification operation. The integrity verification field content stored at a fixed position at the end of the encrypted data stream is extracted. Based on the main text content of the entire encrypted data stream, a new verification content is regenerated according to the fixed data verification rules corresponding to SHA. The verification content generated on-site is compared with the original integrity verification field carried by the data stream. If the two contents are completely consistent, it is determined that the data stream has not been missing or tampered with. Then, the outer layer of encryption encapsulation content is stripped to decrypt and extract the original internal data. From the decrypted data body, the set of data related to the overall operation reported by the device in real time is separated and filtered. The data set obtained after verification and decryption is the return operation parameter vector.

[0036] Using the device instance identifier as the unique retrieval index, a targeted retrieval is initiated to the device parameter storage partition built into the server. The smart cloud box's operating parameters are reported in a fixed 5-second cycle. The cloud stores the baseline parameter vector at 5-second intervals. The complete historical operating parameter data, which was archived after the previous data report was completed, is retrieved from the dedicated storage area of ​​the corresponding smart cloud box. The retrieved historical parameter content is directly used as the parameter baseline vector. Each parameter content in the returned operating parameter vector is compared with the parameter content in the same position in the parameter baseline vector according to the parameter arrangement order. Parameters with differences between the two parameter contents are extracted, summarized, and integrated to form a continuous data sequence. The sequence composed of the summarized difference data is the differential parameter sequence.

[0037] Zero-value compression processing adopts a fixed processing rule of directly eliminating all parameter items with no change. It iterates through all stored parameter items in the differential parameter sequence, checks the numerical change of each parameter item, and directly eliminates the items with zero parameter values ​​in the sequence and does not retain them in the subsequent sequence. Only the items whose parameter values ​​have been verified to have changed are rearranged according to their original order. After eliminating invalid items and reorganizing, a new sequence is formed that only retains the changed data. The sequence obtained after eliminating zero-change data is the non-zero differential parameter sequence.

[0038] The beneficial effects are that by using a two-way encrypted channel to receive encrypted data streams and complete integrity verification, the original operating parameters are ensured to be safe and reliable. Then, by using time-series reference vector difference extraction and zero-value compression, only the changing parameters are retained. This eliminates the need for uploading all parameters, significantly reduces the amount of invalid data stored in the cloud and the computational overhead for parameter parsing, simplifies the amount of data for subsequent analysis and processing of abnormal parameters, and effectively improves the efficiency of cloud device operating status parsing.

[0039] D4. Map the intensity level of the non-zero difference parameter sequence to obtain the level label of the difference parameter sequence, and obtain the global event queue of the smart cloud box according to the association between the level label and the device instance identifier. In this embodiment of the invention, the step of mapping the non-zero difference parameter sequence to intensity levels to obtain level labels for the difference parameter sequence, and obtaining the global event queue of the smart cloud box based on the association between the level labels and the device instance identifier, includes: Based on the device instance identifier, the dynamic device identity code, and the first registration timestamp, calculate the change amplitude value of the non-zero difference parameter sequence; The change amplitude value is matched with the preset intensity level numerical range to obtain the parameter change intensity level of the non-zero difference parameter sequence; Based on the intensity level of the parameter change and the device instance identifier, a temporary event record for the smart cloud box is generated. The temporary event record includes the device instance identifier, intensity level, and timestamp. The temporary event records are subjected to time repeatability determination to obtain the repeatability flag bit of the temporary event records; Based on the repetition flag, the temporary event records are screened and the retained temporary event records are used as the global event queue of the smart cloud box.

[0040] The formula for calculating the magnitude of the change is as follows: ; in, The first of the non-zero difference parameter sequences Each change range value, The first in the non-zero difference parameter sequence One non-zero difference value, The low-order byte that identifies the device instance. This refers to the low-order byte of the dynamic device identification code. The least significant byte of the initial registration timestamp. This is a bitwise XOR operation.

[0041] The last eight consecutive bytes are extracted from the overall byte content of the device instance identifier as the corresponding low-order byte content. Simultaneously, the last eight consecutive bytes are extracted from the overall byte content of the dynamic device identity code as the corresponding low-order byte content, and the last eight consecutive bytes are extracted from the first registration timestamp byte data as the corresponding low-order byte content. The two sets of eight-byte data taken from the device instance identifier and the dynamic device identity code are XORed bit by bit to perform data conversion. The resulting byte data after conversion is uniformly converted into decimal numbers. The decimal numbers and non-zero difference values ​​are multiplied across the entire domain to obtain intermediate operation values. The intermediate operation values ​​are then accumulated with the decimal values ​​obtained from the conversion of the low-order bytes of the first registration timestamp. After completing the entire set of data conversion work for all non-zero difference entries, the final converted value of a single entry is the change range value of the corresponding position.

[0042] The corresponding value is taken from the data at the corresponding position within the non-zero difference parameter sequence. The original non-zero difference values ​​are uniformly converted to absolute values ​​to obtain the value of this item. It is generated by truncating the last eight consecutive bytes from the end of the complete byte string of the device instance identifier. It is generated by truncating the last eight consecutive bytes of the complete byte string of the dynamic device identity code. It is generated by extracting the last eight consecutive bytes from the complete byte string of the first registration timestamp. The first registration timestamp is uniformly recorded and stored by the cloud server during the initial network registration handshake stage of the smart cloud box. All three types of low-order bytes are stored in binary format and then uniformly converted into decimal integers, so that all data involved in the calculation adopt the same decimal numerical unit.

[0043] First to and The two sets of low-order byte raw binary data are XORed bit by bit. After the XOR operation, the resulting binary result is converted into a decimal integer. This integer is then compared with the absolute value of the decimal result. Multiplying decimal numbers yields an intermediate value, which is then summed and converted back to a decimal integer. The final result is generated by performing the accumulation operation. By relying on the unique three device identity information of the smart cloud box to correct the original differential data, the final change amplitude value is bound to the unique characteristics of a single device, eliminating the situation where the fluctuation amplitude of multiple smart cloud boxes with the same parameter is completely consistent, and providing a standardized amplitude basis for subsequent intensity level matching based on the bound device identity.

[0044] When the corresponding value increases positively, the intermediate operation value after the multiplication step also increases positively in sync. , , Assuming the three values ​​generated from the device's inherent registration information remain constant, the final generated The magnitude of the change synchronously follows and increases positively. When the corresponding value decreases in a positive direction, the intermediate calculated value decreases in a positive direction simultaneously. The magnitude of the change synchronously follows and shows a positive decreasing change. , , The corresponding values ​​are fixed and generated from the equipment's factory and initial registration information, and will not fluctuate with changes in the equipment's operating parameters.

[0045] The operation and maintenance platform pre-defines four fixed numerical boundary points and presets four fixed intensity ranges. For example, 0≤A<0.2 is a Level 1 normal event, 0.2≤A<0.5 is a Level 2 minor abnormal event, 0.5≤A<0.8 is a Level 3 moderate fault event, and 0.8≤A≤1 is a Level 4 severe fault event. Based on the boundary points, four independent numerical ranges that do not overlap are formed. Each independent numerical range is uniquely bound to an exclusive intensity level identifier. The generated change amplitude values ​​are retrieved one by one, and the actual value of each change amplitude value is compared with the four preset numerical ranges in turn. If the change amplitude value falls into any of the predetermined ranges, it is directly bound to the exclusive level identifier corresponding to that range. After binding, an identifier that can represent the degree of parameter fluctuation is generated. The identifier generated based on the range matching rules is the parameter change intensity level.

[0046] The system retrieves the matched parameter change intensity level and the corresponding smart cloud box's unique device instance identifier. Simultaneously, it captures the system's standard time-series data corresponding to the moment the data processing is completed. The three pieces of information are integrated and filled into the standardized record carrier according to a fixed storage layout format. The standardized record carrier is divided into three independent storage partitions to store the device instance identifier, intensity level, and timestamp corresponding to the collection time, respectively. After all the information is neatly entered, a complete single record is formed. This record, which integrates multiple types of key information, is the temporary event record.

[0047] The time repetition judgment is uniformly limited to the verification rules for the same smart cloud box reporting the same intensity event repeatedly within a fixed time of 60 seconds with the same monitoring parameters. The corresponding device is identified by the device instance identifier recorded in the temporary event record. Then, the intensity level of parameter changes carried in the record is extracted to determine the event type. The platform's event cache is searched for archived historical temporary event records of the same device and intensity within a 60-second time range. When a matching content is found, the record is marked as having been reported repeatedly. If no matching historical record is found throughout the search, the record is marked as a new reported event. When the same device, the same monitoring parameter, and the same intensity level are reported repeatedly within 60 seconds of natural time, only the first generated temporary event record is retained, and the remaining duplicate records are directly discarded. A fixed binary classification label is generated based on the result of the search for whether it is repeated or not. The label generated by this distinction between repeated status is the repeatability flag.

[0048] The duplicate flag is used to determine two fixed results. When the flag indicates a duplicate, the corresponding temporary event record is discarded and not included in the subsequent queue. When the flag indicates a new event, the entire temporary event record is retained. All generated temporary event records are traversed one by one according to the above filtering rules. All valid temporary event records after filtering are arranged and integrated in the order of their generation. After the chronological arrangement is completed, a complete event summary data is formed. The summary data obtained after duplicate removal and chronological regularization is the global event queue.

[0049] The beneficial effects are that by relying on the device's unique identification data and combining it with a custom formula to quantify the range of parameter changes, parameter fluctuations can be quantified and graded. Then, redundant reporting records in a short period of time are filtered out by repeating events, and a global event queue is generated by summarizing them according to the specifications. This not only realizes the hierarchical and classified management of faults and anomalies and reduces the system resources occupied by repeating events, but also facilitates the orderly scheduling of operation and maintenance tasks by the operation and maintenance platform according to the anomaly level, and optimizes the efficiency of batch cloud box operation and maintenance scheduling.

[0050] D5. Parse the operation and maintenance instructions of the global event queue to obtain the opcode and operand of the operation and maintenance instructions, and perform mutual exclusion lock status bit detection on the opcode and operand to obtain the lock conflict detection flag bit of the operation and maintenance instructions.

[0051] In this embodiment of the invention, parsing the operation and maintenance instructions of the global event queue to obtain the opcode and operands of the operation and maintenance instructions, and performing mutual exclusion lock status bit detection on the opcode and operands to obtain the lock conflict detection flag of the operation and maintenance instructions, includes: The protocol header of the operation and maintenance instruction data in the global event queue is decomposed to obtain the opcode and operands of the operation and maintenance instruction data; The opcode is split into high and low bytes to obtain the high byte and low byte of the opcode, and the high byte is used as the resource type index and the low byte is used as the resource instance index. Based on the resource type index and the resource instance index, the resource locator data of the operation and maintenance instruction is determined; Based on the resource locator data, obtain the lock status flag of the operation and maintenance instruction, wherein the lock status flag includes a read lock flag and a write lock flag; The lock status flag and the opcode are used to determine a conflict. If the write lock flag is locked and the opcode indicates a write operation, it is determined to be a conflict. Otherwise, it is determined to be a non-conflict, and the lock conflict detection flag of the operation and maintenance instruction is obtained.

[0052] The step involves obtaining the lock status flag of the operation and maintenance instruction based on the resource locator data. The lock status flag includes a read lock flag and a write lock flag, including: Based on the resource locator data, the lock status data array of the operation and maintenance instruction is bit-width aligned and addressed to obtain the lock byte address data of the operation and maintenance instruction; Based on the lock byte address data, the corresponding lock state byte data is read from the lock state data array; Based on the low-order bits in the resource locator data, determine the starting bit position of the maintenance instruction within the lock status byte data; Starting from the starting position, the read lock status bit data and write lock status bit data are extracted sequentially to obtain the lock status flag of the operation and maintenance instruction.

[0053] According to the fixed splitting boundaries preset in the operation and maintenance communication protocol, the protocol header of a single operation and maintenance instruction data stored in the global event queue is split. The data is split along the fixed separation position between the protocol header and the instruction body content. The data in the protocol header is directly discarded and the valid instruction body content is retained. Then, a second split is performed according to the fixed field boundaries within the instruction body. After splitting, the content used to identify the operation type and the content used to fill in the control parameters are separated. The content obtained from the split to identify the operation type is the opcode, and the content obtained from the split to fill in the control parameters is the operand.

[0054] The opcode's complete byte content is uniformly divided into two single-byte segments. The first byte is designated as the resource type index, with all values ​​falling within a fixed range of 0 to 255. The second byte is designated as the resource instance index, also with all values ​​falling within a fixed range of 0 to 255. Both types of indexes are stored according to their defined value ranges. After splitting, the resource type index corresponding to the higher byte and the resource instance index corresponding to the lower byte are obtained.

[0055] The byte content of the resource type index is arranged at the beginning of the data, and the byte content of the resource instance index is followed by the end to complete the splicing and integration, forming a continuous and complete exclusive identification data. This complete identification data generated by splicing and integrating the two types of indexes is the resource locator data.

[0056] Bit-width aligned addressing is performed based on resource locator data. The lock state data array adopts a regular array architecture with a uniform eight-byte storage unit. All storage units inside the array are arranged in natural ascending order to store lock information corresponding to various resources. Bit-width aligned addressing matches the total number of complete bits of the resource locator with the fixed bit length of a single array unit. Excess bits are discarded and insufficient bits are padded with zeros to achieve uniform bit width alignment. After alignment, the corresponding storage location number inside the array is mapped out. The content of the storage location number obtained by this mapping is the lock byte address data.

[0057] Based on the already determined lock byte address data, directly jump to the corresponding storage unit position inside the lock state data array, and completely read all the byte content stored inside the array unit. The completely read and obtained unit byte content is the lock state byte data. In the single byte storage space of the lock state, bit 0 is defined as the read lock flag bit, bit 1 is defined as the write lock flag bit, and the remaining bits are reserved for future use.

[0058] The last three fixed bits of the resource locator are extracted as position reference information. The starting extraction point in the bit arrangement order inside the lock status byte data is determined by referring to the binary conversion value corresponding to these three bits. The point obtained by positioning based on the low-order bits is the starting position of the lock flag reading.

[0059] Starting from the locked start position, two adjacent independent bits are extracted sequentially. The first bit is fixedly defined as the read lock status bit data, and the second bit is fixedly defined as the write lock status bit data. The extracted bit data from the two positions are integrated to form a matching identification information. This identification information formed by integrating the two bit data is the lock status flag.

[0060] Based on the original judgment rules, two types of fixed conflict judgment logic are added. When the lock status flags corresponding to any two instructions are marked as read lock, a resource preemption conflict is determined to be triggered. When a single instruction carries a read lock flag and another instruction carries a write lock flag and the target resources are the same, a conflict is also determined to be triggered. The original established rule of determining conflict by combining write lock locking with write operation is retained. If any one of the three judgment conditions is met, a lock conflict detection flag representing a conflict is generated. If none of the three conditions are met, a lock conflict detection flag corresponding to no conflict is generated.

[0061] The beneficial effects are that by disassembling and splitting the operation and maintenance instructions and accurately locating the resource index, and combining bit-width aligned addressing to quickly extract the lock status flag, the system can accurately detect instruction lock conflicts, effectively avoid read and write conflicts on the same cloud box device resources caused by multiple concurrent operation and maintenance instructions, ensure the orderly execution of operation and maintenance operations, prevent instruction execution abnormalities caused by device resource competition, and improve the concurrency stability and operational reliability of the remote operation and maintenance system.

[0062] D6. Based on the lock conflict detection flag, obtain the native instruction frame data packet of the smart cloud box, and update the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet.

[0063] In this embodiment of the invention, the step of obtaining the native instruction frame data packet of the smart cloud box based on the lock conflict detection flag, and updating the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet, includes: When the lock conflict detection flag indicates no conflict, the operation code and operands of the operation and maintenance instruction are encapsulated into the native instruction frame of the smart cloud box. The native instruction frame is sent to the smart cloud box through the bidirectional encrypted channel, and the execution confirmation frame returned by the smart cloud box is received. Update the running status snapshot corresponding to the device instance identifier based on the execution result code in the execution confirmation frame.

[0064] The lock conflict detection flag is fixedly divided into two types of identification content. The subsequent encapsulation operation is initiated only when the flag content is the fixed identification character corresponding to the non-conflict. According to the preset fixed frame header first and frame tail last arrangement format, the operation code content obtained by splitting the operation and maintenance instructions is placed in the fixed storage area between the frame header and frame tail. The operands are then arranged in a regular manner after the operation code. After all fields are assembled according to the predetermined arrangement rules, a complete frame structure data is formed. The assembled complete frame structure data is the original instruction frame.

[0065] Based on the previously established end-to-end AES encrypted bidirectional encrypted channel, the native command frame is transmitted. The server sends the formed native command frame to the channel transmission port, and the message is transmitted through the uplink and downlink of the encrypted channel. The smart cloud box receives the data transmitted through the link and completes the decryption process. After the device completes the corresponding operation and maintenance action according to the command content, it generates a feedback message. The feedback message is transmitted back to the operation and maintenance server through the uplink of the channel. The server completely captures the content of the returned feedback message. The feedback message returned by the device and completely received by the server is the execution confirmation frame.

[0066] The execution result code uniformly adopts a three-digit decimal fixed encoding rule. Different operation and maintenance execution results are matched with unique coded characters that are not repeated. Relying on the device instance identifier as a unique retrieval index, it is directed to the server snapshot storage partition. The running status snapshot uniformly adopts a field-partitioned storage architecture. The snapshot is divided into three independent storage spaces: hardware running partition, firmware running partition, and parameter running partition. The execution result code stored in the fixed field position inside the execution confirmation frame is extracted. The historical storage data in the corresponding partition is modified item by item according to the execution status corresponding to the code. The overall snapshot update operation is completed after all the corresponding field contents have been rewritten.

[0067] The beneficial effects are that the original instruction frame is encapsulated and issued only after there is no lock conflict, the instruction is transmitted securely through the encrypted channel, and the device status snapshot is synchronized in real time by combining the execution results returned by the device. This avoids the problem of failure in issuing conflicting instructions, realizes closed-loop management of operation and maintenance instructions and real-time synchronization of device status, and improves the accuracy and timeliness of remote operation and maintenance of a large number of smart cloud boxes.

[0068] like Figure 2 The diagram shown is a functional module diagram of an intelligent cloud box device management and remote operation and maintenance system provided in an embodiment of the present invention.

[0069] The intelligent cloud box device management and remote operation and maintenance system 100 described in this invention can be installed in an electronic device. Depending on the functions implemented, the intelligent cloud box device management and remote operation and maintenance system 100 may include a device dynamic identity generation module 101, a two-way encrypted channel construction module 102, a parameter timing difference extraction module 103, a hierarchical event queue collection module 104, an operation and maintenance command lock conflict verification module 105, and a status snapshot update module 106. The modules described in this invention can also be referred to as units, which are a series of computer program segments that can be executed by the processor of an electronic device and can perform a fixed function, stored in the memory of the electronic device.

[0070] In this embodiment, the functions of each module / unit are as follows: The device dynamic identity generation module 101 is used to perform a hash operation on the device hardware serial number, firmware version number and first registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and use the dynamic device identity code as an index to generate the device instance identifier of the smart cloud box. The bidirectional encrypted channel construction module 102 is used to generate session key data of the smart cloud box according to the device instance identifier, and use the session key data to encrypt the communication link to establish a bidirectional encrypted channel of the smart cloud box. The parameter timing difference extraction module 103 is used to receive the return operation parameter vector of the smart cloud box through the bidirectional encrypted channel, and perform timing difference comparison on the received vector to obtain the non-zero difference parameter sequence of the return operation parameter vector. The hierarchical event queue collection module 104 is used to perform intensity level mapping on the non-zero difference parameter sequence to obtain the level label of the difference parameter sequence, and obtain the global event queue of the smart cloud box according to the association relationship between the level label and the device instance identifier. The operation and maintenance instruction lock conflict verification module 105 is used to parse the operation and maintenance instructions in the global event queue, obtain the operation code and operands of the operation and maintenance instructions, and perform mutual exclusion lock status bit detection on the operation code and operands to obtain the lock conflict detection flag bit of the operation and maintenance instructions. The state snapshot update module 106 is used to obtain the native instruction frame data packet of the smart cloud box according to the lock conflict detection flag, and update the running state snapshot data corresponding to the device instance identifier according to the native instruction frame data packet.

[0071] In the several embodiments provided by this invention, it should be understood that the disclosed methods and systems can be implemented in other ways. For example, the system embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may be used in actual implementation.

[0072] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0073] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in the form of hardware plus software functional modules.

[0074] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the present invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the present invention.

[0075] This application embodiment can acquire and process relevant data based on artificial intelligence technology. Artificial intelligence is the theory, method, technology, and application system that uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, perceive the environment, acquire knowledge, and use that knowledge to obtain optimal results.

[0076] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.

Claims

1. A method for managing and remotely maintaining intelligent cloud box devices, characterized in that, The method includes: D1. Perform a hash operation on the device hardware serial number, firmware version number, and initial registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and use the dynamic device identity code as an index to generate the device instance identifier of the smart cloud box, including: Obtain the device hardware serial number, firmware version number, and first registration timestamp of the smart cloud box; The device hardware serial number and the firmware version number are concatenated bit by bit to obtain the original registration certificate string of the smart cloud box; Based on the first registration timestamp, the original registration credential string is cyclically shifted and obfuscated to obtain the obfuscated registration data block of the smart cloud box; The identity fields of the obfuscated registration data block are aggregated to obtain the dynamic device identity code of the smart cloud box; The device identity code is bound to the dynamic device identity code to obtain the device instance identifier of the smart cloud box; D2. Based on the device instance identifier, generate session key data for the smart cloud box, and use the session key data to encrypt the communication link to establish a two-way encrypted channel for the smart cloud box, including: The device instance identifier and the first registration timestamp are byte-interleaved and mixed to obtain the hybrid credential data of the smart cloud box; Based on the low-order byte of the dynamic device identity code, the hybrid credential data is rearranged in reverse byte order to obtain the rearranged credential data of the smart cloud box. The session key data of the smart cloud box is obtained by performing nonlinear perturbation deduction on the rearranged credential data; Based on the session key data, the smart cloud box is encrypted to obtain a two-way encrypted channel for the smart cloud box; D3. Receive the return operation parameter vector of the smart cloud box through the bidirectional encrypted channel, and perform time-series differential comparison on the received vector to obtain the non-zero differential parameter sequence of the return operation parameter vector. D4. Map the intensity level of the non-zero difference parameter sequence to obtain the level label of the difference parameter sequence, and obtain the global event queue of the smart cloud box according to the association between the level label and the device instance identifier. D5. Parse the operation and maintenance instructions of the global event queue to obtain the opcode and operands of the operation and maintenance instructions, and perform mutex lock status bit detection on the opcode and operands to obtain the lock conflict detection flag of the operation and maintenance instructions, including: The protocol header of the operation and maintenance instruction data in the global event queue is decomposed to obtain the opcode and operands of the operation and maintenance instruction data; The opcode is split into high and low bytes to obtain the high byte and low byte of the opcode, and the high byte is used as the resource type index and the low byte is used as the resource instance index. Based on the resource type index and the resource instance index, the resource locator data of the operation and maintenance instruction is determined; Based on the resource locator data, obtain the lock status flag of the operation and maintenance instruction, wherein the lock status flag includes a read lock flag and a write lock flag; The lock status flag and the opcode are used to determine a conflict. If the write lock flag is locked and the opcode indicates a write operation, it is determined to be a conflict. Otherwise, it is determined to be a no-conflict operation, and the lock conflict detection flag of the operation and maintenance instruction is obtained. D6. Based on the lock conflict detection flag, obtain the native instruction frame data packet of the smart cloud box, and update the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet.

2. The method for managing and remotely maintaining an intelligent cloud box device as described in claim 1, characterized in that, The step of receiving the return operation parameter vector from the smart cloud box through the bidirectional encrypted channel, and performing a time-series differential comparison on the received vector to obtain the non-zero differential parameter sequence of the return operation parameter vector, includes: The encrypted data stream from the smart cloud box is received through the bidirectional encrypted channel. The encrypted data stream is validated by an integrity verification field to obtain the return operation parameter vector of the smart cloud box; Based on the device instance identifier, the previously stored operating parameter vector is retrieved as the parameter reference vector of the smart cloud box, and the difference between the returned operating parameter vector and the parameter reference vector is extracted to obtain the differential parameter sequence of the returned operating parameter vector. The differential parameter sequence is subjected to zero-value compression to obtain the non-zero differential parameter sequence of the returned running parameter vector.

3. The method for managing and remotely maintaining a smart cloud box device as described in claim 1, characterized in that, The process of mapping the non-zero difference parameter sequence to intensity levels to obtain level labels for the difference parameter sequence, and obtaining the global event queue of the smart cloud box based on the association between the level labels and the device instance identifier, includes: Based on the device instance identifier, the dynamic device identity code, and the first registration timestamp, calculate the change amplitude value of the non-zero difference parameter sequence; The change amplitude value is matched with the preset intensity level numerical range to obtain the parameter change intensity level of the non-zero difference parameter sequence; Based on the intensity level of the parameter change and the device instance identifier, a temporary event record for the smart cloud box is generated. The temporary event record includes the device instance identifier, intensity level, and timestamp. The temporary event records are subjected to time repeatability determination to obtain the repeatability flag bit of the temporary event records; Based on the repetition flag, the temporary event records are screened and the retained temporary event records are used as the global event queue of the smart cloud box.

4. The method for managing and remotely maintaining an intelligent cloud box device as described in claim 3, characterized in that, The formula for calculating the magnitude of the change is as follows: ； in, This represents the i-th variation magnitude value of the non-zero difference parameter sequence. Let i be the i-th non-zero difference value in the non-zero difference parameter sequence. The low-order byte that identifies the device instance. This refers to the low-order byte of the dynamic device identification code. The least significant byte of the initial registration timestamp. This is a bitwise XOR operation.

5. The method for intelligent cloud box device management and remote operation and maintenance as described in claim 1, characterized in that, The step involves obtaining the lock status flag of the operation and maintenance instruction based on the resource locator data. The lock status flag includes a read lock flag and a write lock flag, including: Based on the resource locator data, the lock status data array of the operation and maintenance instruction is bit-width aligned and addressed to obtain the lock byte address data of the operation and maintenance instruction; Based on the lock byte address data, the corresponding lock state byte data is read from the lock state data array; Based on the low-order bits in the resource locator data, determine the starting bit position of the maintenance instruction within the lock status byte data; Starting from the starting position, the read lock status bit data and write lock status bit data are extracted sequentially to obtain the lock status flag of the operation and maintenance instruction.

6. The method for managing and remotely maintaining an intelligent cloud box device as described in claim 1, characterized in that, The step of obtaining the native instruction frame data packet of the smart cloud box based on the lock conflict detection flag, and updating the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet, includes: When the lock conflict detection flag indicates no conflict, the operation code and operands of the operation and maintenance instruction are encapsulated into the native instruction frame of the smart cloud box. The native instruction frame is sent to the smart cloud box through the bidirectional encrypted channel, and the execution confirmation frame returned by the smart cloud box is received. Update the running status snapshot corresponding to the device instance identifier based on the execution result code in the execution confirmation frame.

7. A smart cloud box device management and remote operation and maintenance system, characterized in that, The system for implementing the intelligent cloud box device management and remote operation and maintenance method according to claim 1 includes: The device dynamic identity generation module is used to perform a hash operation on the device hardware serial number, firmware version number, and first registration timestamp of the smart cloud box to obtain the dynamic device identity code of the smart cloud box, and use the dynamic device identity code as an index to generate a device instance identifier for the smart cloud box, including: Obtain the device hardware serial number, firmware version number, and first registration timestamp of the smart cloud box; The device hardware serial number and the firmware version number are concatenated bit by bit to obtain the original registration certificate string of the smart cloud box; Based on the first registration timestamp, the original registration credential string is cyclically shifted and obfuscated to obtain the obfuscated registration data block of the smart cloud box; The identity fields of the obfuscated registration data block are aggregated to obtain the dynamic device identity code of the smart cloud box; The device identity code is bound to the dynamic device identity code to obtain the device instance identifier of the smart cloud box; A two-way encrypted channel construction module is used to generate session key data for the smart cloud box based on the device instance identifier, and to encrypt the communication link using the session key data to establish a two-way encrypted channel for the smart cloud box, including: The device instance identifier and the first registration timestamp are byte-interleaved and mixed to obtain the hybrid credential data of the smart cloud box; Based on the low-order byte of the dynamic device identity code, the hybrid credential data is rearranged in reverse byte order to obtain the rearranged credential data of the smart cloud box. The session key data of the smart cloud box is obtained by performing nonlinear perturbation deduction on the rearranged credential data; Based on the session key data, the smart cloud box is encrypted to obtain a two-way encrypted channel for the smart cloud box; The parameter timing difference extraction module is used to receive the return operation parameter vector of the smart cloud box through the bidirectional encrypted channel, and perform timing difference comparison on the received vector to obtain the non-zero difference parameter sequence of the return operation parameter vector. The hierarchical event queue collection module is used to perform intensity level mapping on the non-zero difference parameter sequence to obtain the level label of the difference parameter sequence, and obtain the global event queue of the smart cloud box according to the association relationship between the level label and the device instance identifier. The operation and maintenance instruction lock conflict verification module is used to parse the operation and maintenance instructions in the global event queue, obtain the opcode and operands of the operation and maintenance instructions, and perform mutual exclusion lock status bit detection on the opcode and operands to obtain the lock conflict detection flag bits of the operation and maintenance instructions, including: The protocol header of the operation and maintenance instruction data in the global event queue is decomposed to obtain the opcode and operands of the operation and maintenance instruction data; The opcode is split into high and low bytes to obtain the high byte and low byte of the opcode, and the high byte is used as the resource type index and the low byte is used as the resource instance index. Based on the resource type index and the resource instance index, the resource locator data of the operation and maintenance instruction is determined; Based on the resource locator data, obtain the lock status flag of the operation and maintenance instruction, wherein the lock status flag includes a read lock flag and a write lock flag; The lock status flag and the opcode are used to determine a conflict. If the write lock flag is locked and the opcode indicates a write operation, it is determined to be a conflict. Otherwise, it is determined to be a no-conflict operation, and the lock conflict detection flag of the operation and maintenance instruction is obtained. The status snapshot update module is used to obtain the native instruction frame data packet of the smart cloud box based on the lock conflict detection flag, and update the running status snapshot data corresponding to the device instance identifier based on the native instruction frame data packet.

Images