Remote desktop control methods, devices, systems and software products

By synchronizing and verifying user information in the server-side operating system and combining it with the remote desktop protocol to interact in a cross-platform environment, the problem of cross-platform adaptation of remote desktop services is solved, achieving efficient and stable remote control and a consistent operating experience.

CN123123327APending Publication Date: 2026-11-17FANGXIN TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611602373.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-10-16
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing remote desktop services cannot achieve cross-platform adaptation across different operating systems, making remote control complex.

Method used

User information is synchronized to the server operating system through a directory access protocol, user information is verified based on the operating system, and remote desktop control interaction is performed with the client in a cross-platform application runtime environment. Screen sharing and control command transmission are realized in a cross-platform environment using remote desktop sessions.

Benefits of technology

It improves the real-time performance, stability, and cross-platform compatibility of remote control, reduces the initialization complexity caused by dedicated clients and coupled links, and achieves unified access and consistent operating experience across platforms.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123327A_ABST
    Figure CN123123327A_ABST
Patent Text Reader

Abstract

This application provides a remote desktop control method, apparatus, system, and program product, relating to the field of remote desktop technology. The method includes: synchronizing at least one user information to the server's operating system based on a directory access protocol; receiving a session request sent by a client's browser, the session request carrying the client's user information; verifying the user information in the session request based on the operating system and the at least one user information; if the user information in the session request is verified successfully, creating a remote desktop session corresponding to the user information in the session request via a remote desktop protocol; and interacting with the client via remote desktop control in a cross-platform application runtime environment based on the remote desktop session. This method can improve the cross-platform adaptability of remote desktop control across different operating systems.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of remote desktop technology, and in particular to a remote desktop control method, device, system and program product. Background Technology

[0002] With the rapid development of cloud computing, mobile internet, and digital office models, efficient and secure screen sharing and real-time interaction capabilities have become core requirements for ensuring business continuity and work efficiency. Staff typically need to quickly and securely access the desktop environment of target servers or office computers through standard browsers or lightweight clients for remote desktop control.

[0003] In related technologies, the client uses Remote Desktop Protocol (RDP) to remotely control the server's desktop.

[0004] Among them, remote desktop services are developed only for a single operating system (such as Windows only or Linux only), which means that remote desktop services cannot run directly on another type of operating system, resulting in complex technical issues of cross-platform adaptation. Summary of the Invention

[0005] This application provides remote desktop control methods, devices, systems, and program products, which can improve the cross-platform adaptability of remote desktop control across different operating systems.

[0006] In a first aspect, this application provides a remote desktop control method, the method being applied to a server, the method comprising:

[0007] Based on the directory access protocol, at least one user information is synchronized to the operating system of the server.

[0008] Receive a session request sent by the client's browser, wherein the session request carries the client's user information;

[0009] Based on the operating system, the user information in the session request is verified according to the at least one user information;

[0010] If the user information in the session request is verified successfully, a remote desktop session corresponding to the user information in the session request is created using the remote desktop protocol.

[0011] Based on the remote desktop session, remote desktop control interaction is performed with the client in a cross-platform application runtime environment.

[0012] In one possible implementation, synchronizing at least one user information to the server's operating system based on a directory access protocol includes:

[0013] User records that obtain at least one user information through the directory access protocol;

[0014] Based on the Hypertext Transfer Protocol triggering mechanism, the user records of at least one user information are synchronized to the Active Directory service domain of the operating system.

[0015] In one possible implementation, the user record for obtaining the at least one user information via the directory access protocol includes:

[0016] The at least one user information is sent to the directory server via the directory access protocol; wherein the at least one user information is used by the directory server to determine the user record of the at least one user information.

[0017] User records from which at least one user information is obtained from the directory server.

[0018] In one possible implementation, the remote desktop control interaction with the client in a cross-platform application runtime environment based on the remote desktop session includes:

[0019] Start and run the local remote desktop service of the server in the cross-platform application runtime environment;

[0020] Based on the local remote desktop service, a handshake interaction is performed with the session management terminal through the application layer protocol of full-duplex communication to obtain the desktop sharing request sent by the client; wherein, the desktop sharing request is generated based on the handshake success signal sent by the session management terminal;

[0021] Establish a real-time communication (RTC) peer-to-peer connection with the client and perform remote desktop control interaction with the client based on the remote desktop session.

[0022] In one possible implementation, the handshake interaction with the session management terminal via a full-duplex communication application layer protocol to obtain the desktop sharing request sent by the client includes:

[0023] The session request is sent to the session management terminal; wherein, the session request is used to determine the signaling service port number requested by the session request;

[0024] Receive the signaling service port number sent by the session management terminal, and start the signaling service module corresponding to the signaling service port number;

[0025] Based on the signaling service module, a handshake interaction is performed with the session management terminal through the application layer protocol of full-duplex communication;

[0026] The server receives the peer node identifier from the session management terminal; simultaneously, it sends the peer node identifier from the server to the session management terminal; wherein, the peer node identifier is used by the session management terminal to generate and send a handshake success signal to the client; the handshake success signal is used by the client to generate a desktop sharing request after opening the remote desktop session page of the browser.

[0027] The signaling service module receives desktop sharing requests sent by the client.

[0028] In one possible implementation, establishing a real-time communication (RTC) peer-to-peer connection with the client and performing remote desktop control interaction with the client based on the remote desktop session includes:

[0029] Based on the screen capture component, the server sends RTC peering connection negotiation information to the client through the signaling service module; at the same time, it receives RTC peering connection negotiation information sent by the client.

[0030] Based on the RTC peer-to-peer connection negotiation information sent by the client, an RTC peer-to-peer connection is established between the screen capture component and the client's browser page;

[0031] The desktop data captured by the screen capture component is sent to the client via the RTC peer-to-peer connection channel; wherein, the desktop data is used by the client to monitor the user's desktop operation data within the remote desktop range in the browser page;

[0032] The system receives desktop operation data transmitted by the client through the RTC peer-to-peer connection channel and restores the desktop operation events corresponding to the desktop operation data.

[0033] Secondly, this application provides a remote desktop control device, which is applied to a server and includes:

[0034] A synchronization module is used to synchronize at least one user information to the operating system of the server based on a directory access protocol.

[0035] A receiving module is used to receive a session request sent by the client's browser, wherein the session request carries the client's user information;

[0036] The verification module is used to verify the user information in the session request based on the operating system and the at least one user information.

