Cloud edge collaborative operation and maintenance method and system

Abstract

The invention provides a cloud edge collaborative operation and maintenance method and system, which can realize high-efficiency encryption of a large-volume troubleshooting script in a full path of pre-diagnosis, troubleshooting script, accompanying issuing and customer receipt. Client identity and script integrity strong authentication; the compliance requirement that the trusteeship does not see the client content is met, and the safety and troubleshooting efficiency of remote operation and maintenance are improved.

Description

Technical Field

[0001] This invention relates to the field of collaborative operation and maintenance technology of data center power environment and network security, and in particular to a cloud-edge collaborative operation and maintenance method and system. Background Technology

[0002] Current managed operations and maintenance systems mostly rely on threshold-based monitoring and alerts, which have the following drawbacks: 1. Traditional monitoring alarms only provide notifications of 'parameter exceeding limits', and customers still need to diagnose and troubleshoot the faults themselves; 2. The phone / text messages are brief and cannot include detailed troubleshooting steps with pictures and text, resulting in a high rate of customer error. 3. Although the hosting provider has access to the on-duty data, the diagnostic conclusions are not issued along with the alarms as an executable troubleshooting package, resulting in poor closed-loop capability.

[0003] Some solutions attempt to introduce pre-diagnostic and executable troubleshooting mechanisms, but these rely on plaintext SMS or email alerts and troubleshooting steps, exposing the content and making it vulnerable to interception or tampering by man-in-the-middle attacks, leading to operational errors. Simple TLS (Transport Layer Security) only protects the transmission channel and cannot ensure the confidentiality and integrity of content during terminal caching and data storage. Asymmetric encryption has high computational overhead and is unsuitable for encrypting large video / image content. Symmetric encryption lacks identity binding, making key distribution difficult. Therefore, there is an urgent need for a new cloud-edge collaborative operation and maintenance method that integrates hybrid encryption mechanisms on top of pre-diagnostic and on-the-go troubleshooting solutions to achieve "efficient encryption of large content + strong identity authentication." Summary of the Invention

[0004] In view of this, the purpose of this invention is to provide a cloud-edge collaborative operation and maintenance method and system, so as to integrate the high efficiency of symmetric encryption and the strong identity authentication of asymmetric encryption into the business closed loop, and realize the end-to-end encryption of data in transmission, storage and display and the end-to-end traceability.

[0005] In a first aspect, embodiments of the present invention provide a cloud-edge collaborative operation and maintenance method, the method comprising: acquiring customer-side data from a remote customer side, and transmitting the customer-side data to a managed operation and maintenance cloud platform after real-time stream encryption; wherein, the customer-side data includes: data from a data center power and environment monitoring system and / or sensor data; the managed operation and maintenance cloud platform receives the customer-side data and outputs at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data; a follow-up solution generator of the managed operation and maintenance cloud platform generates a follow-up solution for each fault root cause based on the troubleshooting script number, and determines an original solution based on the follow-up solution for each fault root cause; the managed operation and maintenance cloud platform randomly generates a symmetric key, encrypts the original solution using the symmetric key to obtain ciphertext, and uses the customer's public key... The system encrypts the symmetric key, stores the ciphertext and the encrypted symmetric key, clears the original symmetric key, and generates a script hash and a root cause hash. The managed operations and maintenance cloud platform uses the troubleshooting script number, the client terminal number, and the time duration as a one-time password seed. This one-time password seed is truncated into multiple digits and sent via SMS to the client terminal. The SMS message includes text, a short link, and multiple digits. The user opens a mini-program via the short link on the client terminal and enters the multiple digits for verification. If the verification is successful, the client terminal downloads the ciphertext and the encrypted symmetric key from the managed operations and maintenance cloud platform. The client decrypts the encrypted symmetric key using their private key to obtain the original symmetric key, and then decrypts the ciphertext using the original symmetric key to obtain the original solution.

[0006] In an optional embodiment of this application, the step of transmitting the client-side data to the managed operation and maintenance cloud platform after real-time streaming encryption includes: encrypting the client-side data in real-time using a Galois Authentication Counter encryption mode based on Transport Layer Security (TLS) and Advanced Encryption Standard (AES) 256-bit; and transmitting the encrypted client-side data to the managed operation and maintenance cloud platform.

[0007] In an optional embodiment of this application, the step of the managed operation and maintenance cloud platform receiving customer-side data and outputting at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data includes: the managed operation and maintenance cloud platform receiving customer-side data and inputting the customer-side data into the pre-diagnostic engine built into the managed operation and maintenance cloud platform; the causal model of the pre-diagnostic engine performs causal relationship reasoning based on the alarm code, device model, and data value corresponding to the customer-side data, and outputs at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data.

