Terminal operation environment security authentication method and system

Abstract

The invention discloses a terminal operation environment security authentication method and system, and relates to the field of information security. The terminal operation environment security authentication method comprises the following steps: collecting terminal equipment data, wherein the terminal equipment data comprises equipment attribute information and an equipment identifier; based on the equipment attribute information and the equipment identifier, determining a Hash commitment of the terminal equipment, the Hash commitment being a security baseline of the terminal equipment; and in a process of performing equipment authentication based on a set verification period, determining whether the terminal equipment is abnormal based on the security baseline, and updating the security baseline according to the collected equipment attribute information in each verification period.

Description

Technical Field

[0001] The present application relates to the field of information security, and in particular to a method and system for authenticating the security of a terminal operating environment. Background Art

[0002] Terminal computers are the basic units of cyberspace activities and the source and destination of information. Protecting the integrity of terminals plays an important role in building a secure network environment and information system.

[0003] Among the related technologies, some provide security protection for terminals by collecting terminal operation status and using technologies such as big data security analysis and machine learning. However, this method relies on a large amount of data processing and analysis, and has low efficiency and poor flexibility. Data storage security technology can also be used, that is, the firmware and file system in the chip are exported through hardware tools and technical means, and the binary data in the device is extracted to provide security protection for the terminal. However, this method mainly focuses on the storage and transmission security of data, cannot guarantee the security and integrity of the device operating environment, and has poor reliability. Summary of the invention

[0004] The embodiments of the present application provide a terminal operating environment security authentication method and system to solve the problems of poor flexibility and reliability of security protection methods in related technologies.

[0005] In a first aspect, an embodiment of the present application provides a terminal operating environment security authentication method, including: Collecting terminal device data, wherein the terminal device data includes device attribute information and device identification; Determine a hash commitment of the terminal device based on the device attribute information and the device identification, where the hash commitment is a security baseline of the terminal device; In the process of performing device authentication based on a set verification cycle, whether the terminal device is abnormal is determined based on the security baseline, wherein each verification cycle updates the security baseline according to the collected device attribute information.

[0006] In a second aspect, an embodiment of the present application provides a terminal operating environment security authentication system, characterized in that it includes: A collection module, used to collect terminal device data, wherein the terminal device data includes device attribute information and device identification; A determination module, configured to determine a hash commitment of the terminal device based on the device attribute information and the device identification, wherein the hash commitment is a security baseline of the terminal device; The authentication module is used to determine whether the terminal device is abnormal based on the security baseline during the device authentication process based on the set verification cycle, wherein each verification cycle updates the security baseline based on the collected device attribute information.

[0007] In a third aspect, an embodiment of the present application provides an electronic device, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0008] In a fourth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented.

[0009] In a fifth aspect, an embodiment of the present application provides a program product, which is stored in a storage medium and is executed by at least one processor to implement the steps of the method described in the first aspect.

[0010] In an embodiment of the present application, firstly, the terminal device data is collected, and the terminal device data includes device attribute information and device identification. Then, based on the device attribute information and device identification, the hash commitment of the terminal device is determined. The hash commitment is the security baseline of the terminal device. Finally, in the process of device authentication based on the set verification cycle, it is determined whether the terminal device is abnormal based on the security baseline, wherein each verification cycle updates the security baseline according to the collected device attribute information. The present application determines the hash commitment by hashing the device attribute information and the device identification, and uses the hash commitment as the security baseline of the terminal device, which increases the security of the terminal device, can ensure that the attribute information of the original device is not leaked, and through periodic verification, the device information of the device is regularly checked, which improves the initiative and real-time nature of device monitoring and improves the reliability of security protection. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings: Figure 1 It is a flowchart of a terminal operating environment security authentication method provided in an embodiment of the present application; Figure 2 is a schematic diagram of a terminal operating environment security authentication system provided in an embodiment of the present application; Figure 3 It is a schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0012] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are 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.

[0013] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here. In addition, the "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0014] The following is combined with Figures 1 to 3 , a terminal operating environment security authentication method and system provided by an embodiment of the present application are described in detail through specific embodiments and their application scenarios.

[0015] The meanings of the terms in the embodiments of this application are as follows: Hash Commitment is a cryptographic technique used to ensure the integrity and immutability of data. It is based on the property of hash functions, that is, any small change to the input data will result in a huge change in the hash value, which makes the hash value a "fingerprint" of the data.