[0037] A creation module is used to create a remote desktop session corresponding to the user information in the session request through the remote desktop protocol if it is determined that the user information in the session request has been verified.

[0038] The control module is used to perform remote desktop control interaction with the client in a cross-platform application runtime environment based on the remote desktop session.

[0039] In one possible implementation, the synchronization module is specifically used to: obtain user records of the at least one user information through the directory access protocol; and synchronize the user records of the at least one user information to the Active Directory service domain of the operating system based on the Hypertext Transfer Protocol triggering mechanism.

[0040] In one possible implementation, the synchronization module is specifically used to: send the at least one user information to a directory server via the directory access protocol; wherein the at least one user information is used by the directory server to determine the user record of the at least one user information; and retrieve the user record of the at least one user information from the directory server.

[0041] In one possible implementation, the control module is specifically configured to: start and run the local remote desktop service of the server in the cross-platform application runtime environment; based on the local remote desktop service, perform a handshake interaction with the session management terminal through a full-duplex communication application layer protocol to obtain a desktop sharing request sent by the client; wherein the desktop sharing request is generated based on a handshake success signal sent by the session management terminal; establish a web real-time communication (RTC) peer connection with the client, and perform remote desktop control interaction with the client based on the remote desktop session.

[0042] In one possible implementation, the control module is specifically configured to: send the session request to the session management terminal; wherein the session request is used to determine the signaling service port number requested by the session request; receive the signaling service port number sent by the session management terminal and start the signaling service module corresponding to the signaling service port number; based on the signaling service module, perform a handshake interaction with the session management terminal through a full-duplex communication application layer protocol; receive the peer node identifier of the session management terminal; simultaneously, send the peer node identifier of the server to the session management terminal; wherein the peer node identifier is used by the session management terminal to generate and send a handshake success signal to the client; the handshake success signal is used by the client to generate a desktop sharing request after opening the remote desktop session page of the browser; and receive the desktop sharing request sent by the client through the signaling service module.

[0043] In one possible implementation, the control module is specifically configured to: send RTC peer-to-peer connection negotiation information of the server to the client via a signaling service module based on the screen capture component; simultaneously, receive the RTC peer-to-peer connection negotiation information sent by the client; establish an RTC peer-to-peer connection between the screen capture component and the client's browser page according to the RTC peer-to-peer connection negotiation information sent by the client; send the desktop data of the server captured by the screen capture component to the client via the RTC peer-to-peer connection channel; wherein the desktop data is used by the client to monitor desktop operation data of the user within the remote desktop range in the browser page; receive the desktop operation data transmitted by the client via the RTC peer-to-peer connection channel; and restore the desktop operation events corresponding to the desktop operation data.

[0044] Thirdly, this application provides a server, comprising: a memory and a processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above.

[0045] Fourthly, this application provides a remote desktop control system, including: a server, a session management terminal, and a client; the server is used to execute the first aspect and / or various possible implementations of the first aspect.

[0046] Fifthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible embodiments of the first aspect.

[0047] In a sixth aspect, this application provides a computer program product, including a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect.

[0048] In a seventh aspect, this application provides a computer program that causes a computer to perform the first aspect and / or various possible implementations of the first aspect.

[0049] The remote desktop control method, apparatus, system, and program products provided in this application synchronize user information to the server operating system based on a directory access protocol. The operating system then verifies the user information in the session request based on at least one synchronized user information, enabling the server to accurately identify the remote access subject. When the user information in the session request is verified, a remote desktop session corresponding to that user information is created. This allows for better adaptation of the remote session establishment process to the server system environment, reducing the initialization complexity caused by dedicated clients and coupled links. By interacting with the client in a cross-platform application runtime environment based on this remote desktop session, screen sharing and control command transmission can be completed within a unified session context in the cross-platform application runtime environment, thereby improving the real-time performance, stability, and cross-platform compatibility of remote control. Attached Figure Description

[0050] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0051] Figure 1 This application provides an illustration of an application scenario.

[0052] Figure 2 A flowchart illustrating a remote desktop control method provided in an embodiment of this application;

[0053] Figure 3 A flowchart illustrating another remote desktop control method provided in an embodiment of this application;

[0054] Figure 4 A schematic diagram of the interaction process of a cross-platform screen sharing and remote interaction system provided in this application embodiment;

[0055] Figure 5 This is a schematic diagram of the structure of a remote desktop control device provided in an embodiment of this application;

[0056] Figure 6 This is a schematic diagram of a server structure provided in an embodiment of this application.

[0057] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0058] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0059] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, processing, transmission, provision, disclosure, and application of the relevant data all comply with relevant laws, regulations, and standards, necessary confidentiality measures have been taken, they do not violate public order and good morals, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0060] It should be noted that this application can be used in the field of remote desktop technology, or in any field other than remote desktop technology, such as remote work and collaboration, implementation of remote work, technical support and team collaboration, etc. The application field of this application is not limited.

[0061] Specific application scenarios for this application include remote technical support, training, conference presentations, desktop assistance, and low-latency video transmission. Figure 1 This application provides an illustration of an application scenario, such as... Figure 1 As shown, a typical deployment of remote desktop control technology usually consists of a client browser 101, a server session management node 102, and a target desktop host 103. The user initiates an access request through the browser web page entry, and the system then establishes a remote desktop session on the server side and completes screen interaction.

[0062] In the above scenarios, remote desktop technology based on the Virtual Network Computing (VNC) protocol uses the Remote Framebuffer (RFB) protocol to transmit screen image data over the Transmission Control Protocol (TCP) / Internet Protocol (IP) network. Due to the use of screenshot transmission, it consumes a lot of bandwidth and has poor real-time performance, especially with significant latency when network conditions are poor. Windows remote desktop technology based on the Remote Desktop Protocol (RDP) is optimized for Windows systems and has limited cross-platform support. The graphical command transmission method consumes a lot of server-side resources.

[0063] To address the aforementioned technical challenges, the remote desktop control method provided in this application first establishes a mapping between user information and the server-side directory. Then, the operating system creates a session based on the synchronized directory identity, and subsequent remote control interactions are carried out on top of this session within the cross-platform application runtime environment. The browser-side session request, server-side directory service synchronization, and operating system session generation are organized into a continuous processing chain, enabling the client's identity to form a directly usable remote desktop session on the server side. Thus, when a user initiates remote access, a corresponding remote desktop session can be established based on the user information in the directory and enter an interactive state within the cross-platform application runtime environment. This shortens the session establishment path, reduces control deviations caused by inconsistencies between identity and session, and meets the requirements for low-latency, precise interactive remote desktop control in cross-platform or cross-operating system environments.

