Host device control method, device, storage medium and electronic device

Abstract

The embodiments of the present application provide a method, apparatus, storage medium, and electronic device for controlling a host device, wherein the method comprises: receiving a target joining request from a target account; in response to the target joining request, extracting the second identity information of a second host device and the connection information of the second host device using the first identity information of the first host device, wherein the connection information is used to indicate the connection relationship between the second host device and other host devices in a distributed system; verifying the attribution of the second host device relative to the initial device link based on the second identity information and the connection information; and when the attribution indicates that the second host device is allowed to belong to the initial device link, adding the second host device to the initial device link to obtain the target device link. Through the present application, the problem of low control efficiency of the host device is solved, thereby achieving the effect of improving the control efficiency of the host device.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computers, and in particular, to a control method, apparatus, storage medium, and electronic device for a host device. Background Art

[0002] Users log in to the host device in the distributed system and then control multiple host devices by connecting the host devices. However, since the host device is allowed to be logged in by the user and is also allowed to be connected by other host devices, accidents may occur due to misoperation, remote operation, and unauthorized operation of the host device.

[0003] In view of the problems in related technologies such as low control efficiency of host devices, no effective solutions have been proposed. Summary of the Invention

[0004] Embodiments of the present application provide a method, apparatus, storage medium, and electronic device for controlling a host device, to at least solve the problem of low control efficiency of the host device in related technologies.

[0005] According to one embodiment of the present application, a method for controlling a host device is provided. A distributed system includes N host devices, M of the N host devices are interconnected to form an initial device link, each host device in the initial device link has identity information indicating that the host device belongs to a target device network, and the initial device link is configured to allow control of the M host devices via a target account. The method is applied to a first host device in the initial device link, and the method includes:

[0006] receiving a target joining request sent by the target account, wherein the target joining request is used to request a second host device among the NM host devices to be added to the initial device link;

[0007] In response to the target join request, extracting second identity information of the second host device and connection information of the second host device using the first identity information of the first host device, wherein the connection information is used to indicate a connection relationship between the second host device and other host devices in the distributed system;

[0008] verifying the attribution of the second host device to the initial device link based on the second identity information and the connection information;

[0009] In a case where the attribution attribute indicates that the second host device is allowed to belong to the initial device link, the second host device is added to the initial device link to obtain a target device link.

[0010] In an exemplary embodiment, extracting the second identity information of the second host device and the connection information of the second host device using the first identity information of the first host device includes: obtaining a first registration code of the first host device in the target device network as the first identity information, wherein the first registration code is used to indicate a unique identifier of the first host device in the target device network; sending the first identity information and a first status code of the first host device to the second host device, wherein the second host device is used to search for the first identity information from first ledger information of a reference device network to which the second host device belongs upon receiving the first identity information and the first status code; parsing the first status code upon finding the first identity information; and extracting the second registration code of the second host device as the second identity information and the second status code of the second host device as the connection information of the second host device if the first status code indicates that the first host device is allowed to connect to other host devices, wherein the first ledger information is used to record registration codes corresponding to host devices included in the reference device network; and receiving the second identity information and the connection information sent by the second host device in response to the first identity information and the first status code.

[0011] In an exemplary embodiment, the verifying the attribution of the second host device relative to the initial device link based on the second identity information and the connection information includes: verifying whether the second host device belongs to the target device network based on the second identity information and second ledger information of the target device network, wherein the second identity information is the registration code of the second host device in the device network to which the second host device belongs, and the second ledger information is used to record the registration codes corresponding to the host devices included in the target device network; verifying whether the second host device is allowed to connect with other host devices based on the connection information; and when it is verified that the second host device belongs to the target device network and that the second host device is allowed to connect with other host devices, determining the attribution to indicate that the second host device is allowed to belong to the initial device link.

[0012] In an exemplary embodiment, verifying whether the second host device belongs to the target device network based on the second identity information and the second ledger information of the target device network includes: searching for the second identity information from the second ledger information; if the second identity information is found in the second ledger information, determining and verifying that the second host device belongs to the target device network; if the second identity information is not found in the second ledger information, determining and verifying that the second host device does not belong to the target device network; verifying whether the second host device is allowed to connect with other host devices based on the connection information includes: if the connection information is used to indicate that the second host device does not have a connection relationship with other host devices in the distributed system, determining and verifying that the second host device is allowed to connect with other host devices; if the connection information is used to indicate that the second host device has a connection relationship with other host devices in the distributed system, determining and verifying that the second host device is not allowed to connect with other host devices.

[0013] In an exemplary embodiment, adding the second host device to the initial device link to obtain the target device link includes: obtaining a reference account of the second host device and the account password corresponding to the reference account; logging into the second host device using the reference account and the account password corresponding to the reference account; and determining that the second host device has been added to the initial device link after logging into the second host device using the reference account and the account password corresponding to the reference account, and determining the initial device link with the second host device as the target device link.

[0014] In an exemplary embodiment, after adding the second host device to the initial device link to obtain the target device link, the method further includes: generating a join record for adding the second host device to the initial device link, wherein the join record carries a timestamp of adding the second host device to the initial device link and event information of adding the second host device to the initial device link; and sending the join record to each host device included in the target device network, wherein each host device included in the target device network is configured to write the join record into the third ledger information corresponding to each host device upon receiving the join record.

