Terminal cross-domain management method, device, equipment and product

Abstract

The invention discloses a terminal cross-domain management method, device, equipment and product, and the method comprises the steps: building a trust relation between domain nodes according to the demands of a user for logging in a cross-domain terminal; when a user logs in a cross-domain terminal, the domain node where the logged-in terminal is located performs user information verification through the domain node where the user is located by using the trust relationship established between the domain nodes; and if the user information passes the verification, allowing the user to log in the cross-domain terminal. The invention discloses a terminal cross-domain management method, a terminal cross-domain management device, terminal cross-domain management equipment and a product, which realize cross-domain management of distributed terminals by removing a centralized management and control mode, can ensure data isolation between domain nodes, improve data privacy, simplify a terminal cross-domain login process and improve use efficiency, and have the advantages of high terminal cross-domain management data security, high reliability and the like. And the characteristics of rich functions and wide application range can be realized.

Description

Technical Field

[0001] The present invention belongs to the field of domestic information and communication technology systems, and in particular, relates to a terminal cross-domain management method, device, equipment and product. Background Art

[0002] With the large-scale promotion of domestically produced trust-based systems, the domestic large-scale trust-based terminal control scenarios are becoming increasingly important. Under existing technical conditions, the traditional centralized control method will put a lot of pressure on the domain control end. With the continuous increase in the number of managed terminals and the continuous expansion of geographical distribution, the hardware performance and cost of centralized control have become issues that cannot be ignored. At the same time, the existing centralized terminal control method will also bring about problems such as high management complexity and heavy administrator tasks. Summary of the invention

[0003] In view of this, the present invention aims to overcome the defects in the prior art and proposes a terminal cross-domain management method, device, equipment and product.

[0004] To achieve the above object, the technical solution of the present invention is achieved as follows: In a first aspect, the present invention discloses a terminal cross-domain management method, comprising: According to the needs of users logging in to cross-domain terminals, a trust relationship between domain nodes is established, wherein the domain nodes include: a domain control terminal and several terminals managed by the domain control terminal; When a user logs in to a terminal across domains, the domain node where the logged-in terminal is located uses the trust relationship established between domain nodes to verify the user information through the domain node where the user is located; If the user information verification is successful, the user is allowed to log in to the cross-domain terminal.

[0005] In another embodiment of the present invention, a trust relationship between domain nodes is established based on the need for a user to log in to a cross-domain terminal, including: based on the need for a user to log in to a cross-domain terminal, an encrypted channel is established between the domain node where the user is located and the domain node where the cross-domain terminal is located, the encrypted channel being used to implement a cross-node service call between the two domain nodes.

[0006] In another embodiment of the present invention, a trust relationship between domain nodes is established based on the need for a user to log in to a cross-domain terminal, including: establishing a cascade relationship between all domain nodes and generating a node tree, and establishing a trust relationship between domain nodes based on the need for a user to log in to a cross-domain terminal using topological data contained in the node tree, wherein the topological data includes: a node ID, a node name, a node domain name, a node communication address, and an upper-level node ID of each domain node.

[0007] In another embodiment of the present invention, the encrypted channel implements cross-node service calls between two domain nodes through a symmetric key.

[0008] In another embodiment of the present invention, a trust relationship between domain nodes is established according to a user's requirement to log in to a cross-domain terminal, including: using an audit node to audit whether the trust relationship can be established.

[0009] In another embodiment of the present invention, each domain node on the node tree stores topology data.

[0010] In another embodiment of the present invention, the topology data is updated according to changes in the node tree.

[0011] In a second aspect, the present invention discloses a terminal cross-domain management device, the device comprising: A trust relationship establishment module is used to establish a trust relationship between domain nodes according to the needs of users logging into cross-domain terminals, wherein the domain nodes include: a domain control terminal and several terminals managed by the domain control terminal; The verification module is used for, when a user logs in to a terminal across domains, the domain node where the logged-in terminal is located, using the trust relationship established between domain nodes to verify the user information through the domain node where the user is located; The login module is used to allow the user to log in to the cross-domain terminal if the user information verification is passed.

