IP Library Granted Patent US 12,250,496
Granted Patent B2
US 12,250,496 · App. 18/338,761 · Granted Mar 11, 2025

Communication sessions with autonomous security device preparation

Inventors: Zachary William Rose (Natick, MA); Bojan Rajkovic (Salem, MA); Justin Forrest (Boston, MA)
Assignee: SimpliSafe, Inc.
H04N7/183H04N23/62H04N23/661
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,250,496
App. No.
18/338,761
Granted
Mar 11, 2025
Kind
B2
Abstract

A method includes receiving, by a first device, a request from a second device to participate in a session, the request being a message compliant with a webRTC framework and including an identifier of a process hosted by the second device; verifying, by the first device, a type of the process hosted by the second device based on the identifier; initiating, by the first device, one or more actions on the first device in response to verification of the type of the process, the actions being other than those to communicate data between the first device and second device; and establishing, by the first device, the session with the second device after initialization of the actions on the first device.

Claims (53)

1. A method comprising:

receiving, by a camera, a request from a session requester to participate in a session, the request including an identifier that encodes a type of the session requester;

making a determination, by the camera, that the type of the session requester encoded in the identifier is authorized to establish the session with the camera;

selecting, by the camera, based on the type of the session requester one or more actions to configure the camera for the session;

initiating, by the camera, the one or more actions; and

establishing, by the camera and in compliance with a Web Real Time Communication (WebRTC) framework, the session with the session requester after initiation of the one or more actions by the camera.

2. The method of claim 1 , wherein initiating the one or more actions comprises initiating a process hosted by the camera that controls a user interface of the camera to output an indication of the type of the session requester, or initiating a process hosted by the camera that records the session.

3. The method of claim 1 , wherein:

initiating the one or more actions comprises initiating a process hosted by the camera that controls a user interface of the camera; and

initiating the process hosted by the camera that controls the user interface comprises initiating a process that controls a light emitting diode to illuminate in a color or a pattern associated with the type of the session requester.

4. The method of claim 1 , wherein:

initiating the one or more actions comprises initiating a process hosted by the camera that records the session; and

initiating the process hosted by the camera that records the session comprises determining that the type of the session requester is a monitor interface.

5. The method of claim 1 , further comprising:

determining that the type of the session requester is a monitor interface;

determining that an event associated with the session is canceled; and

aborting the session with the session requester.

6. The method of claim 1 , wherein receiving, by the camera, the request including the identifier that encodes the type of the session requester comprises receiving, by a location-based device, an identifier of either a customer interface or a monitor interface.

7. The method of claim 6 , wherein the identifier of either the customer interface or the monitor interface specifies a timestamp and an identifier of the camera.

8. The method of claim 7 , further comprising:

determining an actual identifier of the camera; and

comparing the identifier of the camera to the actual identifier of the camera as part of a process to validate the identifier that encodes the type of the session requester.

9. The method of claim 7 , further comprising:

encoding, by the session requester, the identifier that specifies the timestamp and the identifier of the camera.

10. A camera comprising:

memory;

a network interface; and

at least one processor coupled to the memory and the network interface and configured to

receive, via the network interface from a session requester, a request to participate in a session, the request comprising a message that includes an identifier of the session requester,

determine a type of the session requester based on the identifier,

initiate one or more customer actions to configure the camera for the session in response to determining that the type of the session requester is a customer device,

initiate one or more monitoring center actions to configure the camera for the session in response to determining that the type of the session requester is a monitoring center device, and

establish, in compliance with a Web Real Time Communication framework, the session with the session requester upon configuration of the camera by initiating either the one or more customer actions or the one or more monitoring center actions.

11. The camera of claim 10 , wherein the one or more customer actions comprises controlling a user interface of the camera to output an indication of the type of the session requester.

12. The camera of claim 10 , wherein:

the camera is a location-based device; and

to receive the request including the identifier of the session requester comprises to receive an identifier of either a customer interface or a monitor interface.

13. The camera of claim 12 , wherein the identifier specifies the type of the session requester, a timestamp, and an identifier of the camera.

14. The camera of claim 13 , wherein the at least one processor is further configured to:

determine an actual identifier of the camera; and

compare the identifier of the camera to the actual identifier of the camera as part of a process to validate the identifier of the session requester.

15. The camera of claim 13 , wherein the at least one processor is further configured to:

decode the identifier of the session requester to determine the type of the session requester, the timestamp, and the identifier of the camera.

16. A security system comprising:

a camera configured to host a first process, the first process being configured to

receive an identifier of a second process requesting to participate in a real time communication session with the first process;

determine a type of the second process based on the identifier;