[0015] In an exemplary embodiment, the method further includes: detecting whether the first host device is the first host device in the target device link; when the first host device is the first host device in the target device link and receives a local operation instruction, disconnecting the connection between the first host device and the second host device, wherein the local operation instruction is an operation instruction issued by an external device on the first host device; when the first host device is not the first host device in the target device link and receives the local operation instruction, disconnecting the connection between the first host device and the last host device connected to the first host device, as well as the connection between the first host device and the second host device; when the first host device is the first host device in the target device link and receives a reference join request, disconnecting the connection between the first host device and the second host device in response to the reference join request, wherein the reference join request The request is used to request the first host device to join other device links; when the first host device is not the first host device of the target device link and, in the case of receiving the reference joining request, disconnect the connection between the first host device and the previous host device connected to the first host device, and the connection between the first host device and the second host device in response to the reference joining request; when the first host device is the first host device of the target device link and, in the case of exceeding a time threshold without receiving an account operation instruction issued by the target account, disconnect the connection between the first host device and the second host device; when the first host device is not the first host device of the target device link and, in the case of exceeding a time threshold without receiving the account operation instruction issued by the target account, disconnect the connection between the first host device and the previous host device connected to the first host device, and the connection between the first host device and the second host device.

[0016] According to another embodiment of the present application, a host device control apparatus is provided. A distributed system includes N host devices, M of the N host devices are interconnected to form an initial device link, each host device in the initial device link has identity information indicating that the host device belongs to a target device network, and the initial device link is configured to allow control of the M host devices via a target account. The apparatus is applied to a first host device in the initial device link, and includes:

[0017] a receiving module, configured to receive a target joining request sent by the target account, wherein the target joining request is used to request that a second host device among the NM host devices be added to the initial device link;

[0018] an extraction module, configured to respond to the target joining request and extract, using the first identity information of the first host device, the second identity information of the second host device and the connection information of the second host device, wherein the connection information is used to indicate a connection relationship between the second host device and other host devices in the distributed system;

[0019] a verification module, configured to verify the attribution of the second host device to the initial device link based on the second identity information and the connection information;

[0020] The adding module is configured to add the second host device to the initial device link to obtain a target device link when the attribution attribute indicates that the second host device is allowed to belong to the initial device link.

[0021] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. The computer program is configured to execute the steps of any one of the above method embodiments when run.

[0022] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0023] According to another embodiment of the present application, a computer program product is provided, including a computer program, which implements the steps of any of the above method embodiments when executed by a processor.

[0024] Through the present application, a target joining request sent by a target account is received, wherein the target joining request is used to request that a second host device among NM host devices be added to the initial device link; in response to the target joining request, the second identity information of the second host device and the connection information of the second host device are extracted using the first identity information of the first host device, wherein the connection information is used to indicate the connection relationship between the second host device and other host devices in the distributed system; the attribution of the second host device relative to the initial device link is verified based on the second identity information and the connection information; when the attribution is used to indicate that the second host device is allowed to belong to the initial device link, the second host device is added to the initial device link to obtain the target device link. Since it is ensured that the second host device is allowed to belong to the initial device link before the second host device is added to the initial device link, remote regulation operations that occur when the second host device is not allowed to belong to the initial device link are prevented, the problem of low control efficiency of the host device can be solved, thereby achieving the effect of improving the control efficiency of the host device. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 This is a hardware structure block diagram of a server device for a host device control method according to an embodiment of the present application;

[0026] Figure 2 is a flowchart of a control method of a host device according to an embodiment of the present application;

[0027] Figure 3 1 is a schematic diagram of a process in which host A controls host B according to an embodiment of the present application;

[0028] Figure 4 is a flow chart of disconnecting a first host device from a second host device according to an embodiment of the present application;

[0029] Figure 5 is a schematic diagram of a target device network according to an embodiment of the present application;

[0030] Figure 6 is a structural block diagram of a control device of a host device according to an embodiment of the present application;

[0031] Figure 7 This is a structural block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0032] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0033] It should be noted that the terms "first", "second", etc. in the description and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0034] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 This is a hardware structure block diagram of a server device for a host device control method according to an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1 Only one is shown) a processor 102 (the processor 102 may include but is not limited to a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data. The server device may also include a transmission device 106 and an input / output device 108 for communication functions. It will be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components than shown, or with Figure 1 Different configurations shown.

[0035] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the control method of the host device in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, implementing the above-mentioned method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely located relative to the processor 102, and these remote memories may be connected to the server device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0036] Transmission device 106 is used to receive or transmit data via a network. A specific example of the aforementioned network may include a wireless network provided by a communication provider of the server device. In one embodiment, transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to enable communication with the Internet. In another embodiment, transmission device 106 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0037] In this embodiment, a method for controlling a host device is provided. A distributed system includes N host devices. M of the N host devices are interconnected to form an initial device link. Each host device in the initial device link has identity information indicating that the host device belongs to a target device network. The initial device link is configured to allow control of the M host devices via a target account. The method is applied to a first host device in the initial device link. Figure 2 is a flow chart of a control method of a host device according to an embodiment of the present application, such as Figure 2 As shown, the process includes the following steps:

[0038] Step S202: receiving a target joining request sent by the target account, wherein the target joining request is used to request to join a second host device among the NM host devices to the initial device link;

[0039] Step S204: In response to the target join request, extract the second identity information of the second host device and the connection information of the second host device using the first identity information of the first host device, wherein the connection information is used to indicate a connection relationship between the second host device and other host devices in the distributed system;

[0040] Step S206: Verify the attribution of the second host device to the initial device link based on the second identity information and the connection information;

[0041] Step S208 : When the attribution attribute indicates that the second host device is allowed to belong to the initial device link, the second host device is added to the initial device link to obtain a target device link.

[0042] Through the above steps, a target joining request sent by the target account is received, wherein the target joining request is used to request that the second host device among the NM host devices be added to the initial device link; in response to the target joining request, the second identity information of the second host device and the connection information of the second host device are extracted using the first identity information of the first host device, wherein the connection information is used to indicate the connection relationship between the second host device and other host devices in the distributed system; the attribution of the second host device relative to the initial device link is verified based on the second identity information and the connection information; when the attribution is used to indicate that the second host device is allowed to belong to the initial device link, the second host device is added to the initial device link to obtain the target device link. Since it is ensured that the second host device is allowed to belong to the initial device link before the second host device is added to the initial device link, remote regulation operations that occur when the second host device is not allowed to belong to the initial device link are prevented. Therefore, the problem of low control efficiency of the host device can be solved, thereby achieving the effect of improving the control efficiency of the host device.