[0012] In a third aspect, the present invention discloses an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors execute the above method.

[0013] In a fourth aspect, the present invention discloses a computer program product, including a computer program, which implements the above method when executed by a processor.

[0014] Compared with the prior art, the present invention has the following advantages: The present invention discloses a terminal cross-domain management method, device, equipment and product, including: establishing a trust relationship between domain nodes according to the user's need to log in to the cross-domain terminal; when the user logs in to the cross-domain terminal, the domain node where the logged-in terminal is located uses the trust relationship established between the domain nodes to verify the user information through the domain node where the user is located; if the user information verification passes, the user is allowed to log in to the cross-domain terminal. The present invention discloses a terminal cross-domain management method, device, equipment and product, which realizes cross-domain management of distributed terminals by removing the centralized management and control mode, can ensure data isolation between domain nodes, and improve data privacy; simplify the terminal cross-domain login process and improve the use efficiency; have the characteristics of high terminal cross-domain management data security, rich functions and wide application range. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0016] In the attached picture: Figure 1 A schematic diagram of an application scenario of a terminal cross-domain management method according to an embodiment of the present invention; Figure 2 A schematic diagram of a terminal cross-domain management method according to an embodiment of the present invention; Figure 3 A schematic diagram of a node tree of a terminal cross-domain management method according to an embodiment of the present invention; Figure 4 A schematic diagram of a terminal cross-domain management device according to an embodiment of the present invention; Figure 5 The present invention is a schematic diagram of a terminal cross-domain management electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0017] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other.

[0018] In the description of the present invention, it should be further explained that the terms "first", "second", etc. are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first", "second", etc. may explicitly or implicitly include one or more of the features. In the description of the present invention, unless otherwise specified, "plurality" means two or more.

[0019] The present invention discloses a terminal cross-domain management method, device, equipment and product application scenario such as Figure 1As shown, under the existing technical conditions, the traditional centralized control method will put great pressure on the domain control end. With the continuous growth of the number of managed terminals and the continuous expansion of the geographical distribution range, the hardware performance and cost of centralized control have become issues that cannot be ignored. At the same time, the existing centralized terminal control method will also bring about the problems of high management complexity and heavy tasks for administrators. The present invention discloses a terminal cross-domain management method, device, equipment and product, which realizes cross-domain management of terminals by removing the centralized control method, can ensure data isolation between domain nodes, improve data privacy; simplify the terminal cross-domain login process, and improve the use efficiency; it has the characteristics of high terminal cross-domain management data security, rich functions and wide application range.

[0020] The present invention will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0021] In one embodiment disclosed in the present invention, Figure 2 As shown, a terminal cross-domain management method includes: Step S201: establishing a trust relationship between domain nodes according to the user's need to log in to a cross-domain terminal, wherein the domain nodes include: a domain control terminal and several terminals managed by the domain control terminal; In this embodiment, a domain control terminal and several terminals managed by the domain control terminal form a domain control solution, which is represented as a domain node; Exemplarily, the domain control terminal and the terminal are domestically produced trusted computing products.

[0022] In this embodiment, a cascade relationship is first established between all domain nodes, and a node tree is generated. According to the needs of users logging in to cross-domain terminals, a trust relationship between domain nodes is established using the topological data contained in the node tree, wherein the topological data includes: the node ID, node name, node domain name, node communication address and upper-level node ID of each domain node.

[0023] The connection between two domain nodes is called a cascade relationship. The cascade initiator is called the subordinate node, i.e., the child node; the cascade approver is called the superior node, i.e., the parent node; after the cascade is completed, the superior node has the access and control rights of the subordinate node.

