# US 2013/0297792 A1 · System and method for providing session-level access management of access requests to a redirected device from a predetermined session

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2013/0297792 A1
- Document ID: US20130297792A1
- Status: Published application
- Kind: A1
- Application number: 13/651,321
- Filed: 2012-10-12
- Published: 2013-11-07
- Earliest claimed: 2012-05-07
- Assignees: Wyse Technology L.L.C.
- Applicants: Wyse Technology Inc.
- Inventors: Puneet KAUSHIK
- Web page: https://patentgrep.com/patent/US20130297792A1

## CPC

- H04L 67/146: Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
- H04L 63/10: {for controlling access to devices or network resources}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Managing access requests to a device is provided. The operations may include determining that a device stack corresponds to the device that is remote to the server and is connected locally to a client that is remote to the server, the device stack comprising one or more device objects; attaching a device access restriction object on top of the device stack; facilitating restriction of access to the one or more device objects from sessions different from a session associated with the device; receiving, at the device access restriction object, an access request to the device; and determining, at the device access restriction object, whether the access request is allowed access to the device. The access request may be allowed if a session from which the access request is received is a predetermined session.

## Claims

### Claim 1

A method for managing access requests to a device, the method comprising:
determining that a device stack corresponds to the device that is remote to the server and is connected locally to a client that is remote to the server, the device stack comprising one or more device objects;
attaching a device access restriction object on top of the device stack;
facilitating restriction of access to the one or more device objects from sessions different from a session associated with the device;
receiving, at the device access restriction object, an access request to the device; and
determining, at the device access restriction object, whether the access request is allowed access to the device.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the facilitating restriction of access to the one or more device objects comprises:
for each of the one or more device objects in the device stack, determining whether a corresponding symbolic link exists in a global namespace of an object manager namespace (OMN) and moving the symbolic link to a local namespace of the OMN.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the determining whether the access request is allowed access to the device comprises:
determining whether a session from which the access request is received is a predetermined session; and
determining that the access request is allowed if the session from which the access request is received is the predetermined session.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the determining whether the access request is allowed access to the device comprises:
determining whether a session from which the access request is received is the same as a session of the client; and
determining that the access request is allowed if the session from which the access request is received is the same as the session of the client.

### Claim 5 (depends on 1)

The method according to claim 1, comprising: if the access request is not allowed, generating an error message indicating that the device does not exist.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the determining that the device stack corresponds to the device that is remote to the server comprises facilitating traversing the device stack downwards to identify a device object corresponding to a virtual bus driver at the bottom of the device stack.

### Claim 7 (depends on 1)

The method according to claim 1, comprises determining whether the device is configured to be provided with access restriction, wherein the attaching the access restriction object comprises:
attaching the access restriction object on top of the device stack if the device is configured to be provided with access restriction.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the method is performed without hooking to a kernel module.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the device is a USB device.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the access request is made by a process of an application, and wherein receiving the access request to the device comprises:
intercepting the access request to the device made by the process.

### Claim 11

A machine-readable storage medium encoded with instructions executable by one or more processors to perform one or more operations, the one or more operations comprising:
determining, at a server, that a device stack corresponds to the device that is remote to the server and is connected locally to a client that is remote to the server, the device stack comprising one or more device objects;
attaching a device access restriction object on top of the device stack;
facilitating restriction of access to the one or more device objects from sessions different from a session associated with the device;
receiving, at the device access restriction object, an access request to the device; and
determining, at the device access restriction object, whether the access request is allowed access to the device.

### Claim 12 (depends on 11)

The machine-readable storage medium according to claim 11, wherein the facilitating restriction of access to the one or more device objects comprises:
for each of the one or more device objects in the device stack, determining whether a corresponding symbolic link exists in a global namespace of an object manager namespace (OMN) and moving the symbolic link to a local namespace of the OMN.

### Claim 13 (depends on 11)

The machine-readable storage medium according to claim 11, wherein the determining whether the access request is allowed access to the device comprises:
determining whether a session from which the access request is received is a predetermined session; and
determining that the access request is allowed if the session from which the access request is received is the predetermined session.

### Claim 14 (depends on 11)