[0016] UUID (Universally Unique Identifier) ​​is a standardized unique identifier used to ensure uniqueness in distributed systems without central coordination. UUID consists of 32 hexadecimal digits separated by 4 hyphens, forming an 8-4-4-4-12 layout, for example: 123e4567-e89b-12d3-a456-426614174000.

[0017] Device Fingerprinting is a technology used to identify and track devices on the network, even without using traditional identification methods (such as IP addresses or Cookies). Device fingerprinting technology collects various attributes and settings of the device to generate a unique "fingerprint" that can be used to identify the device.

[0018] The generation of device fingerprints is usually based on the following aspects: Browser properties: including browser type, version, language settings, plug-ins (such as Flash, Java), font list, screen resolution, operating system information, etc.

[0019] Hardware attributes: including CPU type, memory size, graphics card model, sound card model, etc.

[0020] Network attributes: including IP address, time zone, geographic location, network connection speed, etc.

[0021] User behavior: including mouse movement trajectory, keyboard input speed, scrolling behavior, etc.

[0022] Software settings: including system settings, browser extensions, installed applications, etc.

[0023] Timestamp: The time setting of the device, sometimes used to generate device fingerprints.

[0024] Other technologies: WebRTC (Web Real-Time Communications) can be used to obtain the user's local IP address, as well as other browser security settings.

[0025] Application scenarios of device fingerprints include: User identification: Identify and track users without relying on Cookies.

[0026] Personalized experience: Provide customized services or content based on the user's device characteristics.

[0027] Security and fraud detection: Identify suspicious device behavior to prevent fraud and abuse.

[0028] Ad targeting: used for advertising to improve the relevance and effectiveness of advertising.

[0029] The advantage of device fingerprint technology is that it does not rely on information actively provided by users, nor is it easily controlled or modified by users directly, so it has a certain degree of anonymity and stability. However, this also raises concerns about privacy protection, because users may not want their devices to be tracked and identified in such detail. Therefore, when using device fingerprint technology, it is necessary to comply with relevant privacy policies and laws and regulations.

[0030] like Figure 1 As shown, it is a flow chart of a terminal operating environment security authentication method provided by an embodiment of the present application. Figure 1 As shown, the terminal operating environment security authentication method may include: the contents shown in S101 to S103.

[0031] In S101, terminal device data is collected, and the terminal device data includes device attribute information and device identification.

[0032] Among them, device attribute information can include hardware configuration, operating system version, installed application list, etc., through which device attribute information can generate device fingerprints. Device identification refers to a unique identifier (such as UUID) assigned to a device when a user or system administrator adds a new device to the monitoring system.

[0033] In S102, based on the device attribute information and the device identification, a hash commitment of the terminal device is determined, and the hash commitment is a security baseline of the terminal device.

[0034] The hash commitment is obtained by hashing the device attribute information and the device identification.

[0035] In S103, during the process of device authentication based on the set verification cycle, it is determined whether the terminal device is abnormal based on the security baseline, wherein the security baseline is updated according to the collected device attribute information in each verification cycle.

[0036] The verification cycle may be every hour, every day, half a day, etc., depending on the actual application and is not limited in this embodiment.

[0037] This embodiment adopts periodic verification to regularly check the security baseline (ie, device attribute information, etc.), rather than responding only when an abnormality occurs, thereby improving the initiative and real-time nature of monitoring.

[0038] In an embodiment of the present application, firstly, the terminal device data is collected, and the terminal device data includes device attribute information and device identification. Then, based on the device attribute information and device identification, the hash commitment of the terminal device is determined. The hash commitment is the security baseline of the terminal device. Finally, in the process of device authentication based on the set verification cycle, it is determined whether the terminal device is abnormal based on the security baseline, wherein each verification cycle updates the security baseline according to the collected device attribute information. The present application determines the hash commitment by hashing the device attribute information and the device identification, and uses the hash commitment as the security baseline of the terminal device, which increases the security of the terminal device, can ensure that the attribute information of the original device is not leaked, and through periodic verification, the device information of the device is regularly checked, which improves the initiative and real-time nature of device monitoring and improves the reliability of security protection.

[0039] In a possible implementation of the present application, determining the hash commitment of a terminal device based on device attribute information and a device identification may include: generating a device fingerprint based on the device attribute information; using a hash algorithm to perform an association calculation on the device fingerprint and the device identification to obtain an initial hash value, the initial hash value being the hash commitment, and the device identification being the universal unique identification code UUID of the terminal device.

