A cross-node remote login method, device and medium based on a TIPC protocol

Abstract

The application discloses a cross-node remote login method and device based on a TIPC protocol and a medium, and aims to solve the technical problem that the network protocol message type is increased and the network overhead is increased in the existing TIPC protocol cluster network because the TIPC protocol itself is not completely reused by introducing a TCP / IP protocol stack and a native Telnet protocol to provide a remote login method. The method comprises the following steps: adding a Telnet protocol in a TIPC protocol cluster network, and agreeing that the service type numbers of all communication nodes in the TIPC protocol cluster network are specified service type numbers; determining the TIPC addresses of each communication node in the TIPC protocol cluster network, and taking the node field value in the TIPC address as the service instance number of the corresponding communication node; based on the online trigger of the communication node, receiving the service type number and the service instance number of the Telnet communication node, determining the Telnet service address of the Telnet communication node, and based on the Telnet service address, realizing the cross-node remote login of the Telnet communication node.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a cross-node remote login method, device and medium based on the TIPC protocol. Background Technology

[0002] Telnet is a simple remote login protocol based on a client / server model. The Telnet server relies on TCP / IP support, listening on port 23 by default, but the port number can be customized. Telnet clients use the IP address and port as addressing parameters to remotely access the Telnet service. Traditional Telnet protocols for cross-node remote login require a TCP / IP protocol stack. In a TIPC cluster network, the conventional approach to using Telnet is to introduce an additional TCP / IP protocol stack, achieving dual-stack coexistence. This represents an additional resource overhead for the existing TIPC cluster network.

[0003] However, the TIPC protocol itself has unique functions such as link state awareness and service publishing. If a remote login method is provided in a TIPC protocol cluster network by introducing the TCP / IP protocol stack and the native Telnet protocol, the characteristics of the TIPC protocol itself will not be reused at all, resulting in an increase in network protocol message types and network overhead. Summary of the Invention

[0004] This application provides a cross-node remote login method, device, and medium based on the TIPC protocol to solve the technical problem that in existing TIPC protocol cluster networks, the introduction of TCP / IP protocol stack and native Telnet protocol to provide remote login methods does not reuse the characteristics of the TIPC protocol itself, resulting in an increase in network protocol message types and network overhead.

[0005] On the one hand, embodiments of this application provide a cross-node remote login method based on the TIPC protocol, including:

[0006] Add the Telnet protocol to the TIPC protocol cluster network, and define the service type number of all communication nodes in the TIPC protocol cluster network as the specified service type number;

[0007] Determine the TIPC address of each communication node in the TIPC protocol cluster network, and use the node field value in the TIPC address as the service instance number of the corresponding communication node;

[0008] Based on the online trigger of the communication node, the service type number and service instance number of the communication node are received, the Telnet service address of the communication node is determined, and cross-node remote login of the communication node is realized based on the Telnet service address.

[0009] In one implementation of this application, determining the TIPC address of each communication node in the TIPC protocol cluster network and using the node field value in the TIPC address as the service instance number of the corresponding communication node specifically includes:

[0010] Determine the region field value and family field value corresponding to each communication node in the TIPC protocol cluster network, and configure a node field value with a unique identifier for each communication node in the TIPC protocol cluster network.

[0011] Based on the region field value, family field value, and node field value, the TIPC address corresponding to each communication node is determined. For each communication node, the node field value corresponding to the communication node is determined from the TIPC address corresponding to the communication node, so as to use the node field value as the service instance number of the communication node.

[0012] In one implementation of this application, before implementing cross-node remote login of the communication node based on the Telnet service address, the method further includes:

[0013] Based on the cross-node remote login triggering of communication nodes to other communication nodes in the TIPC protocol cluster network, the communication node is used as a Telnet client, and the socket type of the Telnet client is adjusted to a specified type;

[0014] The other communication nodes are designated as Telnet servers, and the socket type of the Telnet servers is adjusted to the specified type.

[0015] In one implementation of this application, the step of enabling cross-node remote login of the communication node based on the Telnet service address specifically includes:

[0016] Based on the Telnet service address, the specified service type number and service instance number corresponding to the communication node are determined;

[0017] Based on the specified type of socket corresponding to the Telnet client for cross-node remote login, and according to the specified service type number and service instance number, an access request is initiated to the Telnet server for cross-node remote login.

