CN108347462B - Method and equipment for transmitting operation data - Google Patents

Method and equipment for transmitting operation data Download PDF

Info

Publication number
CN108347462B
CN108347462B CN201710057119.6A CN201710057119A CN108347462B CN 108347462 B CN108347462 B CN 108347462B CN 201710057119 A CN201710057119 A CN 201710057119A CN 108347462 B CN108347462 B CN 108347462B
Authority
CN
China
Prior art keywords
session
gateway
target remote
equipment
connection
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN201710057119.6A
Other languages
Chinese (zh)
Other versions
CN108347462A (en
Inventor
张国良
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Group Holding Ltd
Original Assignee
Alibaba Group Holding Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alibaba Group Holding Ltd filed Critical Alibaba Group Holding Ltd
Priority to CN201710057119.6A priority Critical patent/CN108347462B/en
Publication of CN108347462A publication Critical patent/CN108347462A/en
Application granted granted Critical
Publication of CN108347462B publication Critical patent/CN108347462B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/08—Protocols specially adapted for terminal emulation, e.g. Telnet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/142—Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/148—Migration or transfer of sessions

Abstract

The method comprises the steps that a gateway device is introduced to serve as a data forwarding point in a remote login process, the gateway device obtains a session synchronized by a management device, and session connection is established with a corresponding target remote device based on the session; after session connection is established between the gateway device and the target remote device, the gateway device receives and records an operation instruction under a session sent by the peripheral device, sends the operation instruction to the target remote device, receives and records an operation result returned by the target remote device based on the operation instruction, and sends the operation result to the peripheral device, so that all operation data transmitted between all user devices and the target remote device are transmitted and collected by the gateway device, thereby not only avoiding any operation of the user devices on the operation data, but also ensuring the safety and integrity of all operation data in the session connection process.

Description

Method and equipment for transmitting operation data
Technical Field
The present application relates to the field of computers, and in particular, to a method and an apparatus for transmitting operation data.
Background
In the prior art, ssh (Secure Shell, Secure remote login protocol) is a basic function for remote login in a linux operating system, and a remote login server is performed by using related software (e.g., push, Secure rt, etc.) with ssh (Secure Shell, Secure remote login protocol), but a login interface of a user equipment is optimized. In the prior art, a target login device is logged in through a traditional ssh method for operation, and the specific steps are as follows: firstly, sshd (basic service in linux operating system for receiving ssh login request and logging in target login machine) service is started on a target login device; then, configuring a login account and a key and a certificate of ssh for login use on a target login machine; finally, after the verification of the key and the certificate is passed, the user equipment for remote login logs in the target login equipment through ssh, and the user equipment remotely logs in the target login equipment in a point-to-point mode; however, due to the point-to-point login mode, the traffic and operation between the user equipment and the target login equipment are difficult to monitor; when the remote login is performed in the ssh manner, the user equipment and the target login equipment are directly connected point-to-point, so that the operation instruction performed on the target login equipment can only record the operation of the command line in the operation instruction performed on the target login equipment by the user equipment through the history in the linux operating system, and if the user equipment has the ability to delete the operation instruction and the operation result corresponding to the operation instruction by privilege, the security of the operation data including the operation instruction and the operation result cannot be guaranteed, and the operation data is lost.
Disclosure of Invention
An object of the present application is to provide a method and a device for transmitting operation data, which solve the problems that the security of the operation data is not guaranteed and the operation data is lost due to the fact that a target login device is logged in to perform an operation in a conventional ssh manner.
According to an aspect of the present application, there is provided a method for transmitting operation data at a gateway device, the method including:
acquiring a session synchronized by a management device, and establishing session connection with a corresponding target remote device based on the session;
receiving and recording an operation instruction under the session sent by the peripheral equipment, and sending the operation instruction to the target remote equipment;
and receiving and recording an operation result returned by the target remote equipment based on the operation instruction, and sending the operation result to the peripheral equipment.
Further, in the foregoing method, the session includes a session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device.
Further, in the above method, the acquiring a session synchronized by the management device, and establishing a session connection with a corresponding target remote device based on the session includes:
acquiring a session synchronized by a management device;
judging whether the target remote equipment corresponding to the session establishes session connection or not based on the session identification and the corresponding process identification on the corresponding target remote equipment;
and if so, acquiring the established session connection on the target remote equipment corresponding to the process identification.
Further, in the above method, the determining, based on the session identifier and the process identifier corresponding to the target remote device, whether the target remote device corresponding to the session has already established a session connection further includes:
if not, sending an unconnected notification corresponding to the session to the management device, so that the management device is ready to send the unconnected notification to the target remote device;
acquiring a session connection request sent by the target remote equipment based on the received unconnected notification;
and establishing session connection with the corresponding session process in the target remote equipment based on the session connection request, the session identification and the corresponding process identification on the corresponding target remote equipment.
Further, in the above method, the establishing a session connection with a corresponding session process in a target remote device based on the session connection request, the session identifier, and a corresponding process identifier on the corresponding target remote device includes:
comparing the session identifier and the corresponding process identifier on the corresponding target remote device with the session identifier and the corresponding process identifier in the session connection request,
and when the comparison result is consistent, establishing session connection with the corresponding session process in the target remote equipment.
According to another aspect of the present application, a method for transmitting operation data at a management device is provided, wherein the method comprises:
establishing a session, synchronizing the session to corresponding gateway equipment, and informing corresponding target remote equipment to establish session connection with the gateway equipment based on the session connection state fed back by the gateway equipment according to the session;
receiving a gateway request sent by peripheral equipment based on the received operation instruction under the session;
notifying the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request.
Further, in the foregoing method, the session includes a session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device.
Further, in the above method, the notifying, based on the feedback of the session connection state of the session by the gateway device, that the corresponding target remote device establishes session connection with the gateway device includes:
receiving an unconnected notification corresponding to the state that the target remote device corresponding to the session and the gateway device are not connected, wherein the unconnected notification is fed back by the gateway device based on the session identifier and a corresponding process identifier on a corresponding target remote device;
and based on the unconnected notification, notifying the target remote equipment to start a session process corresponding to the process identification, wherein the session process sends a session connection request to the gateway equipment.
Further, in the above method, the receiving, by the gateway device, a non-connection notification corresponding to a state where the target remote device corresponding to the session and the gateway device do not establish connection based on the session identifier and a corresponding process identifier on the corresponding target remote device by the management device, where the method includes:
receiving the non-connection notification through a local master node, and sending the non-connection notification to a local slave node;
based on the unconnected notification, notifying the target remote device to start a session process corresponding to the process identifier and send a session connection request to the gateway device, including:
and notifying a target remote device to start a session process corresponding to the process identification to send a session connection request to the gateway device through the local slave node based on the unconnected notification.
Further, in the above method, before the notifying that the corresponding target remote device establishes the session connection with the gateway device, the method further includes:
a long connection is established with the target remote device.
Further, in the above method, the establishing a long connection with the target remote device includes:
establishing a long connection with the target remote device through a local slave node.
According to another aspect of the present application, a method for transmitting operation data at a target remote device is provided, wherein the method comprises:
judging whether a notification which is sent by the management equipment and used for establishing session connection with the corresponding gateway equipment is acquired, if so, establishing session connection with the corresponding gateway equipment based on the notification;
receiving an operation instruction under a session corresponding to the session connection sent by the gateway equipment;
and executing the operation instruction to obtain a corresponding operation result, and sending the operation result to the gateway equipment.
Further, in the foregoing method, the session includes a session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device.
Further, in the method, after determining whether a notification sent by the management device to establish session connection with the corresponding gateway device is obtained, the method further includes:
and if not, acquiring the session connection which is established on the target remote equipment and corresponds to the process identification from the gateway equipment.
Further, in the above method, the establishing a session connection with a corresponding gateway device based on the notification further includes:
receiving a notification of establishing session connection with a corresponding gateway device, which is sent by the management device;
based on the notification, starting a session process on the target remote device corresponding to the process identifier, wherein the session process sends a session connection request to the gateway device;
and establishing session connection with the gateway equipment based on the acceptance feedback of the session connection request received by the gateway equipment.
Further, in the above method, the receiving the notification of establishing the session connection with the corresponding gateway device, which is sent by the management device, includes:
and receiving a notice that the management device establishes session connection with the corresponding gateway device through a local slave node.
Further, in the above method, the determining whether to acquire a notification sent by the management device to establish session connection with the corresponding gateway device, and if so, before establishing session connection with the corresponding gateway device based on the notification, the method further includes:
a long connection is established with the management device.
Further, in the above method, the establishing a long connection with the management device includes:
a long connection is established with a local slave node in the management device.
According to another aspect of the present application, there is provided a method of transmitting operation data at a peripheral device, wherein the method includes:
sending a gateway request to the management equipment based on the operation instruction sent by the user equipment under the same session;
receiving the gateway request returned by the management equipment based on the corresponding gateway equipment;
sending the operation instruction to the gateway equipment, and receiving an operation result sent by the gateway equipment based on the operation instruction;
and sending the operation result to the user equipment.
Further, in the foregoing method, the session includes a session identifier, a corresponding process identifier, and a corresponding target remote device.
According to another aspect of the present application, there is provided a gateway device for transmitting operation data, wherein the gateway device includes:
the session connection device is used for acquiring a session synchronized by the management equipment and establishing session connection with the corresponding target remote equipment based on the session;
the issuing device is used for receiving and recording the operation instruction under the session sent by the peripheral equipment and sending the operation instruction to the target remote equipment;
and the reporting device is used for receiving and recording an operation result returned by the target remote equipment based on the operation instruction, and sending the operation result to the peripheral equipment.
Further, in the gateway device, the session includes a session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device.
Further, in the above gateway device, the session connection means is configured to:
acquiring a session synchronized by a management device;
judging whether the target remote equipment corresponding to the session establishes session connection or not based on the session identification and the corresponding process identification on the corresponding target remote equipment;
and if so, acquiring the established session connection on the target remote equipment corresponding to the process identification.
Further, in the above gateway device, the session connection means is configured to:
if not, sending an unconnected notification corresponding to the session to the management device, so that the management device is ready to send the unconnected notification to the target remote device;
acquiring a session connection request sent by the target remote equipment based on the received unconnected notification;
and establishing session connection with the corresponding session process in the target remote equipment based on the session connection request, the session identification and the corresponding process identification on the corresponding target remote equipment.
Further, in the above gateway device, the session connection means is configured to:
comparing the session identifier and the corresponding process identifier on the corresponding target remote device with the session identifier and the corresponding process identifier in the session connection request,
and when the comparison result is consistent, establishing session connection with the corresponding session process in the target remote equipment.
According to another aspect of the present application, there is provided a management apparatus that transmits operation data, wherein the management apparatus includes:
a session establishing device, configured to establish a session, synchronize the session to a corresponding gateway device, and notify, based on a session connection state fed back by the gateway device according to the session, a corresponding target remote device to establish a session connection with the gateway device;
receiving means, configured to receive a gateway request sent by a peripheral device based on the received operation instruction under the session;
a notification device, configured to notify the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request.
Further, in the above management device, the session includes a session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device.
Further, in the above management device, the session establishing means is configured to:
receiving an unconnected notification corresponding to the state that the target remote device corresponding to the session and the gateway device are not connected, wherein the unconnected notification is fed back by the gateway device based on the session identifier and a corresponding process identifier on a corresponding target remote device;
and based on the unconnected notification, notifying the target remote equipment to start a session process corresponding to the process identification, wherein the session process sends a session connection request to the gateway equipment.
Further, in the above management device, the management device includes a local master node and a local slave node, and the session establishing means is configured to:
receiving the non-connection notification through a local master node, and sending the non-connection notification to a local slave node;
and notifying a target remote device to start a session process corresponding to the process identification to send a session connection request to the gateway device through the local slave node based on the unconnected notification.
Further, in the above management device, the session establishing means is further configured to:
a long connection is established with the target remote device.
Further, in the above management device, the session establishing means is configured to:
establishing a long connection with the target remote device through a local slave node.
According to another aspect of the present application, there is provided a target remote device that transmits operation data, wherein the target remote device includes:
the connection establishing device is used for judging whether a notification which is sent by the management equipment and establishes session connection with the corresponding gateway equipment is acquired, and if so, the session connection is established with the corresponding gateway equipment based on the notification;
the instruction receiving device is used for receiving an operation instruction under the session corresponding to the session connection sent by the gateway equipment;
and the execution sending device is used for executing the operation instruction to obtain a corresponding operation result and sending the operation result to the gateway equipment.
Further, in the target remote device, the session includes a session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device.
Further, in the target remote device, the connection establishing apparatus is further configured to:
and if not, acquiring the session connection which is established on the target remote equipment and corresponds to the process identification from the gateway equipment.
Further, in the target remote device, the connection establishing apparatus is further configured to:
receiving a non-connection notification sent by the management equipment;
based on the unconnected notification, starting a session process on the target remote device corresponding to the process identifier, wherein the session process sends a session connection request to the gateway device;
and establishing session connection with the gateway equipment based on the acceptance feedback of the session connection request received by the gateway equipment.
Further, in the target remote device, the connection establishing means is configured to:
and receiving a notice that the management device establishes session connection with the corresponding gateway device through a local slave node.
Further, in the target remote device, the connection establishing apparatus is further configured to:
a long connection is established with the management device.
Further, in the target remote device, the connection establishing means is configured to:
a long connection is established with a local slave node in the management device.
According to another aspect of the present application, there is provided a peripheral device for transmitting operation data, wherein the peripheral device includes:
the request device is used for sending a gateway request to the management equipment based on the operation instruction sent by the user equipment under the same session;
the return device is used for receiving the gateway request returned by the management equipment to the corresponding gateway equipment;
the forwarding device is used for sending the operation instruction to the gateway equipment and receiving an operation result sent by the gateway equipment based on the operation instruction;
and the operation result sending device is used for sending the operation result to the user equipment.
Further, in the peripheral device, the session includes a session identifier, a corresponding process identifier, and a corresponding target remote device.
According to another aspect of the application, there is provided a computing-based device comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
acquiring a session synchronized by a management device, and establishing session connection with a corresponding target remote device based on the session;
receiving and recording an operation instruction under the session sent by the peripheral equipment, and sending the operation instruction to the target remote equipment;
and receiving and recording an operation result returned by the target remote equipment based on the operation instruction, and sending the operation result to the peripheral equipment.
According to another aspect of the application, there is provided a computing-based device comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
establishing a session, synchronizing the session to corresponding gateway equipment, and informing corresponding target remote equipment to establish session connection with the gateway equipment based on the session connection state fed back by the gateway equipment according to the session;
receiving a gateway request sent by peripheral equipment based on the received operation instruction under the session;
notifying the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request.
According to another aspect of the application, there is provided a computing-based device comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
judging whether a notification which is sent by the management equipment and used for establishing session connection with the corresponding gateway equipment is acquired, if so, establishing session connection with the corresponding gateway equipment based on the notification;
receiving an operation instruction under a session corresponding to the session connection sent by the gateway equipment;
and executing the operation instruction to obtain a corresponding operation result, and sending the operation result to the gateway equipment.
According to another aspect of the application, there is provided a computing-based device comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
sending a gateway request to the management equipment based on the operation instruction sent by the user equipment under the same session;
receiving the gateway request returned by the management equipment based on the corresponding gateway equipment;
sending the operation instruction to the gateway equipment, and receiving an operation result sent by the gateway equipment based on the operation instruction;
and sending the operation result to the user equipment.
Compared with the prior art, the method and the system have the advantages that the gateway device is introduced to serve as a data forwarding point in the remote login process, the gateway device firstly obtains a session synchronized by the management device, and session connection is established with the corresponding target remote device based on the session; after the session connection is established between the gateway equipment and the target remote equipment, the gateway equipment receives and records an operation instruction under the session sent by peripheral equipment, and sends the operation instruction to the target remote equipment, so that the target remote equipment executes the received operation instruction and sends an obtained corresponding operation result to the gateway equipment; the gateway device receives and records the operation result returned by the target remote device based on the operation instruction, and sends the operation result to the peripheral device, so that all the operation data transmitted between all the user devices and the target remote device are transmitted and collected at the gateway device, thereby not only avoiding any operation of the user devices on the operation data, but also ensuring the safety and integrity of all the operation data in the session connection process.
Further, the method includes the steps that a session is established at a management device end, the session is synchronized to the corresponding gateway device, and the corresponding target remote device is notified to establish session connection with the gateway device based on the session connection state fed back by the gateway device according to the session; after session connection corresponding to the session is established between the gateway device and target remote equipment, the management device receives a gateway request sent by peripheral equipment based on the received operation instruction under the session; because the management device synchronizes the session to the corresponding gateway device and manages the session and the corresponding gateway device thereof while establishing the session, after receiving a gateway request sent by the peripheral device based on the received operation instruction under the session, the management device notifies the peripheral device of the corresponding gateway device under the session synchronization based on the gateway request, so that the peripheral device sends the operation instruction under the session to the corresponding gateway device under the session synchronization, thereby realizing the accurate sending of the operation instruction under the session to the corresponding gateway device under the session synchronization and ensuring the accurate sending of the operation instruction under the session.
Further, the method comprises the steps that whether a notification of establishing session connection with the corresponding gateway device, which is sent by the management device, is acquired or not is judged at the target remote device side, and if yes, session connection is established with the corresponding gateway device based on the notification; after the session connection corresponding to the session is successfully established between the target remote device and the gateway device, the target remote device receives an operation instruction under the session corresponding to the session connection, which is sent by the gateway device, through the session connection; and then, the target remote equipment executes the operation instruction to obtain a corresponding operation result, and sends the operation result to the gateway equipment, so that the gateway equipment indirectly returns the operation result corresponding to the operation instruction under the session to the user equipment, the transmission of the operation data corresponding to the session through the session connection between the user equipment and the target remote equipment is realized, any operation of the operation data transmitted between the user equipment and the target remote equipment is avoided, and the safety and the integrity of all the operation data in the session connection process are also ensured.
Further, in the remote login process, after a session connection corresponding to a session established by the management device has been established between the introduced gateway device for transmitting operation data and a target remote device, the peripheral device sends a gateway request to the management device based on an operation instruction under the same session sent by the user device, so that the management device notifies the peripheral device of a corresponding gateway device synchronized with the session based on the received gateway request; then, the peripheral device receives the gateway request returned by the management device based on the corresponding gateway device, so that the operation instruction under the session is accurately sent to the corresponding gateway device of the session synchronization, and the accurate issuing of the operation instruction under the session by the subsequent gateway device is ensured; then, the peripheral equipment sends the operation instruction to the gateway equipment and receives an operation result sent by the gateway equipment based on the operation instruction; and finally, the peripheral equipment sends the operation result to the user equipment. The method and the device realize the transmission of the operation data between the user equipment and the target remote equipment through the gateway equipment, avoid the right-lifting deletion of the operation data caused by the point-to-point direct connection between the user equipment and the target remote equipment in the prior art, and ensure the safety and the integrity of all the operation data in the session connection process between the gateway equipment and the target remote equipment.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 illustrates a data flow diagram between a gateway device and a management device, a peripheral device, and a target remote device in a method of transmitting operational data according to an aspect of the present application;
FIG. 2 illustrates a data flow diagram between a management device and a gateway device, a peripheral device, and a target remote device in a method of transmitting operational data according to an aspect of the subject application;
FIG. 3 illustrates a data flow diagram between a target remote device and a management device, gateway device, and peripheral device in a method of transmitting operational data according to an aspect of the subject application;
fig. 4 is a schematic diagram illustrating a data flow between a peripheral device and a user device, a management device and a gateway device in a method of transmitting operation data according to an aspect of the present application;
FIG. 5 illustrates an overall flow diagram of a system method of transferring operational data in accordance with an aspect of the subject application;
fig. 6 is a schematic diagram illustrating an actual application scenario of a method for transmitting operation data in a telnet process according to the present application.
The same or similar reference numbers in the drawings identify the same or similar elements.
Detailed Description
The present application is described in further detail below with reference to the attached figures.
In a typical configuration of the present application, the terminal, the device serving the network, and the trusted party each include one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
Fig. 1 is a schematic diagram illustrating a data flow between a gateway device and a management device, a peripheral device and a target remote device in a method for transmitting operation data according to an aspect of the present application, wherein the method is applied to the gateway device side in a remote login process, and the method includes steps S11, S12 and S13, wherein,
in step S11, the gateway device first obtains a session synchronized by the management device; next, the step S11 establishes a session connection with the corresponding target remote device based on the session; after the session connection is established between the gateway device and the target remote device, step S12 receives and records the operation instruction under the session sent by the peripheral device, and sends the operation instruction to the target remote device, so that the target remote device executes the received operation instruction and sends the obtained corresponding operation result to the gateway device; finally, the step S13 receives and records the operation result returned by the target remote device based on the operation instruction, and sends the operation result to the peripheral device, so that all the operation data transmitted between all the user devices and the target remote device are transmitted and collected at the gateway device, thereby not only avoiding any operation on the operation data by the user devices, but also ensuring the security and integrity of all the operation data in the session connection process.
It should be noted that, in the remote login process in the embodiment of the present application, the Gateway device is preferably a TS Gateway (Terminal Service Gateway device), the management device is preferably a TSM cluster (Terminal Service Manager cluster), the target remote device is preferably a host (host in the Terminal Service remote device), and the peripheral device is preferably a TS Gateway (Terminal Service Gateway device), where the target remote device (host) is a machine that the user device needs to remotely log in, the management device is a device that manages all machines in the remote login process, and the Gateway device (TS Gateway) is a device that actually performs operation data transmission in the remote login process. Of course, the above preference for devices in the remote login process is only a preferred embodiment of an aspect of the present application, and other existing or future possibilities of the gateway device, the management device, the target remote device and the peripheral device, as applicable to the present application, are also included in the scope of protection of the present application and are hereby incorporated by reference.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
Further, the step S11 of acquiring the session synchronized by the management device, and establishing a session connection with the corresponding target remote device based on the session includes:
acquiring a session synchronized by a management device;
judging whether the target remote equipment corresponding to the session establishes session connection or not based on the session identification and the corresponding process identification on the corresponding target remote equipment;
and if so, acquiring the established session connection on the target remote equipment corresponding to the process identification.
In an embodiment of the present application, when the management device sends a Session request, the management device establishes a Session (Session a) based on the Session request, and synchronizes the Session (Session a) to a corresponding Gateway device (TS Gateway 1), so that the Gateway device obtains the Session (Session a) synchronized by the management device in step S11, and makes a Session process corresponding to a Session identifier in a target remote device corresponding to the Session establish Session connection based on the synchronized Session (Session a), and then determines, according to the Session identifier (Session a) of the Session (Session a) and a process identifier (Slave 1) corresponding to the target remote device, whether the target remote device (host1) corresponding to the Session has already established Session connection in step S11; if yes, the step S11 obtains the Session connection already established on the target remote device (host1) corresponding to the process identifier (Slave 1), so that the Session connection corresponding to the process identifier (Slave 1) in the Session (Session a) already established between the gateway device and the target remote device is quickly obtained, and the subsequent gateway device sends the operation instruction under the Session from the user equipment to the target remote device (host1) corresponding to the process identifier (Slave 1) through the established Session connection.
Next to the foregoing embodiment of the present application, the determining, in step S11, whether a session connection has been established by a target remote device corresponding to the session based on the session identifier and a corresponding process identifier on the corresponding target remote device, further includes:
if not, sending an unconnected notification corresponding to the session to the management device, so that the management device is ready to send the unconnected notification to the target remote device;
acquiring a session connection request sent by the target remote equipment based on the received unconnected notification;
and establishing session connection with the corresponding session process in the target remote equipment based on the session connection request, the session identification and the corresponding process identification on the corresponding target remote equipment.
Next, in the foregoing embodiment of the present application, when determining, in step S11, whether a Session connection has been established in a target remote device (host1) corresponding to a Session (Session a) according to the Session identifier (Session a) of the Session and a corresponding process identifier (Slave 1) on the corresponding target remote device; if not, the step S11 is to send, to the management device, a non-connection notification that a Session connection has not been established between the Gateway device (TS Gateway 1) and the target remote device (host1) corresponding to the Session (Session a), so that the management device sends the non-connection notification to the target remote device (host1), when the target remote device (host1) receives the non-connection notification corresponding to the Session, the target remote device (host1) starts a Session process corresponding to a process identifier (Slave 1) on the target remote device (host1) corresponding to the Session (Session a), sends a corresponding Session connection request to the Gateway device (TS Gateway 1), and after the step S11 receives, from the target remote device, the Session connection request sent based on the received non-connection notification, step S11 is to establish a Session connection with the Session process corresponding to the target remote device (host1) based on the Session identifier (Session a) in the Session synchronized by the Session connection request and the process identifier (Slave 1) corresponding to the target remote device (host1), so as to establish a Session connection between the real-time Gateway device (TS Gateway 1) and the target remote device (host1), so that the Gateway device (TS Gateway 1) forwards and collects all the operation data between the user device and the target remote device through the established Session connection.
Further, the step S11 of establishing a session connection with a corresponding session process in the target remote device based on the session connection request, the session identifier and a corresponding process identifier on the corresponding target remote device includes:
comparing the session identifier and the corresponding process identifier on the corresponding target remote device with the session identifier and the corresponding process identifier in the session connection request,
and when the comparison result is consistent, establishing session connection with the corresponding session process in the target remote equipment.
Next, in the foregoing embodiment of the present application, when receiving a Session connection request sent by a target remote device through a Session process corresponding to a process identifier (Slave 1), the Gateway device (TS Gateway 1) compares the Session identifier (Session a) in the Session synchronized by the management device and the corresponding process identifier (Slave 1) on the corresponding target remote device (host1), with the Session identifier (Session ID) and the corresponding process identifier (Slave ID) carried in the Session connection request, and when the comparison result is consistent, that is, when the Session ID is Session a and the Slave ID is Slave1, the Gateway device (TS Gateway 1) establishes a Session connection with the Session process corresponding to the process identifier (Slave 1) in the target remote device (host1), and the Gateway device (TS Gateway 1) and the target remote device (1) corresponding to the Session synchronized by the management device establish a Session connection The accuracy of the session connection established therebetween.
Fig. 2 shows a schematic data flow diagram between a management device and a gateway device, a peripheral device and a target remote device in a method for transmitting operation data according to an aspect of the present application, wherein the method is applied to a management device (TSM cluster) side in a remote login process, the method includes step S21, step S22 and step S23, wherein,
the step S21, establishing a session, synchronizing the session to a corresponding gateway device, and notifying a corresponding target remote device to establish a session connection with the gateway device based on the session connection state fed back by the gateway device according to the session; when the user equipment needs to perform synchronous operation on the target remote equipment after the session connection is established between the gateway equipment and the target remote equipment, sending an operation instruction under the session to peripheral equipment; when the management device synchronizes the session to the corresponding gateway device while establishing the session, the management device already records the corresponding gateway device to which the session is synchronized, and manages the session and the corresponding gateway device, so that after receiving an operation instruction under the session, the peripheral device wants to know to which gateway device to send the operation instruction under the session, and the peripheral device needs to send a gateway request to the management device based on the received operation instruction under the session; next, the step S22 receives a gateway request sent by the peripheral device based on the received operation instruction under the session; finally, the step S23 notifies the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request, so that the peripheral device sends the operation instruction under the session to the corresponding gateway device of the session synchronization, thereby implementing accurate sending of the operation instruction under the session to the corresponding gateway device of the session synchronization, and ensuring accurate sending of the operation instruction under the session.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
Further, the real-time step S21 is to establish a session, synchronize the session to a corresponding gateway device, and notify a corresponding target remote device to establish a session connection with the gateway device before the session connection is established between the target remote device and the gateway device based on the session connection state fed back by the gateway device according to the session, and the method further includes:
a long connection is established with the target remote device.
In an embodiment of the application, before a session is established, the management device establishes long connections with all target remote devices in a remote login process, so that the target remote devices are connected to the management device (TSM cluster) in a reverse long connection manner, and a waiting command is set at the management device end through the long connections, so that the target remote devices are reversely connected to the management device, and further when a notification that the remote login of the target remote devices is required comes, the target remote devices can be rapidly notified to start a corresponding session process and synchronize the session to a corresponding gateway device to establish session connection.
Further, the establishing of the long connection with the target remote device in step S21 includes:
establishing a long connection with the target remote device through a local slave node.
Following the above-mentioned embodiments of the present application, the management device (TSM cluster) includes a local master node (TS MMaster) and a local slave node (TS SMaster) because the management device (TSM cluster) needs to manage all sessions in the telnet process and the gateway devices to which the sessions are synchronized and the long connection with the target remote device, resulting in a large load of resources of the management device and a hard-to-bear load of one machine, wherein the local master node (TS MMaster) is used for the management of all sessions and their gateway devices synchronized to, the local slave node (TS SMmaster) is used for establishing long connection with the corresponding target remote equipment through long connection, so that the resource load in the management equipment (TSM cluster) is reduced, and the system is connected with the local master node (TS MMaster) in a long connection mode, so that the management device (TSM cluster) achieves balanced control on load through the local master node (TS MMaster) and the local slave node (TS SMaster).
Further, the step S21 is that, based on the feedback of the session connection state of the session by the gateway device, notifying the corresponding target remote device to establish a session connection with the gateway device, and includes:
receiving an unconnected notification corresponding to the state that the target remote device corresponding to the session and the gateway device are not connected, wherein the unconnected notification is fed back by the gateway device based on the session identifier and a corresponding process identifier on a corresponding target remote device;
and based on the unconnected notification, notifying the target remote equipment to start a session process corresponding to the process identification, wherein the session process sends a session connection request to the gateway equipment.
Next, in the foregoing embodiment of the present application, after the management device (TSM cluster) establishes a Session (Session a) in a local master node (TS mmster), the Session (Session a) is synchronized to a corresponding Gateway device (TS Gateway 1), the Gateway device (TS Gateway 1) determines whether a Session connection has been established in a target remote device (host1) corresponding to the Session based on the Session identifier (Session a) corresponding to the synchronized Session and a process identifier (Slave 1) corresponding to the target remote device, if yes, the Gateway device (TS Gateway 1) directly obtains a Session connection that has been established in the target remote device (host1) corresponding to the process identifier (Slave 1), and if not, the Gateway device (TS Gateway 1) feeds back an unconnected notification corresponding to the Session to the management device (TSM cluster), then, the step S21 receives an unconnected notification corresponding to the state that the target remote device (host1) corresponding to the session and the Gateway device (TS Gateway 1) do not establish a connection, which is fed back by the Gateway device (TS Gateway 1); based on the received unconnected notification, the step S21 may notify the target remote device (host1) corresponding to the Session (Session a) to start the Session process corresponding to the process identifier (Slave 1), so that the Session process sends a Session connection request to the Gateway device (TS Gateway 1), thereby quickly notifying the corresponding target remote device to start the corresponding Session process and establish Session connection with the corresponding Gateway device, so that the user device may perform transmission of operation data with the target remote device through the Session process in the subsequent step.
Further, in order to balance the resource load in the management device (TSM cluster), where the management device (TSM cluster) includes a local master node (TS mmster) and a local slave node (TS SMaster), and the receiving of the unconnected notification corresponding to the state where the target remote device corresponding to the session and the gateway device do not establish connection, based on the session identifier and the corresponding process identifier on the corresponding target remote device, fed back by the gateway device in step S21 includes:
receiving the non-connection notification through a local master node, and sending the non-connection notification to a local slave node;
based on the unconnected notification, notifying the target remote device to start a session process corresponding to the process identifier and send a session connection request to the gateway device, including:
and notifying a target remote device to start a session process corresponding to the process identification to send a session connection request to the gateway device through the local slave node based on the unconnected notification.
Next, in the foregoing embodiment of the present application, after the management device (TSM cluster) synchronizes the Session (Session a) that is established to the corresponding Gateway device (TS Gateway 1), the Session identifier (Session a) corresponding to the Session that is synchronized by the Gateway device (TS Gateway 1) and the process identifier (Slave 1) corresponding to the target remote device determine whether the target remote device (host1) corresponding to the Session has already established a Session connection, if not, the Gateway device (TS Gateway 1) feeds back an unconnected notification corresponding to the Session to the local master node (TS MMaster) in the management device (TSM cluster), and then the step S21 receives, through the local master node (TS MMaster), the unconnected notification corresponding to the Session that is fed back by the Gateway device (TS Gateway 1), where the target remote device (host1) and the Gateway device (TS Gateway 1) do not establish a connection, and then receives, through the local master node (TS MMaster), the unconnected notification corresponding to the unconnected state that is not established by the Gateway device (TS Gateway 1) Receiving a notification, and sending the non-connection notification to a local Slave node (TS SMmaster) in a broadcast mode, so that the local Slave node (TS SMmaster) which establishes long connection with a target remote device corresponding to the process identifier (Slave 1) receives the non-connection notification corresponding to the session; then, in step S21, based on the non-connection notification, the local Slave node (TS SMaster) that establishes a long connection with the target remote device corresponding to the process identifier (Slave 1) notifies the target remote device (host1) corresponding to the Session (Session a) to start the Session process corresponding to the process identifier (Slave 1), so that the target remote device (host1) starts the Session process corresponding to the process identifier (Slave 1) and establishes a corresponding Session connection with the gateway device based on the Session connection request, by accurately forwarding the non-connection notification corresponding to the Session through the local master node (TS SMaster) and the local Slave node (TS SMaster) at the management device (TSM cluster) end.
FIG. 3 illustrates a data flow diagram between a target remote device and a management device, gateway device, and peripheral device in a method of transmitting operational data according to an aspect of the subject application; wherein, applied to a target remote device (host) side in a remote login process, the method includes step S31, step S32, and step S33, wherein,
in step S31, it is determined whether a notification sent by the management device to establish session connection with the corresponding gateway device is acquired, and if so, session connection is established with the corresponding gateway device based on the notification; after the session connection corresponding to the session is successfully established between the target remote device and the gateway device, the step S32 receives an operation instruction under the session corresponding to the session connection sent by the gateway device through the session connection; then, the step S33 executes the operation instruction to obtain a corresponding operation result, and sends the operation result to the gateway device, so that the gateway device indirectly returns the operation result corresponding to the operation instruction under the session to the user equipment, thereby implementing transmission of the operation data under the session between the user equipment and the target remote device through the session connection, avoiding any operation of the operation data transmitted between the user equipment and the target remote device, and further ensuring the security and integrity of all operation data in the session connection process.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
Further, the step S31 determines whether a notification sent by the management device to establish session connection with the corresponding gateway device is acquired, and if so, before establishing session connection with the corresponding gateway device based on the notification, the method further includes:
a long connection is established with the management device.
It should be noted that, the target remote device includes a terminal service Agent (TS Agent) and at least one session process (Slave), where the terminal service Agent (TS Agent) is configured to manage a process of the target remote login device (host), and once started, the terminal service Agent (TS Agent) is directly connected to a management device (TSM cluster), and the session process (Slave) is configured to start a corresponding session, and ensure that a session performs transmission of operation data in a session process.
In an embodiment of the application, before the target remote device (host) transmits the operation data in the same session through the Gateway device (TS Gateway) and the user device, the terminal service Agent (TS Agent) in the target remote device (host) is connected to the management device (TSM cluster) through a reverse long connection, that is, a long connection is established between the terminal service Agent (TS Agent) and the management device (TSM cluster), the target remote device (host) sets a waiting command through the long connection, so that when a notification that the target remote device (host) needs to be remotely logged in reaches the management device (TSM cluster), the management device (TSM cluster) can quickly notify the target remote device (host), and the terminal service Agent (TS Agent) in the target remote device (host) can immediately start the corresponding session process and transmit the corresponding session process And synchronizing the session to the corresponding gateway equipment to establish session connection.
Further, the establishing of the long connection with the management device in the step S31 includes:
a long connection is established with a local slave node in the management device.
Following the above-mentioned embodiments of the present application, since the management device (TSM cluster) needs to manage all sessions in the telnet process and the Gateway device to which the sessions are synchronized and the long connection with the target remote device, which results in a large resource load of the management device and makes it difficult for one machine to bear, the management device includes a local master node (TS mmster) and a local slave node (TS SMaster), and the target remote device (host) connects the terminal service Agent (TS Agent) in the target remote device (host) to the local slave node (TS SMaster) in the management device (TSM cluster) through a reverse long connection, that is, the terminal service Agent (TS Agent) establishes a long connection with the local slave node (SMaster) in the management device (TSM cluster) before the transmission of the operation data under the same session is performed between the Gateway device (TS Gateway) and the user device, and the terminal service Agent (TS Agent) in the target remote equipment (host) sets a waiting command through the long connection to the management equipment (TSM cluster), so that when the notice that the target remote equipment (host) needs to be remotely logged in reaches the management equipment (TSM cluster), the management equipment (TSM cluster) can quickly notify the terminal service Agent (TS Agent) in the target remote equipment (host), and the terminal service Agent (TS Agent) in the target remote equipment (host) can immediately start a corresponding session process and synchronize the session to the corresponding gateway equipment to establish session connection.
Further, after determining whether to acquire the notification sent by the management device to establish the session connection with the corresponding gateway device, the step S31 further includes:
and if not, acquiring the session connection which is established on the target remote equipment and corresponds to the process identification from the gateway equipment.
Next to the foregoing embodiment of the present application, after determining whether to acquire a notification sent by the management device (TSM cluster) to establish a session connection with the corresponding Gateway device (TS Gateway 1), if not, then it indicates that a session connection corresponding to the session has been established between the target remote device (host1) and the Gateway device (TS Gateway 1), and may directly acquire, from the Gateway device (TS Gateway 1), the session connection already established on the target remote device (host1) corresponding to the process identifier (Slave 1), so that the target remote device (host1) performs transmission of operation data under the session with the user equipment through the session connection already established between the Gateway device (TS Gateway 1) and the session corresponding to the session.
Further, the step S31 of establishing a session connection with the corresponding gateway device based on the notification further includes:
receiving a notification of establishing session connection with a corresponding gateway device, which is sent by the management device;
based on the notification, starting a session process on the target remote device corresponding to the process identifier, wherein the session process sends a session connection request to the gateway device;
and establishing session connection with the gateway equipment based on the acceptance feedback of the session connection request received by the gateway equipment.
It should be noted that the notification corresponds to: when the session is synchronized to the gateway device, and the gateway device determines that the session connection with the corresponding target remote device is not established, the gateway device sends a non-connection notification corresponding to the session to the management device, and the management device receives the non-connection notification and then notifies the corresponding target remote device, that is, the notification sent by the management device and used for establishing the session connection with the corresponding gateway device, received by the target remote device, corresponds to the non-connection notification.
Next, in the foregoing embodiment of the present application, when a session connection is not established between a target remote device (host1) corresponding to a session and the Gateway device (TS Gateway 1), the management device (TSM cluster) may receive a non-connection notification sent by a Gateway device, so that the management device (TSM cluster) forwards the non-connection notification to the corresponding target remote device (host1), after receiving that the non-connection notification is sent by the management device (TSM cluster), in step S31, the target remote device (host1) starts a session process corresponding to the process identifier (Slave 1), and then, after the session process in step S31 sends a session connection request corresponding to the session to the Gateway device (TS Gateway 1) based on the non-connection notification; when the Gateway device (TS Gateway 1) compares, based on the synchronized Session identifier (Session1) corresponding to the Session and the process identifier (Slave 1) in the target device, the Session identifier (Session ID) and the process identifier (Slave ID) in the Session connection request, and then the obtained comparison result is consistent, that is, when the Session ID is Session a and the Slave ID is Slave1, the Gateway device (TS Gateway 1) receives the Session connection request and establishes Session connection with the target remote device, and finally, step S31 establishes Session connection with the Gateway device based on the acceptance feedback that the Gateway device (TS Gateway 1) receives the Session connection request, thereby achieving fast establishment of Session connection corresponding to the Session between the target remote device and the Gateway device.
Further, the receiving of the notification of establishing the session connection with the corresponding gateway device sent by the management device in step S31 includes:
and receiving a notice that the management device establishes session connection with the corresponding gateway device through a local slave node.
Next, in the foregoing embodiment of the present application, before a session is established, in order to quickly obtain a notification from a management device (TSM cluster), a long connection is established between a target remote device and a local Slave node (TS SMaster) in the management device (TSM cluster) through a terminal service Agent (TS Agent), when a session connection is established between a Gateway device and the target remote device, the management device (TSM cluster) sends an unconnected notification corresponding to the session through the local Slave node (TS SMaster), after receiving the unconnected notification in step S31, a session process on the target remote device (host1) corresponding to the process identifier (Slave 1) is started, and the session process sends a session connection request to the Gateway device (TS Gateway 1) based on the unconnected notification corresponding to the session, so as to continue the session between the target remote device (host1) corresponding to the session and the Gateway device (TS Gateway 1) And establishing a session connection corresponding to the process identifier (Slave 1).
Fig. 4 is a schematic diagram illustrating a data flow among a peripheral device, a user device, a management device and a gateway device in a method for transmitting operation data according to an aspect of the present application, wherein the method is applied to a peripheral device (TS Portal) side in a remote login process, the method includes steps S41, S42, S43 and S44, wherein,
after a session connection corresponding to the session established by the management device (TSM cluster) has been established between the introduced Gateway device (TS Gateway 1) for transmitting operation data and the target remote device (host1), the step S41 is to send a Gateway request to the management device (TSM cluster) based on an operation instruction in the same session sent by the user device; to cause a local master node (TS MMmaster) in a managing device (TSM cluster) to inform the peripheral device (TS Portal) of a corresponding Gateway device (TS Gateway 1) synchronized with the session based on the received Gateway request; then, the step S42 receives that the management device returns a corresponding Gateway device (TS Gateway 1) based on the Gateway request; the operation instruction under the session is accurately sent to the corresponding Gateway equipment (TS Gateway 1) of the session synchronization, and the accurate issuing of the operation instruction under the session by the subsequent Gateway equipment is ensured; next, the step S43 sends the operation instruction to the gateway device, and receives an operation result sent by the gateway device based on the operation instruction; finally, the step S44 sends the operation result to the user equipment. The method and the device realize the transmission of the operation data between the user equipment and the target remote equipment through the gateway equipment, avoid the right-lifting deletion of the operation data caused by the point-to-point direct connection between the user equipment and the target remote equipment in the prior art, and ensure the safety and the integrity of all the operation data in the session connection process between the gateway equipment and the target remote equipment.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
FIG. 5 illustrates an overall flow diagram of a system method of transferring operational data in accordance with an aspect of the subject application; wherein, the system method comprises a step S101 to a step S114, wherein,
in step S101, after the user equipment sends a session request, the management equipment establishes a session based on the session request
In step S102, the management device synchronizes the session to the gateway device;
in step S103, the gateway device determines whether to establish a session connection with the target remote device in the session, and if so, directly obtains the session connection step to the gateway device;
if not, the gateway device sends a non-connection notification corresponding to the session connection state corresponding to the session to the management device in the step S103;
in step S104, the management device notifies the corresponding target remote device to establish session connection with the gateway device based on the unconnected notification corresponding to the session;
in step S105, the gateway device establishes session connection with the corresponding target remote device;
in step S106, the peripheral device receives the operation instruction in the same session sent by the user equipment;
in step S107, the peripheral device sends a gateway request to the management device;
in step S108, the management device returns a corresponding gateway device based on the gateway request;
step S109, the peripheral device sends the operation instruction to the gateway device;
in step S110, the gateway device sends the operation instruction to the target remote device;
in the step S111, the target remote device executes the operation instruction and obtains a corresponding operation result;
in step S112, the target remote device sends the operation result to the gateway device;
in step S113, the gateway device sends the operation result to the peripheral device;
in step S114, the peripheral device sends the operation result to the user equipment.
Through the steps S101 to S114, after the session connection is established between the gateway device and the target remote device, the recording and forwarding of all the operation data of the user device and the target remote device in the remote login process is realized through the introduced gateway device, which not only avoids any operation on the operation data by the user device, but also ensures the security and integrity of all the operation data in the session connection process.
In an aspect of the present application, a schematic structural diagram of a gateway device for transmitting operation data, where a gateway device end applied in a remote login process includes: a session connecting device 11, a sending down device 12 and a reporting device 13, wherein,
the session connection device 11 is configured to acquire a session synchronized by the management device; then, the session connection apparatus 11 establishes a session connection with the corresponding target remote device based on the session; after the session connection is established between the gateway device and the target remote device, the issuing device 12 is configured to receive and record an operation instruction under the session sent by the peripheral device, and send the operation instruction to the target remote device, so that the target remote device executes the received operation instruction and sends an obtained corresponding operation result to the gateway device; finally, the reporting device 13 is configured to receive and record an operation result returned by the target remote device based on the operation instruction, and send the operation result to the peripheral device, so that all operation data transmitted between all user devices and the target remote device are transmitted and collected at the gateway device, thereby not only avoiding any operation on the operation data by the user devices, but also ensuring the security and integrity of all operation data in the session connection process.
It should be noted that, in the remote login process in the embodiment of the present application, the Gateway device is preferably a TS Gateway (terminal service Gateway device), the management device is preferably a TSM cluster, the target remote device is preferably a host (host in the terminal service remote device), and the peripheral device is preferably a TS Gateway (terminal service Gateway device), where the target remote device (host) is a machine that the user device needs to remotely log in, the management device is a device that manages all machines in the remote login process, and the Gateway device (TS Gateway) is a device that actually performs operation data transmission in the remote login process. Of course, the above preference for devices in the remote login process is only a preferred embodiment of an aspect of the present application, and other existing or future possibilities of the gateway device, the management device, the target remote device and the peripheral device, as applicable to the present application, are also included in the scope of protection of the present application and are hereby incorporated by reference.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
Further, the session connection device 11 is configured to:
acquiring a session synchronized by a management device;
judging whether the target remote equipment corresponding to the session establishes session connection or not based on the session identification and the corresponding process identification on the corresponding target remote equipment;
and if so, acquiring the established session connection on the target remote equipment corresponding to the process identification.
In an embodiment of the present application, when the management device sends a Session request, the management device establishes a Session (Session a) based on the Session request, and synchronizes the Session (Session a) to a corresponding Gateway device (TS Gateway 1), so that the Gateway device obtains the Session (Session a) synchronized by the management device from the Session connection apparatus 11, and based on the synchronized Session (Session a), makes a Session process corresponding to a Session identifier in a target remote device corresponding to the Session establish Session connection, and then the Session connection apparatus 11 determines, according to the Session identifier (Session a) of the Session (Session a) and a process identifier (Slave 1) corresponding to the target remote device, whether the target remote device (host1) corresponding to the Session has already established Session connection; if so, the Session connection apparatus 11 obtains the Session connection already established on the target remote device (host1) corresponding to the process identifier (Slave 1), so as to quickly obtain the Session connection corresponding to the process identifier (Slave 1) in the Session (Session a) already established between the gateway device and the target remote device, so that the subsequent gateway device sends the operation instruction under the Session from the user equipment to the target remote device (host1) corresponding to the process identifier (Slave 1) through the established Session connection.
Following the above embodiments of the present application, the session connection apparatus 11 is further configured to:
if not, sending an unconnected notification corresponding to the session to the management device, so that the management device is ready to send the unconnected notification to the target remote device;
acquiring a session connection request sent by the target remote equipment based on the received unconnected notification;
and establishing session connection with the corresponding session process in the target remote equipment based on the session connection request, the session identification and the corresponding process identification on the corresponding target remote equipment.
Next, in the foregoing embodiment of the present application, when the Session connection apparatus 11 determines, according to the Session identifier (SessionA) of the Session (Session a) and the corresponding process identifier (Slave 1) on the corresponding target remote device, whether the target remote device (host1) corresponding to the Session has already established Session connection; if not, the Session connection apparatus 11 may send, to the management device, an unconnected notification that a Session connection has not been established between the Gateway device (TS Gateway 1) and the target remote device (host1) corresponding to the Session (Session a), so that the management device sends the unconnected notification to the target remote device (host1), when the target remote device (host1) receives the unconnected notification corresponding to the Session, the target remote device (host1) may start a Session process corresponding to a process identifier (Slave 1) corresponding to the target remote device (host1) corresponding to the Session (Session a), send a corresponding Session connection request to the Gateway device (TS Gateway 1), after the Session connection apparatus 11 receives, from the target remote device, a Session connection request sent based on the unconnected notification received, the Session connection apparatus 11 establishes a Session connection with a Session process corresponding to the target remote device (host1) based on the Session identifier (Session a) in the Session synchronized by the Session connection request and the process identifier (Slave 1) corresponding to the target remote device (host1), so as to establish a Session connection between a real-time Gateway device (TS Gateway 1) and the target remote device (host1), so that the Gateway device (TS Gateway 1) forwards and collects all operation data between the user device and the target remote device through the established Session connection.
Further, the session connection device 11 is configured to:
comparing the session identifier and the corresponding process identifier on the corresponding target remote device with the session identifier and the corresponding process identifier in the session connection request,
and when the comparison result is consistent, establishing session connection with the corresponding session process in the target remote equipment.
Next, in the foregoing embodiment of the present application, when receiving a Session connection request sent by a target remote device through a Session process corresponding to a process identifier (Slave 1), the Gateway device (TS Gateway 1) compares the Session identifier (Session a) in the Session synchronized by the management device and the corresponding process identifier (Slave 1) on the corresponding target remote device (host1), with the Session identifier (Session ID) and the corresponding process identifier (Slave ID) carried in the Session connection request, and when the comparison result is consistent, that is, when the Session ID is Session a and the Slave ID is Slave1, the Gateway device (TS Gateway 1) establishes a Session connection with the Session process corresponding to the process identifier (Slave 1) in the target remote device (host1), and the Gateway device (TS Gateway 1) and the target remote device (1) corresponding to the Session synchronized by the management device establish a Session connection The accuracy of the session connection established therebetween.
According to another aspect of the present application, a structural diagram of a management device for transmitting operation data is shown, wherein a management device (TSM cluster) end applied to a remote login process includes: a session establishing means 21, a receiving means 22 and a notifying means 23, wherein,
the session establishing device 21 is configured to establish a session, synchronize the session to a corresponding gateway device, and notify a corresponding target remote device of establishing a session connection with the gateway device based on a session connection state fed back by the gateway device according to the session; when the user equipment needs to perform synchronous operation on the target remote equipment after the session connection is established between the gateway equipment and the target remote equipment, sending an operation instruction under the session to peripheral equipment; when the management device synchronizes the session to the corresponding gateway device while establishing the session, the management device already records the corresponding gateway device to which the session is synchronized, and manages the session and the corresponding gateway device, so that after receiving an operation instruction under the session, the peripheral device wants to know to which gateway device to send the operation instruction under the session, and the peripheral device needs to send a gateway request to the management device based on the received operation instruction under the session; then, the receiving device 22 is configured to receive a gateway request sent by the peripheral device based on the received operation instruction under the session; finally, the notifying device 23 is configured to notify the peripheral device of the gateway device corresponding to the session synchronization based on the gateway request, so that the peripheral device sends the operation instruction under the session to the gateway device corresponding to the session synchronization, thereby implementing accurate sending of the operation instruction under the session to the gateway device corresponding to the session synchronization, and ensuring accurate issuing of the operation instruction under the session.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
Further, the real-time session establishing device 21 is further configured to:
a long connection is established with the target remote device.
In an embodiment of the application, before a session is established, the management device establishes long connections with all target remote devices in a remote login process, so that the target remote devices are connected to the management device (TSM cluster) in a reverse long connection manner, and a waiting command is set at the management device end through the long connections, so that the target remote devices are reversely connected to the management device, and further when a notification that the remote login of the target remote devices is required comes, the target remote devices can be rapidly notified to start a corresponding session process and synchronize the session to a corresponding gateway device to establish session connection.
Further, the session establishing device 21 is configured to:
establishing a long connection with the target remote device through a local slave node.
Following the above-mentioned embodiments of the present application, the management device (TSM cluster) includes a local master node (TS MMaster) and a local slave node (TS SMaster) because the management device (TSM cluster) needs to manage all sessions in the telnet process and the gateway devices to which the sessions are synchronized and the long connection with the target remote device, resulting in a large load of resources of the management device and a hard-to-bear load of one machine, wherein the local master node (TS MMaster) is used for the management of all sessions and their gateway devices synchronized to, the local slave node (TS SMmaster) is used for establishing long connection with the corresponding target remote equipment through long connection, so that the resource load in the management equipment (TSM cluster) is reduced, and the system is connected with the local master node (TS MMaster) in a long connection mode, so that the management device (TSM cluster) achieves balanced control on load through the local master node (TS MMaster) and the local slave node (TS SMaster).
Further, the session establishing device 21 is configured to:
receiving an unconnected notification corresponding to the state that the target remote device corresponding to the session and the gateway device are not connected, wherein the unconnected notification is fed back by the gateway device based on the session identifier and a corresponding process identifier on a corresponding target remote device;
and based on the unconnected notification, notifying the target remote equipment to start a session process corresponding to the process identification, wherein the session process sends a session connection request to the gateway equipment.
Next, in the foregoing embodiment of the present application, after the management device (TSM cluster) establishes a Session (Session a) in a local master node (TS mmster), the Session (Session a) is synchronized to a corresponding Gateway device (TS Gateway 1), the Gateway device (TS Gateway 1) determines whether a Session connection has been established in a target remote device (host1) corresponding to the Session based on the Session identifier (Session a) corresponding to the synchronized Session and a process identifier (Slave 1) corresponding to the target remote device, if yes, the Gateway device (TS Gateway 1) directly obtains a Session connection that has been established in the target remote device (host1) corresponding to the process identifier (Slave 1), and if not, the Gateway device (TS Gateway 1) feeds back an unconnected notification corresponding to the Session to the management device (TSM cluster), then, the session establishing device 21 receives an unconnected notification corresponding to the state that the target remote device (host1) corresponding to the session and the Gateway device (TS Gateway 1) do not establish connection, which is fed back by the Gateway device (TS Gateway 1); based on the received unconnected notification, the Session establishing apparatus 21 may notify the target remote device (host1) corresponding to the Session (Session a) to start a Session process corresponding to the process identifier (Slave 1), so that the Session process sends a Session connection request to the Gateway device (TS Gateway 1), thereby quickly notifying the corresponding target remote device to start the corresponding Session process and establish Session connection with the corresponding Gateway device, so that the user device performs transmission of operation data with the target remote device through the Session process in the subsequent process.
Further, in order to balance the resource load in the management device (TSM cluster), the management device (TSM cluster) includes a local master node (TS MMaster) and a local slave node (TS SMaster), and the session establishing device 21 is configured to:
receiving the non-connection notification through a local master node, and sending the non-connection notification to a local slave node;
and notifying a target remote device to start a session process corresponding to the process identification to send a session connection request to the gateway device through the local slave node based on the unconnected notification.
Next, in the foregoing embodiment of the present application, after the management device (TSM cluster) synchronizes the Session (Session a) that is established to the corresponding Gateway device (TS Gateway 1), the Session identifier (Session a) corresponding to the Session and the process identifier (Slave 1) corresponding to the target remote device that are synchronized by the Gateway device (TS Gateway 1) determine whether the target remote device (host1) corresponding to the Session already establishes Session connection, if not, the Gateway device (TS Gateway 1) feeds back an unconnected notification corresponding to the Session to the local master node (TS MMaster) in the management device (TSM cluster), and then the Session establishing apparatus 21 receives, through the local master node (TS MMaster), the unconnected state pair of the target remote device (host1) corresponding to the Session and the Gateway device (TS Gateway 1) that are fed back by the Gateway device (TS Gateway 1) A corresponding unconnected notification, and sending the unconnected notification to a local Slave node (TS SMaster) in a broadcast manner, so that the local Slave node (TS SMaster) which establishes a long connection with a target remote device corresponding to the process identifier (Slave 1) receives the unconnected notification corresponding to the session; then, the Session establishing apparatus 21 notifies, based on the non-connection notification, the target remote device (host1) corresponding to the Session (Session a) to start a Session process corresponding to the process identifier (Slave 1) through the local Slave node (TS SMaster) that establishes a long connection with the target remote device corresponding to the process identifier (Slave 1), so that accurate forwarding of the non-connection notification corresponding to the Session is performed at a management device (TSM cluster) end through a local master node (TS mmster) and the local Slave node (TS SMaster), so that the target remote device (host1) starts a Session process corresponding to the process identifier (Slave 1), and establishes a corresponding Session connection with a gateway device based on a Session connection request.
In another aspect of the present application, a schematic diagram of a target remote device for transmitting operation data is shown, wherein the method is applied to a target remote device (host) side in a remote login process, the method includes establishing a connection device 31, an instruction receiving device 32 and an instruction sending device 33, wherein,
the connection establishing device 31 is configured to determine whether a notification sent by the management device and used for establishing session connection with the corresponding gateway device is acquired, and if so, establish session connection with the corresponding gateway device based on the notification; after the session connection corresponding to the session is successfully established between the target remote device and the gateway device, the instruction receiving device 32 is configured to receive, through the session connection, an operation instruction under the session corresponding to the session connection sent by the gateway device; then, the instruction sending device 33 is configured to execute the operation instruction to obtain a corresponding operation result, and send the operation result to the gateway device, so that the gateway device indirectly returns the operation result corresponding to the operation instruction under the session to the user equipment, thereby implementing transmission of the operation data corresponding to the session through the session connection between the user equipment and the target remote equipment, avoiding any operation of the operation data transmitted between the target remote equipment by the user equipment, and further ensuring security and integrity of all operation data in the session connection process.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
Further, the connection establishing device 31 is further configured to:
a long connection is established with the management device.
It should be noted that, the target remote device includes a terminal service Agent (TS Agent) and at least one session process (Slave), where the terminal service Agent (TS Agent) is configured to manage a process of the target remote login device (host), and once started, the terminal service Agent (TS Agent) is directly connected to a management device (TSM cluster), and the session process (Slave) is configured to start a corresponding session, and ensure that a session performs transmission of operation data in a session process.
In an embodiment of the application, before the target remote device (host) transmits the operation data in the same session through the Gateway device (TS Gateway) and the user device, the terminal service Agent (TS Agent) in the target remote device (host) is connected to the management device (TSM cluster) through a reverse long connection, that is, a long connection is established between the terminal service Agent (TS Agent) and the management device (TSM cluster), the target remote device (host) sets a waiting command through the long connection, so that when a notification that the target remote device (host) needs to be remotely logged in reaches the management device (TSM cluster), the management device (TSM cluster) can quickly notify the target remote device (host), and the terminal service Agent (TS Agent) in the target remote device (host) can immediately start the corresponding session process and transmit the corresponding session process And synchronizing the session to the corresponding gateway equipment to establish session connection.
Further, the connection establishing device 31 is configured to:
a long connection is established with a local slave node in the management device.
Following the above-mentioned embodiments of the present application, since the management device (TSM cluster) needs to manage all sessions in the telnet process and the Gateway device to which the sessions are synchronized and the long connection with the target remote device, which results in a large resource load of the management device and makes it difficult for one machine to bear, the management device includes a local master node (TS mmster) and a local slave node (TS SMaster), and the target remote device (host) connects the terminal service Agent (TS Agent) in the target remote device (host) to the local slave node (TS SMaster) in the management device (TSM cluster) through a reverse long connection, that is, the terminal service Agent (TS Agent) establishes a long connection with the local slave node (SMaster) in the management device (TSM cluster) before the transmission of the operation data under the same session is performed between the Gateway device (TS Gateway) and the user device, and the terminal service Agent (TS Agent) in the target remote equipment (host) sets a waiting command through the long connection to the management equipment (TSM cluster), so that when the notice that the target remote equipment (host) needs to be remotely logged in reaches the management equipment (TSM cluster), the management equipment (TSM cluster) can quickly notify the terminal service Agent (TS Agent) in the target remote equipment (host), and the terminal service Agent (TS Agent) in the target remote equipment (host) can immediately start a corresponding session process and synchronize the session to the corresponding gateway equipment to establish session connection.
Further, the connection establishing device 31 is further configured to:
and if not, acquiring the session connection which is established on the target remote equipment and corresponds to the process identification from the gateway equipment.
Next, in the foregoing embodiment of the present application, after determining whether to acquire a notification sent by a management device (TSM cluster) to establish a session connection with a corresponding Gateway device (TS Gateway 1), if not, then the connection establishing apparatus 31 indicates that a session connection corresponding to the session has been established between the target remote device (host1) and the Gateway device (TS Gateway 1), and may directly acquire, from the Gateway device (TS Gateway 1), the session connection already established on the target remote device (host1) corresponding to the process identifier (Slave 1), so that the target remote device (host1) performs transmission of operation data under the session with a user equipment through the session connection already established between the Gateway device (TS Gateway 1) and the session corresponding to the session.
Further, the connection establishing device 31 is further configured to:
receiving a notification of establishing session connection with a corresponding gateway device, which is sent by the management device;
based on the notification, starting a session process on the target remote device corresponding to the process identifier, wherein the session process sends a session connection request to the gateway device;
and establishing session connection with the gateway equipment based on the acceptance feedback of the session connection request received by the gateway equipment.
Next, in the foregoing embodiment of the present application, when a session connection is not established between a target remote device (host1) corresponding to a session and the Gateway device (TS Gateway 1), the management device (TSM cluster) may receive a non-connection notification sent by a Gateway device, so that the management device (TSM cluster) forwards the non-connection notification to the corresponding target remote device (host1), after the connection establishment apparatus 31 receives the non-connection notification sent by the management device (TSM cluster), the target remote device (host1) starts a session process corresponding to the process identifier (Slave 1), and then the session process in the connection establishment apparatus 31 sends a session connection request corresponding to the session to the Gateway device (TS Gateway 1) based on the non-connection notification; when the Gateway device (TS Gateway 1) compares, based on the synchronized Session identifier (Session1) corresponding to the Session and the process identifier (Slave 1) in the target device, the Session identifier (Session ID) and the process identifier (Slave ID) in the Session connection request, and then the obtained comparison result is consistent, that is, when the Session ID is Session a and the Slave ID is Slave1, the Gateway device (TS Gateway 1) receives the Session connection request and establishes Session connection with the target remote device, and finally, the connection establishing apparatus 31 establishes Session connection with the Gateway device based on the receipt feedback that the Gateway device (TS Gateway 1) receives the Session connection request, so as to achieve fast establishment of Session connection corresponding to the Session between the target remote device and the Gateway device.
Further, the connection establishing device 31 is configured to:
and receiving a notice that the management device establishes session connection with the corresponding gateway device through a local slave node.
Next, in the foregoing embodiment of the present application, before a session is established, in order to quickly obtain a notification from a management device (TSM cluster), a long connection is established between a target remote device and a local Slave node (TS SMaster) in the management device (TSM cluster) through a terminal service Agent (TS Agent), when a session connection is established between a Gateway device and the target remote device, the management device (TSM cluster) sends an unconnected notification corresponding to the session through the local Slave node (TS SMaster), after the unconnected notification is received by the connection establishing device 31, a session process on the target remote device (host1) corresponding to the process identifier (Slave 1) is started, and the session process sends a session connection request to the Gateway device (TS Gateway 1) based on the unconnected notification corresponding to the session, so as to continue to connect the target remote device (host1) corresponding to the session and the Gateway device (TS Gateway 1) later ) Establishing a session connection corresponding to the process identification (Slave 1).
In another aspect of the present application, a schematic diagram of a peripheral device for transmitting operation data is shown, wherein the peripheral device is applied to a peripheral device (TS Portal) side in a remote login process, the method includes a request device 41, a return device 42, a forwarding device 43 and an operation result sending device 44, wherein,
after a session connection corresponding to the session established by the management device (TSM cluster) has been established between the introduced Gateway device (TS Gateway 1) for transmitting operation data and the target remote device (host1), the requesting device 41 is configured to send a Gateway request to the management device (TSM cluster) based on an operation instruction in the same session sent by the user device; to cause a local master node (TS MMmaster) in a managing device (TSM cluster) to inform the peripheral device (TS Portal) of a corresponding Gateway device (TS Gateway 1) synchronized with the session based on the received Gateway request; then, the returning device 42 is configured to receive that the management device returns a corresponding Gateway device (TS Gateway 1) based on the Gateway request; the operation instruction under the session is accurately sent to the corresponding Gateway equipment (TS Gateway 1) of the session synchronization, and the accurate issuing of the operation instruction under the session by the subsequent Gateway equipment is ensured; next, the forwarding device 43 is configured to send the operation instruction to the gateway device, and receive an operation result sent by the gateway device based on the operation instruction; finally, the operation result sending device 44 is configured to send the operation result to the user equipment. The method and the device realize the transmission of the operation data between the user equipment and the target remote equipment through the gateway equipment, avoid the right-lifting deletion of the operation data caused by the point-to-point direct connection between the user equipment and the target remote equipment in the prior art, and ensure the safety and the integrity of all the operation data in the session connection process between the gateway equipment and the target remote equipment.
In order to manage the Session and subsequently establish a Session connection corresponding to the Session, the Session includes a Session identifier, the corresponding target remote device, and a corresponding process identifier on the target remote device, that is, the Session includes a Session identifier (Session) for distinguishing from other sessions, a corresponding target remote device (host machine name) for indicating that a Session process corresponding to the Session is established between the gateway device and the corresponding target remote device, and a corresponding process identifier (Slave ID) on the target remote device for indicating that a corresponding Session process is started in the corresponding target remote device to establish a Session connection corresponding to the Session, so as to implement accurate management of the Session.
In summary, according to the present application, a gateway device is introduced as a data forwarding point in a remote login process, and the gateway device first obtains a session synchronized by a management device, and establishes a session connection with a corresponding target remote device based on the session; after the session connection is established between the gateway equipment and the target remote equipment, the gateway equipment receives and records an operation instruction under the session sent by peripheral equipment, and sends the operation instruction to the target remote equipment, so that the target remote equipment executes the received operation instruction and sends an obtained corresponding operation result to the gateway equipment; the gateway device receives and records the operation result returned by the target remote device based on the operation instruction, and sends the operation result to the peripheral device, so that all the operation data transmitted between all the user devices and the target remote device are transmitted and collected at the gateway device, thereby not only avoiding any operation of the user devices on the operation data, but also ensuring the safety and integrity of all the operation data in the session connection process.
Further, the method includes the steps that a session is established at a management device end, the session is synchronized to the corresponding gateway device, and the corresponding target remote device is notified to establish session connection with the gateway device based on the session connection state fed back by the gateway device according to the session; after session connection corresponding to the session is established between the gateway device and target remote equipment, the management device receives a gateway request sent by peripheral equipment based on the received operation instruction under the session; because the management device synchronizes the session to the corresponding gateway device and manages the session and the corresponding gateway device thereof while establishing the session, after receiving a gateway request sent by the peripheral device based on the received operation instruction under the session, the management device notifies the peripheral device of the corresponding gateway device under the session synchronization based on the gateway request, so that the peripheral device sends the operation instruction under the session to the corresponding gateway device under the session synchronization, thereby realizing the accurate sending of the operation instruction under the session to the corresponding gateway device under the session synchronization and ensuring the accurate sending of the operation instruction under the session.
Further, the method comprises the steps that whether a notification of establishing session connection with the corresponding gateway device, which is sent by the management device, is acquired or not is judged at the target remote device side, and if yes, session connection is established with the corresponding gateway device based on the notification; after the session connection corresponding to the session is successfully established between the target remote device and the gateway device, the target remote device receives an operation instruction under the session corresponding to the session connection, which is sent by the gateway device, through the session connection; and then, the target remote equipment executes the operation instruction to obtain a corresponding operation result, and sends the operation result to the gateway equipment, so that the gateway equipment indirectly returns the operation result corresponding to the operation instruction under the session to the user equipment, the transmission of the operation data corresponding to the session through the session connection between the user equipment and the target remote equipment is realized, any operation of the operation data transmitted between the user equipment and the target remote equipment is avoided, and the safety and the integrity of all the operation data in the session connection process are also ensured.
Further, in the remote login process, after a session connection corresponding to a session established by the management device has been established between the introduced gateway device for transmitting operation data and a target remote device, the peripheral device sends a gateway request to the management device based on an operation instruction under the same session sent by the user device, so that the management device notifies the peripheral device of a corresponding gateway device synchronized with the session based on the received gateway request; then, the peripheral device receives the gateway request returned by the management device based on the corresponding gateway device, so that the operation instruction under the session is accurately sent to the corresponding gateway device of the session synchronization, and the accurate issuing of the operation instruction under the session by the subsequent gateway device is ensured; then, the peripheral equipment sends the operation instruction to the gateway equipment and receives an operation result sent by the gateway equipment based on the operation instruction; and finally, the peripheral equipment sends the operation result to the user equipment. The method and the device realize the transmission of the operation data between the user equipment and the target remote equipment through the gateway equipment, avoid the right-lifting deletion of the operation data caused by the point-to-point direct connection between the user equipment and the target remote equipment in the prior art, and ensure the safety and the integrity of all the operation data in the session connection process between the gateway equipment and the target remote equipment.
As shown in fig. 6, in a practical application scenario of the method for transmitting operation data in the remote login process provided by the present application, in the practical application scenario of the system method, the system method comprises a user equipment (DEV-OPS), a terminal service management device (TSM cluster), a terminal service peripheral device (TS Portal), a terminal service Gateway device (TS Gateway) and a target remote device (host), in order to achieve the purpose of resource load balancing, the terminal service management device (TSM cluster) comprises a local master node (TS MMmaster) and a local slave node (TS SMmaster), the local master node (TS MMaster) is used for the management of all sessions and their synchronized gateway devices, the local slave node (TS SMmaster) is used for establishing long connection with the corresponding target remote equipment in a long connection mode, so that the resource load in a management device (TSM cluster) is reduced; the target remote equipment (host) comprises a terminal service Agent (TS Agent) and at least one session process (Slave), wherein the terminal service Agent (TS Agent) is used for managing the target remote login equipment (host) process, and the session process (Slave) is used for connecting the target remote equipment with the corresponding gateway equipment so as to transmit the corresponding operation data in the session in the following process.
In the practical application scenario of the present application in fig. 6, first, in the managed target remote device cluster, the TSAgent deployed in each target remote device may be connected to a local slave node (TS SMaster) in the terminal service management device (TSM cluster) through a long connection, so as to set a wait command in the TS SMaster, so that the notification can be quickly sent to the target remote device in the following.
Then, when the user equipment needs to log in the target device (host1) remotely, sending a session request to a local master node (TS MMaster) in the terminal service management device (TSM cluster) through a TJ API (Application Programming interface) provided externally for authenticating a session request and accessing an internal system of a Terminal Service (TS), establishing a session based on the session request in the local master node (TS MMaster) in the terminal service management device (TSM cluster) after authenticating the session request in the TJ API through an identity of a login account, an account password and a key, and synchronizing the established session to the terminal service Gateway device (TS Gateway 1), wherein, in order to manage the session and subsequently establish a session connection corresponding to the session, the Session includes a Session identifier (Session a), the corresponding target remote device (host1), and a corresponding process identifier (Slave 1) on the target remote device (host 1).
Then, the terminal service Gateway device (TS Gateway 1) determines whether the target remote device (host1) corresponding to the session has started a session process corresponding to the process identifier (Slave 1), establishes session connection with the current terminal service Gateway device (TS Gateway 1), and directly obtains the session connection between the terminal service Gateway device (TS Gateway 1) corresponding to the session and the process identifier (Slave 1) in the target remote device (host1) if it is determined that the session connection has been established, so as to subsequently transmit operation data under the session; if the Session connection is not established, the terminal service Gateway device (TS Gateway 1) sends a non-connection notification corresponding to the Session (Session A) to a local host node (TS MMaster) in a terminal service management device (TSM cluster);
then, a local master node (TS mmster) in the terminal service management device (TSM cluster) sends the received non-connection notification corresponding to the Session (Session a) to all local Slave nodes (TS smster) in the terminal service management device (TSM cluster) in a broadcast manner, and when the local Slave nodes (TS smster) detect that a long-connection target remote device (host1) which keeps a connection by itself contains a process identifier (Slave 1) corresponding to the Session, the local Slave nodes (TS smster 1) send the received non-connection notification corresponding to the Session (Session a) to a terminal service Agent (TS Agent) in the target remote device (host1) in a long-connection manner;
then, a terminal service Agent (TS Agent) in the target remote device (host1) starts a Session process corresponding to a process identifier (Slave 1) in the Session based on the received unconnected notification corresponding to the Session (Session a), and sends a Session connection request corresponding to the Session to the terminal service Gateway device (TS Gateway 1) through the Session process; when the terminal service Gateway device (TS Gateway 1) receives the Session connection request, the Session identifier (Session a) in the Session synchronized by the management device and the corresponding process identifier (Slave 1) on the corresponding target remote device (host1) are first identified, comparing with the Session ID carried in the Session connection request and the corresponding process ID, when the comparison result is consistent, that is, when the Session ID is Session a and the Slave ID is Slave1, the Gateway device (TS Gateway 1) will establish a session connection with the session process corresponding to the process identifier (Slave 1) in the target remote device (host1), so as to achieve the accuracy of establishing a session connection between the Gateway device (TS Gateway 1) corresponding to the session synchronized by the management device and the target remote device (host 1).
Immediately after the Session connection between the Gateway device (TS Gateway 1) and the target remote device (host1) has been established, when a user equipment wants to operate the target remote device (host1), the user equipment sends an operation instruction under the Session (Session a) to the terminal service peripheral device (TS Portal 1) through a VIP (network balancing loader), wherein the VIP (network balancing loader) is configured to search a corresponding terminal service peripheral device (TS Portal 1) according to a health check to receive the operation instruction under the Session (Session a) so as to achieve the purpose of load balancing, and simultaneously, can open a network between the user equipment and the terminal service peripheral device; when a terminal service peripheral device (TS Portal 1) receives an operation instruction under the Session (Session A), in order to know which Gateway device (TS Gateway) the operation instruction under the Session (Session A) is sent to, a Gateway request corresponding to the Session needs to be sent to a local host node (TS MMaster) in a terminal service management device (TSM cluster) for establishing the Session (Session A).
Then, the local master node (TS MMmaster) in the terminal service management device (TSM cluster) searches for the Gateway device (TS Gateway 1) synchronized with the Session (Session A) at the beginning based on the received Gateway request corresponding to the Session (Session A), and notifies the terminal service peripheral device (TS Portal 1) of the Gateway device (TS Gateway 1) corresponding to the Gateway request corresponding to the Session (Session A), so that the terminal service peripheral device (TS Portal 1) sends the operation instruction under the Session (Session A) to the Gateway device (TS Gateway 1) based on the received notification of sending the operation instruction to the Gateway device (TS Gateway 1), thereby realizing the accurate issue of the operation instruction under the Session (Session A).
Then, the Gateway device (TS Gateway 1) sends the operation instruction under the Session (Session a) to the target remote device (host1) through the corresponding Session process in the Session (Session a), so that the target remote device (host1) obtains a corresponding operation result based on executing the received operation instruction under the Session (Session a), and sends the operation result to the Gateway device (TS Gateway 1), so that the Gateway device (TS Gateway 1) indirectly returns the operation result corresponding to the operation instruction under the Session (Session a) to the user device (DEV-OPS), thereby implementing transmission of the corresponding operation data under the Session through the Session connection between the user device and the target remote device, and avoiding any operation of the operation data transmitted between the user device and the target remote device, and the safety and integrity of all operation data in the session connection process are also ensured.
A computing-based device according to the present application, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
acquiring a session synchronized by a management device, and establishing session connection with a corresponding target remote device based on the session;
receiving and recording an operation instruction under the session sent by the peripheral equipment, and sending the operation instruction to the target remote equipment;
and receiving and recording an operation result returned by the target remote equipment based on the operation instruction, and sending the operation result to the peripheral equipment.
A computing-based device according to the present application, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
establishing a session, synchronizing the session to corresponding gateway equipment, and informing corresponding target remote equipment to establish session connection with the gateway equipment based on the session connection state fed back by the gateway equipment according to the session;
receiving a gateway request sent by peripheral equipment based on the received operation instruction under the session;
notifying the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request.
A computing-based device according to the present application, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
judging whether a notification which is sent by the management equipment and used for establishing session connection with the corresponding gateway equipment is acquired, if so, establishing session connection with the corresponding gateway equipment based on the notification;
receiving an operation instruction under a session corresponding to the session connection sent by the gateway equipment;
and executing the operation instruction to obtain a corresponding operation result, and sending the operation result to the gateway equipment.
A computing-based device according to the present application, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
sending a gateway request to the management equipment based on the operation instruction sent by the user equipment under the same session;
receiving the gateway request returned by the management equipment based on the corresponding gateway equipment;
sending the operation instruction to the gateway equipment, and receiving an operation result sent by the gateway equipment based on the operation instruction;
and sending the operation result to the user equipment.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
It should be noted that the present application may be implemented in software and/or a combination of software and hardware, for example, implemented using Application Specific Integrated Circuits (ASICs), general purpose computers or any other similar hardware devices. In one embodiment, the software programs of the present application may be executed by a processor to implement the steps or functions described above. Likewise, the software programs (including associated data structures) of the present application may be stored in a computer readable recording medium, such as RAM memory, magnetic or optical drive or diskette and the like. Additionally, some of the steps or functions of the present application may be implemented in hardware, for example, as circuitry that cooperates with the processor to perform various steps or functions.
In addition, some of the present application may be implemented as a computer program product, such as computer program instructions, which when executed by a computer, may invoke or provide methods and/or techniques in accordance with the present application through the operation of the computer. Program instructions which invoke the methods of the present application may be stored on a fixed or removable recording medium and/or transmitted via a data stream on a broadcast or other signal-bearing medium and/or stored within a working memory of a computer device operating in accordance with the program instructions. An embodiment according to the present application comprises an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein the computer program instructions, when executed by the processor, trigger the apparatus to perform a method and/or a solution according to the aforementioned embodiments of the present application.
It will be evident to those skilled in the art that the present application is not limited to the details of the foregoing illustrative embodiments, and that the present application may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the application being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or steps, and the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.

