# US 2025/0094547 A1 · Secure token for screen sharing

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

- Number: US 2025/0094547 A1
- Document ID: US20250094547A1
- Status: Published application
- Kind: A1
- Application number: 17/996,123
- Filed: 2022-07-28
- Published: 2025-03-20
- Earliest claimed: 2022-07-28
- Assignees: Rakuten Symphony, Inc.
- Applicants: Rakuten Symphony, Inc.
- Inventors: Dharmendra Kumar JAIN; Vishal PARASHAR; Priyank KASERA
- Web page: https://patentgrep.com/patent/US20250094547A1

## CPC

- G06F 21/31: User authentication
- H04L 65/403: Arrangements for multi-party communication, e.g. for conferences (data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15)
- G06F 3/1454: {involving copying of the display data of a local workstation or window to a remote workstation or window so that an actual copy of the data is displayed simultaneously on two or more displays, e.g. teledisplay}
- H04L 63/0838: {using one-time-passwords}
- H04L 63/108: {when the policy decisions are valid for a limited amount of time}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/55: Push-based network services
- G06Q 10/101: Collaborative creation, e.g. joint development of products or services
- G09G 2358/00: Arrangements for display data security
- H04L 65/4015: {where at least one of the additional parallel sessions is real time or time sensitive, e.g. white board sharing, collaboration or spawning of a subconference}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G09G: ARRANGEMENTS OR CIRCUITS FOR CONTROL OF INDICATING DEVICES USING STATIC MEANS TO PRESENT VARIABLE INFORMATION (arrangements for transferring data between digital computers and displays G06F3/14; static indicating arrangements comprising an association of a number of separate sources or light control cells G09F9/00; static indicating arrangements comprising integral associations of a number of light sources H01J, H01K, H10H, H05B33/12; scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission, details thereof H04N1/00)

## Abstract

A method of screen sharing include receiving, by a first server device and from a user device, device information corresponding to the user device, generating, by the first server device, a device identifier (ID) based on the device information, receiving, by the first server device and from the user device, a request for a token, generating, by the first server device, a token based on the device ID, and sending, by the first server device, the token to the user device.

## Claims

### Claim 1

A method of screen sharing, comprising:
receiving, by a first server device and from a user device, device information corresponding to the user device;
generating, by the first server device, a device identifier (ID) based on the device information;
receiving, by the first server device and from the user device, a request for a token;
generating, by the first server device, a token based on the device ID; and
sending, by the first server device, the token to the user device.

### Claim 2 (depends on 1)

The method of claim 1, further comprising sending, by the user device, the generated token to a second server device.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
in response to receiving the generated token from the user device, sending, by the second server device and to the user device, a notification that the generated token has been confirmed; and
in response to receiving the notification that the generated token has been confirmed, accepting, by the user device, a screen sharing request for sharing a screen of the user device with the second server device.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
determining, by the first server device, whether the generated token is unique from in-use tokens; and
generating, by the first server device, a subsequent token when the previously generated token is determined to not be unique from in-use tokens.

### Claim 5 (depends on 1)

The method of claim 1, further comprising setting, by the first server device, a validity time period for the token.

### Claim 6 (depends on 5)

The method of claim 5, wherein the validity time period is set based on a predetermined time period.

### Claim 7 (depends on 1)

The method of claim 1, further comprising mapping, by the first server device, the token to the device ID.

### Claim 8

A system for screen sharing, comprising:
a user device; and
a first server device configured to:
receive, from the user device, device information corresponding to the user device;
generate a device identifier (ID) based on the device information;
receive, from the user device, a request for a token;
generate a token based on the device ID; and
send the token to the user device.

### Claim 9 (depends on 8)

The system of claim 8, further comprising a second server device, wherein the user device is configured to send the generated token to a second server device.

### Claim 10 (depends on 9)

The system of claim 9, wherein the second server device is configured to, in response to receiving the generated token from the user device, send, to the user device, a notification that the generated token has been confirmed; and
wherein the user device is further configured to, in response to receiving the notification that the generated token has been confirmed, accept, by the user device, a screen sharing request for sharing a screen of the user device with the second server device.

### Claim 11 (depends on 8)

The system of claim 8, wherein the first server device is further configured to:
determine whether the generated token is unique from in-use tokens; and
generate a subsequent token when the previously generated token is determined to not be unique from in-use tokens.

### Claim 12 (depends on 8)

The system of claim 8, wherein the first server device is further configured to set a validity time period for the token.

### Claim 13 (depends on 12)

The system of claim 12, wherein the validity time period is set based on a predetermined time period.

### Claim 14 (depends on 8)

The system of claim 8, wherein the first server device is further configured to map the token to the device ID.

### Claim 15

A non-transitory computer-readable storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to:
receive, by a first server device and from a user device, device information corresponding to the user device;
generate, by the first server device, a device identifier (ID) based on the device information;
receive, by the first server device and from the user device, a request for a token;
generate, by the first server device, a token based on the device ID; and
send, by the first server device, the token to the user device.

### Claim 16 (depends on 15)

The storage medium of claim 15, wherein the instructions, when executed, further cause the at least one processor to send, by the user device, the generated token to a second server device.

### Claim 17 (depends on 16)

The storage medium of claim 16, wherein the instructions, when executed, further cause the at least one processor to:
in response to receiving the generated token from the user device, send, by the second server device and to the user device, a notification that the generated token has been confirmed; and
in response to receiving the notification that the generated token has been confirmed, accept, by the user device, a screen sharing request for sharing a screen of the user device with the second server device.

### Claim 18 (depends on 15)

The storage medium of claim 15, wherein the instructions, when executed, further cause the at least one processor to:
determine, by the first server device, whether the generated token is unique from in-use tokens; and
generate, by the first server device, a subsequent token when the previously generated token is determined to not be unique from in-use tokens.

### Claim 19 (depends on 15)

The storage medium of claim 15, wherein the instructions, when executed, further cause the at least one processor to set, by the first server device, a validity time period for the token.

### Claim 20 (depends on 19)

The storage medium of claim 19, wherein the validity time period is set based on a predetermined time period.