[0024] In this embodiment, an audit node is used to audit whether a trust relationship can be established. Exemplarily, the audit node can be a third-party audit node. The trust authorization performed by the third-party audit node is controllable, traceable, and highly secure.

[0025] In this embodiment, two domain nodes in a trust relationship are established through review, and the trusted domain node has the access right and control right of the trusting domain node.

[0026] Step S202: When a user logs in to a cross-domain terminal, the domain node where the logged-in terminal is located uses the trust relationship established between domain nodes to verify the user information through the domain node where the user is located; Step S203: If the user information verification is passed, the user is allowed to log in to the cross-domain terminal.

[0027] A terminal cross-domain management method disclosed in this embodiment realizes cross-domain management of terminals by removing the centralized management and control mode, which can ensure data isolation between domain nodes, improve data privacy, simplify the terminal cross-domain login process, and improve usage efficiency.

[0028] Based on the previous embodiment, in another embodiment of the present invention, Figure 2 As shown, step S201, according to the needs of the user logging in to the cross-domain terminal, establish a trust relationship between domain nodes, including: according to the needs of the user logging in to the cross-domain terminal, establish an encrypted channel between the domain node where the user is located and the domain node where the logged-in cross-domain terminal is located, and the encrypted channel is used to implement cross-node service calls between two domain nodes.

[0029] In this embodiment, the cross-node service calling process is as follows: Cross-node service calls involve parameters such as serviceName, method, uri, header, and body. The requesting domain node sends the above information to the target domain node through an encrypted channel. After parsing, the target domain node uses other parameters to call the corresponding service interface according to the serviceName routing configuration. After obtaining the returned data results, it is encrypted and returned to the requesting domain node. The requesting domain node decrypts the data results returned by the business interface, and finally realizes cross-node service calls. Exemplarily, domain node A calls the service of domain node B across nodes to obtain the number of managed terminals of domain node B. The process is as follows: 1. Each domain node has its own business service busiService, which listens to port 8080 and provides a query interface countTerminal for obtaining the number of managed terminals in the domain node. The interface is the HTTP protocol GET method; 2. Domain node A assembles the encrypted message: serviceName=busiService, port=8080, method=GET, uri= / countTerminal, hearer=default, body=none; 3. When domain node A initiates a cross-node service call, it selects domain node B in the node tree as the target, obtains the communication address of domain node B, and sends the assembled encrypted message to domain node B through the encrypted channel; 4. After receiving the encrypted message, domain node B parses the request and obtains the service address of busiService as monit-web.kmp.local through the locally configured routing table. It then initiates a local interface call. The complete path of the interface is: http: / / monit-web.kcm.local:8080 / countTerminal; The local interface returns the result, and domain node B returns the result to domain node A through an encrypted channel; 5. Domain node A receives the result, parses and displays it, and the cross-node service call is completed.

[0030] In this embodiment, cross-node service calling supports calling all business interfaces of all business services on domain nodes, and has the characteristics of being universal, powerful, and having a wide range of applications.

[0031] In this embodiment, the encrypted channel implements cross-node service calls between two domain nodes through a symmetric key.

[0032] Exemplarily, the process of establishing an encrypted channel is as follows: The trust relationship includes the upper domain node and the lower domain node. After the trust relationship is reviewed and approved, the upper domain node will generate an asymmetric key pair, including private key P1 and public key P2, and deliver the public key P2 to the lower domain node offline. The lower domain node generates an asymmetric key pair for the lower domain node, including private key C1 and public key C2. The lower domain node uses the public key P2 of the upper domain node to encrypt the symmetric key negotiation factor information S1 and public key C2 generated by the lower domain node, and sends it to the upper domain node; the upper domain node uses the private key P1 to decrypt the symmetric key negotiation factor information S1 and public key C2, and the upper domain node generates the symmetric key negotiation factor. S2, further combines the symmetric key negotiation factor S1 with the symmetric key negotiation factor S2 to generate a symmetric key; the upper domain node uses the public key C2 to encrypt the symmetric key negotiation factor S2 and sends it to the lower domain node; the lower domain node uses the private key C1 to decrypt and obtain the symmetric key negotiation factor S2, and further combines the symmetric key negotiation factor S1 with the symmetric key negotiation factor S2 to generate a symmetric key. At this time, both the upper domain node and the lower domain node obtain the symmetric key generated by the combination of the symmetric key negotiation factor S1 and the symmetric key negotiation factor S2, and the subsequent communication between the two domain nodes uses this symmetric key for encryption and decryption.