Claims (44)

1. A method for transmitting operation data at a gateway device, wherein the method comprises:
acquiring a session synchronized by a management device, and establishing session connection with a corresponding target remote device based on the session;
receiving and recording an operation instruction under the session sent by the peripheral equipment, and sending the operation instruction to the target remote equipment, wherein the operation instruction is an operation instruction sent to the target remote equipment by the user equipment;
and receiving and recording an operation result returned by the target remote equipment based on the operation instruction, and sending the operation result to the peripheral equipment.
2. The method of claim 1, wherein the session comprises a session identification, a corresponding target remote device, and a corresponding process identification on the target remote device.
3. The method of claim 2, wherein the obtaining of the session synchronized by the management device, and establishing a session connection with the corresponding target remote device based on the session, comprises:
acquiring a session synchronized by a management device;
judging whether the target remote equipment corresponding to the session establishes session connection or not based on the session identification and the corresponding process identification on the corresponding target remote equipment;
and if so, acquiring the established session connection on the target remote equipment corresponding to the process identification.
4. The method of claim 3, wherein the determining whether a session connection has been established with a target remote device corresponding to the session based on the session identifier and a corresponding process identifier on the corresponding target remote device further comprises:
if not, sending an unconnected notification corresponding to the session to the management device, so that the management device is ready to send the unconnected notification to the target remote device;
acquiring a session connection request sent by the target remote equipment based on the received unconnected notification;
and establishing session connection with the corresponding session process in the target remote equipment based on the session connection request, the session identification and the corresponding process identification on the corresponding target remote equipment.
5. The method of claim 4, wherein the establishing a session connection with a corresponding session process in a target remote device based on the session connection request and the session identifier and a corresponding process identifier on the corresponding target remote device comprises:
comparing the session identifier and the corresponding process identifier on the corresponding target remote device with the session identifier and the corresponding process identifier in the session connection request,
and when the comparison result is consistent, establishing session connection with the corresponding session process in the target remote equipment.
6. A method for transmitting operation data at a management device, wherein the method comprises:
establishing a session, synchronizing the session to corresponding gateway equipment, and informing corresponding target remote equipment to establish session connection with the gateway equipment based on the session connection state fed back by the gateway equipment according to the session;
receiving a gateway request sent by peripheral equipment based on the received operation instruction under the session, wherein the operation instruction is an operation instruction sent to target remote equipment by user equipment;
notifying the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request.
7. The method of claim 6, wherein the session comprises a session identification, the corresponding target remote device, and a corresponding process identification on the target remote device.
8. The method of claim 7, wherein the notifying the corresponding target remote device of establishing the session connection with the gateway device based on the session connection state fed back by the gateway device according to the session comprises:
receiving an unconnected notification corresponding to the state that the target remote device corresponding to the session and the gateway device are not connected, wherein the unconnected notification is fed back by the gateway device based on the session identifier and a corresponding process identifier on a corresponding target remote device;
and based on the unconnected notification, notifying the target remote equipment to start a session process corresponding to the process identification, wherein the session process sends a session connection request to the gateway equipment.
9. The method of claim 8, wherein the management device comprises a local master node and a local slave node, and receiving an unconnected notification corresponding to a state where the target remote device corresponding to the session and the gateway device do not establish a connection, fed back by the gateway device based on the session identifier and a corresponding process identifier on a corresponding target remote device comprises:
receiving the non-connection notification through a local master node, and sending the non-connection notification to a local slave node;
based on the unconnected notification, notifying the target remote device to start a session process corresponding to the process identifier and send a session connection request to the gateway device, including:
and notifying a target remote device to start a session process corresponding to the process identification to send a session connection request to the gateway device through the local slave node based on the unconnected notification.
10. The method of claim 9, wherein prior to notifying the corresponding target remote device to establish a session connection with the gateway device, further comprising:
a long connection is established with the target remote device.
11. The method of claim 10, wherein the establishing a long connection with a target remote device comprises:
establishing a long connection with the target remote device through a local slave node.
12. A method for transmitting operation data at a target remote device, wherein the method comprises:
judging whether a notification which is sent by the management equipment and used for establishing session connection with the corresponding gateway equipment is acquired, if so, establishing session connection with the corresponding gateway equipment based on the notification;
receiving an operation instruction under the session corresponding to the session connection, which is sent by the gateway device, wherein the operation instruction is an operation instruction sent to a target remote device by a user device;
and executing the operation instruction to obtain a corresponding operation result, and sending the operation result to the gateway equipment.
13. The method of claim 12, wherein the session comprises a session identification, the corresponding target remote device, and a corresponding process identification on the target remote device.
14. The method of claim 13, wherein determining whether to acquire a notification sent by the management device to establish a session connection with the corresponding gateway device further comprises:
and if not, acquiring the session connection which is established on the target remote equipment and corresponds to the process identification from the gateway equipment.
15. The method of claim 13, wherein the establishing a session connection with a corresponding gateway device based on the notification further comprises:
receiving a notification of establishing session connection with a corresponding gateway device, which is sent by the management device;
based on the notification, starting a session process on the target remote device corresponding to the process identifier, wherein the session process sends a session connection request to the gateway device;
and establishing session connection with the gateway equipment based on the acceptance feedback of the session connection request received by the gateway equipment.
16. The method of claim 15, wherein the receiving the notification sent by the management device to establish the session connection with the corresponding gateway device comprises:
and receiving a notice that the management device establishes session connection with the corresponding gateway device through a local slave node.
17. The method according to claim 16, wherein the determining whether to acquire a notification sent by the management device to establish the session connection with the corresponding gateway device, and if so, before establishing the session connection with the corresponding gateway device based on the notification, further includes:
a long connection is established with the management device.
18. The method of claim 17, wherein the establishing a long connection with a management device comprises:
a long connection is established with a local slave node in the management device.
19. A method of transmitting operation data at a peripheral device, wherein the method comprises:
sending a gateway request to a management device based on an operation instruction under the same session sent by a user device, wherein the session is a session between the gateway device and a target remote device;
receiving the gateway request returned by the management equipment based on the corresponding gateway equipment;
sending the operation instruction to the gateway device, and receiving an operation result sent by the gateway device based on the operation instruction, wherein the gateway device receives and records the operation instruction under the session sent by the peripheral device, and sends the operation instruction to the target remote device, so that the target remote device executes the operation instruction to obtain a corresponding operation result, and sends the operation result to the gateway device;
and sending the operation result to the user equipment.
20. The method of claim 19, wherein the session comprises a session identification, a corresponding process identification, and a corresponding target remote device.
21. A gateway device for transmitting operational data, wherein the gateway device comprises:
the session connection device is used for acquiring a session synchronized by the management equipment and establishing session connection with the corresponding target remote equipment based on the session;
the issuing device is used for receiving and recording the operation instruction under the session sent by the peripheral equipment and sending the operation instruction to the target remote equipment, wherein the operation instruction is the operation instruction sent to the target remote equipment by the user equipment;
and the reporting device is used for receiving and recording an operation result returned by the target remote equipment based on the operation instruction, and sending the operation result to the peripheral equipment.
22. The gateway device of claim 21, wherein the session comprises a session identification, the corresponding target remote device, and a corresponding process identification on the target remote device.
23. The gateway device of claim 22, wherein the session connection means is configured to:
acquiring a session synchronized by a management device;
judging whether the target remote equipment corresponding to the session establishes session connection or not based on the session identification and the corresponding process identification on the corresponding target remote equipment;
and if so, acquiring the established session connection on the target remote equipment corresponding to the process identification.
24. The gateway device of claim 23, wherein the session connection means is configured to:
if not, sending an unconnected notification corresponding to the session to the management device, so that the management device is ready to send the unconnected notification to the target remote device;
acquiring a session connection request sent by the target remote equipment based on the received unconnected notification;
and establishing session connection with the corresponding session process in the target remote equipment based on the session connection request, the session identification and the corresponding process identification on the corresponding target remote equipment.
25. The gateway device of claim 24, wherein the session connection means is for:
comparing the session identifier and the corresponding process identifier on the corresponding target remote device with the session identifier and the corresponding process identifier in the session connection request,
and when the comparison result is consistent, establishing session connection with the corresponding session process in the target remote equipment.
26. A management apparatus that transmits operation data, wherein the management apparatus comprises:
a session establishing device, configured to establish a session, synchronize the session to a corresponding gateway device, and notify, based on a session connection state fed back by the gateway device according to the session, a corresponding target remote device to establish a session connection with the gateway device;
receiving means, configured to receive a gateway request sent by a peripheral device based on a received operation instruction under the session, where the operation instruction is an operation instruction sent by a user equipment to a target remote device;
a notification device, configured to notify the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request.
27. The management device of claim 26, wherein the session includes a session identification, the corresponding target remote device, and a corresponding process identification on the target remote device.
28. The management device of claim 27, wherein the establish session means is to:
receiving an unconnected notification corresponding to the state that the target remote device corresponding to the session and the gateway device are not connected, wherein the unconnected notification is fed back by the gateway device based on the session identifier and a corresponding process identifier on a corresponding target remote device;
and based on the unconnected notification, notifying the target remote equipment to start a session process corresponding to the process identification, wherein the session process sends a session connection request to the gateway equipment.
29. The management device of claim 28, wherein the management device comprises a local master node and a local slave node, and the means for establishing a session is configured to:
receiving the non-connection notification through a local master node, and sending the non-connection notification to a local slave node;
and notifying a target remote device to start a session process corresponding to the process identification to send a session connection request to the gateway device through the local slave node based on the unconnected notification.
30. The management device of claim 29, wherein the establish session means is further for:
a long connection is established with the target remote device.
31. The management device of claim 30, wherein the establish session means is to:
establishing a long connection with the target remote device through a local slave node.
32. A target remote device that transmits operational data, wherein the target remote device comprises:
the connection establishing device is used for judging whether a notification which is sent by the management equipment and establishes session connection with the corresponding gateway equipment is acquired, and if so, the session connection is established with the corresponding gateway equipment based on the notification;
the instruction receiving device is used for receiving an operation instruction under the session corresponding to the session connection, which is sent by the gateway device, wherein the operation instruction is an operation instruction sent to a target remote device by user equipment;
and the execution sending device is used for executing the operation instruction to obtain a corresponding operation result and sending the operation result to the gateway equipment.
33. The target remote device of claim 32, wherein the session comprises a session identification, the corresponding target remote device, and a corresponding process identification on the target remote device.
34. The target remote device of claim 33, wherein the means for establishing a connection is further for:
and if not, acquiring the session connection which is established on the target remote equipment and corresponds to the process identification from the gateway equipment.
35. The target remote device of claim 33, wherein the means for establishing a connection is further for:
receiving a notification of establishing session connection with a corresponding gateway device, which is sent by the management device;
based on the notification, starting a session process on the target remote device corresponding to the process identifier, wherein the session process sends a session connection request to the gateway device;
and establishing session connection with the gateway equipment based on the acceptance feedback of the session connection request received by the gateway equipment.
36. The target remote device of claim 35, wherein the means for establishing a connection is configured to:
and receiving a notice that the management device establishes session connection with the corresponding gateway device through a local slave node.
37. The target remote device of claim 36, wherein the means for establishing a connection is further for:
a long connection is established with the management device.
38. The target remote device of claim 37, wherein the means for establishing a connection is configured to:
a long connection is established with a local slave node in the management device.
39. A peripheral device for transferring operational data, wherein the peripheral device comprises:
the request device is used for sending a gateway request to the management equipment based on an operation instruction under the same session sent by the user equipment, wherein the session is a session between the gateway equipment and the target remote equipment;
the return device is used for receiving the gateway request returned by the management equipment to the corresponding gateway equipment;
the forwarding device is used for sending the operation instruction to the gateway equipment and receiving an operation result sent by the gateway equipment based on the operation instruction, wherein the gateway equipment receives and records the operation instruction under the session sent by the peripheral equipment and sends the operation instruction to the target remote equipment so that the target remote equipment executes the operation instruction to obtain a corresponding operation result, and the operation result is sent to the gateway equipment;
and the operation result sending device is used for sending the operation result to the user equipment.
40. The peripheral device of claim 39, wherein the session comprises a session identification, a corresponding process identification, and a corresponding target remote device.
41. A computing-based device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
acquiring a session synchronized by a management device, and establishing session connection with a corresponding target remote device based on the session;
receiving and recording an operation instruction under the session sent by the peripheral equipment, and sending the operation instruction to the target remote equipment, wherein the operation instruction is an operation instruction sent to the target remote equipment by the user equipment;
and receiving and recording an operation result returned by the target remote equipment based on the operation instruction, and sending the operation result to the peripheral equipment.
42. A computing-based device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
establishing a session, synchronizing the session to corresponding gateway equipment, and informing corresponding target remote equipment to establish session connection with the gateway equipment based on the session connection state fed back by the gateway equipment according to the session;
receiving a gateway request sent by peripheral equipment based on the received operation instruction under the session, wherein the operation instruction is an operation instruction sent to target remote equipment by user equipment;
notifying the peripheral device of the corresponding gateway device of the session synchronization based on the gateway request.
43. A computing-based device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
judging whether a notification which is sent by the management equipment and used for establishing session connection with the corresponding gateway equipment is acquired, if so, establishing session connection with the corresponding gateway equipment based on the notification;
receiving an operation instruction under the session corresponding to the session connection, which is sent by the gateway device, wherein the operation instruction is an operation instruction sent to a target remote device by a user device;
and executing the operation instruction to obtain a corresponding operation result, and sending the operation result to the gateway equipment.
44. A computing-based device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to:
sending a gateway request to a management device based on an operation instruction under the same session sent by a user device, wherein the session is a session between the gateway device and a target remote device;
receiving the gateway request returned by the management equipment based on the corresponding gateway equipment;
sending the operation instruction to the gateway device, and receiving an operation result sent by the gateway device based on the operation instruction, wherein the gateway device receives and records the operation instruction under the session sent by the peripheral device, and sends the operation instruction to the target remote device, so that the target remote device executes the operation instruction to obtain a corresponding operation result, and sends the operation result to the gateway device;
and sending the operation result to the user equipment.
CN201710057119.6A 2017-01-23 2017-01-23 Method and equipment for transmitting operation data Active CN108347462B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201710057119.6A CN108347462B (en) 2017-01-23 2017-01-23 Method and equipment for transmitting operation data

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201710057119.6A CN108347462B (en) 2017-01-23 2017-01-23 Method and equipment for transmitting operation data