[0043] Optionally, in this embodiment, the host device control method proposed in this application is used in a wide range of scenarios, including but not limited to: operation and maintenance personnel monitoring the behavior of the host device, operation and maintenance personnel controlling the host device to perform operations, etc. In the following embodiments, the usage scenarios are not limited, and the host device control method proposed in this application can be used in any scenario that requires controlling one or more host devices through a target account.

[0044] Optionally, in this embodiment, the above-mentioned distributed system includes N host devices, where N is an integer greater than 1. It is possible but not limited to connecting multiple host devices among the N host devices to each other to form one or more device links. For example, taking the distributed system including host device 1, host device 2, host device 3, host device 4 and host device 5 as an example, it is possible but not limited to connecting host device 1 and host device 2 to form device link 1, and connecting host device 3, host device 4 and host device 5 in sequence to form device link 2, etc.

[0045] Optionally, in this embodiment, for host devices belonging to the same initial device link, they all have identity information for indicating that the host device belongs to the target device network. It can be but not limited to screening P host devices from the N host devices included in the distributed system to join the target device network, and then connecting M host devices among the P host devices that have joined the target device network to each other to form an initial device link, where P is a positive integer less than or equal to N, and M is an integer less than or equal to P and greater than 1.

[0046] Optionally, in this embodiment, it is possible but not limited to installing a remote control authority management program in the N host devices included in the distributed system. The remote control authority management program is used to add the host devices installed with the remote control authority management program to the same target device network and assign the host devices added to the target device network their identity information in the target device network. For example, using the remote control authority management program installed on each host device, multiple host devices that have the remote control authority management program installed and are network-reachable are formed into a blockchain network, and a unique registration code is randomly generated for each host device as the host device's identity information in the blockchain network. It should be noted that the registration code cannot be changed and is strongly bound to the current host device. The host device can use, but is not limited to, the private key and public key derived from the registration code to perform identity authentication between host devices in the target device network, and each host device connected to the target device network will automatically obtain all account data in the current target device network after completing registration and authentication.

[0047] Optionally, in this embodiment, the host devices belonging to the target device network may be allowed to remotely interconnect in a P2P (Peer to Peer, peer-to-peer network) manner, but is not limited to the above.

[0048] In the technical solution provided in the above step S202, the user can, but is not limited to, send a request to the initial device link and the host device in the initial device link through the target account. For example, the user sends a target joining request to the host device in the initial device link through the target account to request that the second host device among the NM host devices be added to the initial device link; the user sends an account operation instruction to the host device in the initial device link through the target account to control the host device in the initial device link to perform an operation, etc.

[0049] In the technical solution provided in the above step S204, it is possible but not limited to that in the process of adding the first host device to the target device network, the first host device is assigned a unique identifier in the target device network as the first identity information of the first host device, for example: the first host device is added to the target device network using a remote control authority management program installed on the first host device, and a unique registration code is randomly generated for each first host device as the first identity information of the first host device in the target device network.

[0050] Optionally, in this embodiment, the first identity information of the first host device may be sent to the second host device, but is not limited to the first identity information of the first host device, and the second identity information and connection information of the second host device may be returned by the second host device. Alternatively, the second identity information and connection information of the second host device may be obtained by other means.

[0051] In an exemplary embodiment, the first identity information of the first host device can be used to extract the second identity information of the second host device and the connection information of the second host device in the following manner, but is not limited to: obtaining a first registration code of the first host device in the target device network as the first identity information, wherein the first registration code is used to indicate a unique identifier of the first host device in the target device network; sending the first identity information and a first status code of the first host device to the second host device, wherein the second host device is used to search for the first identity information from first ledger information of a reference device network to which the second host device belongs upon receiving the first identity information and the first status code; parsing the first status code upon finding the first identity information; and extracting the second registration code of the second host device as the second identity information and the second status code of the second host device as the connection information of the second host device when the first status code indicates that the first host device is allowed to connect to other host devices, wherein the first ledger information is used to record registration codes corresponding to host devices included in the reference device network; and receiving the second identity information and the connection information sent by the second host device in response to the first identity information and the first status code.

[0052] Optionally, in this embodiment, a status code can be generated for each host device included in the target device network based on whether each host device exists in the device link, but is not limited to: if the host device exists in the device link, the status code of the host device is set to 1; if the host device does not exist in the device link, the status code of the host device is set to 0. In other words, if the status code of the host device is 1, it is considered that the host device has a connection relationship with other host devices, that is, it has been controlled to respond to requests issued by a specific account; if the status code of the host device is 0, it is considered that the host device does not have a connection relationship with other host devices, that is, the host device is not controlled and is allowed to join the device link. Furthermore, the status code can also be used to indicate the position of the host device in the device link, for example, setting the status code of the host device to 1-N, where N is the position of the host device in the device link, etc.

[0053] Optionally, in this embodiment, the last host device in the device chain can still be allowed to connect to the next host device. Therefore, the status code of the host device can be set to ANB, N is the position of the host device in the device chain, A is used to indicate whether there is a previous host device connected to the host device in the initial device chain, and B is used to indicate whether there is a next host device connected to the host device in the initial device chain. For example, taking the status code of the host device as 1-3-0 as an example, it can be seen that the host device is the third host device in the initial device chain and the last host device in the initial device chain.

[0054] Optionally, in this embodiment, the first registration code and the first status code of the first host device are sent to the second host device. The second host device can be used, but is not limited to, to verify the connection status of the first host device based on the first registration code and the first status code of the first host device. For example, when it is determined according to the first registration code that the first host device and the second host device belong to the same device network, and when it is determined according to the first status code that the first host device allows connection to the host device, the second host device determines that the connection status of the first host device is to allow the first host device to connect to the second host device.