[0018] In one implementation of this application, after initiating an access request to the Telnet server for cross-node remote login, the method further includes:

[0019] The Telnet server, which enables remote login across nodes, receives access requests from Telnet clients that also enable remote login across nodes, and binds the specified service type number and service instance number corresponding to the Telnet client based on the access request.

[0020] Based on the specified type of socket corresponding to the Telnet server, the Telnet client is monitored for services, and based on the service monitoring trigger, the corresponding services are provided to the Telnet client.

[0021] In one implementation of this application, after receiving the service type number and service instance number of the communication node based on the online triggering of the communication node, and determining the Telnet service address of the communication node, the method further includes:

[0022] Based on the transparent inter-process communication protocol, the Telnet service address of the communication node is broadcast in the TIPC protocol cluster network, and the Telnet service address broadcast by other communication nodes in the TIPC protocol cluster network is received.

[0023] Based on the Telnet service address of each communication node, maintain the name table in the communication node to obtain the name table corresponding to each communication node.

[0024] In one implementation of this application, after maintaining a name table in the communication nodes based on the Telnet service address of each communication node to obtain the name table corresponding to each communication node, the method further includes:

[0025] Based on the name table, identify the services in the TIPC protocol cluster network that can be remotely logged in across nodes, and determine the communication nodes corresponding to the services that can be remotely logged in across nodes.

[0026] The Telnet service address of each communication node corresponding to the service that can be remotely logged in across nodes is determined so that the corresponding target communication node can be logged in based on the specified service type number and service instance number in the Telnet service address, thereby realizing remote login to the target communication node.

[0027] In one implementation of this application, the step of defining the service type number of all communication nodes in the TIPC protocol cluster network as a specified service type number specifically includes:

[0028] Receive cross-node remote login requests and determine the TIPC protocol cluster network corresponding to the cross-node remote login request;

[0029] All communication nodes in the TIPC protocol cluster network are identified, and based on the cross-node remote login requirement, the service type number of all communication nodes in the TIPC protocol cluster network is defined as a specified service type number.

[0030] On the other hand, embodiments of this application also provide a cross-node remote login device based on the TIPC protocol, the device comprising:

[0031] At least one processor;

[0032] And, a memory communicatively connected to the at least one processor;

[0033] The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform a cross-node remote login method based on the TIPC protocol as described above.

[0034] On the other hand, embodiments of this application also provide a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0035] The above describes a cross-node remote login method based on the TIPC protocol.

[0036] This application provides a cross-node remote login method, device, and medium based on the TIPC protocol, which has at least the following beneficial effects:

[0037] By defining the service type number (SType) of all communication nodes in a TIPC protocol cluster network as a designated SType number, cross-node remote login within the TIPC protocol cluster network becomes more convenient. Using the node field value in the TIPC address of each communication node as its corresponding service instance number ensures the uniqueness of the service address for each communication node in the TIPC protocol cluster network. Through the agreed-upon designated SType number and service instance number, the Telnet service address of each communication node can be determined. Leveraging the communication features supported by the TIPC protocol itself, the Telnet protocol can be adapted to enable cross-node remote login based on the Telnet service address. This approach avoids introducing a new protocol stack beyond the TIPC protocol, reducing design and development costs, maximizing the reuse of the TIPC protocol's inherent features, and providing a cross-node remote login method at a relatively low cost. Attached Figure Description

[0038] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0039] Figure 1 A flowchart illustrating a cross-node remote login method based on the TIPC protocol provided in this application embodiment;

[0040] Figure 2 A schematic diagram of Telnet service in a TIPC protocol cluster network provided in this application embodiment;

[0041] Figure 3 This is a schematic diagram of the internal structure of a cross-node remote login device based on the TIPC protocol, provided as an embodiment of this application. Detailed Implementation