Publications (2)

Publication Number Publication Date
CN108347462A CN108347462A (en) 2018-07-31
CN108347462B true CN108347462B (en) 2021-02-23

Family

ID=62961901

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201710057119.6A Active CN108347462B (en) 2017-01-23 2017-01-23 Method and equipment for transmitting operation data

Country Status (1)

Country Link
CN (1) CN108347462B (en)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110011910B (en) * 2019-04-08 2022-01-18 陈鹏 Gateway communication system and gateway communication method supporting multi-protocol device access
CN113905080A (en) * 2021-09-27 2022-01-07 深信服科技股份有限公司 Management method, device, system and storage medium

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7506368B1 (en) * 2003-02-13 2009-03-17 Cisco Technology, Inc. Methods and apparatus for network communications via a transparent security proxy
CN102045375A (en) * 2009-10-22 2011-05-04 华为技术有限公司 Remote command interaction method and bastion host
CN103283209A (en) * 2011-04-18 2013-09-04 北京新媒传信科技有限公司 Application service platform system and implementation method thereof
CN105337756A (en) * 2014-08-13 2016-02-17 中兴通讯股份有限公司 Centralized operation and maintenance method and device
CN106230877A (en) * 2016-06-30 2016-12-14 宁波翼动通讯科技有限公司 The method for remote management of a kind of equipment, system and equipment

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7684432B2 (en) * 2003-05-15 2010-03-23 At&T Intellectual Property I, L.P. Methods of providing data services over data networks and related data networks, data service providers, routing gateways and computer program products
CN100574207C (en) * 2004-02-03 2009-12-23 华为技术有限公司 The method of a kind of Operation and Maintenance client and remote equipment direct communication
US7903671B2 (en) * 2005-08-04 2011-03-08 Cisco Technology, Inc. Service for NAT traversal using IPSEC
US9385918B2 (en) * 2012-04-30 2016-07-05 Cisco Technology, Inc. System and method for secure provisioning of virtualized images in a network environment

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7506368B1 (en) * 2003-02-13 2009-03-17 Cisco Technology, Inc. Methods and apparatus for network communications via a transparent security proxy
CN102045375A (en) * 2009-10-22 2011-05-04 华为技术有限公司 Remote command interaction method and bastion host
CN103283209A (en) * 2011-04-18 2013-09-04 北京新媒传信科技有限公司 Application service platform system and implementation method thereof
CN105337756A (en) * 2014-08-13 2016-02-17 中兴通讯股份有限公司 Centralized operation and maintenance method and device
CN106230877A (en) * 2016-06-30 2016-12-14 宁波翼动通讯科技有限公司 The method for remote management of a kind of equipment, system and equipment