[0055] Optionally, in this embodiment, when the second host device detects that the first status code is used to indicate that the first host device is allowed to connect to other host devices, the second host device extracts the second registration code of the second host device as the second identity information, and extracts the second status code of the second host device as the connection information of the second host device and sends it to the first host device.

[0056] In an exemplary embodiment, the first identity information of the first host device can be used, but is not limited to, in the following manner to extract the second identity information of the second host device and the connection information of the second host device: obtaining a first registration code of the first host device in the target device network as the first identity information, wherein the first registration code is used to indicate a unique identifier of the first host device in the target device network; using the first identity information and a first status code of the first host device to generate a first verification request, wherein the first verification request carries a target private key generated according to the first identity information; sending the first verification request to the second host device, wherein the second host device is used to extract the target private key from the first verification request upon receiving the first verification request, and extract the target private key from the first verification request; The method further comprises searching for a target public key corresponding to the target private key in the fourth ledger information of the reference device network to which the second host device belongs. When the target public key is found, parsing the first status code, and when the first status code indicates that the first host device is allowed to connect to other host devices, extracting the second registration code of the second host device as the second identity information, and extracting the second status code of the second host device as the connection information of the second host device, wherein the first ledger information is used to record the registration codes corresponding to the host devices included in the reference device network, and the fourth ledger information is used to record the public keys and private keys corresponding to the host devices included in the reference device network; and receiving the second identity information and the connection information sent by the second host device in response to the first identity information and the first status code.

[0057] Optionally, in this embodiment, host devices belonging to the same device network may, but are not limited to, have the same account book information and a registration code that is unique in the device network. The host device may, but is not limited to, use a private key and a public key derived from its registration code to perform identity authentication between host devices in the device network. For example, the host device retains the private key and broadcasts the public key in the device network. The host devices in the device network can parse the information sent by the host device through the public key and authenticate that the information they receive belongs to the host device corresponding to the public key.

[0058] Optionally, in this embodiment, taking the target device network as a blockchain and the initial device link as a control link constructed in the blockchain through the control method of the host device proposed in this application as an example, when the user requests to add the host device to the device link, all remote control operations will be recorded on the blockchain, providing an unalterable audit trail, improving the security of the system, reducing the risk of single point failure of the centralized authentication server, and increasing the transparency of operations.

[0059] In the technical solution provided in the above step S206, the first host device can, but is not limited to, verify whether the second host device belongs to the target device network based on the second identity information, and verify whether the second host device is allowed to connect with other host devices (be controlled by other host devices) based on the connection information. If the second host device belongs to the target device network and the second host device is allowed to connect with other host devices, the first host device determines the attribution of the second host device relative to the initial device link to indicate that the second host device is allowed to belong to the initial device link.

[0060] In an exemplary embodiment, the attribution of the second host device relative to the initial device link can be verified based on the second identity information and the connection information in the following manner, but is not limited to: verifying whether the second host device belongs to the target device network based on the second identity information and the second ledger information of the target device network, wherein the second identity information is the registration code of the second host device in the device network to which the second host device belongs, and the second ledger information is used to record the registration codes corresponding to the host devices included in the target device network; verifying whether the second host device is allowed to connect with other host devices based on the connection information; and when it is verified that the second host device belongs to the target device network and that the second host device is allowed to connect with other host devices, determining the attribution to indicate that the second host device is allowed to belong to the initial device link.

[0061] Optionally, in this embodiment, the registration code corresponding to the second identity information may be searched in the second account book information, but is not limited to. If the registration code corresponding to the second identity information is found in the second account book information, it is determined that the second host device belongs to the target device network based on the second identity information and the second account book information of the target device network; or, if the registration code corresponding to the second identity information is not found in the second account book information, it is determined that the second host device does not belong to the target device network based on the second identity information and the second account book information of the target device network.

[0062] Optionally, in this embodiment, the connection information of the second host device is the status code of the second host device. The meaning of the status code of the second host device can be parsed, but is not limited to, to determine whether the second host device is allowed to connect with other host devices. For example, if the status code is 0, indicating that the host device is not controlled by other hosts (i.e., the host device has not joined the device link), and the status code is 1, indicating that the host device is controlled by other hosts (i.e., the host device has joined the device link), when the status code of the second host device is equal to 0, it is determined that the second host device is allowed to connect with other host devices.

[0063] It's important to note that during the second host device's verification of the first host device, it must verify whether the first host device is allowed to control other host devices. This means that the first host device will only be allowed to connect to other host devices if it's not already a host device in the device chain, or if it's the last host device in the device chain. During the first host device's verification of the second host device, it must also verify that the second host device is not already a host device in the device chain before it's allowed to connect to other host devices. This ensures that adding the second host device to the initial device chain won't interfere with the operation of the device chain it originally belonged to. Therefore, adding the second host device to the initial device chain is permitted only if it's already a host device that's not already a host device in the device chain.

[0064] In an exemplary embodiment, the following method may be used to verify whether the second host device belongs to the target device network based on the second identity information and the second ledger information of the target device network, including: searching the second identity information from the second ledger information; if the second identity information is found in the second ledger information, determining and verifying that the second host device belongs to the target device network; if the second identity information is not found in the second ledger information, determining and verifying that the second host device does not belong to the target device network; and the following method may be used to verify whether the second host device is allowed to connect with other host devices based on the connection information, including, but not limited to: if the connection information is used to indicate that the second host device does not have a connection relationship with other host devices in the distributed system, determining and verifying that the second host device is allowed to connect with other host devices; if the connection information is used to indicate that the second host device has a connection relationship with other host devices in the distributed system, determining and verifying that the second host device is not allowed to connect with other host devices.