[0064] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0065] Figure 2 This is a flowchart illustrating a remote desktop control method provided in an embodiment of this application, as shown below. Figure 2 As shown, this method is applied to the server side, and the method includes:

[0066] 201. Based on the directory access protocol, synchronize at least one user information to the server's operating system.

[0067] The executing entity in this embodiment can be the server in the remote desktop control interaction system, i.e. the controlled end, which generally refers to the computer or terminal device that is remotely controlled. The server can accept remote commands from the remote desktop control interaction system and push screens to the client.

[0068] For example, after retrieving at least one user information, the server can invoke a Lightweight Directory Access Protocol (LDAP) adapted to the operating system's directory structure to synchronize the user information to the operating system. For instance, if the operating system is Linux, the user information can be synchronized directly via LDAP.

[0069] The directory access protocol can be a synchronization protocol used for identity directory maintenance. Specifically, it can process user information through a directory access interface, creating records in the server-side operating system's directory that correspond to the client's user information. The server-side operating system's directory service can be a local directory database, a domain directory cache, a session identity index table, or other identity storage structures that the operating system can query during session creation.

[0070] Furthermore, during user information synchronization, the server can first determine the directory object to be synchronized based on each user's information, then generate a directory write instruction according to the protocol rules, writing each user's information into the directory entry. If necessary, the server can also standardize each user's information to meet the operating system's requirements for directory field format, length, and encoding. This synchronization result enables the server's operating system to obtain an identifiable and queryable user identity foundation within its directory system, thus providing a prerequisite for subsequent session creation based on the remote desktop protocol.

[0071] For example, based on the LDAP protocol, in a Linux operating system environment, user information is centrally stored in the directory information tree of the LDAP server. The Linux operating system can subsequently query and authenticate user information through Name Service Switch (NSS) / Pluggable Authentication Modules (PAM). In a Windows operating system, user information is centrally stored in Active Directory (AD) on the domain controller. The Windows operating system can subsequently query and authenticate user information through Kerberos Network Authentication Protocol (KNAP) / LDAP.

[0072] Based on the above process, it can be seen that the directory access protocol is used here to realize the synchronization between user information and the operating system directory. Through the synchronized directory records, the server can form an identity context that can be used for session generation on the operating system side.

[0073] 202. Receive a session request sent by the client's browser. The session request carries the client's user information.

[0074] In this embodiment, the executing entity can be the server in a remote desktop control interaction system, i.e., the controlled end, which generally refers to a computer or terminal device that is remotely controlled. The server can accept remote commands from the remote desktop control interaction system and push screens to the client. The client is the controlling end, which actively initiates connection requests and sends operation commands to the server.

[0075] For example, the server can deploy an operating system that supports remote desktop control capabilities and receive session requests initiated by client browsers through a browser-facing access interface. These session requests can be generated when a user triggers remote access through a webpage and then sent to the server via a network link. The client browser can be a browser program running on a client (e.g., a desktop terminal, mobile terminal, or other terminal capable of performing webpage access functions). When the user enters the access target, login credentials, or selects a remote desktop resource in the browser page, the browser encapsulates user information related to this access into the session request and sends it to the server. This user information identifies the entity initiating the remote desktop control access and may specifically include user identifiers, account identifiers, domain identity identifiers, or other data that can be used to identify the user.

[0076] Upon receiving the session request, the server first parses the request message and extracts its fields to confirm that it contains user information that can be used for subsequent processing before proceeding to the next processing stage. This receiving process constitutes the entry point of the remote desktop control link, enabling the server to obtain the identity data corresponding to the access subject before establishing a remote desktop session, thereby providing input for subsequent directory synchronization.

[0077] Based on the above process, it can be seen that the session request initiated by the client browser and the user information carried therein form the initial source of subsequent session processing. The server can determine the access object corresponding to the session to be created through this request and continuously guide the request processing flow to the subsequent directory synchronization stage.

[0078] In one example, a custom plugin is deployed on the server. This custom plugin is deployed within the operating system. The custom plugin maintains a version snapshot library locally using "user identifier + device identifier + operating system instance identifier" as the key, recording user configuration, storage mount status, version identifiers of each module, and dependencies. When a session request is received, the custom plugin retrieves the latest user record and historical user record of the user information in the session request from the directory service through the directory access protocol. The customized plugin combines data from historical active sessions in the user history, such as application startup frequency, average startup time, peak processor and memory resources, and frequently accessed configuration files, to generate a corresponding preload plan (including resource configurations required for loading the session). It mounts the session-level temporary cache as an independent directory of the operating system, and pre-copies or hard links the aforementioned preload plan file to the session-level temporary cache and establishes path mappings. This ensures that background-running local remote desktop service applications prioritize reading data from the session-level temporary cache upon startup. This allows for simultaneous user synchronization and data preparation, reducing application startup latency and remote fetching times after remote desktop session creation, shortening environment initialization time, and enabling the desktop environment to reach an interactive, ready state in a very short time. This significantly improves the smoothness and resource utilization of lightweight remote desktop access.

[0079] 203. Based on the operating system, verify the user information in the session request according to at least one user information.

[0080] For example, based on the operating system, all synchronized user information is obtained, and this user information is used to verify the user information in the received session request to determine whether the user information in the session request has passed the verification.

[0081] For example, in a Linux operating system environment, upon receiving user information for a session request, the operating system invokes PAM (Programming Account Management). PAM maps the user information to a Distinguished Name (DN) in the directory, and then uses this DN to initiate a binding request to the LDAP server. The LDAP server internally performs a password comparison and returns a success or failure result to the Linux operating system. If the comparison is successful, the Linux operating system can send the user information to the LDAP server for verification. The server will then query and authenticate the user information in all synchronized user records and return a result indicating whether the verification passed, thus completing the verification process.

[0082] For another example, in a Windows domain environment, the implementation primarily uses the Kerberos protocol combined with Active Directory. Upon receiving user information for a session request, the Windows security support provider interface automatically selects the Kerberos protocol. Relying on Kerberos's ticket exchange mechanism, the password is not transmitted directly but instead uses an encrypted timestamp to prove identity. This allows the Windows system to send the user information for the session request to the directory server for verification via the directory access protocol. The server then searches through all synchronized user information to authenticate the user information for the session request, determining whether the user information has passed verification, thus completing the verification process.