[0040] In this embodiment, the device fingerprint m is first generated based on the device attribute information, such as hardware configuration, operating system version, installed application list, etc., and then the device fingerprint and UUID are associated and calculated using a secure hash algorithm to generate an initial hash value, that is, H=Hash(m || UUID), which is the hash commitment of the device fingerprint. The hash processing combined with UUID and device fingerprint increases the security of the system and protects the original device fingerprint information from being leaked.

[0041] In a possible implementation of the present application, before determining whether the terminal device is abnormal based on the security baseline, the terminal operating environment security authentication method may also include: triggering the device authentication process at a set time according to the set verification cycle; in each verification cycle, updating the device fingerprint based on the collected device attribute information to obtain a device update fingerprint; and using a hash algorithm to associate the device update fingerprint and the device identification to obtain an updated hash value.

[0042] That is, the system can automatically trigger the verification process according to the preset verification cycle and complete the device authentication.

[0043] In this embodiment, in each verification cycle, the current status information of the device can be re-collected, the device fingerprint m' can be updated, and then the updated device fingerprint and UUID can be associated and calculated using the same hash algorithm as the initialization to generate a new fingerprint hash value H'=Hash(m'||UUID). This embodiment can monitor the device status in real time through periodic verification, timely discover and respond to potential security threats, and through hash verification, the original device fingerprint information will not be leaked, thereby enhancing privacy protection.

[0044] In a possible implementation of the present application, determining whether a terminal device is abnormal based on a security baseline may include: obtaining a current timestamp; using a hash algorithm to perform an association calculation on an updated hash value and a current timestamp to obtain an associated hash value; and determining whether the terminal device is abnormal based on the associated hash value and a hash commitment.

[0045] In this embodiment, the current timestamp Time can be obtained first, and the associated hash value of the current timestamp Time and the updated hash value H' can be calculated: h=Hash(H'|| Time), and then based on the associated hash value and hash commitment, it is determined whether the terminal device is abnormal.

[0046] Furthermore, determining whether the terminal device is abnormal based on the associated hash value and hash commitment may include: obtaining a hash commitment associated value based on the hash commitment and the current timestamp; when the associated hash value and the hash commitment associated value are the same, determining that the terminal device is normal and the device authentication of the terminal device has passed; when the associated hash value and the hash commitment associated value are not the same, determining that the terminal device is abnormal and triggering an alarm.

[0047] That is, the device's security baseline, i.e., hash commitment, and the current timestamp can be hashed to obtain the associated hash value corresponding to the hash commitment, i.e., hash commitment associated value: h'=Hash(H || Time). The associated hash value h' corresponding to the hash commitment is compared with the associated hash value h of the device corresponding to the current timestamp to determine whether the terminal device is abnormal. Compared with traditional security solutions such as firewalls and intrusion detection systems, periodic hash verification may have lower implementation and maintenance costs, reduce dependence on complex hardware and software, reduce the total cost of ownership (TCO) of the enterprise, and is easier to implement.

[0048] In a possible implementation of the present application, before determining whether the terminal device is abnormal based on comparing the associated hash value and the hash commitment, the terminal operating environment security authentication method may also include: determining the validity of the current timestamp based on whether the current timestamp is within the current time range; if the current timestamp is valid, querying the hash commitment of the terminal device.

[0049] In one embodiment, the device may send the UUID, Time and h triplet to the center for verification. The center performs the verification process as follows: 1) First determine the validity of the Time stamp and whether it is within the valid deviation range of the current time.

[0050] 2) If Time is valid, query the database through UUID to obtain the hash commitment H.

[0051] 3) Calculate the hash value h'=Hash(H || Time) and compare whether it is equal to h. If they are equal, the verification passes. Otherwise, the verification fails, indicating that the device has changed.