[0065] Optionally, in this embodiment, the first host device and the second host device achieve mutual authentication through the above process, ensuring that both the first host device and the second host device establishing the connection are verified legal entities, reducing the risk of being impersonated by a malicious third party, and preventing man-in-the-middle attacks by verifying the identity of the other party, ensuring that subsequent data transmitted through the link is transmitted directly between the intended communicating parties. After the communicating parties verify their identities with each other, a trust relationship can be established, laying the foundation for further communication and data exchange, and mutual authentication can strengthen access control policies to ensure that only authorized hosts can access sensitive resources.

[0066] In the technical solution provided in the above step S208, the first host device may, but is not limited to, establish a connection with the second host device to add the second host device to the initial device link and obtain the target device link.

[0067] In an exemplary embodiment, the second host device can be added to the initial device link to obtain the target device link in the following manner, but is not limited to: obtaining a reference account of the second host device and the account password corresponding to the reference account; logging into the second host device using the reference account and the account password corresponding to the reference account; after logging into the second host device using the reference account and the account password corresponding to the reference account, determining that the second host device has been added to the initial device link, and determining the initial device link to which the second host device has been added as the target device link.

[0068] In an exemplary embodiment, after the second host device is added to the initial device link to obtain the target device link, the following method may be used, but is not limited to: generating a joining record for adding the second host device to the initial device link, wherein the joining record carries a timestamp of adding the second host device to the initial device link and event information of adding the second host device to the initial device link; and sending the joining record to each host device included in the target device network, wherein each host device included in the target device network is configured to write the joining record into the third ledger information corresponding to each host device upon receiving the joining record.

[0069] In an exemplary embodiment, an example of a process in which host A controls host B is provided. Figure 3 FIG. 1 is a schematic diagram of a process in which host A controls host B according to an embodiment of the present application. Figure 3 As shown, taking the first host device as host A and the second host device as host B as an example, host A can obtain control of host B through, but is not limited to, the following methods to achieve remote control of host B:

[0070] When host A attempts to remotely connect to host B, it sends its authentication information (first registration code) and status code to host B, attempting to connect. Based on host A's authentication information, host B determines that hosts A and B belong to the same device network and, based on host A's status code, allows host A to connect. After successfully authenticating host A, host B sends back its authentication information (second registration code) and status code. Host A verifies host B based on its authentication information and status code. After successfully authenticating host B, host A logs in to host B using its username and password. If host B successfully verifies its username and password, host A is allowed to remotely control host B, gaining control of host B. If the user and password verification succeeds, host B changes its status code to 1 and broadcasts its new control chain, based on host A's existing control chain and its own, to the target device network. Host A, in turn, broadcasts its new control chain to the target device network based on host B's response. The ledger host in the target device network verifies the remote control information based on the public information of hosts A and B and records it in the data ledger.

[0071] Moreover, during the mutual verification process between host A and host B, if either party fails to verify the other party, the other party's IP and other information will be broadcast and recorded in the log.

[0072] In an exemplary embodiment, Figure 4 is a flow chart of disconnecting a first host device from a second host device according to an embodiment of the present application. Figure 4 As shown, the connection between the first host device and the second host device can be disconnected by, but is not limited to, the following steps:

[0073] Step S402: Detecting whether the first host device is the first host device in the target device link; Step S404: If the first host device is the first host device in the target device link and, upon receiving a local operation instruction, disconnecting the first host device from the second host device, wherein the local operation instruction is an operation instruction issued by an external device on the first host device; If the first host device is not the first host device in the target device link and, upon receiving the local operation instruction, disconnecting the first host device from the last host device connected to the first host device, and disconnecting the first host device from the second host device;

[0074] Step S406: If the first host device is the first host device of the target device link and receives a reference join request, responding to the reference join request to disconnect the first host device from the second host device, wherein the reference join request is used to request the first host device to join another device link; if the first host device is not the first host device of the target device link and receives the reference join request, responding to the reference join request to disconnect the first host device from the last host device to which the first host device was connected, and disconnect the first host device from the second host device;

[0075] Step S408: When the first host device is the first host device of the target device link and the account operation instruction issued by the target account is not received within a time threshold, the connection between the first host device and the second host device is disconnected; when the first host device is not the first host device of the target device link and the account operation instruction issued by the target account is not received within the time threshold, the connection between the first host device and the previous host device to which the first host device was connected, as well as the connection between the first host device and the second host device are disconnected.

[0076] Optionally, in this embodiment, the above processes can be performed simultaneously in the control method of the host device proposed in this application, but are not limited to, and step S404, step S406 and step S408 can be performed in parallel, that is, when any situation in step S404, step S406 and step S408 is detected, the corresponding step can be executed.

[0077] In the technical solution provided in the above step S404, when the first host device receives a local IO control device (local operation instruction) such as a mouse or keyboard, the connection between the first host device and the second host device is disconnected. Furthermore, when the first host device has a host device connected to the upper level, the connection with the upper level host device is continued to be disconnected.

[0078] In the technical solution provided in the above step S406, when other host devices attempt to connect to the first host device, the first host device disconnects from the second host device. Further, when the first host device has a host device connected to the upper level, the connection with the upper level host device continues to be disconnected.

[0079] In the technical solution provided in the above step S408, if the first host device does not receive the account operation instruction (which may include but is not limited to a join request and a control instruction for the host device in the target device link, etc.) issued by the target account for a time period exceeding a time threshold, the first host device disconnects from the second host device. Furthermore, if the first host device has a host device at the upper level connected to it, the connection with the upper level host device is further disconnected.

[0080] Optionally, in this embodiment, when the target device link changes, the host device that has changed may, but is not limited to, proactively modify its own status code and broadcast it to the host device at the next level.

[0081] Optionally, in this embodiment, taking the target device network as a blockchain network as an example, the control method of the host device proposed in this application provides a distributed remote control authority management system based on blockchain. The method and system provide a safe, reliable and transparent remote control authority management system through blockchain technology, which effectively prevents unauthorized operations and improves the authority control capability of the host device. The control chain integrity protection mechanism ensures the security of multi-level remote control. In addition, all operations are recorded on the blockchain, providing real-time auditing and tracking capabilities, which helps to quickly discover and respond to security incidents.