[0008] In an optional embodiment of this application, after the step of inputting customer-side data into the pre-diagnostic engine built into the managed operation and maintenance cloud platform, the method further includes: the pre-diagnostic engine accessing the customer-side data into the abnormal sample library and constructing a causal model based on the trained fault chain knowledge graph.

[0009] In an optional embodiment of this application, the aforementioned managed operation and maintenance cloud platform pre-stores a script template library, which includes: troubleshooting steps in text, image, and short video formats for each type of root cause of failure; the accompanying solution generator of the managed operation and maintenance cloud platform generates an accompanying solution for each root cause of failure based on the troubleshooting script number, including: the accompanying solution generator of the managed operation and maintenance cloud platform calls the corresponding troubleshooting steps from the script template library based on the troubleshooting script number as the accompanying solution for each root cause of failure.

[0010] In an optional embodiment of this application, after the above-mentioned client terminal opens the mini-program via a short link and enters multiple digits into the mini-program for verification, the method further includes: if the verification fails, the managed operation and maintenance cloud platform resends the multiple digits to the client terminal.

[0011] In an optional embodiment of this application, after the step of decrypting the ciphertext with the symmetric key before encryption to obtain the original scheme, the method further includes: the client terminal playing the original scheme through memory decoding.

[0012] In optional embodiments of this application, the above method further includes: the user clicking a designated button in the mini-program via a client terminal; the mini-program digitally signing the completion flag, timestamp, and script hash to generate a signature file; the client terminal transmitting the signature file and the current client-side data to the managed operation and maintenance cloud platform; the managed operation and maintenance cloud platform verifying the signature file and determining whether the remote client-side has returned to normal based on the current client-side data; if the signature file verification is successful and the remote client-side has returned to normal, the managed operation and maintenance cloud platform closing the alarm work order; if the signature file verification fails or the remote client-side has not returned to normal, the managed operation and maintenance cloud platform re-outputting at least one fault root cause probability and troubleshooting script number corresponding to the client-side data.

[0013] In optional embodiments of this application, the above method further includes: the managed operation and maintenance cloud platform packaged the script hash, root cause hash, encrypted symmetric key and signature file, and called the timestamp service interface to generate a timestamp certificate; the managed operation and maintenance cloud platform stored the timestamp certificate and hash package in the platform database.

[0014] Secondly, embodiments of the present invention also provide a cloud-edge collaborative operation and maintenance system, comprising: a data acquisition and transmission module, used to acquire customer-side data from a remote customer side, and transmit the customer-side data to a managed operation and maintenance cloud platform after real-time stream encryption; wherein, the customer-side data includes: data from a data center power and environment monitoring system and / or sensor data; a pre-diagnosis module, used by the managed operation and maintenance cloud platform to receive customer-side data, and output at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data; a random solution generation module, used by the managed operation and maintenance cloud platform's accompanying solution generator to generate accompanying solutions for each fault root cause based on the troubleshooting script number, and to determine the original solution based on the accompanying solutions for each fault root cause; and a hybrid encryption module, used by the managed operation and maintenance cloud platform to randomly generate a symmetric key, and to encrypt the original solution using the symmetric key to obtain ciphertext, which is then used by the customer-side cloud platform. The system uses a public key to encrypt the symmetric key, stores the ciphertext and the encrypted symmetric key, clears the unencrypted symmetric key, and generates a script hash and a root cause hash. A text message push module is used by the managed operations and maintenance cloud platform to use the troubleshooting script number, client terminal number, and time duration as a one-time password seed. This one-time password seed is truncated into multiple digits and pushed to the client terminal via text. The text message includes text, a short link, and multiple digits. A solution delivery module is used by the user to open a mini-program via a short link on the client terminal, enter multiple digits into the mini-program for verification. If verification is successful, the client terminal downloads the ciphertext and the encrypted symmetric key from the managed operations and maintenance cloud platform, decrypts the encrypted symmetric key using the client's private key to obtain the unencrypted symmetric key, and decrypts the ciphertext using the unencrypted symmetric key to obtain the original solution.

[0015] The embodiments of the present invention bring the following beneficial effects: This invention provides a cloud-edge collaborative operation and maintenance method and system, which can achieve efficient encryption of large-volume troubleshooting scripts throughout the entire path from pre-diagnosis to troubleshooting scripts to on-the-go distribution to customer receipts; strong authentication of customer identity and script integrity; and meet the compliance requirements that the hosting provider cannot see customer content, thereby improving the security and troubleshooting efficiency of remote operation and maintenance.