[0083] 204. If the user information in the session request is verified, a remote desktop session corresponding to the user information in the session request is created using the remote desktop protocol.

[0084] For example, after the user information has been synchronized to the operating system's directory on the server, if the user information in the session request is verified successfully, the server can invoke the session creation capabilities provided by the operating system and start a remote desktop session instance in conjunction with the remote desktop protocol. The remote desktop protocol is used here to support the establishment and communication of remote desktop sessions. The server generates a corresponding session context based on the user information in the session request and requests the operating system to create the target session accordingly.

[0085] In practice, after verifying the user information in the session request, the server can read the identity entry associated with that user information from the directory. The local security authority then creates an access token for the user information in the session request and initiates the session creation process (i.e., initiates a creation request) based on this access token through the operating system's session management interface. Upon receiving the creation request, the operating system allocates the corresponding session resources for the remote desktop session according to the user identity corresponding to the user information in the session request and sets the session state to an interactive state.

[0086] The remote desktop session created by the operating system corresponds to the user information in the session request, enabling the remote desktop session to persist as an independent control object on the server side and be available for subsequent access and operation by the client. If multiple available desktop resources or multiple concurrent session requests exist in the implementation environment, the server can also distinguish the session instances corresponding to different users according to the identifiers in the directory, avoiding session context confusion.

[0087] By using user information in the session request as the basis for session establishment, the remote desktop protocol generates a remote desktop session on the operating system side that matches the user information, thereby enabling subsequent interactions to be established on a clear user context.

[0088] 205. Based on remote desktop sessions, remote desktop control interaction with clients is performed in a cross-platform application runtime environment.

[0089] For example, once a remote desktop session is created and running, the server can establish a remote desktop control interaction link with the client browser within the cross-platform application runtime environment. This interaction link can include desktop information transmission between the server and the client, as well as the client sending control commands back to the server. The cross-platform application runtime environment is configured to provide unified runtime support on the operating system, ensuring consistent server-side processing logic. The server captures changes to the target operating system desktop within the remote desktop session and sends the relevant information to the client browser, which then displays the remote desktop screen. Simultaneously, the client browser collects user input on the browser interface, converts this input into control messages, and sends them back to the server. The server then maps these control messages to the corresponding remote desktop session to drive the operating system to perform corresponding desktop operations within the cross-platform application runtime environment.

[0090] Since this interaction is built upon the aforementioned directory synchronization and session creation, client input can directly affect the session instance corresponding to their user information, and the server can continuously maintain input / output synchronization and control responses based on the session state. If window switching, resolution changes, or input device status changes during the session, the server can update the session parameters according to the remote desktop protocol to ensure that the content displayed on the client remains consistent with the server's desktop state.

[0091] Cross-platform application runtime environments can be implemented using a unified runtime framework, containerized runtime layer, or abstraction adaptation layer. The selected model or framework can reduce the differences in adaptation to different target operating system interfaces. For example, cross-platform applications based on the Electron platform can also choose other models in practical applications, and this application does not limit this.

[0092] This step establishes a continuous link between user synchronization, session requests, user authentication, session creation, and subsequent control. The client can access the corresponding remote desktop session and complete interactive operations through a browser, while the server maintains the session's operation and control processing on the operating system side within the cross-platform application runtime environment. It should be understood that the above example is for illustrative purposes only and is not limiting.

[0093] This embodiment provides a remote desktop control method applied to the server side. Based on a directory access protocol, at least one user information is synchronized to the server's operating system. Then, by receiving a session request sent by the client's browser and extracting the user information from it, the user information in the session request is verified using all the synchronized user information. If the verification is successful, a remote desktop session corresponding to the user information in the session request is created using a remote desktop protocol. Based on this remote desktop session, remote desktop control interaction is performed with the client in a cross-platform application runtime environment. This establishes a correspondence between user information and session instances on the server side, thereby meeting the requirements for session establishment and control interaction in remote access scenarios. Furthermore, it enables a unified access method and consistent operating experience for remote desktop services on different operating systems, improving cross-platform adaptability.

[0094] Figure 3 A flowchart illustrating another remote desktop control method provided in this application embodiment is shown below. Figure 3 As shown, the method includes:

[0095] 301. The server obtains at least one user record containing user information through a directory access protocol.

[0096] The directory access protocol is used to send a synchronization request carrying one or more pre-acquired user information to the directory server, and the directory server parses, retrieves and matches the user information to determine the user record corresponding to the user information and then returns it to the server.

[0097] For example, in actual operation, the server first initiates a query to the directory server according to the directory access protocol. The directory server determines a unique user record based on the user's identity identifier, account attributes, or access attributes and returns it. The user record is used to represent the content of the user information in the directory service and is written to the target directory as a subsequent synchronization object.

[0098] In one possible implementation, step 301 includes the following steps:

[0099] The first step is to send at least one user information to the directory server via the directory access protocol; wherein, the at least one user information is used by the directory server to identify the user record of at least one user information.

[0100] The second step is to retrieve at least one user record containing user information from the directory server.

[0101] Specifically, the directory access protocol is used for directory data interaction between the server and the directory server. The directory server receives one or more pre-acquired user information entries and matches them with corresponding user records. The user information serves as an index for directory matching and may include user identifiers, account attributes, login names, domain identifiers, or other fields associated with identity. The user records carry the identity entries returned by the directory server after retrieval. After receiving a session request, the server encapsulates the user information it carries into a query message according to the directory access protocol and sends it to the directory server. The directory server performs a search, comparison, and location in its maintained directory database based on the user information, generates a user record corresponding to the user information, and returns it to the server. The server then receives the user record returned by the directory server through the directory access protocol and saves it as directory data required for subsequent synchronization processing.

[0102] If the directory server returns multiple matching records, the server can select the target user record based on preset matching rules, domain scope, or attribute consistency conditions. In practical applications, the directory access protocol can also be implemented using directory access protocols such as LDAP, and this application does not limit this.

[0103] Based on the above method, the server can first submit user information to the directory server to complete the record location, and then receive the user record returned by the directory server. This allows the user's identity to be directly used for subsequent session establishment in the directory system, thereby providing a stable data foundation for synchronizing user information to the operating system directory and creating remote desktop sessions, and reducing the impact of directory record selection deviation on subsequent session creation.

[0104] 302. The server uses the Hypertext Transfer Protocol triggering mechanism to synchronize at least one user record of user information to the Active Directory service domain of the operating system.

