IP Library Granted Patent US 12,481,663
Granted Patent B2
US 12,481,663 · App. 18/336,846 · Granted Nov 25, 2025

Unified description scheme for controlling and operating network connected devices

Inventors: David Kenneth Evans (Los Altos Hills, CA); Michael Alexander Yurochko (Los Gatos, CA); Yaron Sheba (Mountain View, CA); Kristopher Charles Linquist (Milpitas, CA); Hitesh Kalra (Cupertino, CA); David Frank Russell Weir (San Jose, CA); Rajiv Ramanasankaran (San Jose, CA); Shalin Harshadkumar Patel (San Carlos, CA)
Assignee: Comcast Cable Communications, LLC
G06F16/24573G06F16/21H04L67/12
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,481,663
App. No.
18/336,846
Granted
Nov 25, 2025
Kind
B2
Abstract

The present disclosure relates to configuring and operating Internet of things (IoT) elements connected by a network. A computing device receives an interface component corresponding to an IoT element. The computing device retrieves a description of the interface component at least describing a set of restrictions of an operation of the IoT element. The computing device deploys the interface component in the computing device to at least translate events and commands specific to the IoT element to common events and commands for processing in the computing device. The computing device sends at least a subset of the description of the interface component to a user device to cause the user device to generate a user interface for configuring the operation of the IoT element.

Claims (49)

1 . A method comprising:

sending, by a first computing device and to a second computing device, at least a portion of interface information associated with an Internet of Things (IoT) device, wherein the interface information indicates a plurality of functions for controlling the IoT device and indicates positions of content in an interface associated with the IoT device to cause output of the content at the indicated positions to enable control of the IoT device; and

receiving, by the first computing device and from the second computing device, a message indicating one or more controls associated with the IoT device.

2 . The method of claim 1 , wherein the interface information is from a third computing device associated with a manufacturer of the IoT device.

3 . The method of claim 1 , wherein the portion of the interface information indicates at least one of:

dimensions of one or more user interface elements associated with the content,

identification of a type of the one or more user interface elements, or

properties associated with the one or more the user interface elements.

4 . The method of claim 1 , further comprising:

causing, based on the one or more controls and the interface information, the IoT device to perform one or more actions associated with the one or more controls.

5 . The method of claim 1 , wherein the interface information comprises at least one of:

application programming interface (API) information used to communicate with the IoT device,

security information to authenticate the second computing device when controlling the IoT device, or

metadata comprising attributes associated with the IoT device.

6 . The method of claim 5 , wherein the metadata further comprises a link to configuration information to enable or disable a function of the plurality of functions.

7 . The method of claim 5 , wherein the attributes comprise at least one of: a manufacturer of the IoT device, a mode of the IoT device, a version of the IoT device, an operating system of the IoT device, a state of the IoT device, and a protocol for communicating with the IoT device.

8 . A device comprising:

one or more processors; and

memory storing instructions that, when executed by the one or more processors, cause the device to:

send, to a computing device, at least a portion of interface information associated with an Internet of Things (IoT) device, wherein the interface information indicates a plurality of functions for controlling the IoT device and indicates positions of content in an interface associated with the IoT device to cause output of the content at the indicated positions to enable control of the IoT device; and

receive, from the computing device, a message indicating one or more controls associated with the IoT device.

9 . The device of claim 8 , wherein the interface information is from a second computing device associated with a manufacturer of the IoT device.

10 . The device of claim 8 , wherein the portion of the interface information indicates at least one of:

dimensions of one or more user interface elements associated with the content,

identification of a type of the one or more user interface elements, or

properties associated with the one or more the user interface elements.

11 . The device of claim 8 , wherein the instructions, when executed by the one or more processors, further cause the device to:

cause, based on the one or more controls and the interface information, the IoT device to perform one or more actions associated with the one or more controls.

12 . The device of claim 8 , wherein the interface information comprises at least one of:

application programming interface (API) information used to communicate with the IoT device,

security information to authenticate the computing device when controlling the IoT device, or

metadata comprising attributes associated with the IoT device.

13 . The device of claim 12 , wherein the metadata further comprises a link to configuration information to enable or disable a function of the plurality of functions.

14 . The device of claim 12 , wherein the attributes comprise at least one of: a manufacturer of the IoT device, a mode of the IoT device, a version of the IoT device, an operating system of the IoT device, a state of the IoT device, and a protocol for communicating with the IoT device.

15 . A non-transitory computer-readable storage medium storing computer-readable instructions that, when executed by a processor, cause:

sending, by a first computing device and to a second computing device, at least a portion of interface information associated with an Internet of Things (IoT) device, wherein the interface information indicates a plurality of functions for controlling the IoT device and indicates positions of content in an interface associated with the IoT device to cause output of the content at the indicated positions to enable control of the IoT device; and

receiving, by the first computing device and from the second computing device, a message indicating one or more controls associated with the IoT device.

16 . The non-transitory computer-readable storage medium of claim 15 , wherein the interface information is from a third computing device associated with a manufacturer of the IoT device.

17 . The non-transitory computer-readable storage medium of claim 15 , wherein the portion of the interface information indicates at least one of:

dimensions of one or more user interface elements associated with the content,

identification of a type of the one or more user interface elements, or

properties associated with the one or more the user interface elements.

18 . The non-transitory computer-readable storage medium of claim 15 , wherein the instructions that, when executed by the processor further cause:

causing, based on the one or more controls and the interface information, the IoT device to perform one or more actions associated with the one or more controls.

19 . The non-transitory computer-readable storage medium of claim 15 , wherein the interface information comprises at least one of:

application programming interface (API) information used to communicate with the IoT device,

security information to authenticate the second computing device when controlling the IoT device, or

metadata comprising attributes associated with the IoT device.

20 . The non-transitory computer-readable storage medium of claim 19 , wherein the metadata further comprises a link to configuration information to enable or disable a function of the plurality of functions, and wherein the attributes comprise at least one of: a manufacturer of the IoT device, a mode of the IoT device, a version of the IoT device, an operating system of the IoT device, a state of the IoT device, and a protocol for communicating with the IoT device.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2023
From: EVANS, DAVID KENNETH; YUROCHKO, MICHAEL ALEXANDER; SHEBA, YARON; LINQUIST, KRISTOPHER CHARLES; KALRA, HITESH; WEIR, DAVID FRANK RUSSELL; RAMANASANKARAN, RAJIV; PATEL, SHALIN HARSHADKUMAR
To: STRINGIFY INC.
Reel/Frame 064460/0916 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 2, 2023
From: STRINGIFY INC.
To: COMCAST CABLE COMMUNICATIONS, LLC
Reel/Frame 064461/0035 →
Continuity (3)
Continuation 15092501 · Apr 6, 2016
Provisional Application 62206143 · Aug 17, 2015
Related Publication 20230409580A1 · Dec 21, 2023
References Cited (49)
US 7133907B2 · Carlson et al. · 2006 [cited by applicant]
US 9210534B1 · Matthieu et al. · 2015 [cited by applicant]
US 9600571B2 · Shaashua et al. · 2017 [cited by applicant]
US 11876868B2 · Atarius · 2024 [cited by examiner]
US 20080256014A1 · Gould et al. · 2008 [cited by applicant]
US 20100138007A1 · Clark et al. · 2010 [cited by applicant]
US 20100162210A1 · Briden et al. · 2010 [cited by applicant]
US 20100175010A1 · Jeyabalan et al. · 2010 [cited by applicant]
US 20110276908A1 · O'Riordan · 2011 [cited by applicant]
US 20140047322A1 · Kim et al. · 2014 [cited by applicant]
US 20140244833A1 · Sharma et al. · 2014 [cited by applicant]
US 20150019710A1 · Shaashua et al. · 2015 [cited by applicant]
US 20150019714A1 · Shaashua et al. · 2015 [cited by applicant]
US 20150347114A1 · Yoon · 2015 [cited by examiner]
US 20160041534A1 · Gupta · 2016 [cited by applicant]
US 20160043962A1 · Kim et al. · 2016 [cited by applicant]
US 20160044032A1 · Kim et al. · 2016 [cited by applicant]
US 20160048114A1 · Matthieu et al. · 2016 [cited by applicant]
US 20160065653A1 · Chen et al. · 2016 [cited by applicant]
US 20160080932A1 · Jin et al. · 2016 [cited by applicant]
US 20160112240A1 · Sundaresan et al. · 2016 [cited by applicant]
US 20160135241A1 · Gujral et al. · 2016 [cited by applicant]
US 20160147402A1 · Muench · 2016 [cited by applicant]
US 20160173293A1 · Kennedy · 2016 [cited by applicant]
US 20160179993A1 · Maturana et al. · 2016 [cited by applicant]
US 20160182309A1 · Maturana et al. · 2016 [cited by applicant]
US 20160197798A1 · Britt · 2016 [cited by examiner]
US 20160226732A1 · Kim et al. · 2016 [cited by applicant]
US 20160241445A1 · Kim · 2016 [cited by applicant]
US 20160255066A1 · Green et al. · 2016 [cited by applicant]
US 20160308861A1 · Ameling et al. · 2016 [cited by applicant]
US 20160357522A1 · Wee et al. · 2016 [cited by applicant]
US 20160357524A1 · Maluf et al. · 2016 [cited by applicant]
US 20160374134A1 · Kweon · 2016 [cited by examiner]
US 20160379464A1 · Sedayao et al. · 2016 [cited by applicant]
US 20170005390A1 · Zakaria · 2017 [cited by examiner]
US 20170005820A1 · Zimmerman et al. · 2017 [cited by applicant]
US 20170024290A1 · Kaulgud et al. · 2017 [cited by applicant]
US 20170026472A1 · Bugenhagen et al. · 2017 [cited by applicant]
US 20170048476A1 · Freiin et al. · 2017 [cited by applicant]
US 20170052688A1 · Evans et al. · 2017 [cited by applicant]
US 20170054810A1 · Evans et al. · 2017 [cited by applicant]
US 20170063611A1 · Sheba et al. · 2017 [cited by applicant]
US 20180191867A1 · Siebel et al. · 2018 [cited by applicant]
ES 2767048T3 · 2020 [cited by examiner]
Mios, Main Page, Las modified Apr. 23, 2015, 2 Pages, [online] [retrieved on Jan. 12, 2017] Retrieved from the internet <URL:http://wiki.mios.com/index.php/Main_Page>. [cited by applicant]
Nest Labs, “API Introduction,” Archived on web.archive.org on Jun. 26, 2014, 5 Pages, [online] [retrieved on Jan. 18, 2017] Retrieved from the internet <URL:http://web.archive.org/web/20140626020517/https://developer.ne… [cited by applicant]
US Patent Application filed on Jun. 30, 2020, entitled “Platform for Controlling and Operating Network Connected Devices”, U.S. Appl. No. 16/917,723. [cited by applicant]
U.S. Appl. No. 62/172,466, filed Jun. 8, 2015 entitled Physical Space Map Overlay and Interaction for an Internet of Things Integrated Developer Environment. [cited by applicant]