[0016] Other features and advantages of this disclosure will be set forth in the following description, or some features and advantages may be inferred from the description or determined without doubt, or may be learned by practicing the techniques described above.

[0017] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings. Attached Figure Description

[0018] To more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0019] Figure 1 A flowchart illustrating a cloud-edge collaborative operation and maintenance method provided in an embodiment of the present invention; Figure 2 This is a schematic diagram of the overall process of a cloud-edge collaborative operation and maintenance method provided in an embodiment of the present invention; Figure 3 A schematic diagram of the internal logic of a pre-diagnostic engine provided in an embodiment of the present invention; Figure 4 A schematic diagram of a hybrid encryption process provided in an embodiment of the present invention; Figure 5 This is a schematic diagram of the structure of a cloud-edge collaborative operation and maintenance system provided in an embodiment of the present invention; Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0021] Currently, there is an urgent need for a new cloud-edge collaborative operation and maintenance method that integrates hybrid encryption mechanisms on the basis of pre-diagnosis and on-the-go troubleshooting solutions to achieve "high-efficiency encryption of large content + strong identity authentication".

[0022] Based on this, embodiments of the present invention provide a cloud-edge collaborative operation and maintenance method and system, specifically a cloud-edge collaborative operation and maintenance method and system based on symmetric and asymmetric encryption, involving a managed remote operation and maintenance system that can integrate the high efficiency of symmetric encryption and the strong identity authentication of asymmetric encryption into the business closed loop, realizing end-to-end data encryption and traceability in transmission, storage, and display.

[0023] To facilitate understanding of this embodiment, a cloud-edge collaborative operation and maintenance method disclosed in this embodiment of the invention will first be described in detail.

[0024] Example 1: This invention provides a cloud-edge collaborative operation and maintenance method, see [link to relevant documentation]. Figure 1 The flowchart shown illustrates a cloud-edge collaborative operation and maintenance method, which includes the following steps: Step S102: The remote client side acquires client-side data, performs real-time stream encryption on the client-side data, and transmits it to the managed operation and maintenance cloud platform; wherein, the client-side data includes: data from the data center power and environment monitoring system and / or sensor data.

[0025] In some embodiments, client-side data can be encrypted in real-time using a Galois Certified Counter encryption mode based on Transport Layer Security (TLS) and Advanced Encryption Standard (AES) 256-bit; the encrypted client-side data can then be transmitted to the managed cloud platform.

[0026] See also Figure 2 The diagram shows the overall process of a cloud-edge collaborative operation and maintenance method. In this embodiment, data acquisition and transmission can be performed: the remote client side obtains data from the data center power and environment monitoring system and / or sensor data as client-side data, and transmits the client-side data to the managed operation and maintenance cloud platform after real-time stream encryption.

[0027] This embodiment can encrypt client-side data in real time using TLS (Transport Layer Security) + AES (Advanced Encryption Standard)-256-GCM (Galovar Authentication Counter Encryption Mode), and transmit it encrypted over a remote network to the managed cloud platform. Using AES-256-GCM mode provides both encryption and integrity authentication, preventing data tampering during transmission.

[0028] Step S104: The managed operation and maintenance cloud platform receives customer-side data and outputs at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data.

[0029] In some embodiments, the managed operation and maintenance cloud platform receives customer-side data and inputs the customer-side data into the pre-diagnostic engine built into the managed operation and maintenance cloud platform; the causal model of the pre-diagnostic engine performs causal relationship reasoning based on the alarm code, device model, and data value corresponding to the customer-side data, and outputs at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data.

[0030] In some embodiments, the pre-diagnostic engine accesses customer-side data into an anomaly sample library and constructs a causal model based on a trained fault chain knowledge graph.

[0031] like Figure 2 As shown, and see Figure 3The diagram illustrates the internal logic of a pre-diagnostic engine. This embodiment enables pre-diagnostic processing: real-time streams (telemetry / Modbus / SNMP) enter the pre-diagnostic engine (edge ​​or cloud), access an anomaly sample library, and construct a causal model based on a trained fault chain knowledge graph. The causal model performs causal reasoning based on alarm codes, device models, and monitoring / sensor values ​​(e.g., 'UPS input voltage = 0 → battery discharge → temperature rise'), outputting the Top 3 probabilities of fault root causes and the corresponding troubleshooting script ID.

[0032] Step S106: The accompanying solution generator of the managed operation and maintenance cloud platform generates an accompanying solution for each root cause of the fault based on the troubleshooting script number, and determines the original solution based on the accompanying solution for each root cause of the fault.