[0105] The Hypertext Transfer Protocol (HTTP or http) triggering mechanism is used to trigger a synchronization action after the server completes the acquisition of user records. This is based on browser requests, web page interaction messages, or HTTP messages received by the server, so that the user records are written to or mapped to the Active Directory service domain of the operating system. The directory service domain is used to carry the synchronized directory content and is managed uniformly by the operating system.

[0106] For example, when the Hypertext Transfer Protocol (HTTP) trigger condition is met, the server synchronizes the user record to a preset target directory within the Active Directory service domain. The target directory can be set as a directory object associated with session creation. The server completes attribute mapping, field binding, or directory entry updates during writing to ensure that the synchronized user record is consistent with the operating system's directory structure.

[0107] In this way, user information is first located through the directory access protocol, and then the directory is written to the user record by the hypertext transfer protocol trigger mechanism. This enables the directory in the server's operating system to obtain the user information corresponding to the client user in a timely manner, thereby providing a unified identity basis for the subsequent creation of remote desktop sessions based on user information, and making the connection between user synchronization and session establishment more coherent, reducing session creation deviations caused by inconsistencies in user records.

[0108] In one possible implementation, after step 302, the method includes: storing user records containing all user information in a shared storage device, enabling the operating system to access the user records in the shared storage device via a network file system protocol.

[0109] The directory stores user information related to remote desktop sessions, while the shared storage device centrally stores this directory and allows different access nodes to share read and write access to the same content within it. After the operating system mounts the shared storage device via the Network File System (NFS) protocol, it can recognize the directory within the shared storage device as a locally accessible directory. The NFS protocol establishes a remote file access path between the operating system and the shared storage device, enabling the operating system to read, update, or synchronize data in the directory without altering the directory's logical consistency.

[0110] Specifically, after synchronizing all user information, the server can write the target directory to the preset mount path of the shared storage device and configure corresponding access permissions and sharing attributes for the directory, ensuring its continuous availability at the network layer. During startup or session creation, the operating system establishes a network file system connection to the shared storage device based on the pre-configured mount information and maps the directory to the local file system namespace, allowing user records created in the directory to be directly accessed and invoked by the remote desktop session. Because the directory is stored on the shared storage device, multiple processing nodes on the server can perform access and maintenance operations based on the same directory content, and the results of directory modifications can be reflected to each accessing end in real time via the network file system protocol.

[0111] By placing the directory on a shared storage device and allowing it to be accessed by the operating system via the network file system protocol, the directory content can be stored uniformly and accessed consistently on the server side. This enables remote desktop sessions to directly read user information based on the same directory context during creation and operation. This approach reduces content discrepancies caused by directory copying, ensuring that the directory data upon which the session depends remains synchronized and consistent, thus supporting the continuous execution of remote desktop control interactions.

[0112] 303. The server receives a session request sent by the client's browser, and the session request carries the client's user information.

[0113] For example, this step can be referred to as step 202, which will not be repeated here.

[0114] 304. The server, based on the operating system, verifies the user information in the session request based on at least one user information.

[0115] For example, this step can be referred to as step 203, which will not be repeated here.

[0116] 305. If the server determines that the user information in the session request has been verified, it creates a remote desktop session corresponding to the user information in the session request through the remote desktop protocol.

[0117] For example, this step can be referred to as step 204, which will not be repeated here.

[0118] 306. The server starts and runs the local remote desktop service in the cross-platform application runtime environment.

[0119] The cross-platform application runtime environment provides unified runtime support for the server-side local remote desktop service on the target operating system, shielding the underlying system differences from the upper-layer business processing, allowing the local remote desktop service to reside on the server side in a consistent manner. The server-side local application service is used to carry out local processing related to the remote desktop session, receive handshake information from the session management end, and collaboratively complete the establishment of peer-to-peer connections for Web Real-Time Communication (WebRTC).

[0120] For example, the server first loads a cross-platform application runtime environment on the operating system, and then starts the local remote desktop service application within that environment. The local remote desktop service application can run as a resident process so that it can immediately enter the processing state after receiving signaling from the session management terminal.

[0121] 307. The server, based on the local remote desktop service, performs a handshake interaction with the session management terminal through the application layer protocol of full-duplex communication to obtain the desktop sharing request sent by the client; the desktop sharing request is generated based on the handshake success signal sent by the session management terminal.

[0122] The session management terminal, acting as a signaling and scheduling node, transmits a signal to the client side that can trigger the establishment of a desktop sharing session after a successful handshake. The desktop sharing request represents the client's intention to initiate the sharing of the remote desktop session and serves as the triggering input for establishing subsequent desktop interaction links.

[0123] For example, the local remote desktop service establishes a handshake interaction with the session management terminal through the application layer protocol of full-duplex communication. During the interaction, it receives a handshake success signal returned by the session management terminal and drives the client to generate a desktop sharing request based on the signal. The desktop sharing request can be automatically generated by the client after opening the remote desktop session page and sent to the server.

[0124] In one possible implementation, step 307 includes:

[0125] Step 1: Send the session request to the session management terminal; the session request is used to determine the signaling service port number requested by the session request.

[0126] Step 2: Receive the signaling service port number sent by the session management terminal and start the signaling service module corresponding to the signaling service port number.

[0127] Step 3: Based on the signaling service module, a handshake interaction is performed with the session management terminal through the application layer protocol of full-duplex communication.

[0128] Step 4: Receive the peer node identifier from the session management terminal; simultaneously, send the server's peer node identifier to the session management terminal; the peer node identifier is used by the session management terminal to generate and send a handshake success signal to the client; the handshake success signal is used by the client to generate a desktop sharing request after opening the remote desktop session page in the browser.

[0129] Step 5: Receive desktop sharing requests from clients via the signaling service module.

[0130] The session request represents the server's intention to initiate session negotiation and carries port request information corresponding to the target signaling service. Upon receiving the session request, the session management terminal returns the corresponding signaling service port number according to preset port allocation rules. The signaling service module establishes listening and sending / receiving capabilities corresponding to the signaling service port number on the server side. Internally, it may include a port binding unit, a message sending / receiving unit, and a handshake state maintenance unit, so that it can immediately enter an interactive state after the port number takes effect. The peer node identifier uniquely identifies the communication nodes of both parties in the session. After receiving the peer node identifier from the server, the session management terminal associates it with the client-side identifier to generate a handshake success signal. The browser's remote desktop session page serves as the client's web session entry point. After receiving the handshake success signal, the client opens the page and generates a desktop sharing request after the page scripts are loaded. The desktop sharing request carries the remote desktop session identifier, connection context, and sharing authorization information, and is sent to the server via the signaling service module.

