Loading A Mirror Driver In Remote Terminal Server Session

• US 20080209048A1
• Filed: 02/28/2007
• Published: 08/28/2008
• Est. Priority Date: 02/28/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Chen, Hao, Sampath, Sriram, Santiago, Pravin
• Application Number:
  US11/680,446
• Publication Number:
  US 20080209048A1
• Time in Patent Office: Days
• US Class Current: 709/227
• CPC Class Codes: H04L 67/131 Protocols for games, networked simulations or virtual reality
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/148 Migration or transfer of sessions
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Described are systems and methods for loading mirror drivers in remote sessions of a remote server that enables remote sessions at various computing or client devices to access the mirror drivers. The mirror drivers are video display drivers which receives video rendering output and/or graphics output from a graphics device interface. Such video rendering output and/or graphics output received may be a mirror image of the video rendering output and/or graphics output send to display drivers for displaying on monitor.

Claims

1. A server comprising:

a memory;

one or more processors operatively coupled to the memory;

one or more mirror drivers in the memory; and

a graphics module configured to access and load the mirror drivers in a remote server sessions, whereby one or more scenarios are possible in remoting sessions run at a client device.

2. The server of claim 1, wherein the one or more mirror drivers and one or more display drivers, are registered in a graphics device list.

3. The server of claim 2, wherein the graphics device list includes information of display drivers that are visible to the server.

4. The server of claim 1, wherein details of the mirror drivers are added to a graphics device list.

5. The server of claim 4, wherein the details are obtained from a registry of the server.

6. The server of claim 1, wherein graphics module identifies if the client device is enabled for loading.

7. The server of claim 1, wherein the sessions are stored as part of client device node information.

8. The server of claim 1 further comprising a program that triggers a video initialization to open the sessions.

9. A system comprising:

a server; and

one or more client devices in remote session with the server, wherein one or more mirror drivers in the server facilitates the client devices to modify graphics features of a display of each of the client devices.

10. The system of claim 9, wherein the server hosts applications that rely on the one or more mirror drivers and are accessed by the client devices.

11. The system of claim 10, wherein the applications include one or more of the following:

collaborative screen sharing, net meeting, and desktop mangnifier.

12. The system of claim 9, wherein the loading of the mirror driver in a remote session enhances functionality and makes other scenarios.

13. The system of claim 9, wherein modifying graphics features of a display of a client device is independent of other client devices.

14. A method comprising:

setting a mirror driver in a server;

accessing the mirror driver to obtain information regarding the mirror driver; and

loading the mirror deriver into the server.

15. The method of claim 14, wherein the setting is performed by detecting the presence of the mirror driver.

16. The method of claim 14, wherein the accessing includes adding the information to a graphics device list.

17. The method of claim 14, wherein the information includes parameters associated with the mirror driver, the parameters include modes and configurations.

18. The method of claim 14, wherein the information is configured to allow remote sessions to enumerate the mirror driver.

19. The method of claim 14, wherein the loading includes collecting the information to determine status of the mirror driver.

20. The method of claim 19, wherein the status denotes whether the mirror driver is loaded.