# US 11,785,282 B1 · Web-hosted video recording and associated systems and methods

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

- Number: US 11,785,282 B1
- Document ID: US11785282B1
- Status: Granted
- Kind: B1
- Application number: 18/085,389
- Filed: 2022-12-20
- Granted: 2023-10-10
- Earliest claimed: 2022-05-07
- Assignees: Loom, Inc.
- Applicants: Loom, Inc.
- Inventors: Harshyt Goel; Brendon John Muschamp; Jae Eun Lee; Justin Reidy
- Web page: https://patentgrep.com/patent/US11785282B1

## CPC

- H04N 21/2743: Video hosting of uploaded data from client
- H04N 21/4334: {Recording operations (recording of a television signal H04N5/76; arrangements for recording or accumulating broadcast information or broadcast-related information H04H60/27)}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/3247: {involving digital signatures}
- H04L 9/40: Network security protocols
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/126: {the source of the received data}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04L 67/53: using third party service providers
- H04N 21/2541: {Rights Management (protecting software against unauthorised usage in a vending or licensing environment G06F21/10; security in data switching network management H04L41/28; security management or policies for network security H04L63/20; access security in wireless networks H04W12/08)}
- H04N 21/25875: {involving end-user authentication (restricting access to computer systems by authenticating users using a predetermined code G06F21/33; arrangements for secret or secure communication including means for verifying the identity or authority of a user of the system H04L9/32; networks authentication protocols H04L63/08; authentication in wireless network security H04W12/06)}
- H04N 21/26613: {for generating or managing keys in general (key distribution for secret or secure communication involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP] H04L9/083; network support of key management H04L63/06; key management for network security in communication control or processing H04W12/04)}
- H04N 21/4788: communicating with other users, e.g. chatting {(arrangements for providing for computer conferences, e.g. chat rooms, to substation in data switching networks H04L12/1813; distributed application using peer-to-peer [P2P] networks H04L67/104)}
- H04N: PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for loginless video recording from a third-party website viewed on a user device are provided. The present invention enables users to record a video while browsing a third-party website without the need for installing recording software or logging into a recording service, thus paving the way to anonymous online recording and messaging. In one embodiment, the method, executable by a recording server, includes receiving a signed token associated with a user access request to a third-party server; receiving from the user device an iframe request including the signed token, in response to a user recording request; verifying a signature of the signed token; transmitting to the user device code for generating an iframe for display on the third-party website at the user device; receiving from the iframe a session validation request; generating a recording session; and receiving from the iframe a recording action request.

## Claims

### Claim 1

A method, executable by a recording server, for video recording from a third-party website viewed on a user device, comprising:
receiving, from the user device, an iframe request in response to a user recording request on the third-party website, wherein the third-party website is hosted on a third-party server and enables a user to initiate a recording on the user device, wherein the iframe request comprises a signed token associated with a user access request to the third-party server, and wherein the signed token was received by the user device from the third-party server;
verifying a signature of the signed token using public key cryptography, wherein the verifying comprises obtaining a key associated with the third-party server from a recording database;
transmitting an iframe recorder interface code to the user device, in response to the verifying of the signature of the signed token, wherein the iframe recorder interface code comprises program code for generating an iframe for display on the third-party website at the user device;
receiving, from the iframe on the user device, a session validation request;
generating a recording session in response to receiving the session validation request by:
validating the recording session by associating the recording session with the third-party server, and
transmitting a validation response to the iframe; and
receiving, from the iframe on the user device, a recording action request, in response to receiving a recording action to control a recording on the user device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the iframe recorder interface code generates a video recorder interface for viewing in the third-party website on the user device.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
generating a video recording in response to receiving the recording action request.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
generating a link to a completed recording; and
transmitting the link to the third-party website for display on the user device.

### Claim 5 (depends on 1)

The method of claim 1, wherein the signed token is encrypted using an encryption key that is known only to the recording server.

### Claim 6 (depends on 1)

The method of claim 1, wherein the signed token comprises a user session ID and a token validity time.

### Claim 7 (depends on 1)

The method of claim 1, wherein the recording action is selected from the group consisting of a starting, a stopping, a previewing, an editing, and a canceling of the recording.

### Claim 8 (depends on 1)

The method of claim 1, wherein the recording server is configured for creating a third-party session associated with a guest account upon receiving the iframe request from the user device.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
generating a recording upon execution of a starting of the recording, wherein the guest account is activated by the execution of the starting of the recording, and wherein the guest account owns the recording.

### Claim 10 (depends on 8)

The method of claim 8, further comprising:
generating a link to a completed recording upon execution of a stopping of the recording, wherein the guest account is deactivated by the execution of the stopping of the recording.

### Claim 11

A non-transitory storage medium storing program code for video recording from a third-party website viewed on a user device, the program code executable by a hardware processor at a recording server, the program code when executed by the hardware processor causing the hardware processor to:
receive, from the user device, an iframe request in response to a user recording request on the third-party website, wherein the third-party website is hosted on a third-party server and enables a user to initiate a recording on the user device, wherein the iframe request comprises a signed token associated with a user access request to the third-party server, and wherein the signed token was received by the user device from the third-party server;
verify a signature of the signed token using public key cryptography, wherein the program code to verify comprises program code to obtain a key associated with the third-party server from a recording database;
transmit an iframe recorder interface code to the user device, in response to the verifying of the signature of the signed token, wherein the iframe recorder interface code comprises program code for generating an iframe for display on the third-party website at the user device;
receive, from the iframe on the user device, a session validation request;
generate a recording session in response to receiving the session validation request by program code to:
validate the recording session by associating the recording session with the third-party server, and
transmit a validation response to the iframe; and
receive, from the iframe on the user device, a recording action request, in response to receiving a recording action to control a recording on the user device.

### Claim 12 (depends on 11)

The non-transitory storage medium of claim 11, wherein the iframe recorder interface code generates a video recorder interface for viewing in the third-party website on the user device.

### Claim 13 (depends on 11)

The non-transitory storage medium of claim 11, wherein the program code further comprises program code to generate a video recording in response to receiving the recording action request.

### Claim 14 (depends on 13)

The non-transitory storage medium of claim 13, wherein the program code further comprises program code to:
generate a link to a completed recording; and
transmit the link to the third-party website for display on the user device.

### Claim 15 (depends on 11)

The non-transitory storage medium of claim 11, wherein the signed token is encrypted using an encryption key that is known only to the recording server.

### Claim 16 (depends on 11)

The non-transitory storage medium of claim 11, wherein the signed token comprises a user session ID and a token validity time.

### Claim 17 (depends on 11)

The non-transitory storage medium of claim 11, wherein the recording action is selected from the group consisting of a starting, a stopping, a previewing, an editing, and a canceling of the recording.

### Claim 18 (depends on 11)

The non-transitory storage medium of claim 11, wherein the recording server is configured for creating a third-party session associated with a guest account upon receiving the iframe request from the user device.

### Claim 19 (depends on 18)

The non-transitory storage medium of claim 18, wherein the program code further comprises program code to:
generate a recording upon execution of a starting of the recording, wherein the guest account is activated by the execution of the starting of the recording, and wherein the guest account owns the recording.

### Claim 20 (depends on 18)

The non-transitory storage medium of claim 18, wherein the program code further comprises program code to:
generate a link to a completed recording upon execution of a stopping of the recording, wherein the guest account is deactivated by the execution of the stopping of the recording.