[0131] Specifically, the server first sends a session request to the session management terminal. After the session management terminal returns the signaling service port number, the server starts the corresponding signaling service module and maintains a listening state. Then, based on this signaling service module, it completes a two-way handshake with the session management terminal using a full-duplex application layer protocol. After exchanging peer node identifiers, the session management terminal sends a handshake success signal to the client. The client then opens the remote desktop session page in its browser and generates a desktop sharing request, which it sends to the server. After receiving the desktop sharing request through the started signaling service module, the server can proceed with the subsequent real-time web communication peer connection establishment process.

[0132] By using the above method, the server can form a continuous signaling link between port negotiation, node identifier exchange and desktop sharing request reception, so as to keep the session negotiation and page triggering consistent, thereby improving the accuracy of remote desktop session establishment and response continuity.

[0133] For example, Figure 4 This application provides an example of an interactive flow diagram of a cross-platform screen sharing and remote interaction system, as shown in the embodiment. Figure 4As shown, the cross-platform screen sharing and remote interaction system is a WebRTC-based system that includes a session plugin (a custom plugin deployed on the server), a domain user synchronization plugin (a synchronization module deployed on the server), a cross-platform server (the server itself), a session management terminal, and a front-end client (the client). The synchronization module enables unified synchronization of platform users, Windows Active Directory (AD) service domain users, and Linux LDAP users. The custom plugin creates isolated, dedicated remote desktops and configures desktop parameters, automatically launching the cross-platform server application in the background. The session management terminal is responsible for dynamic port allocation, global session management, and signaling scheduling. The server establishes the WebRTC media link based on signaling interaction, enabling low-latency streaming media display of the remote desktop screen. Simultaneously, client keyboard and mouse commands are transmitted back to the server via the WebRTC data channel and executed locally, achieving complete remote control. Specifically, the browser initiates a session request to the session management terminal, which verifies the request before initiating a session request to the custom plugin (rdp-plugin). The session request carries key information such as username and node name. The custom plugin synchronizes user information corresponding to LDAP to the Windows Active Directory domain via HTTP triggering using a custom function (ldap_ad_sync). For Linux systems, it directly synchronizes user information via LDAP and mounts the shared storage of user information on the Windows Server or Linux operating system via Network File System (NFS). This allows the operating system to access the shared storage device through NFS, turning it into a usable drive letter or directory, allowing users to access the same files as if they were on a local disk. The custom plugin (rdp-plugin) initiates a remote desktop session with the specified user on the specified Windows Server / Linux system via the RDP protocol and sets the desktop refresh rate. After the remote desktop session is created, the custom plugin launches the server-side (based on Electron, cross-platform supported) application running in the background. Once the local remote desktop service application starts, the browser sends a session request to the session management terminal. This request includes parameters such as username, node IP, and node name to request the port number used to start the signaling service module (a full-duplex communication application layer protocol (WebSocket) server) on the server. After the signaling service module starts, it attempts to connect and handshake with the session management terminal multiple times via WebSocket. Both parties inform each other of their respective peer identifiers (peerId) and record them.After the signaling service module and the session management terminal successfully handshake, the session management terminal sends a handshake success signal to the client. The remote desktop session page in the client's browser can then be opened. The browser will initiate a remote desktop sharing request to the signaling service module through the signaling interaction channel established by the handshake. The desktop sharing request carries the information needed for the browser and screen capture component to establish WebRTC, including the client's peerId, which is used to establish a real-time communication (RTC) peer connection between the client browser and the server. Furthermore, the cross-platform application based on the Electron platform solves the problem of traditional remote desktop clients only supporting a single operating system, enabling seamless access for Windows / Linux users.

[0134] 308. Establish a peer-to-peer RTC connection between the server and the client, and perform remote desktop control interaction with the client based on a remote desktop session.

[0135] For example, after receiving a desktop sharing request, the server establishes a real-time communication (RTC) peer-to-peer connection with the client and synchronizes image frames, mouse events, and keyboard events of the remote desktop session on the connection, thereby completing the remote desktop control interaction.

[0136] Among them, the Real-Time Communication (RTC) peer-to-peer connection is used to establish a real-time communication link between the client browser and the server to carry out bidirectional transmission of desktop data and control data.

[0137] By hosting local application services within a cross-platform application runtime environment, the server-side processing logic remains consistent. A full-duplex signaling handshake connects the session management end, client, and server, triggering desktop sharing requests upon successful handshake. Furthermore, RTC peer-to-peer connections carry the data transmission of remote desktop sessions, enabling real-time exchange of remote visuals and control commands. This allows local remote desktop services to run consistently across different operating systems, with a clearer triggering relationship between handshake signaling and sharing requests. Once the RTC peer-to-peer connection is established, desktop interaction data can be directly carried, resulting in a clearer path for establishing remote desktop sessions and more coherent control interactions, making it suitable for remote support scenarios in heterogeneous environments.

[0138] In one possible implementation, step 308 includes:

[0139] Step 1: Based on the screen capture component, send the server's RTC peer-to-peer connection negotiation information to the client through the signaling service module; at the same time, receive the RTC peer-to-peer connection negotiation information sent by the client.

[0140] Step 2: Based on the RTC peering connection negotiation information sent by the client, establish an RTC peering connection between the screen capture component and the client's browser page.

[0141] Step 3: Send the server-side desktop data captured by the screen capture component to the client through the RTC peer-to-peer connection channel; the desktop data is used by the client to monitor the user's desktop operation data within the remote desktop range in the browser page.

[0142] Step 4: Receive desktop operation data transmitted by the client through the RTC peer-to-peer connection channel; and restore the desktop operation events corresponding to the desktop operation data.

[0143] The screen capture component initiates the underlying collector to capture the current desktop screen of the server and generates RTC peer connection negotiation information for RTC negotiation. The signaling service module relays the negotiation information between the server and the client's browser page. The RTC peer connection establishes a point-to-point communication channel facing the browser page after negotiation. Desktop data is the desktop screen information acquired in real time by the screen capture component, desktop operation data is the control data obtained by the client based on mouse and keyboard actions within the browser page, and desktop operation events are the input event expressions obtained by the server after parsing and reconstructing the control data.