[0082] Optionally, in this embodiment, in order to better understand the above-mentioned target device network in the host device control method proposed in this application, the above-mentioned process is described below in combination with an optional embodiment, but it is not used to limit the technical solution of the embodiment of this application.

[0083] In one exemplary embodiment, an example of a target device network is provided. Figure 5 is a schematic diagram of a target device network according to an embodiment of the present application, such as Figure 5 As shown in the figure, taking a target device network consisting of host devices A, B, C, and D as an example, the blockchain network is composed of network-reachable host devices A, B, C, and D, which have installed a remote control permission management program to form a blockchain network. Host devices A, B, C, and D have unique identities within the blockchain network and are remotely connected in a P2P manner. In other words, host devices A, B, C, and D are allowed to authenticate each other and establish a connection to form a device link.

[0084] After installation, the remote control permission management program will randomly generate a unique registration code for the current host device. This registration code cannot be changed and is strongly bound to the current host device. The private key and public key derived from this registration code are used for identity authentication between host devices in the blockchain network.

[0085] Each host device connected to the blockchain network will automatically obtain all the ledger data in the current blockchain after completing registration and authentication. Each host device connected to the blockchain network has a status code. The default value is 0, indicating that it is not controlled by other hosts. When another host device remotely controls it, the status code will be set to 1, indicating that it is in a remotely controlled state.

[0086] The remote control permissions of the host device are protected by registration codes and status codes, allowing only other authenticated host devices within the blockchain network to remotely control it, while isolating and denying remote control to hosts outside the blockchain network. Furthermore, when the host device is identified as being under remote control and input is received from local IO control devices such as the mouse or keyboard (when local operation is detected), the upstream and downstream connections in the control chain are actively disconnected.

[0087] When remote control is required between host devices, authentication is performed using the unique signature information sent by the other party in the blockchain. The signature in the broadcast message is also verified to confirm whether the sender is a legitimate host in the blockchain. When communication is required between host devices in the blockchain network, data transmission between hosts is encrypted, enabling encrypted transmission of communication data between different hosts in the entire system.

[0088] This log records events within the blockchain network, recording information such as connection establishment, disconnection, and authentication success / failure by different hosts using timestamps. Furthermore, it can, but is not limited to, hashing data such as log information from the target device network to generate the hash code for the current block, receive and process information broadcast by other hosts in the blockchain, broadcast event information for its own host, and execute blockchain contracts. Furthermore, it is responsible for storing and updating host status codes.

[0089] In the host device control method proposed in this application, the immutability and decentralization characteristics of the blockchain are used to enhance the security and transparency of remote control, and then distributed authentication of user identity and permissions is performed through the blockchain network to ensure that only authorized users can perform remote control operations. The host devices authenticate each other before establishing a remote control session, which increases security. Smart contracts are used to automatically perform permission checks and operation log records, which reduces manual intervention and improves efficiency and security. The system maintains complete control chain records to ensure that each link of multi-level remote control is authorized and verified. If any host in the control chain is controlled by an unauthorized user, the system will automatically disconnect the control chain of the host and all subsequent hosts, and require the user to re-authenticate. All remote control operations will be recorded on the blockchain, providing an unalterable audit trail. Through the above mechanism, the system can effectively prevent unauthorized operations and unauthorized access, thereby enhancing the security of the jump server.

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

[0091] In this embodiment, a control device for a host device is also provided. The distributed system includes N host devices, and M host devices of the N host devices are interconnected to form an initial device link. The host devices in the initial device link all have identity information for indicating that the host device belongs to the target device network. The initial device link is configured to allow the M host devices to be controlled by the target account. The device is applied to the first host device in the initial device link. The device is used to implement the above-mentioned embodiments and preferred implementation methods, and those that have been explained will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceivable.

[0092] Figure 6 is a structural block diagram of a control device of a host device according to an embodiment of the present application, such as Figure 6 As shown, the device includes:

[0093] a receiving module 62 configured to receive a target joining request sent by the target account, wherein the target joining request is used to request that a second host device among the NM host devices be added to the initial device link;

[0094] an extraction module 64, configured to, in response to the target joining request, extract, using the first identity information of the first host device, the second identity information of the second host device and the connection information of the second host device, wherein the connection information is used to indicate a connection relationship between the second host device and other host devices in the distributed system;

[0095] a verification module 66, configured to verify the attribution of the second host device to the initial device link based on the second identity information and the connection information;

[0096] The adding module 68 is configured to add the second host device to the initial device link to obtain a target device link when the attribution attribute indicates that the second host device is allowed to belong to the initial device link.

[0097] Through the above-mentioned device, a target joining request sent by a target account is received, wherein the target joining request is used to request that a second host device among NM host devices be added to the initial device link; in response to the target joining request, the second identity information of the second host device and the connection information of the second host device are extracted using the first identity information of the first host device, wherein the connection information is used to indicate the connection relationship between the second host device and other host devices in the distributed system; the attribution of the second host device relative to the initial device link is verified based on the second identity information and the connection information; when the attribution indicates that the second host device is allowed to belong to the initial device link, the second host device is added to the initial device link to obtain the target device link. Since it is ensured that the second host device is allowed to belong to the initial device link before the second host device is added to the initial device link, remote regulation operations that occur when the second host device is not allowed to belong to the initial device link are prevented. Therefore, the problem of low control efficiency of the host device can be solved, thereby achieving the effect of improving the control efficiency of the host device.

[0098] In an exemplary embodiment, the extraction module includes:

[0099] a first acquiring unit, configured to acquire a first registration code of the first host device in the target device network as the first identity information, wherein the first registration code is used to indicate a unique identifier of the first host device in the target device network;