[0042] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0043] This application provides a method, device, and medium for cross-node remote login based on the TIPC protocol. By defining the service type number of all communication nodes in the TIPC protocol cluster network as a specified service type number, cross-node remote login in the TIPC protocol cluster network becomes more convenient. By using the node field value in the TIPC address of each communication node in the TIPC protocol cluster network as the service instance number of the corresponding communication node, the uniqueness of the service address of each communication node in the TIPC protocol cluster network can be guaranteed. Through the agreed-upon specified service type number and service instance number, the Telnet service address of each communication node can be determined. Utilizing the communication characteristics supported by the TIPC protocol itself, the Telnet protocol is adaptively modified, thereby enabling cross-node remote login based on the Telnet service address. This approach does not introduce a new protocol stack besides the TIPC protocol, reducing design and development costs, maximizing the reuse of the TIPC protocol's inherent characteristics, and providing a cross-node remote login method at a relatively low cost. This solution addresses the technical problem in existing TIPC protocol cluster networks where providing remote login methods by introducing TCP / IP protocol stacks and native Telnet protocol completely fails to reuse the characteristics of the TIPC protocol itself, leading to an increase in network protocol message types and network overhead.

[0044] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0045] Figure 1 This is a flowchart illustrating a cross-node remote login method based on the TIPC protocol, provided in an embodiment of this application.

[0046] The analysis method involved in the embodiments of this application can be implemented by a terminal device or a server, and this application does not impose any special limitations on it. For ease of understanding and description, the following embodiments are all described in detail using a server as an example.

[0047] It should be noted that the server can be a single device or a system composed of multiple devices, i.e., a distributed server. This application does not make any specific limitations on this.

[0048] like Figure 1 As shown in the figure, an embodiment of this application provides a cross-node remote login method based on the TIPC protocol, including:

[0049] 101. Add the Telnet protocol to the TIPC protocol cluster network and define the service type number of all communication nodes in the TIPC protocol cluster network as the specified service type number.

[0050] Traditional Telnet protocol for cross-node remote login relies on the TCP / IP protocol stack, requiring the additional use of TCP / IP and native Telnet. While the TIPC protocol possesses unique features such as link state awareness and service publishing, it doesn't fully utilize these features, leading to increased network protocol message types and overhead. This application addresses this issue by introducing Telnet into a TIPC-based cluster network and modifying the conventional Telnet protocol. It replaces traditional IP service / addressing with TIPC service / addressing, eliminating the need for TCP / IP service listening and directly using TIPC service addresses {type, instance}. The corresponding Telnet client also incorporates TIPC address parameters, providing an IP-independent cross-node remote login method. The TIPC service address consists of two parts: service type and service instance.

[0051] Specifically, in one embodiment of this application, the server receives a cross-node remote login request, determines the TIPC protocol cluster network corresponding to the cross-node remote login request, then determines all communication nodes in the TIPC protocol cluster network, and, based on the cross-node remote login request, agrees on the service type number of all communication nodes in the TIPC protocol cluster network as a specified service type number.

[0052] 102. Determine the TIPC address of each communication node in the TIPC protocol cluster network, and use the node field value in the TIPC address as the service instance number of the corresponding communication node.

[0053] Specifically, in one embodiment of this application, the server needs to determine the region field value and family field value corresponding to each communication node in the TIPC protocol cluster network, and configure a node field value with a unique identifier for each communication node in the TIPC protocol cluster network. Then, based on the region field value, family field value, and node field value, the server can determine the TIPC address corresponding to each communication node. For each communication node, the server determines the node field value corresponding to the communication node from the TIPC address corresponding to the communication node, thereby using the node field value as the service instance number of the communication node.

[0054] 103. Based on the online trigger of the communication node, receive the service type number and service instance number of the communication node, determine the Telnet service address of the communication node, and realize cross-node remote login of the communication node based on the Telnet service address.

[0055] In one embodiment, upon triggering the online status of a communication node, the server receives the service type number and service instance number of the communication node, determines the Telnet service address of the communication node, and then broadcasts the Telnet service address of the communication node in the TIPC protocol cluster network based on the transparent inter-process communication protocol. The server also receives the Telnet service addresses broadcast by other communication nodes in the TIPC protocol cluster network. Then, based on the Telnet service addresses of each communication node, the server maintains the name table in the communication node to obtain the name table corresponding to each communication node.

[0056] In one embodiment of this application, the server maintains a name table for each communication node based on its Telnet service address. After obtaining the name table for each communication node, the server determines the services that can be remotely logged into across nodes in the TIPC protocol cluster network based on the name table, and determines the communication nodes corresponding to the services that can be remotely logged into across nodes. Then, the server determines the Telnet service address of each communication node corresponding to the services that can be remotely logged into across nodes, so that the server can log into the corresponding target communication node based on the specified service type number and service instance number in the Telnet service address, thereby realizing remote login to the target communication node. In this way, the communication node can use the name table provided by TIPC to query the services available for login in the network in real time.