Also Published As

Publication number Publication date
CN108347462A (en) 2018-07-31

Similar Documents

Publication Publication Date Title
JP6386069B2 (en) Connection management method, apparatus, electronic equipment, program, and recording medium
KR102167613B1 (en) Message push method and device
WO2021238990A1 (en) Authentication method and apparatus, electronic device, server, program, and storage medium
WO2019144832A1 (en) Device connection method, device and system
CN110677383B (en) Firewall wall opening method and device, storage medium and computer equipment
WO2015154246A1 (en) Fault handling method, device and system based on network function virtualization
CN112800129B (en) Block state updating method, device, system and electronic equipment
US20140032173A1 (en) Information processing apparatus, and monitoring method
US20170373939A1 (en) Data uploading method, apparatus, and system
CN106911648B (en) Environment isolation method and equipment
CN109547524B (en) User behavior storage method, device, equipment and storage medium based on Internet of things
JP2001520777A (en) Interface for interfacing a client program to a network device in a telecommunications network
CN108347462B (en) Method and equipment for transmitting operation data
CN112769652A (en) Node service monitoring method, device, equipment and medium
CN108347449B (en) Method and equipment for managing remote login
CN102739446B (en) The method and apparatus for selecting Network Time Protocol server
KR101395830B1 (en) Session checking system via proxy and checkhing method thereof
KR102567900B1 (en) Method and Apparatus for Ensuring Continuous Device Operational Stability in Cloud Degraded Mode
WO2016091141A1 (en) Method and apparatus for information collection
CN111327447A (en) Distributed system, arbitration method, node device and storage medium
WO2019001562A1 (en) Model loading method and apparatus, storage medium, and computer device
CN111490997B (en) Task processing method, proxy system, service system and electronic equipment
JP6511218B2 (en) INFORMATION PROCESSING SYSTEM, TERMINAL DEVICE, AND INFORMATION PROCESSING METHOD
JP2018113493A (en) Client device, system, information processing method and program
CN103457771A (en) Method and device for HA virtual machine cluster management

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant