Interactive session implementation methods, apparatus, devices, and computer-readable storage media
By creating a multi-session management agent component in the Windows Server operating system and modifying the system configuration, the complexity of RDP servers and protocols is bypassed, solving the problems of difficult RDP server maintenance and high development costs, and realizing controllable and maintainable interactive session creation.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- WUHAN OPENKER COMPUTING
- Filing Date
- 2026-03-31
- Publication Date
- 2026-07-03
AI Technical Summary
In existing technologies, RDP servers on the Windows Server operating system cannot be directly repaired, and the RDP protocol is complex, resulting in poor maintainability and high development costs.
By creating a multi-session management agent component and modifying the system configuration to load the component at startup, the client connection processing and authentication flow is migrated to a third-party component, bypassing the native RDP server and complex RDP protocol.
It achieves high controllability and maintainability, reduces development difficulty and cost, and provides a foundation for customizable interactive session creation.
Smart Images
Figure CN122332008A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, specifically to an interactive session implementation method, apparatus, device, and computer-readable storage medium. Background Technology
[0002] The Windows Server operating system supports multiple concurrent interactive sessions through its integrated Remote Desktop Services (RDS). This means that multiple remote users can log in to the same server simultaneously, each with their own independent desktop environment, process space, and memory area, running in isolation. This feature enables the server to act as a terminal server, achieving centralized utilization and multi-user sharing of computing resources.
[0003] The conventional way to implement multiple sessions is by relying on the Remote Desktop Protocol (RDP) server component in RDS. When a user initiates a connection request through a remote desktop client, the RDP server running on Windows Server listens for the request, assigns a unique session ID to each authenticated user, and starts a separate RDP protocol stack instance to handle the data transmission for that session. The RDP protocol is responsible for compressing and encrypting the desktop output of that specific session before pushing it to the remote client, while also receiving and transmitting keyboard and mouse operations from the client.
[0004] However, the above solution has the following drawbacks: First, the RDP server is fully integrated into the Windows operating system, and Microsoft has not provided its source code. When the RDP server encounters problems, developers cannot directly fix them; they can only manually work around the issue or wait for system updates, resulting in poor maintainability and controllability.
[0005] Secondly, the RDP protocol itself is extremely complex, and the cost of learning and fully implementing it is very high. Even the official RDP documentation provided by Microsoft may contain errors and omissions, further increasing the difficulty of custom development based on RDP. Summary of the Invention
[0006] This application provides an interactive session implementation method, apparatus, device, and computer-readable storage medium that can bypass the dependence on native RDP servers and the complex implementation of RDP protocols, and realize interactive session creation under the Windows Server system in a customizable and maintainable manner.
[0007] In a first aspect, embodiments of this application provide an interactive session implementation method, the interactive session implementation method comprising: When the operating system's built-in remote desktop service starts, it loads the multi-session management agent component and calls the interface provided by the multi-session management agent component so that the multi-session management agent component can establish a communication connection with the client. The multi-session management agent component receives user identity credentials sent by the client through the communication connection and calls the login interface of the remote desktop service to create an interactive session.
[0008] In conjunction with the first aspect, in one implementation, after invoking the login interface of the remote desktop service to create an interactive session, the method further includes: Remote desktop interaction is achieved by capturing the desktop image of the interactive session and sending it to the client for display.
[0009] In conjunction with the first aspect, in one implementation, before loading the multi-session management agent component when the remote desktop service built into the operating system starts, the method further includes: Create a multi-session management agent component; Register the multi-session management agent component with the operating system; Modify the configuration information of the operating system's built-in Remote Desktop service to enable the Remote Desktop service to load the multi-session management agent component at startup.
[0010] In conjunction with the first aspect, in one implementation, modifying the configuration information of the operating system's built-in remote desktop service includes: Write a unique identifier for the multi-session management agent component into the registry corresponding to the remote desktop service built into the operating system, so that the remote desktop service can locate and load the multi-session management agent component based on the unique identifier when it starts.
[0011] In conjunction with the first aspect, in one implementation, the step of invoking the interface provided by the multi-session management proxy component to establish a communication connection between the multi-session management proxy component and the client includes: Call the listening interface provided by the multi-session management agent component to start the listener; The multi-session management agent component receives connection requests from clients through the listener and establishes a communication connection with the clients.
[0012] In conjunction with the first aspect, in one implementation, the multi-session management agent component receives user identity credentials sent by the client through the communication connection and invokes the login interface of the remote desktop service to create an interactive session, including: The multi-session management agent component uses the user identity credentials received through the communication connection as parameters to call the login interface of the remote desktop service; In response to the call to the login interface, the remote desktop service requests the network information of the client from the multi-session management agent component; In response to requests from the Remote Desktop Service, the Multi Session Management Agent component provides the Remote Desktop Service with the client's network information; After receiving the network information, the remote desktop service creates an interactive session and returns the identification information of the created interactive session to the multi-session management agent component; After the remote desktop service returns the identification information, it sends a login query to the multi-session management agent component; In response to the login prompt, the multi-session management agent component returns an indication that login is allowed; Upon receiving the permission to log in, the remote desktop service completes the session login process and returns an interactive session login notification to the multi-session management agent component.
[0013] In conjunction with the first aspect, in one implementation, the operating system is a Windows Server operating system, and the multi-session management agent component is a COM component.
[0014] Secondly, embodiments of this application provide an interactive session implementation apparatus, the interactive session implementation apparatus comprising: The loading module is used to load the multi-session management agent component when the remote desktop service built into the operating system starts, and to call the interface provided by the multi-session management agent component so that the multi-session management agent component can establish a communication connection with the client. A module is created to receive user credentials sent by the client via the communication connection through the multi-session management agent component, and to call the login interface of the remote desktop service to create an interactive session.
[0015] Thirdly, embodiments of this application provide an interactive session implementation device, the interactive session implementation device including a processor, a memory, and an interactive session implementation program stored in the memory and executable by the processor, wherein when the interactive session implementation program is executed by the processor, it implements the steps of the interactive session implementation method as described in the first aspect.
[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing an interactive session implementation program, wherein when the interactive session implementation program is executed by a processor, it implements the steps of the interactive session implementation method as described in the first aspect.
[0017] The beneficial effects of the technical solutions provided in this application include: In this embodiment, by creating an independent multi-session management proxy component and modifying the system configuration to load this component into the native remote desktop service, the client connection processing and authentication flow is successfully migrated from the internal system to a customizable third-party component. This method directly solves the maintenance difficulties caused by the inability to modify the native RDP server in existing technologies, as well as the high development costs caused by the complexity of the RDP protocol. It eliminates the need to understand and implement the complex RDP protocol; it only requires the proxy component to receive credentials and call the standard login interface to trigger the creation of an interactive session at the system level, providing a foundation for subsequent remote desktop interaction and exhibiting high controllability and maintainability. Attached Figure Description
[0018] Figure 1 This is a flowchart illustrating an embodiment of the interactive session implementation method of this application; Figure 2 This is a schematic diagram of a scenario from one embodiment of the interactive session implementation method of this application; Figure 3 This is a schematic diagram of the functional modules of an embodiment of the interactive session implementation device of this application; Figure 4 This is a schematic diagram of the hardware structure of the interactive session implementation device involved in the embodiments of this application. Detailed Implementation
[0019] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.
[0020] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.
[0021] Firstly, embodiments of this application provide an interactive session implementation method.
[0022] In one embodiment, reference is made to Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the interactive session implementation method of this application. Figure 1 As shown, the interactive session implementation methods include: Step S10: When the remote desktop service built into the operating system starts, it loads the multi-session management agent component and calls the interface provided by the multi-session management agent component so that the multi-session management agent component can establish a communication connection with the client. In this embodiment, the operating system is a Windows Server operating system, and the multi-session management agent component is a COM component.
[0023] Furthermore, in one embodiment, before step S10, the method further includes: Create a multi-session management agent component; register the multi-session management agent component with the operating system; modify the configuration information of the remote desktop service that comes with the operating system so that the remote desktop service loads the multi-session management agent component when it starts up.
[0024] In this embodiment, the developer needs to create a multi-session management agent component, which is a COM component DLL file that implements a specific interface.
[0025] Subsequently, the DLL file of the COM component is registered in the system registry using a registration command provided by the Windows system (such as regsvr32), making it a COM component that the system can recognize and call.
[0026] Next, the configuration information of the operating system's built-in Remote Desktop Services (RDS) needs to be modified so that the Remote Desktop Services loads the multi-session management agent component at startup. Furthermore, in one embodiment, modifying the configuration information of the remote desktop service built into the operating system includes: Write a unique identifier for the multi-session management agent component into the registry corresponding to the remote desktop service built into the operating system, so that the remote desktop service can locate and load the multi-session management agent component based on the unique identifier when it starts.
[0027] In this embodiment, a unique identifier (UUID, Universally Unique Identifier) for the multi-session management agent component is written into the system registry key corresponding to the RDS service. After this configuration, the next time the RDS service starts, it will locate and load the DLL file of the COM component from the registry based on this UUID, thereby injecting the custom agent component into the process space of the RDS service.
[0028] Furthermore, in one embodiment, the step of invoking the interface provided by the multi-session management proxy component to establish a communication connection between the multi-session management proxy component and the client includes: Call the listening interface provided by the multi-session management agent component to start the listener; The multi-session management agent component receives connection requests from clients through the listener and establishes a communication connection with the clients.
[0029] In this embodiment, after the RDS service successfully loads the multi-session management agent component, it calls the interface provided by the multi-session management agent component according to a preset process. Specifically, the RDS service calls a listening interface exposed by the multi-session management agent component. This call to the listening interface instructs the multi-session management agent component to start a listener, for example, to perform TCP listening on a predefined port (such as 12345).
[0030] After the listener starts, it enters a waiting state. When a client program (which needs to be developed separately to replace the standard RDP client) initiates a connection request, the listener of the multi-session management proxy component will receive the request and successfully establish a TCP communication connection with the client. At this point, the channel for subsequent data transmission is ready.
[0031] In step S20, the multi-session management agent component receives the user identity credentials sent by the client through the communication connection and calls the login interface of the remote desktop service to create an interactive session.
[0032] In this embodiment, after the connection is established, the client program sends the user's identity credentials (i.e., username and password) to the multi-session management agent component through the established TCP communication connection. After receiving the credentials, the multi-session management agent component begins to operate its core functions, performing a series of sophisticated interactions with the RDS service to complete the creation of an interactive session.
[0033] Further, in one embodiment, step S20 includes: The multi-session management agent component uses the user identity credentials received through the communication connection as parameters to call the login interface of the remote desktop service; In response to the call to the login interface, the remote desktop service requests the network information of the client from the multi-session management agent component; In response to requests from the Remote Desktop Service, the Multi Session Management Agent component provides the Remote Desktop Service with the client's network information; After receiving the network information, the remote desktop service creates an interactive session and returns the identification information of the created interactive session to the multi-session management agent component; After the remote desktop service returns the identification information, it sends a login query to the multi-session management agent component; In response to the login prompt, the multi-session management agent component returns an indication that login is allowed; Upon receiving the permission to log in, the remote desktop service completes the session login process and returns an interactive session login notification to the multi-session management agent component.
[0034] In this embodiment, the process for creating an interactive session is as follows: The multi-session management agent component takes the received username and password as parameters, calls the login interface provided by the RDS service, and requests the system to create a new interactive session.
[0035] In response to the login interface call, the RDS service requests network information from the multi-session management agent component, such as the client's IP address and computer name. The agent component responds to this request by providing the relevant information to the RDS service. This information is then logged by the RDS service and displayed in management tools such as Windows Server Task Manager for session identification and monitoring.
[0036] After receiving and recording the client information, the RDS service allocates system resources and initializes the session data structure at the underlying level, formally creating a new interactive session. Once created, the RDS service returns the session's unique identifier (session ID) to the multi-session management agent component.
[0037] After receiving the session ID, the RDS service sends a login query to the multi-session management agent component, which is equivalent to a final security checkpoint, asking whether the user is allowed to finally access their desktop.
[0038] The multi-session management agent component responds to this query by returning an "Allow login" instruction to the RDS service.
[0039] After receiving the login permission instruction, the RDS service performs the final login cleanup, switching the user to the newly created session, at which point the user can see the desktop. Finally, the RDS service returns a "Interactive session login complete" notification to the multi-session management agent component, marking the successful completion of the entire session creation and login process.
[0040] In this embodiment, by creating an independent multi-session management proxy component and modifying the system configuration to load this component into the native remote desktop service, the client connection processing and authentication flow is successfully migrated from the internal system to a customizable third-party component. This method directly solves the maintenance difficulties caused by the inability to modify the native RDP server in existing technologies, as well as the high development costs caused by the complexity of the RDP protocol. It eliminates the need to understand and implement the complex RDP protocol; it only requires the proxy component to receive credentials and call the standard login interface to trigger the creation of an interactive session at the system level, providing a foundation for subsequent remote desktop interaction and exhibiting high controllability and maintainability.
[0041] Furthermore, in one embodiment, after step S20, the method further includes: Remote desktop interaction is achieved by capturing the desktop image of the interactive session and sending it to the client for display.
[0042] In this embodiment, after the interactive session is created and logged in, the remote user needs to see the desktop and perform operations. At this point, the complex RDP protocol is no longer relied upon.
[0043] The server can run a standalone screenshot program, or the multi-session management agent component can call relevant system APIs to periodically or event-wise capture desktop images of the interactive session. The captured images, after necessary encoding and compression, are sent to the client via an established TCP communication connection (or a newly established dedicated data channel).
[0044] After receiving the image data, the client program decodes it and displays it on the user interface. Simultaneously, the client's keyboard and mouse actions can be captured and transmitted back to the server via a TCP connection. The server-side program then simulates this input into the corresponding session, thus achieving complete remote desktop interaction.
[0045] In a preferred embodiment, the image capture program can employ differential imaging technology to capture only the changing areas of the screen for encoding and transmission, thereby reducing network bandwidth consumption. The client program is then responsible for stitching the received image blocks together to create a complete desktop display.
[0046] Furthermore, in one embodiment, reference is made to Figure 2 , Figure 2 This is a schematic diagram illustrating a scenario of one embodiment of the interactive session implementation method of this application. For example... Figure 2 As shown, the timing sequence in this scenario is as follows: Implement a Windows COM component called OE-RDS Server (i.e., the multi-session management agent component mentioned earlier). Register the OE-RDS Server with the operating system using the regsve32 command; Modify the registry of the RDS Service service and write the UUID of the OE-RDSServer component; The next time the RDS Service starts, it will load the OE-RDS Server's DLL via UUID; The RDS Service calls the OE-RDS Server's initialization interface; The RDS Service calls the OE-RDS Server's listening interface. The listener listens on port number 12345 so that it can start listening for incoming connections. Implement a standalone program called OE-RDS Client, which connects to port 12345 of the OE-RDS Server via TCP and sends the Windows username and password to the OE-RDS Server; After receiving the username and password from the OE-RDS Client, the OE-RDS Server calls the RDS Service's user login interface and passes the username and password parameters to this interface. The RDS Service calls the OE-RDS interface to request information such as the client's IP address and computer name, which will be displayed in the Windows Server Task Manager. The RDS Service has notified you that an interactive session ID has been created. The RDS Service calls the OE-RDS interface to ask whether login is allowed, and OE-RDS returns that login is allowed. The RDS Service notifies the OE-RDS interactive session that login has been completed, and the interactive session has now entered the desktop. The interactive session is now ready. You can use a screenshot program to send the image of the current session to the remote end, thus achieving a remote desktop effect.
[0047] Secondly, embodiments of this application also provide an interactive session implementation device.
[0048] In one embodiment, reference is made to Figure 3 , Figure 3 This is a schematic diagram of the functional modules of an embodiment of the interactive session implementation device of this application. Figure 3 As shown, the interactive session implementation device includes: The loading module 10 is used to load the multi-session management agent component when the remote desktop service built into the operating system starts, and to call the interface provided by the multi-session management agent component so that the multi-session management agent component can establish a communication connection with the client. Module 20 is created to receive user identity credentials sent by the client via the communication connection through the multi-session management agent component, and to call the login interface of the remote desktop service to create an interactive session.
[0049] Furthermore, in one embodiment, the interactive session implementation apparatus further includes a capture module, used for: Remote desktop interaction is achieved by capturing the desktop image of the interactive session and sending it to the client for display.
[0050] Furthermore, in one embodiment, the interactive session implementation apparatus further includes a deployment module for: Create a multi-session management agent component; Register the multi-session management agent component with the operating system; Modify the configuration information of the operating system's built-in Remote Desktop service to enable the Remote Desktop service to load the multi-session management agent component at startup.
[0051] Furthermore, in one embodiment, the deployment module is used for: Write a unique identifier for the multi-session management agent component into the registry corresponding to the remote desktop service built into the operating system, so that the remote desktop service can locate and load the multi-session management agent component based on the unique identifier when it starts.
[0052] Furthermore, in one embodiment, the loading module 10 is used for: Call the listening interface provided by the multi-session management agent component to start the listener; The multi-session management agent component receives connection requests from clients via the listener and establishes a communication connection with the clients.
[0053] Furthermore, in one embodiment, a creation module 20 is used for: The multi-session management agent component uses the user identity credentials received through the communication connection as parameters to call the login interface of the remote desktop service; In response to the login interface call via the remote desktop service, a request is made to the multi-session management agent component to obtain the client's network information; The multi-session management agent component responds to requests from the remote desktop service by providing the remote desktop service with the client's network information; After receiving the network information through the remote desktop service, an interactive session is created, and the identification information of the created interactive session is returned to the multi-session management agent component; After returning the identification information via the remote desktop service, a login query is sent to the multi-session management agent component; The multi-session management agent component responds to the login request and returns an indication that login is allowed. Upon receiving the permission to log in, the remote desktop service completes the session login process and returns an interactive session login notification to the multi-session management agent component.
[0054] Furthermore, in one embodiment, the operating system is a Windows Server operating system, and the multi-session management agent component is a COM component.
[0055] The functions of each module in the above-mentioned interactive session implementation device correspond to the steps in the above-mentioned interactive session implementation method embodiment, and their functions and implementation processes will not be described in detail here.
[0056] Thirdly, embodiments of this application provide an interactive session implementation device, which can be a personal computer (PC), laptop computer, server, or other device with data processing capabilities.
[0057] Reference Figure 4 , Figure 4 This is a schematic diagram of the hardware structure of the interactive session implementation device involved in the embodiments of this application. In the embodiments of this application, the interactive session implementation device may include a processor, a memory, a communication interface, and a communication bus.
[0058] The communication bus can be of any type and is used to interconnect the processor, memory, and communication interface.
[0059] Communication interfaces include input / output (I / O) interfaces, physical interfaces, and logical interfaces used for interconnecting internal devices within an interactive session implementation device, as well as interfaces used for interconnecting the interactive session implementation device with other devices (such as other computing devices or user equipment). Physical interfaces can be Ethernet interfaces, fiber optic interfaces, ATM interfaces, etc.; user equipment can be displays, keyboards, etc.
[0060] Memory can be various types of storage media, such as random access memory (RAM), read-only memory (ROM), non-volatile RAM (NVRAM), flash memory, optical storage, hard disk, programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), etc.
[0061] The processor can be a general-purpose processor, which can call the interactive session implementation program stored in memory and execute the interactive session implementation method provided in the embodiments of this application. For example, the general-purpose processor can be a central processing unit (CPU). The method executed when the interactive session implementation program is called can be referred to in the various embodiments of the interactive session implementation method of this application, and will not be repeated here.
[0062] Those skilled in the art will understand that Figure 4 The hardware structure shown does not constitute a limitation of this application and may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0063] Fourthly, embodiments of this application also provide a computer-readable storage medium.
[0064] The present application provides a computer-readable storage medium storing an interactive session implementation program, wherein when the interactive session implementation program is executed by a processor, it implements the steps of the interactive session implementation method described above.
[0065] The method implemented when the interactive session implementation program is executed can be referred to in various embodiments of the interactive session implementation method of this application, and will not be repeated here.
[0066] It should be noted that the sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0067] The terms "comprising" and "having," and any variations thereof, in the specification, claims, and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus. The terms "first," "second," and "third," etc., are used to distinguish different objects, etc., and do not indicate a sequence, nor do they limit "first," "second," and "third" to different types.
[0068] In the description of the embodiments of this application, terms such as "exemplary," "for example," or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplary," "for example," or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary," "for example," or "for instance" is intended to present the relevant concepts in a concrete manner.
[0069] In the description of the embodiments of this application, unless otherwise stated, " / " means "or". For example, A / B can mean A or B. The "and / or" in the text is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more.
[0070] In some processes described in the embodiments of this application, multiple operations or steps are included in a specific order. However, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or they may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.
[0071] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device to execute the methods described in the various embodiments of this application.
[0072] The above are merely preferred embodiments of this application and do not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.
Claims
1. An interactive session implementation method, characterized by, The interactive session implementation method includes: When the operating system's built-in remote desktop service starts, it loads the multi-session management agent component and calls the interface provided by the multi-session management agent component so that the multi-session management agent component can establish a communication connection with the client. The multi-session management agent component receives user identity credentials sent by the client through the communication connection and calls the login interface of the remote desktop service to create an interactive session.
2. The interactive session implementation method of claim 1, wherein, Following the invocation of the remote desktop service's login interface to create an interactive session, the following is also included: Remote desktop interaction is achieved by capturing the desktop image of the interactive session and sending it to the client for display.
3. The interactive session implementation method of claim 1, wherein, Before loading the multi-session management agent component when the remote desktop service built into the operating system starts, it also includes: Create a multi-session management agent component; Register the multi-session management agent component with the operating system; Modify the configuration information of the operating system's built-in Remote Desktop service to enable the Remote Desktop service to load the multi-session management agent component at startup.
4. The interactive session implementation method of claim 3, wherein, The modification of the configuration information of the operating system's built-in remote desktop service includes: Write a unique identifier for the multi-session management agent component into the registry corresponding to the remote desktop service built into the operating system, so that the remote desktop service can locate and load the multi-session management agent component based on the unique identifier when it starts.
5. The interactive session implementation method of claim 1, wherein, The step of calling the interface provided by the multi-session management proxy component to establish a communication connection between the multi-session management proxy component and the client includes: Call the listening interface provided by the multi-session management agent component to start the listener; The multi-session management agent component receives connection requests from clients through the listener and establishes a communication connection with the clients.
6. The interactive session implementation method as described in claim 1, characterized in that, The multi-session management agent component receives user identity credentials sent by the client through the communication connection and calls the login interface of the remote desktop service to create an interactive session, including: The multi-session management agent component uses the user identity credentials received through the communication connection as parameters to call the login interface of the remote desktop service; In response to the call to the login interface, the remote desktop service requests the network information of the client from the multi-session management agent component; In response to requests from the Remote Desktop Service, the Multi Session Management Agent component provides the Remote Desktop Service with the client's network information; After receiving the network information, the remote desktop service creates an interactive session and returns the identification information of the created interactive session to the multi-session management agent component; After the remote desktop service returns the identification information, it sends a login query to the multi-session management agent component; In response to the login prompt, the multi-session management agent component returns an indication that login is allowed; Upon receiving the permission to log in, the remote desktop service completes the session login process and returns an interactive session login notification to the multi-session management agent component.
7. The interactive session implementation method as described in claim 1, characterized in that, The operating system is Windows Server, and the multi-session management agent component is a COM component.
8. An interactive session implementation device, characterized in that, The interactive session implementation device includes: The loading module is used to load the multi-session management agent component when the remote desktop service built into the operating system starts, and to call the interface provided by the multi-session management agent component so that the multi-session management agent component can establish a communication connection with the client. A module is created to receive user credentials sent by the client via the communication connection through the multi-session management agent component, and to call the login interface of the remote desktop service to create an interactive session.
9. An interactive session implementation device, characterized in that, The interactive session implementation device includes a processor, a memory, and an interactive session implementation program stored in the memory and executable by the processor, wherein when the interactive session implementation program is executed by the processor, it implements the steps of the interactive session implementation method as described in any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores an interactive session implementation program, wherein when the interactive session implementation program is executed by a processor, it implements the steps of the interactive session implementation method as described in any one of claims 1 to 7.