Method and system for preventing malicious SRB configuration software access
By receiving and comparing the characteristic codes of the configuration software in the SRB system, combining encryption processing and key sharing, the security risks caused by malware access are solved, and higher system security and stability are achieved.
Patent Information
- Application Number
- CN202411039093.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-07-31
- Publication Date
- 2024-11-29
AI Technical Summary
The communication methods of existing SRB configuration software pose security risks. Malware can cause system stability threats and data leakage by modifying device configuration, and it is necessary to enhance its ability to resist malware attacks to ensure data transmission security.
By receiving and comparing the feature codes in the configuration packets sent by the SRB configuration software, ensuring that the feature code is consistent with the pre-stored code of the system, the configuration instructions are accepted, and the encryption processing and key sharing mechanism are used to verify the identity of the software and update dynamically Feature code to prevent illegal access.
It significantly enhances the identity verification capabilities of the SRB system, effectively prevents malware access, improves system security and stability, reduces maintenance costs and risks, and ensures the security and controllability of data transmission.
Smart Images

Figure CN119051900A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of network security technology, and in particular to a method and system for preventing malicious SRB configuration software from accessing. Background Art
[0002] The secure real-time bus (SRB) is an industrial data fieldbus built on high-performance semiconductor components. As a collection of signal lines, the traditional bus (BUS) is widely used between various components of embedded systems, including high-performance controller chips, memory, communication interfaces, etc., as well as the underlying software and communication protocols that support the operation of these hardware. These buses transmit binary data and implement key functions such as data transmission and conversion, system control, etc. according to specific instructions.
[0003] As a further development of bus technology, SRB technology places special emphasis on the stability, security and real-time performance of data transmission, making it particularly suitable for industrial environments with strict performance requirements. However, in existing technical implementations, SRB configuration software, as the core tool for managing SRB systems, usually runs on a PC and communicates with multiple SRB devices connected by cables through standard Ethernet.
[0004] Although this communication method provides high compatibility and flexibility, it also brings certain security risks. As long as the message format sent by the SRB configuration software meets the standard, the configuration of the SRB device will be modified, which provides an opportunity for malicious software to access. Once the malicious SRB configuration software successfully accesses the system, it may pose a serious threat to the stable operation of the system, and even lead to serious consequences such as data leakage and equipment damage.
[0005] Therefore, it is necessary to improve and optimize the existing SRB system communication mechanism to enhance its ability to resist malware attacks and ensure the security of data transmission, so as to better meet the demand for high-performance bus technology in the field of industrial automation. Summary of the invention
[0006] In view of the above problems, the present application provides a method for preventing malicious SRB configuration software from accessing, including the following contents:
[0007] In a first aspect, the present application provides a method for preventing malicious SRB configuration software from accessing, the method comprising:
[0008] Receive a configuration message sent by the SRB configuration software, wherein the configuration message carries a first SRB feature code;
[0009] Acquire the first SRB feature code, and compare the first SRB feature code with the second SRB feature code, where the second SRB feature code is pre-stored in the SRB system;
[0010] When the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, the SRB configuration software is regarded as legal software, and the configuration instructions in the configuration message sent by the SRB configuration software are accepted.
[0011] Optionally, before receiving the configuration message sent by the SRB configuration software, the method further includes:
[0012] Setting a second SRB feature code in the SRB system, where the second SRB feature code is in the form of a number, a date or a character string;
[0013] Writing the second SRB feature code into the SRB system;
[0014] The second SRB feature code is sent to the SRB configuration software and stored in a configuration message of the SRB configuration software as the first SRB feature code.
[0015] Optionally, before receiving the configuration message sent by the SRB configuration software, the method further includes:
[0016] Encrypting the first SRB feature code using a key;
[0017] Sharing the key between the SRB device and the SRB configuration software;
[0018] The acquiring the first SRB feature code and comparing the first SRB feature code with the second SRB feature code comprises:
[0019] The encrypted first SRB feature code is decrypted using the key, and the decrypted first SRB feature code is compared with the second SRB feature code.
[0020] Optionally, the first SRB feature code and the second SRB feature code are dynamically updated at preset periods.
[0021] Optionally, when the comparison result shows that the first SRB feature code and the second SRB feature code are inconsistent, the SRB configuration software is regarded as illegal software and configuration is rejected.
[0022] Optionally, the method further includes: when the comparison result shows that the first SRB feature code and the second SRB feature code are inconsistent, feeding back to the SRB configuration software that illegal software has been identified.
[0023] In a second aspect, the present application provides a system for preventing malicious SRB configuration software from accessing, the system comprising:
[0024] SRB system side and PC side;
[0025] The PC terminal includes SRB configuration software for sending configuration to the SRB system terminal;
[0026] The SRB system end includes a plurality of SRB devices, and each SRB device is connected by a cable; each SRB device in the SRB system end is connected to the PC end via a network port or a serial port;
[0027] The SRB system end is used to receive a configuration message sent by the SRB configuration software, wherein the configuration message carries a first SRB feature code; obtain the first SRB feature code, compare the first SRB feature code with the second SRB feature code, and the second SRB feature code is pre-stored in the SRB system; when the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, the SRB configuration software is regarded as legal software, and the configuration instructions issued by the SRB configuration software are accepted.
[0028] Optionally, before the SRB system end receives the configuration message sent by the SRB configuration software, a second SRB feature code is set on the SRB system end, where the second SRB feature code is in the form of a number, a date or a character string;
[0029] Writing the second SRB feature code into the SRB system end;
[0030] The second SRB feature code is sent to the SRB configuration software on the PC side and stored in a configuration message of the SRB configuration software as the first SRB feature code.
[0031] Optionally, before the SRB system receives the configuration message sent by the SRB configuration software, the method further includes encrypting the first SRB feature code using a key;
[0032] Sharing the key between the SRB device and the SRB configuration software;
[0033] The acquiring the first SRB feature code and comparing the first SRB feature code with the second SRB feature code comprises:
[0034] The encrypted first SRB feature code is decrypted using the key, and the decrypted first SRB feature code is compared with the second SRB feature code.
[0035] Optionally, the SRB system end dynamically updates the first SRB feature code and the second SRB feature code at every preset period.
[0036] Optionally, when the comparison result of the SRB system shows that the first SRB feature code and the second SRB feature code are inconsistent, the SRB configuration software is regarded as illegal software and configuration is rejected.
[0037] Optionally, when the comparison result of the SRB system shows that the first SRB feature code and the second SRB feature code are inconsistent, feedback is given to the SRB configuration software indicating that illegal software has been identified.
[0038] In a third aspect, the present application provides a device comprising a memory and a processor, the memory being used to store instructions or codes, and the processor being used to execute the instructions or codes, so that the device executes the method for preventing malicious SRB configuration software from accessing as described in any implementation of the first aspect.
[0039] In a fourth aspect, the present application provides a computer-readable storage medium, in which code is stored. When the code is executed, the device executing the code implements the method for preventing malicious SRB configuration software from accessing as described in any implementation of the first aspect.
[0040] The present application provides a method for preventing malicious SRB configuration software from accessing. When executing the method, first receive a configuration message sent by the SRB configuration software, the configuration message carries a first SRB feature code, obtain the first SRB feature code, compare the first SRB feature code with the second SRB feature code, the second SRB feature code is pre-stored in the SRB system, and when the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, the SRB configuration software is regarded as legitimate software, and the configuration instructions in the configuration message sent by the SRB configuration software are accepted.
[0041] By implementing the above technical solution, the SRB system's identity authentication capability for access configuration software is significantly enhanced, effectively preventing illegal access by malicious software or unauthorized software. Specifically, the SRB configuration software is required to carry a specific first SRB feature code when sending a configuration message, and compare it with the second SRB feature code pre-stored in the system. This verification mechanism ensures that only legitimate configuration software with the correct feature code can successfully access the system and send configuration instructions, thereby greatly improving the security of the system. In addition, the technical solution also promotes the standardization and controllability of SRB system operations. Only when the identity of the configuration software is confirmed by the system will the configuration instructions it sends be accepted and executed, avoiding system anomalies or failures caused by incorrect configuration or malicious operations. This not only ensures the stability of the system operation, but also reduces the maintenance costs and risks caused by human errors or malicious attacks.
[0042] In summary, this technical solution achieves strict control and identity authentication of SRB configuration software access by introducing a feature code comparison mechanism, providing a more secure and reliable data transmission and configuration management solution for the SRB system. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] In order to more clearly illustrate the technical solutions in this embodiment or the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0044] Figure 1 A schematic diagram of the connection structure between SRB configuration software and SRB system in the prior art provided in an embodiment of the present application;
[0045] Figure 2 A flowchart of a method for preventing malicious SRB configuration software from accessing provided by an embodiment of the present application;
[0046] Figure 3 A structural diagram of a system for preventing malicious SRB configuration software from accessing provided in an embodiment of the present application. DETAILED DESCRIPTION
[0047] As described in the background technology of this application, the SRB configuration software runs on a PC, and the SRB system is composed of multiple SRB devices connected by cables. The SRB configuration software is connected to the devices in the SRB system through a network port or a serial port. Figure 1 As shown, Figure 1A schematic diagram of the connection structure between SRB configuration software and SRB system in the prior art provided in an embodiment of the present application. In the prior art, since the communication between SRB configuration software and SRB devices adopts a standard Ethernet method, as long as the message format sent by the SRB configuration software to the SRB device is legal, the configuration of the SRB device will be changed, so there will be a problem of malicious SRB configuration software accessing the SRB system.
[0048] In order to solve the above technical problems, an embodiment of the present application provides a method for preventing malicious SRB configuration software from accessing, the method comprising:
[0049] Receive a configuration message sent by SRB configuration software, wherein the configuration message carries a first SRB feature code; obtain the first SRB feature code; compare the first SRB feature code with the second SRB feature code, wherein the second SRB feature code is pre-stored in the SRB system; when the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, regard the SRB configuration software as legal software, and accept the configuration instructions in the configuration message sent by the SRB configuration software.
[0050] In this way, by implementing the above technical solution, the SRB system's identity authentication capability for access configuration software is significantly enhanced, effectively preventing illegal access by malicious software or unauthorized software. Specifically, the SRB configuration software is required to carry a specific first SRB feature code when sending a configuration message, and compare it with the second SRB feature code pre-stored in the system. This verification mechanism ensures that only legitimate configuration software with the correct feature code can successfully access the system and send configuration instructions, thereby greatly improving the security of the system.
[0051] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0052] First, the technical terms involved in the embodiments of the present application are introduced:
[0053] SRB: Security Real-time Bus (SRB for short);
[0054] SRB device: a device that implements the SRB bus requirements;
[0055] SRB system: A collection of devices consisting of multiple SRB devices that communicate with each other through the SRB bus to implement specific functions;
[0056] SRB configuration software: software that usually runs on a PC to configure SRB devices and SRB systems.
[0057] Figure 2 A flowchart of a method for preventing malicious SRB configuration software from accessing provided by an embodiment of the present application. Figure 2 As shown, the method for preventing malicious SRB configuration software from accessing provided by the embodiment of the present application may include:
[0058] S201. Receive a configuration message sent by SRB configuration software, where the configuration message carries a first SRB feature code.
[0059] The SRB system receives a configuration message sent from the SRB configuration software, wherein the configuration message includes a data packet of instructions and parameters required for configuring the SRB system.
[0060] The first SRB feature code: a unique identifier generated by the SRB system and used to verify the legitimacy of the software. After being generated in the SRB configuration system, it is sent to the SRB configuration software. A configuration message format is defined in the SRB configuration software, which includes an SRB feature code field. The SRB feature code field can be in various forms such as numbers, dates, or strings, and is sent to the SRB system along with the configuration message sent by the configuration software.
[0061] In an implementation of the embodiment of the present application, before receiving the configuration message sent by the SRB configuration software, the method further includes:
[0062] A second SRB feature code is set in the SRB system, wherein the second SRB feature code is in the form of a number, a date or a character string; the second SRB feature code is written into the SRB system; the second SRB feature code is sent to the SRB configuration software and stored in a configuration message of the SRB configuration software as the first SRB feature code.
[0063] The second SRB feature code is pre-set in the SRB system, corresponding to the first SRB feature code, and is used to verify the unique identifier of the software identity. The feature code can be in the form of a number, date, or string. The specific format and content are determined according to the actual application scenario and requirements. For example:
[0064] Number: can be a serial number, version number, etc., such as 12345.
[0065] Date: Indicates a specific time or date, such as 2023-04-01 (YYYY-MM-DD).
[0066] String: Can be any text, such as a device name or an operation instruction.
[0067] After the second SRB feature code is determined, it is further written into the SRB system, where the SRB system includes a plurality of SRB devices, and the second SRB feature code is written into each SRB device respectively.
[0068] In order to enhance the security of the SRB signature code, in an implementation method of an embodiment of the present application, before receiving the configuration message sent by the SRB configuration software, the SRB signature code is encrypted, and the encryption key is shared between the SRB device and the SRB configuration software. In this way, even if the signature code is intercepted during transmission, it cannot be easily parsed.
[0069] First, select an encryption algorithm to encrypt the first SRB feature code. Common encryption algorithms include symmetric encryption algorithms (such as AES, DES) and asymmetric encryption algorithms (such as RSA). In the embodiment of the present application, taking the AES algorithm as an example, a key is first generated. This key is usually a binary sequence of a fixed length. For AES-256, the key length is 256 bits (32 bytes). The generation of the key should be random and complex enough to ensure the security of the encryption. The generated key and the first SRB feature code are used as input and encrypted using the AES algorithm. The encrypted data will be a binary sequence that cannot directly identify the original information. The key is then sent to the SRB device by the configuration software, or securely shared between the two parties through some security mechanism (such as a key exchange protocol).
[0070] The following is a specific introduction through an example:
[0071] Assume that the first SRB feature code is the string "SecureSRB2023" and the key is a randomly generated AES-256 key. On the SRB device side, use the AES algorithm and the key to encrypt "SecureSRB2023" to obtain a string of encrypted binary data. Then, send the encrypted data and the key (or the encrypted version of the key) to the SRB configuration software in a secure manner (such as an HTTPS connection). On the configuration software side, use the same key to decrypt the encrypted data and restore the original first SRB feature code "SecureSRB2023".
[0072] This step ensures that only legitimate software with the correct key and signature can configure the SRB system by encrypting and verifying the signature, effectively preventing the intrusion and malicious configuration of illegal software. The following describes how to verify the legitimacy of the software by comparing the two signatures.
[0073] S202: Obtain the first SRB feature code, and compare the first SRB feature code with the second SRB feature code.
[0074] When the SRB device in the SRB system receives the configuration message sent by the SRB configuration software, the message is parsed to obtain a first SRB feature code, and the first SRB feature code is compared with a second SRB feature code pre-stored in the SRB system.
[0075] When the first SRB feature code is an encrypted SRB feature code, before comparing with the second SRB feature code, the first SRB feature code needs to be decrypted to obtain the decrypted first SRB feature code, and then the decrypted first SRB feature code is compared with the second SRB feature code.
[0076] S203: When the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, the SRB configuration software is regarded as legal software, and the configuration instructions in the configuration message sent by the SRB configuration software are accepted.
[0077] If the comparison result shows that the first SRB signature code and the second SRB signature code are consistent, the SRB system will regard the SRB configuration software as legal software, accept the configuration instructions in the configuration message sent by it, and perform the corresponding system configuration. If the signature codes are inconsistent, the system will regard the SRB configuration software as illegal software, refuse to execute its configuration request, and may issue a warning to the administrator to prompt that illegal software has been identified.
[0078] This process ensures that only legal software can configure the SRB system, improving the security and stability of the system. At the same time, by providing administrators with identification information of illegal software, it helps to promptly discover and deal with potential security threats.
[0079] In one implementation of the embodiment of the present application, in order to further improve the security of the system, the first SRB feature code and the second SRB feature code are dynamically updated every preset period. Specifically, a preset period (such as daily, weekly or monthly) is pre-set, and the first SRB feature code and the second SRB feature code are automatically updated during this period. In this way, even if illegal software obtains the current feature code, it cannot continue to be used after the update.
[0080] When the comparison result shows that the first SRB feature code and the second SRB feature code are inconsistent, the SRB configuration software is regarded as illegal software and configuration is rejected. Furthermore, the cause of the problem can be fed back to the SRB configuration software through an error code or error message to facilitate rapid location and resolution of the problem.
[0081] The above are some specific implementations of a method for preventing malicious SRB configuration software from accessing provided by the embodiment of the present application. Based on this, the present application also provides a corresponding device. The device provided by the embodiment of the present application will be introduced from the perspective of functional modularization.
[0082] Figure 3 A schematic diagram of the structure of a system for preventing malicious SRB configuration software from accessing provided by an embodiment of the present application. Figure 3 As shown, the system for preventing malicious SRB configuration software from accessing provided by the embodiment of the present application includes:
[0083] SRB system end 300 and PC end 310;
[0084] The PC terminal includes SRB configuration software for sending configuration to the SRB system terminal;
[0085] The SRB system end includes multiple SRB devices 301, and each SRB device is connected by a cable; each SRB device in the SRB system end is connected to the PC end through a network port or a serial port;
[0086] The SRB system end is used to receive a configuration message sent by the SRB configuration software, wherein the configuration message carries a first SRB feature code; obtain the first SRB feature code, compare the first SRB feature code with the second SRB feature code, and the second SRB feature code is pre-stored in the SRB system; when the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, the SRB configuration software is regarded as legal software, and the configuration instructions issued by the SRB configuration software are accepted.
[0087] In an implementation of the embodiment of the present application, before the SRB system end receives the configuration message sent by the SRB configuration software, a second SRB feature code is set on the SRB system end, and the second SRB feature code is in the form of a number, a date or a character string;
[0088] Writing the second SRB feature code into the SRB system end;
[0089] The second SRB feature code is sent to the SRB configuration software on the PC side and stored in a configuration message of the SRB configuration software as the first SRB feature code.
[0090] In an implementation of the embodiment of the present application, before the SRB system receives the configuration message sent by the SRB configuration software, it also includes encrypting the first SRB feature code using a key;
[0091] Sharing the key between the SRB device and the SRB configuration software;
[0092] The acquiring the first SRB feature code and comparing the first SRB feature code with the second SRB feature code comprises:
[0093] The encrypted first SRB feature code is decrypted using the key, and the decrypted first SRB feature code is compared with the second SRB feature code.
[0094] In an implementation manner of the embodiment of the present application, the SRB system end dynamically updates the first SRB feature code and the second SRB feature code every preset period.
[0095] In an implementation of the embodiment of the present application, when the comparison result of the SRB system shows that the first SRB feature code and the second SRB feature code are inconsistent, the SRB configuration software is regarded as illegal software and configuration is rejected.
[0096] In an implementation of the embodiment of the present application, when the comparison result of the SRB system side shows that the first SRB feature code and the second SRB feature code are inconsistent, feedback is given to the SRB configuration software indicating that illegal software has been identified.
[0097] The embodiments of the present application also provide corresponding devices and computer storage media for implementing the solutions provided by the embodiments of the present application.
[0098] The device includes a memory and a processor, the memory is used to store instructions or codes, and the processor is used to execute the instructions or codes so that the device executes the method described in any embodiment of the present application.
[0099] The computer storage medium stores codes, and when the codes are executed, a device executing the codes implements the method described in any embodiment of the present application.
[0100] Through the description of the above implementation methods, it can be known that those skilled in the art can clearly understand that all or part of the steps in the above-mentioned embodiment method can be implemented by means of software plus a general hardware platform. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a read-only memory (ROM) / RAM, a magnetic disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network communication device such as a router) to execute the methods described in each embodiment of the present application or some parts of the embodiments.
[0101] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.
[0102] It should also be noted that the various embodiments in this specification are described in a progressive manner, and the same and similar parts between the various embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and apparatus embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments. The device and apparatus embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components indicated as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.
[0103] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
Claims
1. A method for preventing malicious SRB configuration software from accessing, characterized in that: Applied to a safe real-time bus (SRB) system, the method comprises: Receive a configuration message sent by the SRB configuration software, wherein the configuration message carries a first SRB feature code; Acquire the first SRB feature code, and compare the first SRB feature code with the second SRB feature code, where the second SRB feature code is pre-stored in the SRB system; When the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, the SRB configuration software is regarded as legal software, and the configuration instructions in the configuration message sent by the SRB configuration software are accepted.
2. The method according to claim 1, characterized in that: Before receiving the configuration message sent by the SRB configuration software, the method further includes: Setting a second SRB feature code in the SRB system, where the second SRB feature code is in the form of a number, a date or a character string; Writing the second SRB feature code into the SRB system; The second SRB feature code is sent to the SRB configuration software and stored in a configuration message of the SRB configuration software as the first SRB feature code.
3. The method according to claim 1, characterized in that Before receiving the configuration message sent by the SRB configuration software, the method further includes: Encrypting the first SRB feature code using a key; Sharing the key between the SRB device and the SRB configuration software; The acquiring the first SRB feature code and comparing the first SRB feature code with the second SRB feature code comprises: The encrypted first SRB feature code is decrypted using the key, and the decrypted first SRB feature code is compared with the second SRB feature code.
4. The method according to claim 1, characterized in that: The first SRB feature code and the second SRB feature code are dynamically updated at every preset period.
5. The method according to claim 1, characterized in that When the comparison result shows that the first SRB feature code and the second SRB feature code are inconsistent, the SRB configuration software is regarded as illegal software and configuration is rejected.
6. The method according to claim 5, characterized in that The method further comprises: When the comparison result shows that the first SRB feature code and the second SRB feature code are inconsistent, feedback is given to the SRB configuration software indicating that illegal software has been identified.
7. A system for preventing malicious SRB configuration software from accessing, characterized in that: The system includes an SRB system end and a PC end; The PC terminal includes SRB configuration software for sending configuration to the SRB system terminal; The SRB system end includes a plurality of SRB devices, and each SRB device is connected by a cable; each SRB device in the SRB system end is connected to the PC end via a network port or a serial port; The SRB system end is used to receive a configuration message sent by the SRB configuration software, wherein the configuration message carries a first SRB feature code; obtain the first SRB feature code, and compare the first SRB feature code with the second SRB feature code, wherein the second SRB feature code is pre-stored in the SRB system; When the comparison result shows that the first SRB feature code and the second SRB feature code are consistent, the SRB configuration software is regarded as legal software, and the configuration instructions issued by the SRB configuration software are accepted.
8. The device according to claim 7, characterized in that Before the SRB system end receives the configuration message sent by the SRB configuration software, the SRB system end sets a second SRB feature code, wherein the second SRB feature code is in the form of a number, a date or a character string; Writing the second SRB feature code into the SRB system end; The second SRB feature code is sent to the SRB configuration software on the PC side and stored in a configuration message of the SRB configuration software as the first SRB feature code.
9. A computing device, characterized in that The computing device includes: a memory and a processor; The memory is used to store computer programs; The processor is configured to implement the method according to any one of claims 1 to 6 when executing the computer program.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.