[0033] In some embodiments, the managed operations and maintenance cloud platform pre-stores a script template library, which includes troubleshooting steps in text, image, and short video formats for each type of root cause of failure. The accompanying solution generator of the managed operations and maintenance cloud platform calls the corresponding troubleshooting steps from the script template library based on the troubleshooting script number as an accompanying solution for each root cause of failure.

[0034] like Figure 2 As shown, this embodiment can generate accompanying solutions: for each type of root cause, a checklist of troubleshooting steps in both text and short video formats is pre-set to form a script template library; based on the script ID output by the diagnosis, the corresponding template is called to encapsulate it into an accompanying solution, and the original solution P is output.

[0035] Step S108: The managed operation and maintenance cloud platform randomly generates a symmetric key, uses the symmetric key to encrypt the original scheme to obtain ciphertext, uses the customer's public key to encrypt the symmetric key, stores the ciphertext and the encrypted symmetric key, clears the symmetric key before encryption, and generates script hash and root cause hash.

[0036] like Figure 2 As shown, and see Figure 4 The diagram illustrates a hybrid encryption process. This embodiment can perform hybrid encryption: The platform randomly generates a 256-bit symmetric key (SYMK); the original scheme P is encrypted using AES-256-GCM to generate ciphertext P' (with authentication token); then the client's public key (PBK, supporting RSA-2048 or ECC-256) is used to encrypt SYMK to generate SYMK-Env; the platform only retains P'+SYMK-Env, and immediately clears SYMK from memory to prevent key leakage; finally, a script hash and root cause hash are generated for subsequent timestamp and integrity verification.

[0037] In step S110, the managed operation and maintenance cloud platform uses the troubleshooting script number, the client terminal number, and the time duration as a one-time password seed. The one-time password seed is truncated into multiple digits and an SMS message is sent to the client terminal. The SMS message includes text, a short link, and multiple digits.

[0038] like Figure 2 As shown, this embodiment can deliver the accompanying solution: the platform uses the script ID + customer mobile phone number (i.e., the customer terminal is a mobile phone) + time window (30 minutes) as a time-based one-time password (TOTP) seed, and uses HMAC-SHA256 to truncate it into a 6-8 digit TOTP; push it to the customer's mobile phone via SMS (text + short link + TOTP).

[0039] In step S112, the user opens the mini-program via a short link on the client terminal and enters a multi-digit number into the mini-program for verification. If the verification is successful, the client terminal downloads the ciphertext and the encrypted symmetric key from the managed operation and maintenance cloud platform, decrypts the encrypted symmetric key using the client's private key to obtain the original symmetric key, and decrypts the ciphertext using the original symmetric key to obtain the original scheme.

[0040] In some embodiments, if verification fails, the managed cloud platform resends the multi-digit number to the client terminal.

[0041] In some embodiments, the client terminal plays the original program via memory decoding.

[0042] like Figure 2 As shown, the customer opens the mini-program via a short link, enters TOTP for verification (if it fails 3 times, the platform will automatically resend a new TOTP), and after successful verification, P'+SYMK-Env is automatically downloaded; the customer uses their private key (PRK) to decrypt SYMK-Env to obtain SYMK, and then uses SYMK to decrypt P' to obtain the plaintext script P, which can then be used to view the troubleshooting script video. The playback process uses read-only memory decoding and does not write to the local file system to prevent leakage.

[0043] In some embodiments, a user clicks a designated button in a mini-program via a client terminal. The mini-program digitally signs the completion flag, timestamp, and script hash to generate a signature file. The client terminal transmits the signature file and the current client-side data to the managed operations and maintenance cloud platform. The managed operations and maintenance cloud platform verifies the signature file and determines whether the remote client-side has recovered based on the current client-side data. If the signature file is successfully verified and the remote client-side has recovered, the managed operations and maintenance cloud platform closes the alarm work order. If the signature file verification fails or the remote client-side has not recovered, the managed operations and maintenance cloud platform re-outputs at least one fault root cause probability and troubleshooting script number corresponding to the client-side data.

[0044] like Figure 2 As shown, this embodiment can perform receipt verification: After the customer confirms the completion of each step according to the troubleshooting checklist on the mini-program, if they click "Repaired", the mini-program uses PRK to digitally sign the completion mark + timestamp + script hash to generate a signature file S; upload S and monitoring / sensor data snapshots to the managed operation and maintenance cloud platform; the managed operation and maintenance cloud platform uses public key PBK to verify the legality of the signature and pulls the remote monitoring / sensor data values ​​to compare whether it has returned to normal. If it is normal, the alarm work order is closed; if it is not repaired, the system automatically upgrades and pushes the script corresponding to the top 2 root causes, or the customer can also choose to transfer to manual video assistance.

[0045] In some embodiments, the managed operation and maintenance cloud platform packages the script hash, root cause hash, encrypted symmetric key and signature file, and calls the timestamp service interface to generate a timestamp certificate; the managed operation and maintenance cloud platform stores the timestamp certificate and hash package in the platform database.

[0046] like Figure 2 As shown, this embodiment can perform trusted timestamp notarization: the managed operation and maintenance cloud platform packages the script hash + root cause hash + SYMK-Env + signature file S, calls the trusted timestamp service interface to generate a trusted timestamp certificate (TSC); the TSC and hash package are stored in the platform database. If any party tampers with the file afterward, it will cause a hash mismatch, realizing second-level discovery and audit traceability.

[0047] This invention provides a cloud-edge collaborative operation and maintenance method that enables efficient encryption of large-volume troubleshooting scripts throughout the entire path from pre-diagnosis to troubleshooting scripts, to on-the-go distribution, and to customer feedback; strong authentication of customer identity and script integrity; and compliance requirements that the hosting provider cannot see customer content, thereby improving the security and troubleshooting efficiency of remote operation and maintenance.

[0048] The method provided in the embodiments of the present invention has the following main advantages: 1. End-to-end encryption: Encryption is applied throughout the entire process, from data collection, transmission, storage to display, to prevent information leakage; 2. Highly efficient encryption mechanism: It uses symmetric encryption to process large amounts of data and asymmetric encryption to protect the key, balancing security and performance. 3. Strong identity authentication: Customers sign with their private keys and the platform verifies the signature with its public key to ensure that the operation is non-repudiable; 4. Compliance Guarantee: The hosting provider cannot decrypt client content, thus meeting data sovereignty and privacy compliance requirements; 5. Closed-loop operation and maintenance: Automates the entire process of diagnosis, distribution, execution, verification, and evidence storage, improving the efficiency of fault response and repair; 6. Trusted Audit: Introduces trusted timestamps to support post-event auditing and accountability.

[0049] Example 2: This embodiment provides a specific example of a cloud-edge collaborative operation and maintenance method for high-temperature UPS batteries, which is implemented based on the above embodiment.

[0050] (1) Scenario: The UPS battery temperature in a computer room at 03:45 was 48℃ (threshold 40℃).

[0051] (2) Pre-diagnosis: Input: UPS temperature rises, air conditioning supply pressure decreases Reasoning: Top 1 root cause: Clogged air conditioner filter leads to decreased airflow and increased room temperature, high confidence level; Top 2 root cause: UPS fan failure, medium confidence level; Top 3 root cause: Abnormal battery internal resistance, low confidence level.

[0052] Script ID: HVAC-FILTER-01 (Filter Cleaning).

[0053] (3) Accompanying solution generation: The platform calls the template library based on the script ID and automatically generates an accompanying solution that includes a video of air conditioner filter disassembly and cleaning, a checklist of illustrated steps, and service operation instructions; (4) Encryption and delivery: SYMK encryption solution obtains P'; PBK encryption of SYMK obtains SYMK-Env, generating TOTP verification code; customer SMS notification "03:45 The air conditioner filter between the UPS rows is clogged, the air supply volume decreases and the battery is hot, please flush. Click yyw.com / abcd to view the encryption operation guide, verification code 149527 (valid for 30 minutes)".

[0054] (5) Customer confirmation: The customer clicks the short link, jumps to open the mini program, enters the TOTP verification code, and immediately downloads the encryption package (P' + SYMK-Env) to start local decryption (if the verification fails 3 times, the platform will automatically resend the SMS); after decryption, the script video will start playing, and the repair operation will be performed according to the video. Confirm that the troubleshooting steps that have been performed are checked. At 04:01, all steps are completed and click <Repaired>; the mini program uses PRK to sign the completion mark + timestamp + script hash to generate a signature file S; automatically upload S and monitoring / sensor data snapshots to the platform; (6) Platform verification: After the platform verifies the signature using PBK, it pulls the monitoring / sensor data values ​​for comparison. At 04:04, the UPS battery temperature is 36℃. If the problem is confirmed to have been repaired, the work order will be automatically closed. If the problem has not been resolved, the Top 2 root cause script will be pushed or the customer can choose to receive manual video assistance. (7) Trusted timestamp notation: The platform packages the script hash + root cause hash + SYMK-Env + signature file S, and immediately applies for a trusted timestamp notation to achieve non-repudiation audit.

[0055] (8) Implementation effect: After a fault alarm, the fault diagnosis and troubleshooting solution are automatically completed within 3 minutes; non-technical users can operate the troubleshooting by reading the text message, which significantly improves the efficiency of fault response, processing and repair; the whole process is encrypted, signed and timestamped to ensure security and compliance.

[0056] Example 3: Corresponding to the above method embodiments, this invention provides a cloud-edge collaborative operation and maintenance system, see [link to relevant documentation]. Figure 5 The diagram shown illustrates the structure of a cloud-edge collaborative operation and maintenance system, which includes: The data acquisition and transmission module 51 is used to acquire customer-side data from the remote customer side, and transmit the customer-side data to the managed operation and maintenance cloud platform after real-time stream encryption; wherein, the customer-side data includes: data from the data center power and environment monitoring system and / or sensor data; The pre-diagnostic module 52 is used by the managed operation and maintenance cloud platform to receive customer-side data and output at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data. The ad-hoc solution generation module 53 is used by the ad-hoc solution generator of the managed operation and maintenance cloud platform to generate an ad-hoc solution for each fault root cause based on the troubleshooting script number, and to determine the original solution based on the ad-hoc solution for each fault root cause. The hybrid encryption module 54 is used to randomly generate a symmetric key for the managed operation and maintenance cloud platform, encrypt the original scheme with the symmetric key to obtain ciphertext, encrypt the symmetric key with the customer's public key, store the ciphertext and the encrypted symmetric key, clear the symmetric key before encryption, and generate script hash and root cause hash. The SMS push module 55 is used by the managed operation and maintenance cloud platform to use the troubleshooting script number, customer terminal number, and time as a one-time password seed, truncate the one-time password seed into multiple digits, and push the SMS to the customer terminal; the SMS includes: text, short link, and multiple digits; The accompanying solution distribution module 56 is used by users to open the mini-program via a short link on the client terminal, and input a multi-digit number into the mini-program for verification. If the verification is successful, the client terminal downloads the ciphertext and the encrypted symmetric key from the managed operation and maintenance cloud platform, decrypts the encrypted symmetric key using the client's private key to obtain the original symmetric key, and decrypts the ciphertext using the original symmetric key to obtain the original solution.

[0057] This invention provides a cloud-edge collaborative operation and maintenance system that can achieve efficient encryption of large-volume troubleshooting scripts throughout the entire path from pre-diagnosis to troubleshooting scripts to on-the-go distribution to customer feedback; strong authentication of customer identity and script integrity; and meet the compliance requirements that the hosting provider cannot see customer content, thereby improving the security and troubleshooting efficiency of remote operation and maintenance.

[0058] The aforementioned data acquisition and transmission module is used to encrypt client-side data in real time using a Galois certified counter encryption mode based on transport layer security protocols and advanced encryption standards (256-bit); and to transmit the encrypted client-side data to the managed operation and maintenance cloud platform.

[0059] The aforementioned pre-diagnostic module is used by the managed operation and maintenance cloud platform to receive customer-side data and input the customer-side data into the pre-diagnostic engine built into the managed operation and maintenance cloud platform. The causal model of the pre-diagnostic engine performs causal relationship reasoning based on the alarm code, device model, and data value corresponding to the customer-side data, and outputs at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data.

[0060] The aforementioned pre-diagnosis module is also used by the pre-diagnosis engine to access customer-side data into an anomaly sample library and build a causal model based on the trained fault chain knowledge graph.

[0061] The aforementioned managed operation and maintenance cloud platform pre-stores a script template library, which includes troubleshooting steps in text, image, and short video formats for each type of root cause of failure. The aforementioned ad-hoc solution generation module is used by the managed operation and maintenance cloud platform's ad-hoc solution generator to call the corresponding troubleshooting steps from the script template library based on the troubleshooting script number as an ad-hoc solution for each root cause of failure.

[0062] The aforementioned accompanying solution distribution module is also used to resend multiple digits to the client terminal if the verification fails.

[0063] The aforementioned accompanying solution distribution module is also used by the client terminal to decode and play the original solution through memory.

[0064] The aforementioned device further includes: a receipt verification module, used by the user to click a designated button in the mini-program via the client terminal; the mini-program digitally signs the completion flag, timestamp, and script hash to generate a signature file; the client terminal transmits the signature file and the current client-side data to the managed operation and maintenance cloud platform; the managed operation and maintenance cloud platform verifies the signature file and determines whether the remote client-side has returned to normal based on the current client-side data; if the signature file verification is successful and the remote client-side has returned to normal, the managed operation and maintenance cloud platform closes the alarm work order; if the signature file verification fails or the remote client-side has not returned to normal, the managed operation and maintenance cloud platform re-outputs at least one fault root cause probability and troubleshooting script number corresponding to the client-side data.

[0065] The aforementioned device also includes: a trusted timestamp storage module, used by the managed operation and maintenance cloud platform to package the script hash, root cause hash, encrypted symmetric key and signature file, and call the timestamp service interface to generate a timestamp certificate; the managed operation and maintenance cloud platform stores the timestamp certificate and hash package in the platform database.

[0066] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working process of the cloud-edge collaborative operation and maintenance system described above can be referred to the corresponding process in the aforementioned embodiments of the cloud-edge collaborative operation and maintenance method, and will not be repeated here.

[0067] Example 4: This invention also provides an electronic device for running the above-described cloud-edge collaborative operation and maintenance method; see [link to related documentation]. Figure 6 The diagram shows the structure of an electronic device, which includes a memory 100 and a processor 101. The memory 100 is used to store one or more computer instructions, which are executed by the processor 101 to implement the cloud-edge collaborative operation and maintenance method described above.

[0068] Furthermore, Figure 6 The electronic device shown also includes a bus 102 and a communication interface 103, with the processor 101, the communication interface 103 and the memory 100 connected via the bus 102.

[0069] The memory 100 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 103 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 102 may be an ISA bus, PCI bus, or EISA bus, etc. The bus can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 6 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0070] Processor 101 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of processor 101 or by instructions in software form. Processor 101 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this invention. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this invention can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software module can reside in a readily available storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory 100, and processor 101 reads information from memory 100 and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiments.

[0071] This invention also provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are called and executed by a processor, they cause the processor to implement the aforementioned cloud-edge collaborative operation and maintenance method. For specific implementation details, please refer to the method embodiments, which will not be repeated here.

[0072] The computer program product of the cloud-edge collaborative operation and maintenance method and system provided in the embodiments of the present invention includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods in the preceding method embodiments. For specific implementation, please refer to the method embodiments, which will not be repeated here.

[0073] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the system and / or device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0074] Furthermore, in the description of the embodiments of the present invention, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "linking" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in the present invention based on the specific circumstances.

[0075] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, essentially, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0076] In the description of this invention, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing the invention and for simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0077] Finally, it should be noted that the above-described embodiments are merely specific implementations of the present invention, used to illustrate the technical solutions of the present invention, and not to limit it. The scope of protection of the present invention is not limited thereto. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments within the technical scope disclosed in the present invention, or make equivalent substitutions for some of the technical features; and these modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be covered within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A cloud-edge collaborative operation and maintenance method, characterized in that, The method includes: The remote client side acquires client-side data, and transmits the client-side data to the managed operation and maintenance cloud platform after real-time stream encryption; wherein, the client-side data includes: data from the data center power and environment monitoring system and / or sensor data; The managed operation and maintenance cloud platform receives the customer-side data and outputs at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data. The accompanying solution generator of the managed operation and maintenance cloud platform generates an accompanying solution for each root cause of the fault based on the troubleshooting script number, and determines the original solution based on the accompanying solution for each root cause of the fault. The managed operation and maintenance cloud platform randomly generates a symmetric key, uses the symmetric key to encrypt the original scheme to obtain ciphertext, uses the client's public key to encrypt the symmetric key, stores the ciphertext and the encrypted symmetric key, clears the symmetric key before encryption, and generates a script hash and a root cause hash. The managed operation and maintenance cloud platform uses the troubleshooting script number, client terminal number, and time duration as a one-time password seed, truncates the one-time password seed into multiple digits, and pushes the SMS to the client terminal; wherein, the SMS includes: text, short link, and the multiple digits; The user opens the mini-program through the short link on the client terminal, enters the multi-digit number into the mini-program for verification; if the verification is successful, the client terminal downloads the ciphertext and the encrypted symmetric key from the managed operation and maintenance cloud platform, decrypts the encrypted symmetric key using the client's private key to obtain the original symmetric key, and decrypts the ciphertext using the original symmetric key to obtain the original scheme.

2. The method according to claim 1, characterized in that, The steps of transmitting the customer-side data to the managed operation and maintenance cloud platform after real-time streaming encryption include: The client-side data is encrypted in real time using a Galois certified counter encryption mode based on transport layer security protocols and advanced encryption standards (256-bit). The encrypted real-time stream of the client-side data is transmitted to the managed operation and maintenance cloud platform.