[0144] Specifically, the server first uses a screen capture component to capture desktop image frames and encapsulates them into media data suitable for RTC transmission. Simultaneously, the server sends RTC peer-to-peer connection negotiation information, including encoding / decoding capabilities, transmission parameters, and session identifiers, to the client via the signaling service module. Upon receiving this information, the client's browser generates corresponding RTC peer-to-peer connection negotiation information and sends it back to the server via the signaling service module. The server then establishes an RTC peer-to-peer connection based on the negotiation results. After the RTC peer-to-peer connection is established, the server's screen capture component continuously sends desktop image frames captured at a set frame rate to the browser. The browser renders these frames as remote desktop display content and captures the user's mouse movements, clicks, double-clicks, key inputs, and scroll wheel actions based on the preset remote desktop interaction areas on the page. These actions are encoded into desktop operation data and sent back via the RTC channel. The server then parses the corresponding desktop operation events and maps them to the remote desktop session for execution.

[0145] In this way, both desktop screen transmission and control command feedback are completed within the RTC peer-to-peer connection channel, enabling browser pages to directly participate in the remote desktop interaction process and allowing the server to quickly restore the received desktop operation data into executable events. This achieves real-time screen control and input synchronization in the remote desktop session, improving the real-time performance of remote desktop operations.

[0146] For example, combining Figure 4Upon receiving a desktop sharing request, the signaling service module on the server side sends an RTC Peer Connection establishment operation object to the server-side screen capture component (preparing for subsequent audio / video / data transmission). This initiates screen capture, and the screen capture component simultaneously begins listening for various messages from the signaling service module. The signaling service module, acting as an intermediary, forwards RTC Peer Connection negotiation information (such as Session Description Protocol (SDP) and Interactive Connectivity Establishment (ICE) candidates) between the two ends (screen capture component and client page), ensuring a stable WebRTC connection is established. The client's browser page, based on the information forwarded by the signaling service module, establishes its own RTC Peer Connection operation object. Then, the client's browser page receives and renders the remote desktop view from the server through the established WebRTC channel. Meanwhile, the server-side screen capture component continuously captures screen video and audio, transmitting the captured local desktop video and audio streams to the client via the WebRTC channel. The client-side page monitors user actions such as mouse movement, clicks, and keyboard input within the remote desktop's display area on the browser page. These captured events are converted into a custom format and transmitted from the client to the server via a WebRTC data channel. The server parses the event data and uses Electron and Node.js to call the local operating system's (Application Programming Interface, API) to reconstruct the corresponding mouse and keyboard operations, enabling control of the remote desktop. This process fully covers the entire logic from "initiating a session" to "remote control," relying on core technologies such as WebSocket signaling negotiation, WebRTC real-time communication, and mouse and keyboard event reconstruction to achieve screen sharing and interactive control of the remote desktop. Specifically, deep integration of the server-side screen capture component with RTC Peer Connection, and the exchange of bilateral connection information via signaling services, reduces data transmission hops, lowers end-to-end latency, and improves the real-time performance of remote desktop operations, achieving a latency of approximately 30ms. Simultaneously, by calling the local operating system API through Electron and Node.js, the server can accurately reconstruct the user's mouse and keyboard operations on the client-side page.

[0147] In this embodiment, based on the above embodiments, at the environment construction level, the deep coupling of customized plugins and directory access protocols enables automated silent initialization of user context, storage channels, and business applications, significantly improving deployment efficiency and environment consistency in multi-tenant concurrent scenarios. At the communication link level, the unified scheduling of full-duplex application layer protocol handshake and web real-time communication peer-to-peer connection framework enables dynamic and precise allocation of signaling routes and rapid establishment of point-to-point direct connection channels, significantly reducing network penetration latency and connection establishment time. At the interactive control level, the downlink rendering of audio and video and the uplink transmission of operation commands reuse the same low-latency data channel, ensuring a high degree of synchronization between remote images and physical operations, providing users with an immersive, high-fidelity remote desktop control experience close to local direct connection.

[0148] Figure 5 This is a schematic diagram of the structure of a remote desktop control device provided in an embodiment of this application, as shown below. Figure 5 As shown, this device is used on the server side, and the device includes:

[0149] Synchronization module 401 is used to synchronize at least one user information to the operating system of the server based on the directory access protocol;

[0150] The receiving module 402 is used to receive a session request sent by the client's browser, the session request carrying the client's user information;

[0151] The verification module 403 is used to verify the user information in the session request based on the operating system and at least one user information.

[0152] Module 404 is created to create a remote desktop session corresponding to the user information in the session request if the user information in the session request is verified successfully via the remote desktop protocol.

[0153] The control module 405 is used for remote desktop control interaction with the client in a cross-platform application runtime environment based on a remote desktop session.

[0154] In one possible implementation, the synchronization module 401 is specifically used to: obtain user records of at least one user information through a directory access protocol; and synchronize the user records of at least one user information to the Active Directory service domain of the operating system based on a Hypertext Transfer Protocol triggering mechanism.

[0155] In one possible implementation, the synchronization module 401 is specifically used to: send at least one user information to a directory server via a directory access protocol; wherein the at least one user information is used by the directory server to determine the user record of the at least one user information; and retrieve the user record of the at least one user information from the directory server.

[0156] In one possible implementation, the control module 405 is specifically configured to: start and run the local remote desktop service of the server in the cross-platform application runtime environment; based on the local remote desktop service, perform a handshake interaction with the session management terminal through a full-duplex communication application layer protocol to obtain a desktop sharing request sent by the client; wherein, the desktop sharing request is generated based on the handshake success signal sent by the session management terminal; establish a web real-time communication (RTC) peer connection with the client, and perform remote desktop control interaction with the client based on the remote desktop session.

[0157] In one possible implementation, the control module 405 is specifically configured to: send a session request to the session management terminal; wherein the session request is used to determine the signaling service port number requested by the session request; receive the signaling service port number sent by the session management terminal and start the signaling service module corresponding to the signaling service port number; based on the signaling service module, perform a handshake interaction with the session management terminal through a full-duplex communication application layer protocol; receive the peer node identifier of the session management terminal; simultaneously, send the peer node identifier of the server to the session management terminal; wherein the peer node identifier is used by the session management terminal to generate and send a handshake success signal to the client; the handshake success signal is used by the client to generate a desktop sharing request after opening the remote desktop session page of the browser; and receive the desktop sharing request sent by the client through the signaling service module.