[0033] In this embodiment, the establishment of an encrypted channel effectively improves the security of terminal cross-domain access. The connection between nodes in each domain uses an independent symmetric key, which maximizes the security of the overall network environment.

[0034] In another embodiment of the present invention, Figure 3As shown, each domain node on the domain node tree stores topological data, and the topological data is updated according to changes in the domain node tree.

[0035] In this embodiment, if Figure 3 As shown, the domain node tree topology data is automatically spread to each domain node in the node tree, ensuring that each domain node has the same full topology data.

[0036] For example, Figure 3 As shown in the figure, when a domain node is added to the node tree: Domain node E is connected to domain node B. Domain node E is a newly added domain node in the node tree. At this time, it is necessary to notify other domain nodes A, C, and D in the node tree to ensure that the topological data of all domain nodes in the node tree are consistent; After the connection between domain node E and domain node B is approved, domain node B will automatically notify the upper domain node A and the lower domain node D that a new domain node E has joined the node tree; After receiving the notification, domain node A will automatically notify the upper domain node (none) and the lower domain node C that a new domain node E has been added to the node tree, and so on, to achieve the addition of new domain nodes to the node tree; For example, Figure 3 As shown, when the node tree deletes a domain node: like Figure 3 As shown, domain node E cancels the connection to domain node B. Domain node E is the deleted domain node of the node tree. At this time, other domain nodes A, C, and D of the node tree need to be notified to ensure that the topological data of all domain nodes on the node tree are consistent.

[0037] After the approval of domain node E to cancel the connection with domain node B is passed, domain node B will automatically notify the upper-level domain node A and the lower-level domain node D, and the node tree will delete domain node E; After receiving the notification, the level domain node A node will automatically notify the upper level domain node (none) and the lower level domain node C, and the node tree deletes the domain node E, and so on, to achieve the node tree deleting the domain node; In this embodiment, because all domain nodes on the node tree store the topological data of each domain node, the target domain node can be visually selected based on the trust requirements between the node tree and the domain nodes, and a trust relationship can be established between any two domain nodes.

[0038] In this embodiment, a new domain node can be added to the node tree after being approved, and each domain node holds the full amount of topological data that is automatically synchronized, thereby solving the problem in the prior art that the domain node cannot perceive the overall topological data and cannot view its own topological position.

[0039] like Figure 1 and Figure 2As shown, in step S202, when a user logs in to a cross-domain terminal, the domain node where the logged-in terminal is located uses the trust relationship established between domain nodes to verify the user information through the domain node where the user is located. An example is as follows: Domain node B trusts domain node A. The cross-domain authentication process is as follows: 1. The domain name of domain node A is A.local, and the domain name of domain node B is B.local; 2. userB is a user of domain node B, and the complete user information is userB@B.local; terminal terminalA is added to domain node A and receives control from domain node A; at this time, userB is on a business trip to the area where domain node A is located, and needs to log in using terminal terminalA. This scenario involves terminal cross-domain authentication; 3. When the terminal terminates A, enter the username userB@B.local and password to initiate login authentication; the authentication service of domain node A parses userB@B.local and finds that it is a user of domain node B. At this time, domain node A initiates a cross-node service call and forwards the authentication to domain node B. The request parameters are serviceName=authService, port=8000, method=POST, uri= / auth, hearer=default, body={user:userB,password:xxx}; 4. Domain node B receives the request, parses the parameters, searches the local routing table for the authService address kim.local, and executes the local interface call: The full path of the interface is http: / / kim.local:8000 / auth; The body is {user:userB,password:xxx}; 5. Domain node B returns the authentication result to domain node A through an encrypted channel; 6. Domain node A receives the authentication result, the authentication is successful, user userB logs in to terminal terminal A successfully, and the cross-domain authentication process is completed.