The machine-readable storage medium according to claim 11, wherein the determining whether the access request is allowed access to the device comprises:
determining whether a session from which the access request is received is the same as a session of the client; and
determining that the access request is allowed if the session from which the access request is received is the same as the session of the client.

### Claim 15 (depends on 11)

The machine-readable storage medium according to claim 11, comprising: if the access request is not allowed, generating an error message indicating that the device does not exist.

### Claim 16 (depends on 11)

The machine-readable storage medium according to claim 11, wherein the determining that the device stack corresponds to the device that is remote to the server comprises facilitating traversing the device stack downwards to identify a device object corresponding to a virtual bus driver at the bottom of the device stack.

### Claim 17 (depends on 11)

The machine-readable storage medium according to claim 11, wherein the one or more operations comprise determining whether the device is configured to be provided with access restriction, wherein the attaching the access restriction object comprises:
attaching the access restriction object on top of the device stack if the device is configured to be provided with access restriction.

### Claim 18 (depends on 11)

The machine-readable storage medium of claim 11, wherein the one or more operations are performed without hooking to a kernel module.

### Claim 19 (depends on 11)

The machine-readable storage medium according to claim 11, wherein the device is a USB device.

### Claim 20 (depends on 11)

The machine-readable storage medium of claim 11, wherein the access request is made by a process of an application, and wherein receiving the access request to the device comprises:
intercepting the access request to the device made by the process.

### Claim 21

An apparatus, comprising:
one or more modules configured to perform one or more operations comprising:
determining, at a server, that a device stack corresponds to the device that is remote to the server and is connected locally to a client that is remote to the server, the device stack comprising one or more device objects;
attaching a device access restriction object on top of the device stack;
facilitating restriction of access to the one or more device objects from sessions different from a session associated with the device;
receiving, at the device access restriction object, an access request to the device; and
determining, at the device access restriction object, whether the access request is allowed access to the device.

### Claim 22 (depends on 21)

The apparatus according to claim 21, wherein the facilitating restriction of access to the one or more device objects comprises:
for each of the one or more device objects in the device stack, determining whether a corresponding symbolic link exists in a global namespace of an object manager namespace (OMN) and moving the symbolic link to a local namespace of the OMN.

### Claim 23 (depends on 21)

The apparatus according to claim 21, wherein the determining whether the access request is allowed access to the device comprises:
determining whether a session from which the access request is received is a predetermined session; and
determining that the access request is allowed if the session from which the access request is received is the predetermined session.

### Claim 24 (depends on 21)

The apparatus according to claim 21, wherein the determining whether the access request is allowed access to the device comprises:
determining whether a session from which the access request is received is the same as a session of the client; and
determining that the access request is allowed if the session from which the access request is received is the same as the session of the client.

### Claim 25 (depends on 21)

The apparatus according to claim 21, comprising: if the access request is not allowed, generating an error message indicating that the device does not exist.

### Claim 26 (depends on 21)

The apparatus according to claim 21, wherein the determining that the device stack corresponds to the device that is remote to the server comprises facilitating traversing the device stack downwards to identify a device object corresponding to a virtual bus driver at the bottom of the device stack.

### Claim 27 (depends on 21)

The apparatus according to claim 21, wherein the one or more operations comprise determining whether the device is configured to be provided with access restriction, wherein the attaching the access restriction object comprises:
attaching the access restriction object on top of the device stack if the device is configured to be provided with access restriction.

### Claim 28 (depends on 21)

The apparatus according to claim 21, wherein the one or more operations are performed without hooking to a kernel module.

### Claim 29 (depends on 21)

The apparatus according to claim 21, wherein the device is a USB device.

### Claim 30 (depends on 21)

The apparatus according to claim 21, wherein the access request is made by a process of an application, and wherein receiving the access request to the device comprises:
intercepting the access request made by the process to the device.

### Claim 31

An apparatus comprising:
means for determining that a device stack corresponds to the device that is remote to the server and is connected locally to a client that is remote to the server, the device stack comprising one or more device objects;
means for attaching a device access restriction object on top of the device stack;
means for facilitating restriction of access to the one or more device objects from sessions different from a session associated with the device;
receiving, at the device access restriction object, an access request to the device; and
means for determining, at the device access restriction object, whether the access request is allowed access to the device.