[0158] In one possible implementation, the control module 405 is specifically configured to: send RTC peer-to-peer connection negotiation information from the server to the client via the signaling service module based on the screen capture component; simultaneously, receive the RTC peer-to-peer connection negotiation information sent by the client; establish an RTC peer-to-peer connection between the screen capture component and the client's browser page based on the RTC peer-to-peer connection negotiation information sent by the client; send the server's desktop data captured by the screen capture component to the client via the RTC peer-to-peer connection channel; wherein the desktop data is used by the client to monitor the user's desktop operation data within the remote desktop range in the browser page; receive the desktop operation data transmitted by the client via the RTC peer-to-peer connection channel; and restore the desktop operation events corresponding to the desktop operation data.

[0159] The apparatus in this embodiment can execute the technical solutions in the above method. Its specific implementation process and technical principles are the same, and will not be repeated here.

[0160] Figure 6 This application provides a schematic diagram of a server structure, as shown in the embodiment of the present application. Figure 6 As shown, the server includes: a memory 501 and a processor 502; the memory 501 is used to store the executable instructions of the processor 502.

[0161] The processor 502 is configured to perform the method provided in the above embodiments.

[0162] The server also includes a receiver 503 and a transmitter 504. The receiver 503 is used to receive instructions and data sent by other devices, and the transmitter 504 is used to send instructions and data to external devices.

[0163] The specific implementation process of the processor can be found in the above method embodiments, and its implementation principle and technical effect are similar, so it will not be repeated here.

[0164] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0165] This application also provides a remote desktop control system, including: a server, a session management terminal, and a client; the server stores computer execution instructions, which, when executed on the computer, cause the computer to execute the technical solutions of the above embodiments.

[0166] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed on a computer, cause the computer to perform the technical solutions described above.

[0167] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory, electrically erasable programmable read-only memory, erasable programmable read-only memory, programmable read-only memory, read-only memory, magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0168] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. The readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an application-specific integrated circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in a device.

[0169] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solutions in the above embodiments.

[0170] This application also provides a computer program stored in a computer-readable storage medium. At least one processor can read the computer program from the computer-readable storage medium, and when the at least one processor executes the computer program, it can implement the technical solutions in the above embodiments.

[0171] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0172] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as magnetic disks or optical disks.

[0173] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A remote desktop control method, characterized in that, The method is applied to the server side, and the method includes: Based on the directory access protocol, at least one user information is synchronized to the operating system of the server. Receive a session request sent by the client's browser, wherein the session request carries the client's user information; Based on the operating system, the user information in the session request is verified according to the at least one user information; If the user information in the session request is verified successfully, a remote desktop session corresponding to the user information in the session request is created using the remote desktop protocol. Based on the remote desktop session, remote desktop control interaction is performed with the client in a cross-platform application runtime environment.

2. The method according to claim 1, characterized in that, The method of synchronizing at least one user information to the server's operating system based on the directory access protocol includes: User records that obtain at least one user information through the directory access protocol; Based on the Hypertext Transfer Protocol triggering mechanism, the user records of at least one user information are synchronized to the Active Directory service domain of the operating system.

3. The method according to claim 2, characterized in that, The user records that obtain the at least one user information through the directory access protocol include: The at least one user information is sent to the directory server via the directory access protocol; wherein the at least one user information is used by the directory server to determine the user record of the at least one user information. User records from which at least one user information is obtained from the directory server.

4. The method according to any one of claims 1-3, characterized in that, The remote desktop control interaction with the client in a cross-platform application runtime environment based on the remote desktop session includes: Start and run the local remote desktop service of the server in the cross-platform application runtime environment; Based on the local remote desktop service, a handshake interaction is performed with the session management terminal through the application layer protocol of full-duplex communication to obtain the desktop sharing request sent by the client; wherein, the desktop sharing request is generated based on the handshake success signal sent by the session management terminal; Establish a real-time communication (RTC) peer-to-peer connection with the client and perform remote desktop control interaction with the client based on the remote desktop session.

5. The method according to claim 4, characterized in that, The process of handshaking with the session management terminal via a full-duplex communication application layer protocol to obtain the desktop sharing request sent by the client includes: The session request is sent to the session management terminal; wherein, the session request is used to determine the signaling service port number requested by the session request; Receive the signaling service port number sent by the session management terminal, and start the signaling service module corresponding to the signaling service port number; Based on the signaling service module, a handshake interaction is performed with the session management terminal through the application layer protocol of full-duplex communication; The server receives the peer node identifier from the session management terminal; simultaneously, it sends the peer node identifier from the server to the session management terminal; wherein, the peer node identifier is used by the session management terminal to generate and send a handshake success signal to the client; the handshake success signal is used by the client to generate a desktop sharing request after opening the remote desktop session page of the browser. The signaling service module receives desktop sharing requests sent by the client.

6. The method according to claim 4, characterized in that, The establishment of a web-based real-time communication (RTC) peer-to-peer connection with the client, and the remote desktop control interaction with the client based on the remote desktop session, includes: Based on the screen capture component, the server sends RTC peering connection negotiation information to the client through the signaling service module; at the same time, it receives RTC peering connection negotiation information sent by the client. Based on the RTC peer-to-peer connection negotiation information sent by the client, an RTC peer-to-peer connection is established between the screen capture component and the client's browser page; The desktop data captured by the screen capture component is sent to the client via the RTC peer-to-peer connection channel; wherein, the desktop data is used by the client to monitor the user's desktop operation data within the remote desktop range in the browser page; The system receives desktop operation data transmitted by the client through the RTC peer-to-peer connection channel and restores the desktop operation events corresponding to the desktop operation data.

7. A remote desktop control device, characterized in that, The device is used on a server side, and the device includes: A synchronization module is used to synchronize at least one user information to the operating system of the server based on a directory access protocol. A receiving module is used to receive a session request sent by the client's browser, wherein the session request carries the client's user information; The verification module is used to verify the user information in the session request based on the operating system and the at least one user information. A creation module is used to create a remote desktop session corresponding to the user information in the session request through the remote desktop protocol if it is determined that the user information in the session request has been verified. The control module is used to perform remote desktop control interaction with the client in a cross-platform application runtime environment based on the remote desktop session.

8. A server-side component, characterized in that, include: Memory and processor; The memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-6.

9. A remote desktop control system, characterized in that, include: Server, session management terminal, and client; The server is used to perform the method as described in any one of claims 1-6.

10. A computer program product, characterized in that, The computer program product includes a computer program that, when executed by a processor, implements the method described in any one of claims 1-6.