[0057] In one embodiment of this application, before the server enables cross-node remote login of communication nodes based on the Telnet service address, it triggers cross-node remote login of other communication nodes based on the communication nodes in the TIPC protocol cluster network, treats the communication nodes as Telnet clients, and adjusts the socket type of the Telnet clients to a specified type. Then, the server treats the other communication nodes as Telnet servers and adjusts the socket type of the Telnet servers to a specified type.

[0058] Specifically, in one embodiment of this application, the server determines the specified service type number and service instance number corresponding to the communication node based on the Telnet service address, and then, based on the specified type of socket corresponding to the Telnet client that remotely logs in across nodes, and according to the corresponding specified service type number and service instance number, initiates an access request to the Telnet server that remotely logs in across nodes.

[0059] In one embodiment of this application, after the server initiates an access request to the Telnet server for cross-node remote login, it receives the access request from the Telnet client for cross-node remote login through the Telnet server for cross-node remote login. Based on the access request, the server binds the specified service type number and service instance number corresponding to the Telnet client. Then, the server listens for services on the Telnet client based on the specified type of socket corresponding to the Telnet server, and provides the corresponding services to the Telnet client based on the service listening trigger.

[0060] Figure 2 This application provides a schematic diagram of Telnet service in a TIPC protocol cluster network, as illustrated in an embodiment. In one embodiment, such as... Figure 2As shown, this application stipulates that the TIPC addresses of the three devices are <1.10.1>, <1.10.2>, and <1.10.3>, respectively. After each node comes online, it starts a pre-agreed service address: the service type number is 1023, and the service instance number is the NODE field value of its respective TIPC address. Figure 2 The service address marked in the middle is the telnet service address in TIPC format for each node.

[0061] The above are embodiments of the method proposed in this application. Based on the same inventive concept, embodiments of this application also provide a cross-node remote login device based on the TIPC protocol, the structure of which is as follows: Figure 3 As shown.

[0062] Figure 3 This is a schematic diagram of the internal structure of a cross-node remote login device based on the TIPC protocol, provided as an embodiment of this application. Figure 3 As shown, the device includes:

[0063] At least one processor;

[0064] And, a memory that is communicatively connected to at least one processor;

[0065] The memory stores instructions that can be executed by at least one processor, and the instructions, when executed by at least one processor, enable at least one processor to:

[0066] Add the Telnet protocol to the TIPC protocol cluster network, and define the service type number of all communication nodes in the TIPC protocol cluster network as the specified service type number;

[0067] Determine the TIPC address of each communication node in the TIPC protocol cluster network, and use the node field value in the TIPC address as the service instance number of the corresponding communication node;

[0068] Based on the online trigger of the communication node, the service type number and service instance number of the communication node are received, the Telnet service address of the communication node is determined, and cross-node remote login of the communication node is realized based on the Telnet service address.

[0069] This application embodiment also provides a non-volatile computer storage medium storing computer-executable instructions, wherein the computer-executable instructions are configured as follows:

[0070] Add the Telnet protocol to the TIPC protocol cluster network, and define the service type number of all communication nodes in the TIPC protocol cluster network as the specified service type number;

[0071] Determine the TIPC address of each communication node in the TIPC protocol cluster network, and use the node field value in the TIPC address as the service instance number of the corresponding communication node;

[0072] Based on the online trigger of the communication node, the service type number and service instance number of the communication node are received, the Telnet service address of the communication node is determined, and cross-node remote login of the communication node is realized based on the Telnet service address.

[0073] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the description of the method embodiments.

[0074] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0075] The devices and media provided in this application are one-to-one with the methods. Therefore, the devices and media also have similar beneficial technical effects as their corresponding methods. Since the beneficial technical effects of the methods have been described in detail above, the beneficial technical effects of the devices and media will not be repeated here.