3. The method according to claim 1, characterized in that, The steps of the managed operation and maintenance cloud platform receiving the customer-side data and outputting at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data include: The managed operation and maintenance cloud platform receives the customer-side data and inputs the customer-side data into the pre-diagnostic engine built into the managed operation and maintenance cloud platform; The causal model of the pre-diagnostic engine performs causal reasoning based on the alarm code, device model, and data value corresponding to the customer-side data, and outputs at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data.

4. The method according to claim 3, characterized in that, After inputting the customer-side data into the pre-diagnostic engine built into the managed operations and maintenance cloud platform, the method further includes: The pre-diagnostic engine connects the customer-side data to the abnormal sample library and constructs the causal model based on the trained fault chain knowledge graph.

5. The method according to claim 1, characterized in that, The managed operation and maintenance cloud platform has a script template library pre-stored, which includes troubleshooting steps in text, image and short video formats for each type of fault root cause. The steps of the accompanying solution generator of the managed operation and maintenance cloud platform to generate an accompanying solution for each root cause of a fault based on the troubleshooting script number include: The accompanying solution generator of the managed operation and maintenance cloud platform calls the corresponding troubleshooting steps from the script template library based on the troubleshooting script number as the accompanying solution for each root cause of the fault.

6. The method according to claim 1, characterized in that, After the step where the client terminal opens the mini-program via the short link and enters the multi-digit number into the mini-program for verification, the method further includes: If the verification fails, the managed cloud platform will resend the multi-digit number to the client terminal.

7. The method according to claim 1, characterized in that, After the step of decrypting the ciphertext using the symmetric key used for encryption to obtain the original scheme, the method further includes: The client terminal plays the original solution via memory decoding.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The user clicks a designated button in the mini-program through the client terminal, and the mini-program digitally signs the completion flag, timestamp, and script hash to generate a signature file; The client terminal transmits the signature file and the current client-side data to the managed operation and maintenance cloud platform. The managed operation and maintenance cloud platform verifies the signature file and determines whether the remote client side has returned to normal based on the current client side. If the signature file is successfully verified and the remote client side returns to normal, the managed operation and maintenance cloud platform closes the alarm work order. If the verification of the signature file fails or the remote client side does not recover, the managed operation and maintenance cloud platform will re-output at least one fault root cause probability and troubleshooting script number corresponding to the client side data.

9. The method according to claim 8, characterized in that, The method further includes: The managed operation and maintenance cloud platform packages the script hash, the root cause hash, the encrypted symmetric key and the signature file, and calls the timestamp service interface to generate a timestamp certificate. The managed cloud platform stores the timestamp certificate and hash packet in the platform database.

10. A cloud-edge collaborative operation and maintenance system, characterized in that, The system includes: The data acquisition and transmission module is used to acquire customer-side data from the remote customer side, and transmit the customer-side data to the managed operation and maintenance cloud platform after real-time stream encryption; wherein, the customer-side data includes: data from the data center power and environment monitoring system and / or sensor data; The pre-diagnosis module is used by the managed operation and maintenance cloud platform to receive the customer-side data and output at least one fault root cause probability and troubleshooting script number corresponding to the customer-side data. The ad-hoc solution generation module is used by the ad-hoc solution generator of the managed operation and maintenance cloud platform to generate an ad-hoc solution for each root cause of the fault based on the troubleshooting script number, and to determine the original solution based on the ad-hoc solution for each root cause of the fault. The hybrid encryption module is used to randomly generate a symmetric key on the managed operation and maintenance cloud platform, encrypt the original scheme with the symmetric key to obtain ciphertext, encrypt the symmetric key with the client's public key, store the ciphertext and the encrypted symmetric key, clear the symmetric key before encryption, and generate script hash and root cause hash. The SMS push module is used by the managed operation and maintenance cloud platform to use the troubleshooting script number, the client terminal number, and the time duration as a one-time password seed, truncate the one-time password seed into multiple digits, and push the SMS to the client terminal; wherein, the SMS includes: text, a short link, and the multiple digits; The accompanying solution delivery module is used by the user to open the mini-program through the short link on the client terminal, input the multi-digit number into the mini-program for verification; if the verification is successful, the client terminal downloads the ciphertext and the encrypted symmetric key from the managed operation and maintenance cloud platform, decrypts the encrypted symmetric key using the client's private key to obtain the original symmetric key, and decrypts the ciphertext using the original symmetric key to obtain the original solution.

Images