[0052] That is, if the currently received hash value is inconsistent with the hash value calculated in combination with the stored hash commitment, the system will identify it as an anomaly. Furthermore, based on the anomaly detection results, the system can automatically trigger an alarm to notify the administrator or security team; the system can also automatically perform some preliminary response measures, such as limiting the network access rights of the device or isolating the device; the security team can also conduct an in-depth analysis of the anomaly to determine the cause and nature of the anomaly; then, based on the analysis results, take corresponding repair measures, such as patching, updating the configuration, or removing malware; if the device has been repaired and confirmed to be safe, update the hash baseline of the device for future verification. Detailed anomaly reports and repair feedback can also be generated for users to check, and based on the anomaly and response results, the monitoring strategy and parameters can be optimized to improve the monitoring efficiency and accuracy of the system. Through the above embodiments, not only can the integrity of the device be monitored in real time, but also rapid responses can be made when anomalies are found to protect the security and stability of the system.

[0053] In a possible implementation of the present application, after determining the hash commitment of the terminal device, the terminal operating environment security authentication method may also include: storing the hash commitment in a central database or a distributed ledger as a security baseline for the terminal device.

[0054] That is, the hash commitment H of the UUID and device fingerprint can be stored in a central database or distributed ledger as a security baseline for the device.

[0055] The embodiment of the present application utilizes hash processing that combines UUID with device fingerprint to increase the security of the system and protect the original device fingerprint information from being leaked; the concept of periodic verification is introduced to perform regular checks on device fingerprints instead of responding only when an abnormality occurs, thereby improving the initiative and real-time nature of monitoring; compared with traditional security monitoring solutions that consume a lot of resources, the present embodiment is lightweight in design, has little impact on system performance, and is suitable for use by enterprises of all sizes; the present embodiment pays special attention to privacy protection and avoids direct exposure of sensitive information through hash processing.

[0056] Figure 2 Schematic diagram of the terminal operating environment security authentication system provided in the embodiment of the present application. Figure 2 As shown, the terminal operating environment security authentication system may include a collection module 201 , a determination module 202 and an authentication module 203 .

[0057] Among them, the collection module 201 is used to collect terminal device data, and the terminal device data includes device attribute information and device identification; the determination module 202 is used to determine the hash commitment of the terminal device based on the device attribute information and the device identification, and the hash commitment is the security baseline of the terminal device; the authentication module 203 is used to determine whether the terminal device is abnormal based on the security baseline during the device authentication process based on the set verification cycle, wherein each verification cycle updates the security baseline based on the collected device attribute information.

[0058] In the embodiment of the present application, first, the acquisition module 201 acquires the terminal device data, and the terminal device data includes device attribute information and device identification. Then, the determination module 202 determines the hash commitment of the terminal device based on the device attribute information and the device identification. The hash commitment is the security baseline of the terminal device. Finally, the authentication module 203 determines whether the terminal device is abnormal based on the security baseline during the device authentication process based on the set verification cycle, wherein each verification cycle updates the security baseline based on the collected device attribute information. The present application determines the hash commitment by hashing the device attribute information and the device identification, and uses the hash commitment as the security baseline of the terminal device, which increases the security of the terminal device, can ensure that the attribute information of the original device is not leaked, and through periodic verification, the device information of the device is regularly checked, which improves the initiative and real-time nature of device monitoring and improves the reliability of security protection.

[0059] In a possible implementation of the present application, the determination module 202 is used to: generate a device fingerprint based on device attribute information; use a hash algorithm to associate the device fingerprint and the device identification to obtain an initial hash value, the initial hash value is a hash commitment, and the device identification is the universal unique identification code UUID of the terminal device.

[0060] In a possible implementation of the present application, the authentication module 203 is used to: trigger the device authentication process at a set time according to the set verification cycle; update the device fingerprint based on the collected device attribute information in each verification cycle to obtain the device update fingerprint; use the hash algorithm to associate the device update fingerprint and the device identification to obtain an updated hash value.

[0061] In a possible implementation of the present application, the authentication module 203 is used to: obtain a current timestamp; use a hash algorithm to perform an association calculation on the updated hash value and the current timestamp to obtain an associated hash value; and determine whether the terminal device is abnormal based on the associated hash value and the hash commitment.

[0062] In one possible implementation of the present application, the authentication module 203 is used to: obtain a hash commitment association value based on the hash commitment and the current timestamp; when the associated hash value and the hash commitment association value are the same, determine that the terminal device is normal and the device authentication of the terminal device is passed; when the associated hash value and the hash commitment association value are not the same, determine that the terminal device is abnormal and trigger an alarm.

[0063] In a possible implementation of the present application, the authentication module 203 is used to: determine the validity of the current timestamp based on whether the current timestamp is within the current time range; and query the hash commitment of the terminal device if the current timestamp is valid.