in response to determining that the type of the second process is a customer device, configure the camera for the real time communication session, wherein to configure comprises to initiate one or more customer processes on the camera or to set one or more customer operational parameters of the camera other than communication session parameters;

in response to determining that the type of the second process is a monitoring center device, configure the camera for the real time communication session, wherein to configure comprises to initiate one or more monitoring center processes on the camera or to set one or more monitoring center operational parameters of the camera other than communication session parameters; and

establish, subsequent to configuration of the camera, the real time communication session with the second process.

17. The security system of claim 16 , wherein the one or more monitoring center processes comprises recording the real time communication session.

18. The security system of claim 16 , wherein to receive the identifier of the second process comprises to receive, by a process hosted by a location-based device, an identifier of either a customer interface or a monitor interface.

19. The method of claim 1 , further comprising, after initiating the one or more actions to configure the camera, and after establishing the session in compliance with the WebRTC framework, opening a WebRTC communication channel with the session requester.

Assignments (2)
SECURITY INTEREST Recorded Nov 12, 2025
From: SIMPLISAFE, INC.
To: CAPITAL ONE, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 073579/0854 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 19, 2023
From: ROSE, ZACHARY WILLIAM; RAJKOVIC, BOJAN; FORREST, JUSTIN
To: SIMPLISAFE, INC.
Reel/Frame 064317/0375 →
Continuity (2)
Provisional Application 63482137 · Jan 30, 2023
Related Publication 20240259532A1 · Aug 1, 2024
References Cited (27)
US 11063989B2 · Morgan · 2021 [cited by examiner]
US 11064208B2 · Amini · 2021 [cited by examiner]
US 11743303B2 · Bishop · 2023 [cited by examiner]
US 20140115114A1 · Garmark · 2014 [cited by examiner]
US 20170200356A1 · Kim · 2017 [cited by examiner]
US 20170301201A1 · Siann · 2017 [cited by examiner]
US 20190141088A1 · Morgan et al. · 2019 [cited by applicant]
US 20240007720A1 · Saxena · 2024 [cited by examiner]
CN 114024941A · 2022 [cited by applicant]
Alvestrand, “Overview: Real-Time Protocols for Browser-Based Applications”, Internet Engineering Task Force RFC 8825, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Rescorla, “Security Considerations for WebRTC”, Internet Engineering Task Force RFC 8826, ISSN2010-1721 (Jan. 2021). [cited by applicant]
Rescorla, “WebRTC Security Architecture”, Internet Engineering Task Force RFC 8827, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Uberti et al., “WebRTC IP Address Handling Requirements”, Internet Engineering Task Force RFC 8828, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Uberti et al., “JavaScript Session Establishment Protocol (JSEP)”, Internet Engineering Task Force RFC 8829, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Jesup et al., “WebRTC Data Channels”, Internet Engineering Task Force RFC 8831, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Jesup et al., “WebRTC Data Channel Establishment Protocol”, Internet Engineering Task Force RFC 8832, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Thomson, “Application-Layer Protocol Negotiation (ALPN) for WebRTC”, Internet Engineering Task Force RFC 8833, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Perkins et al., “Media Transport and Use of RTP in WebRTC”, Internet Engineering Task Force RFC 8834, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Alvestrand, “Transports for WebRTC”, Internet Engineering Task Force RFC 8835, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Uberti, “WebRTC Forward Error Correction Requirements”, Internet Engineering Task Force RFC 8854, ISSN 2070-1721 (Jan. 2021). [cited by applicant]
Valin et al., “WebRTC Audio Codec and Processing Requirements”, Internet Engineering Task Force RFC 7874, ISSN 2070-1721 (May 2016). [cited by applicant]
Proust, “Additional WebRTC Audio Codecs for Interoperability”, Internet Engineering Task Force RFC 7875, ISSN 2070-1721 (May 2016). [cited by applicant]
Roach, “WebRTC Video Processing and Codec Requirements”, Internet Engineering Task Force RFC 7742, ISSN 2070-1721 (Mar. 2016). [cited by applicant]
Perumal et al., “Session Traversal Utilities for NAT (STUN) Usage for Consent Freshness”, Internet Engineering Task Force RFC 7675, ISSN 2070-1721 (Oct. 2015). [cited by applicant]
Holmberg et al., “Web Real-Time Communication Use Cases and Requirements”, Internet Engineering Task Force RFC 7478, ISSN 2070-1721 (Mar. 2015). [cited by applicant]
Communication Relating to the Results of the Partial International Search and Provisional Opinion Accompanying the Partial Search Result, PCT Application PCT/US2024/012605 (13 pages) (mailed May 10, 2024). [cited by applicant]
International Search Report and Written Opinion, PCT Application PCT/US2024/012605 (17 pages) (mailed Jul. 1, 2024). [cited by applicant]