[0100] a sending unit, configured to send the first identity information and a first status code of the first host device to the second host device, wherein the second host device is configured to, upon receiving the first identity information and the first status code, search for the first identity information from first ledger information of a reference device network to which the second host device belongs; upon finding the first identity information, parse the first status code; and, if the first status code indicates that the first host device is allowed to connect to another host device, extract a second registration code of the second host device as the second identity information, and extract the second status code of the second host device as the connection information of the second host device, wherein the first ledger information is configured to record registration codes corresponding to host devices included in the reference device network;

[0101] A receiving unit is configured to receive the second identity information and the connection information sent by the second host device in response to the first identity information and the first status code.

[0102] In an exemplary embodiment, the verification module includes:

[0103] a first verification unit, configured to verify whether the second host device belongs to the target device network based on the second identity information and second ledger information of the target device network, wherein the second identity information is a registration code of the second host device in the device network to which the second host device belongs, and the second ledger information is used to record the registration codes corresponding to the host devices included in the target device network;

[0104] a second verification unit, configured to verify, based on the connection information, whether the second host device is allowed to connect to another host device;

[0105] The first determining unit is configured to, when it is verified that the second host device belongs to the target device network and the second host device is allowed to connect to other host devices, determine that the attribution is used to indicate that the second host device is allowed to belong to the initial device link.

[0106] In an exemplary embodiment, the first verification unit is further used to: search for the second identity information from the second ledger information; if the second identity information is found in the second ledger information, determine and verify that the second host device belongs to the target device network; if the second identity information is not found in the second ledger information, determine and verify that the second host device does not belong to the target device network; the second verification unit is further used to: if the connection information is used to indicate that the second host device does not have a connection relationship with other host devices in the distributed system, determine and verify that the second host device is allowed to connect with other host devices; if the connection information is used to indicate that the second host device has a connection relationship with other host devices in the distributed system, determine and verify that the second host device is not allowed to connect with other host devices.

[0107] In an exemplary embodiment, the joining module includes:

[0108] A second acquiring unit, configured to acquire a reference account of the second host device and an account password corresponding to the reference account;

[0109] a login unit, configured to log in to the second host device using the reference account and the account password corresponding to the reference account;

[0110] The second determining unit is configured to determine that the second host device has been added to the initial device link when the second host device is logged in using the reference account and the account password corresponding to the reference account, and to determine the initial device link with the second host device as the target device link.

[0111] In an exemplary embodiment, after adding the second host device to the initial device link to obtain the target device link, the apparatus further includes:

[0112] a generating module, configured to generate a joining record for joining the second host device to the initial device link, wherein the joining record carries a timestamp of joining the second host device to the initial device link and event information of joining the second host device to the initial device link;

[0113] A sending module is configured to send the joining record to each host device included in the target device network, wherein each host device included in the target device network is configured to write the joining record into the third ledger information corresponding to each host device when receiving the joining record.

[0114] In an exemplary embodiment, the apparatus further comprises:

[0115] a detection module, configured to detect whether the first host device is the first host device in the target device link;

[0116] a first disconnection module configured to disconnect the first host device from the second host device when the first host device is the first host device of the target device link and receives a local operation instruction, wherein the local operation instruction is an operation instruction issued by an external device on the first host device; a second disconnection module configured to disconnect the first host device from the last host device connected to the first host device and disconnect the first host device from the second host device when the first host device is not the first host device of the target device link and receives the local operation instruction;

[0117] a third disconnection module configured to, if the first host device is the first host device of the target device link and, upon receiving a reference join request, disconnect the first host device from the second host device in response to the reference join request, wherein the reference join request is used to request the first host device to join another device link; and a fourth disconnection module configured to, if the first host device is not the first host device of the target device link and, upon receiving the reference join request, disconnect the first host device from the last host device to which the first host device was connected, and disconnect the first host device from the second host device in response to the reference join request.

[0118] a fifth disconnection module, configured to disconnect the first host device from the second host device when the first host device is the first host device in the target device link and the account operation instruction issued by the target account is not received within a time threshold; a sixth disconnection module, configured to disconnect the first host device from the previous host device to which the first host device was connected, and the first host device from the second host device when the first host device is not the first host device in the target device link and the account operation instruction issued by the target account is not received within the time threshold.

[0119] It should be noted that the above modules can be implemented through software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.

[0120] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored. The computer program is configured to execute the steps of any of the above method embodiments when run.

[0121] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk, or an optical disk.

[0122] An embodiment of the present application further provides an electronic device, Figure 7 is a structural block diagram of an electronic device according to an embodiment of the present application, such as Figure 7 As shown, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.

[0123] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.

[0124] An embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps in any one of the above method embodiments are implemented.

[0125] An embodiment of the present application further provides another computer program product, comprising a non-volatile computer-readable storage medium, wherein the non-volatile computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of any of the above method embodiments are implemented.

[0126] An embodiment of the present application further provides a computer program, which includes computer instructions stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device performs the steps of any of the above method embodiments.

[0127] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail here.

[0128] Obviously, those skilled in the art should understand that the modules or steps of the present application described above can be implemented using a general-purpose computing device, they can be concentrated on a single computing device, or distributed across a network composed of multiple computing devices, they can be implemented using program code executable by the computing device, and thus, they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be performed in a different order than herein, or they can be fabricated into separate integrated circuit modules, or multiple modules or steps can be fabricated into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.

[0129] The above description is merely a preferred embodiment of the present application and is not intended to limit the present application. Various modifications and variations are possible for those skilled in the art. Any modifications, equivalent substitutions, improvements, etc. made within the principles of the present application shall be included within the scope of protection of the present application.

Claims