[0064] In a possible implementation manner of the present application, the terminal operating environment security authentication system may further include a storage module.

[0065] Among them, the storage module is used to store the hash commitment in a central database or distributed ledger as a security baseline for the terminal device.

[0066] The terminal operating environment security authentication system provided in the embodiment of the present application can achieve Figure 1-3 The various processes implemented in the method embodiment achieve the same technical effect and will not be described again here to avoid repetition.

[0067] like Figure 3 As shown, an embodiment of the present application also provides an electronic device 300, including a processor 301, a memory 302, and a program or instruction stored in the memory 302 and executable on the processor 301. When the program or instruction is executed by the processor 301, each process of the above-mentioned method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0068] The embodiment of the present application also provides a storage medium, on which a program or instruction is stored, and when the program or instruction is executed by a processor, each process of the above method embodiment is implemented. And the same technical effect can be achieved, and to avoid repetition, it will not be repeated here.

[0069] The processor is the processor in the server described in the above embodiment. The storage medium includes computer storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk.

[0070] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned terminal operating environment security authentication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0071] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0072] The embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned terminal operating environment security authentication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0073] An embodiment of the present application further provides a processing device, which is configured to execute the various processes of the above-mentioned terminal operating environment security authentication method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0074] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and system in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0075] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0076] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A terminal operating environment security authentication method, characterized in that: include: Collecting terminal device data, wherein the terminal device data includes device attribute information and device identification; Determine a hash commitment of the terminal device based on the device attribute information and the device identification, where the hash commitment is a security baseline of the terminal device; In the process of performing device authentication based on a set verification cycle, whether the terminal device is abnormal is determined based on the security baseline, wherein each verification cycle updates the security baseline according to the collected device attribute information.

2. The method according to claim 1, characterized in that The determining the hash commitment of the terminal device based on the device attribute information and the device identification includes: Based on the device attribute information, generate a device fingerprint; The device fingerprint and the device identification are associated and calculated using a hash algorithm to obtain an initial hash value, where the initial hash value is the hash commitment, and the device identification is the universal unique identification code UUID of the terminal device.

3. The method according to claim 2, characterized in that Before determining whether the terminal device is abnormal based on the security baseline, the method further includes: According to the set verification cycle, the device authentication process is triggered regularly; In each verification cycle, the device fingerprint is updated based on the collected device attribute information to obtain a device update fingerprint; A hash algorithm is used to perform an association calculation on the device update fingerprint and the device identification to obtain an updated hash value.

4. The method according to claim 3, characterized in that The determining whether the terminal device is abnormal based on the security baseline includes: Get the current timestamp; Using a hash algorithm to perform an association calculation on the updated hash value and the current timestamp to obtain an associated hash value; Based on the associated hash value and the hash commitment, it is determined whether the terminal device is abnormal.

5. The method according to claim 4, characterized in that The determining whether the terminal device is abnormal based on the associated hash value and the hash commitment includes: Based on the hash commitment and the current timestamp, obtaining a hash commitment associated value; When the associated hash value and the hash commitment associated value are the same, it is determined that the terminal device is normal and the device authentication of the terminal device is passed; In the case where the associated hash value and the hash commitment associated value are not the same, it is determined that the terminal device is abnormal and an alarm is triggered.

6. The method according to claim 4, characterized in that Before determining whether the terminal device is abnormal based on the comparison between the associated hash value and the hash commitment, the method further includes: Determining the validity of the current timestamp based on whether the current timestamp is within a current time range; When the current timestamp is valid, query the hash commitment of the terminal device.

7. The method according to claim 1, characterized in that After determining the hash commitment of the terminal device, the method further includes: The hash commitment is stored in a central database or distributed ledger as a security baseline for the terminal device.

8. A terminal operating environment security authentication system, characterized in that: include: A collection module, used to collect terminal device data, wherein the terminal device data includes device attribute information and device identification; A determination module, configured to determine a hash commitment of the terminal device based on the device attribute information and the device identification, wherein the hash commitment is a security baseline of the terminal device; The authentication module is used to determine whether the terminal device is abnormal based on the security baseline during the device authentication process based on the set verification cycle, wherein each verification cycle updates the security baseline based on the collected device attribute information.

9. An electronic device, characterized in that: The method comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method according to any one of claims 1 to 7.

10. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images