[0076] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0077] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0078] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0079] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0080] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0081] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0082] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0083] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0084] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A cross-node remote login method based on the TIPC protocol, characterized in that, The method includes: Add the Telnet protocol to the TIPC protocol cluster network, and define the service type number of all communication nodes in the TIPC protocol cluster network as the specified service type number; Determine the TIPC address of each communication node in the TIPC protocol cluster network, and use the node field value in the TIPC address as the service instance number of the corresponding communication node; Based on the online trigger of the communication node, the service type number and service instance number of the communication node are received, the Telnet service address of the communication node is determined, and cross-node remote login of the communication node is realized based on the Telnet service address; the Telnet service address is a TIPC address that includes the service type number and service instance number. Based on the transparent inter-process communication protocol, the Telnet service address of the communication node is broadcast in the TIPC protocol cluster network, and the Telnet service address broadcast by other communication nodes in the TIPC protocol cluster network is received. Based on the Telnet service address of each of the communication nodes, maintain the name table in the communication nodes to obtain the name table corresponding to each of the communication nodes; Based on the name table, identify the services in the TIPC protocol cluster network that can be remotely logged in across nodes, and determine the communication nodes corresponding to the services that can be remotely logged in across nodes. The Telnet service address of each communication node corresponding to the service that can be remotely logged in across nodes is determined so that the corresponding target communication node can be logged in based on the specified service type number and service instance number in the Telnet service address, thereby realizing remote login to the target communication node.

2. The cross-node remote login method based on the TIPC protocol according to claim 1, characterized in that, The step of determining the TIPC address of each communication node in the TIPC protocol cluster network and using the node field value in the TIPC address as the service instance number of the corresponding communication node specifically includes: Determine the region field value and family field value corresponding to each communication node in the TIPC protocol cluster network, and configure a node field value with a unique identifier for each communication node in the TIPC protocol cluster network. Based on the region field value, family field value, and node field value, the TIPC address corresponding to each communication node is determined. For each communication node, the node field value corresponding to the communication node is determined from the TIPC address corresponding to the communication node, so as to use the node field value as the service instance number of the communication node.

3. The cross-node remote login method based on the TIPC protocol according to claim 1, characterized in that, Before implementing cross-node remote login of the communication node based on the Telnet service address, the method further includes: Based on the cross-node remote login triggering of communication nodes to other communication nodes in the TIPC protocol cluster network, the communication node is used as a Telnet client, and the socket type of the Telnet client is adjusted to a specified type; The other communication nodes are designated as Telnet servers, and the socket type of the Telnet servers is adjusted to the specified type.

4. The cross-node remote login method based on the TIPC protocol according to claim 3, characterized in that, The method of enabling cross-node remote login of the communication node based on the Telnet service address specifically includes: Based on the Telnet service address, the specified service type number and service instance number corresponding to the communication node are determined; Based on the specified type of socket corresponding to the Telnet client for cross-node remote login, and according to the specified service type number and service instance number, an access request is initiated to the Telnet server for cross-node remote login.

5. A cross-node remote login method based on the TIPC protocol according to claim 4, characterized in that, After initiating an access request to the Telnet server for cross-node remote login, the method further includes: The Telnet server, which enables remote login across nodes, receives access requests from Telnet clients that also enable remote login across nodes, and binds the specified service type number and service instance number corresponding to the Telnet client based on the access request. Based on the specified type of socket corresponding to the Telnet server, the Telnet client is monitored for services, and based on the service monitoring trigger, the corresponding services are provided to the Telnet client.

6. The cross-node remote login method based on the TIPC protocol according to claim 1, characterized in that, The step of defining the service type number of all communication nodes in the TIPC protocol cluster network as a specified service type number specifically includes: Receive cross-node remote login requests and determine the TIPC protocol cluster network corresponding to the cross-node remote login request; All communication nodes in the TIPC protocol cluster network are identified, and based on the cross-node remote login requirement, the service type number of all communication nodes in the TIPC protocol cluster network is defined as a specified service type number.

7. A cross-node remote login device based on the TIPC protocol, characterized in that, The device includes: At least one processor; And, a memory communicatively connected to the at least one processor; The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform a cross-node remote login method based on the TIPC protocol as described in any one of claims 1-6.

8. A non-volatile computer storage medium storing computer-executable instructions, characterized in that, The computer-executable instructions are set as follows: A cross-node remote login method based on the TIPC protocol as described in any one of claims 1-6.

Images