[0040] The present invention also discloses a terminal cross-domain management device, such as Figure 4 As shown, including: The trust relationship establishment module 401 is used to establish a trust relationship between domain nodes according to the needs of users logging into cross-domain terminals, wherein the domain nodes include: a domain control terminal and several terminals managed by the domain control terminal; Verification module 402, used for, when a user logs in to a terminal across domains, the domain node where the logged-in terminal is located, using the trust relationship established between domain nodes, to verify the user information through the domain node where the user is located; The login module 403 is used to allow the user to log in to the cross-domain terminal if the user information verification is passed.

[0041] The present invention also discloses an electronic device, such as Figure 5 As shown, an embodiment is disclosed, which is a block diagram of an electronic device suitable for the above-mentioned terminal cross-domain management.

[0042] The electronic device 50 of this embodiment includes a processor 501, which can perform various appropriate actions and processes according to the program stored in the ROM 502 or the program loaded from the storage part 508 to the RAM 503. The processor 501 may include, for example, a general-purpose microprocessor, an instruction set processor and / or a related chipset and / or a dedicated microprocessor, etc. The processor 501 may also include an onboard memory for caching purposes. The processor 501 may include a single processing unit or multiple processing units for performing different actions of the method flow according to the embodiment of the present invention.

[0043] In RAM503, various programs and data required for the operation of electronic device 50 are stored. Processor 501, ROM502 and RAM503 are connected to each other via bus 504, and processor 501 performs various operations of the method flow according to the embodiment of the present invention by executing the program in ROM502 and / or RAM503. It should be noted that the program can also be stored in one or more memories other than ROM502 and RAM503, and processor 501 can also perform various operations of the method flow according to the embodiment of the present invention by executing the program stored in one or more memories.

[0044] According to an embodiment of the present invention, the electronic device 50 may further include an I / O interface 505, which is also connected to the bus 504. The electronic device 50 may further include one or more of the following components connected to the I / O interface 505: an input portion 506 including a keyboard, a mouse, etc.; an output portion 507 including a cathode ray tube, a liquid crystal display, and a speaker; a storage portion 508 including a hard disk, etc.; and a communication portion 509 including a network interface card such as a LAN card, a modem, etc. The communication portion 509 performs communication processing via a network such as the Internet. A drive 5010 is also connected to the I / O interface 505 as needed. A removable medium 5011, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 5010 as needed, so that a computer program read therefrom is installed into the storage portion 508 as needed.

[0045] The present invention also provides a computer-readable storage medium.

[0046] The computer-readable storage medium may be included in the electronic device / device system described in the above embodiment; or it may exist independently without being assembled into the electronic device / device. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, the method according to the embodiment of the present invention is implemented.

[0047] According to an embodiment of the present invention, the computer-readable storage medium may be a non-volatile computer-readable storage medium. For example, it may include but is not limited to: a portable computer disk, a hard disk, a random access memory RAM, a read-only memory ROM, an erasable programmable read-only memory EPROM or a flash memory, a portable compact disk read-only memory CD-ROM, an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present invention, the computer-readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, apparatus, or device.

[0048] Embodiments of the present invention also include a computer program product.

[0049] The computer program product includes a computer program, which contains program codes for executing the method provided by the embodiment of the present invention. When the computer program product runs on an electronic device, the program codes are used to enable the electronic device to implement the method provided by the embodiment of the present invention.