1. A method for controlling a host device, characterized in that: A distributed system includes N host devices, M of the N host devices are interconnected to form an initial device link, where N is an integer greater than 1, and M is an integer less than or equal to N and greater than 1. The host devices in the initial device link each have identity information indicating that the host device belongs to a target device network. The initial device link is configured to allow control of the M host devices through a target account. The method is applied to a first host device in the initial device link, and the method includes: receiving a target joining request sent by the target account, wherein the target joining request is used to request a second host device among the NM host devices to be added to the initial device link; In response to the target join request, extracting second identity information of the second host device and connection information of the second host device using the first identity information of the first host device, wherein the connection information is used to indicate a connection relationship between the second host device and other host devices in the distributed system; verifying the attribution of the second host device to the initial device link based on the second identity information and the connection information; In a case where the attribution attribute indicates that the second host device is allowed to belong to the initial device link, the second host device is added to the initial device link to obtain a target device link.

2. The method according to claim 1, characterized in that The extracting the second identity information of the second host device and the connection information of the second host device by using the first identity information of the first host device includes: Obtaining a first registration code of the first host device in the target device network as the first identity information, wherein the first registration code is used to indicate a unique identifier of the first host device in the target device network; sending the first identity information and a first status code of the first host device to the second host device, wherein the second host device is configured to, upon receiving the first identity information and the first status code, search for the first identity information from first ledger information of a reference device network to which the second host device belongs; if the first identity information is found, parse the first status code; and if the first status code indicates that the first host device is allowed to connect to other host devices, extract a second registration code of the second host device as the second identity information, and extract the second status code of the second host device as the connection information of the second host device, wherein the first ledger information is configured to record registration codes corresponding to host devices included in the reference device network; The second identity information and the connection information are received, which are sent by the second host device in response to the first identity information and the first status code.

3. The method according to claim 1, characterized in that The verifying the attribution of the second host device relative to the initial device link according to the second identity information and the connection information includes: verifying whether the second host device belongs to the target device network based on the second identity information and second ledger information of the target device network, wherein the second identity information is a registration code of the second host device in the device network to which the second host device belongs, and the second ledger information is used to record the registration codes corresponding to the host devices included in the target device network; verifying, according to the connection information, whether the second host device is allowed to connect to other host devices; When it is verified that the second host device belongs to the target device network and the second host device is allowed to connect to other host devices, the attribution is determined to indicate that the second host device is allowed to belong to the initial device link.

4. The method according to claim 3, characterized in that Verifying whether the second host device belongs to the target device network based on the second identity information and the second ledger information of the target device network includes: searching for the second identity information from the second ledger information; if the second identity information is found in the second ledger information, determining that the second host device belongs to the target device network; if the second identity information is not found in the second ledger information, determining that the second host device does not belong to the target device network; The verifying whether the second host device is allowed to connect with other host devices based on the connection information includes: when the connection information is used to indicate that the second host device does not have a connection relationship with other host devices in the distributed system, determining and verifying that the second host device is allowed to connect with other host devices; when the connection information is used to indicate that the second host device has a connection relationship with other host devices in the distributed system, determining and verifying that the second host device is not allowed to connect with other host devices.

5. The method according to claim 1, wherein The adding the second host device to the initial device link to obtain a target device link includes: Obtaining a reference account of the second host device and an account password corresponding to the reference account; Logging into the second host device using the reference account and the account password corresponding to the reference account; When the second host device is logged in using the reference account and the account password corresponding to the reference account, it is determined that the second host device has been added to the initial device link, and the initial device link with the second host device is determined as the target device link.

6. The method according to claim 1, characterized in that After adding the second host device to the initial device link to obtain the target device link, the method further includes: generating a joining record for joining the second host device to the initial device link, wherein the joining record carries a timestamp of joining the second host device to the initial device link and event information of joining the second host device to the initial device link; The joining record is sent to each host device included in the target device network, wherein each host device included in the target device network is configured to write the joining record into the third ledger information corresponding to each host device when receiving the joining record.

7. The method according to claim 1, characterized in that The method further comprises: detecting whether the first host device is the first host device in the target device link; If the first host device is the first host device of the target device link and receives a local operation instruction, disconnect the first host device from the second host device, wherein the local operation instruction is an operation instruction issued by an external device on the first host device; if the first host device is not the first host device of the target device link and receives the local operation instruction, disconnect the first host device from the last host device connected to the first host device, and disconnect the first host device from the second host device; If the first host device is the first host device of the target device link and receives a reference join request, responding to the reference join request to disconnect the first host device from the second host device, wherein the reference join request is used to request the first host device to join another device link; if the first host device is not the first host device of the target device link and receives the reference join request, responding to the reference join request to disconnect the first host device from the last host device to which the first host device was connected, and disconnect the first host device from the second host device; If the first host device is the first host device of the target device link and the account operation instruction issued by the target account is not received within a time threshold, the connection between the first host device and the second host device is disconnected; if the first host device is not the first host device of the target device link and the account operation instruction issued by the target account is not received within the time threshold, the connection between the first host device and the last host device connected to the first host device, as well as the connection between the first host device and the second host device are disconnected.

8. A control device for a host device, characterized in that: A distributed system includes N host devices, M of the N host devices are interconnected to form an initial device link, where N is an integer greater than 1, and M is an integer less than or equal to N and greater than 1. The host devices in the initial device link each have identity information indicating that the host device belongs to a target device network. The initial device link is configured to allow control of the M host devices through a target account. The apparatus is applied to a first host device in the initial device link, and includes: a receiving module, configured to receive a target joining request sent by the target account, wherein the target joining request is used to request that a second host device among the NM host devices be added to the initial device link; an extraction module, configured to respond to the target joining request and extract, using the first identity information of the first host device, the second identity information of the second host device and the connection information of the second host device, wherein the connection information is used to indicate a connection relationship between the second host device and other host devices in the distributed system; a verification module, configured to verify the attribution of the second host device to the initial device link based on the second identity information and the connection information; The adding module is configured to add the second host device to the initial device link to obtain a target device link when the attribution attribute indicates that the second host device is allowed to belong to the initial device link.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method according to any one of claims 1 to 7 when executed by a processor.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.

Images