[0050] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of a signal on a network medium. The program code included in the computer program may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0051] According to an embodiment of the present invention, the program code for executing the computer program provided by the embodiment of the present invention can be written by any combination of one or more programming languages, and specifically, these computing programs can be implemented using high-level process and / or object-oriented programming languages. Programming languages ​​include but are not limited to programming languages ​​such as Java, C++, python, C language or similar. The program code can be executed completely on the user computing device, partially on the user device, partially on the remote computing device, or completely on the remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network or a wide area network, or can be connected to an external computing device.

[0052] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram may represent a module, a program segment, or a part of a code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box may also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions. It can be understood by those skilled in the art that the features recorded in the various embodiments and / or claims of the present invention can be combined and / or combined in various ways, even if such a combination or combination is not explicitly recorded in the present invention. In particular, without departing from the spirit and teachings of the present invention, the features described in the various embodiments and / or claims of the present invention may be combined and / or combined in a variety of ways. All of these combinations and / or combinations fall within the scope of the present invention.

[0053] The embodiments of the present invention are described above. However, these embodiments are only for the purpose of illustration, and are not intended to limit the scope of the present invention. Although the embodiments are described above, this does not mean that the measures in the various embodiments cannot be used in combination. The scope of the present invention is limited by the attached claims and their equivalents. Without departing from the scope of the present invention, those skilled in the art may make various substitutions and modifications, which should all fall within the scope of the present invention.

Claims

1. A terminal cross-domain management method, characterized in that: include: According to the needs of users logging into cross-domain terminals, a trust relationship between domain nodes is established, wherein the domain nodes include: a domain control terminal and a plurality of terminals managed by the domain control terminal; When the user logs in to the cross-domain terminal, the domain node where the logged-in terminal is located uses the trust relationship established between the domain nodes to verify the user information through the domain node where the user is located; If the user information verification is passed, the user is allowed to log in to the cross-domain terminal.

2. A terminal cross-domain management method according to claim 1, characterized in that: The establishing of a trust relationship between domain nodes based on the need of a user logging into a cross-domain terminal includes: establishing an encrypted channel between the domain node where the user is located and the domain node where the cross-domain terminal is located based on the need of the user logging into the cross-domain terminal, wherein the encrypted channel is used to implement a cross-node service call between the two domain nodes.

3. A terminal cross-domain management method according to claim 1, characterized in that: The method of establishing a trust relationship between domain nodes according to the need of a user logging in to a cross-domain terminal includes: establishing a cascade relationship between all the domain nodes and generating a node tree, and establishing a trust relationship between the domain nodes according to the need of a user logging in to a cross-domain terminal using topological data contained in the node tree, wherein the topological data includes: a node ID, a node name, a node domain name, a node communication address, and an upper-level node ID of each domain node.

4. A terminal cross-domain management method according to claim 2, characterized in that: The encrypted channel implements cross-node service calls between the two domain nodes through a symmetric key.

5. A terminal cross-domain management method according to claim 1, characterized in that: The establishing of a trust relationship between domain nodes according to a user's requirement to log in to a cross-domain terminal includes: utilizing an audit node to audit whether the trust relationship can be established.

6. A terminal cross-domain management method according to claim 3, characterized in that: Each of the domain nodes on the node tree stores the topology data.

7. A terminal cross-domain management method according to claim 3, characterized in that: The topology data is updated according to changes in the node tree.

8. A terminal cross-domain management device, characterized in that: The device comprises: A trust relationship establishment module, used to establish a trust relationship between domain nodes according to the needs of users logging into cross-domain terminals, wherein the domain nodes include: a domain control terminal and a plurality of terminals managed by the domain control terminal; A verification module, configured to verify user information through the domain node where the logged-in terminal is located by using the trust relationship established between the domain nodes when the user logs in to the cross-domain terminal; The login module is used to allow the user to log in to the cross-domain terminal if the user information verification is passed.

9. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors are caused to perform the method according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 7 is implemented.

Images