IP Library › Granted Patent US 12,438,775
Granted Patent B2
US 12,438,775 · App. 17/870,940 · Granted Oct 7, 2025

Automated configuration of machine-to-machine systems

Inventors: Silviu Petria (Stilpeni, RO); Andra Paraschiv (Braila, RO); George Cristian Dumitru Milescu (Bucharest, RO); Ulf Christian Bjorkengren (Bjarred, SE); Shao-Wen Yang (San Jose, CA)
Assignee: Intel Corporation
H04L41/0886H04L12/66H04L67/34H04W4/38H04W4/50H04W4/70
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,438,775
App. No.
17/870,940
Granted
Oct 7, 2025
Kind
B2
Abstract

A gateway is provided with configuration management logic to identify a set of configurations corresponding to a deployment of a particular application, and automatically send corresponding configuration data to a set of devices in range of the gateway. Service management logic of the gateway determines that assets on the set of devices correspond to one or more asset abstractions defined for the particular application, where the configuration data is sent to the set of devices based on the assets corresponding to the asset abstractions. Sensor data is received during the deployment as generated by a sensor asset of one of the devices, the sensor data is processed according to service logic of the particular application to generate a result, and actuating data is generated and sent during the deployment to an actuator asset on the set of devices based on the result.

Claims (71)

1. An apparatus comprising:

a gateway device comprising:

an antenna to connect to a plurality of devices over a wireless network;

an interface to couple to a cloud service over a network;

a processor;

an internet of things (IoT) orchestrator executable by the processor to:

receive an IoT application, wherein the IoT application indicates a plurality of models to be accessed and used in the IoT application and defines interactions between the plurality of models to be applied in one or more workflows of the IoT application, wherein the plurality of models comprise two or more device models and at least one web service model, each of the two or more device models comprise a respective abstract representation of a respective one of a plurality of device types and operational capabilities of the corresponding device type, the at least one web service model comprises an abstract representation of a web service to be accessed from the cloud service to interact with at least one of the devices types associated with the two or more device models to perform the one or more workflows of the IoT application, and the IoT application is to use a plurality of communication protocols based on one or more of the plurality of models to perform the one or more workflows;

determine a mapping of at least a subset of the plurality of devices to the associated respective device types of the two or more device models of the IoT application;

deploy a system comprising at least the subset of the plurality of devices and the web service based on the mapping; and

orchestrate interactions between at least the subset of the plurality of devices based on the IoT application to cause the system to perform the one or more workflows based on the interactions defined in the IoT application.

2. The apparatus of claim 1 , wherein the IoT orchestrator is further to access configuration data for the system, the configuration data identifies settings for the system, wherein the system is deployed based on the settings.

3. The apparatus of claim 1 , wherein at least a portion of the IoT application is received from the cloud service.

4. The apparatus of claim 1 , wherein the plurality of models are selected for the IoT application from a set of predefined models and the plurality of models comprise a subset of the set of predefined models.

5. The apparatus of claim 1 , wherein the IoT application defines the at least one web service model comprises a plurality of web models to abstract a plurality of different web services to be used in performance of the one or more workflows.

6. The apparatus of claim 5 , wherein the IoT orchestrator is further executable to:

orchestrate interactions between one or more of the plurality of devices with the plurality of different web services based on the IoT application in connection with performance of the one or more workflows.

7. The apparatus of claim 1 , wherein the web service comprises one of a data storage service, an information hosting service, a geolocation service, or a computational service.

8. The apparatus of claim 1 , wherein the plurality of device types comprise one or more sensors and one or more actuators.

9. The apparatus of claim 1 , wherein the IoT orchestrator is further executable to push code to one of the plurality of devices based on the corresponding one of the plurality of models.

10. The apparatus of claim 1 , wherein the plurality of devices utilize different protocols in the plurality of communication protocols, and orchestrating interactions between the plurality of devices comprises translating communications between the plurality of devices during performance of the one or more workflows.

11. The apparatus of claim 1 , wherein the IoT orchestrator is further executable to:

identify a different plurality of devices connected to the network, wherein the different plurality of devices comprises at least one particular device not in common with the plurality of devices;

determine a mapping of the different plurality of devices to the plurality of device types in the device models of the IoT application;

deploy another instance of the system comprising the different plurality of devices; and

orchestrate interactions between the different plurality of devices based on the IoT application to cause the other instance of the system to perform the one or more workflows based on the IoT application.

12. The apparatus of claim 1 , wherein the device types of the two or more device models comprise at least one actuator device type, the one or more workflows comprises automatically actuating at least one actuator device associated with the at least one actuator device type based on inputs of one or more other device types or web services based on the interactions defined in the IoT application.

13. The apparatus of claim 12 , wherein the plurality of models comprise a motion sensor model, a computation model, and an alarm model, and the particular function comprises actuating an alarm based on interactions between the motion sensor model, the computation model, and the alarm model.

14. The apparatus of claim 12 , wherein the plurality of models comprises at least one of a light sensor model, a temperature sensor model, a humidity sensor model, a computation model, a data storage model, and a light actuator model, and the particular function comprises actuating a light based on interactions between at least two of light sensor model, a temperature sensor model, a humidity sensor model, a computation model, a data storage model, and a light actuator model.

15. A method comprising:

receiving a definition of an internet of things (IoT) application at a gateway device, wherein the IoT application comprises a plurality of models and defines interactions between the plurality of models, wherein the plurality of models comprise two or more device models and at least one web service model, each of the two or more device models comprise a respective abstract representation of a respective one of a plurality of device types and operational capabilities of the corresponding device type, the at least one web service model comprises an abstract representation of a web service to be accessed from the cloud service to interact with at least one of the devices types associated with the two or more device models to perform the one or more workflows of the IoT application, and the IoT application is to use a plurality of communication protocols corresponding to the two or more device models to perform a workflow;

identifying, at the gateway device, a plurality of devices connected to a local network;

determining, at the gateway device, a mapping of the plurality of devices to the respective device types associated with the two or more device models of the IoT application;

deploying, using the gateway device, a system comprising the web service and the plurality of devices based on the mapping; and

orchestrating, at the gateway device, performance of the workflow using the deployed system based on the interactions defined in the IoT application.

16. The method of claim 15 , comprising pushing code to one or more of plurality of devices based on the IoT application for use in performance of the workflow.

17. The method of claim 15 , comprising:

identifying another device connected to the network;

determining that the other device maps to a particular one of the plurality of models; and

substituting a particular device in the plurality of devices mapped to the particular model with the other device in the system.

18. The method of claim 15 , comprising:

receiving an update to the IoT application or one or more of the plurality of models;

redeploying the system based on the update.

19. A system comprising:

a plurality of devices; and

a gateway device, coupled to the plurality of devices by a local wireless network, the gateway device comprising:

an antenna to connect to the plurality of devices over the local wireless network;

an interface to couple to a cloud-based computing system over a network;

a processor;

an internet of things (IoT) orchestrator executable by the processor to:

identify an IoT application, wherein the IoT application indicates a plurality of models to be accessed and used in the IoT application and defines interactions between the plurality of models to be applied in one or more workflows of the IoT application, wherein the plurality of models comprise two or more device models and at least one web service model, each of the two or more device models comprise a respective abstract representation of a respective one of a plurality of device types and operational capabilities of the corresponding device type, the at least one web service model comprises an abstract representation of a web service to be accessed from the cloud service to interact with at least one of the devices types associated with the two or more device models to perform the one or more workflows of the IoT application, and the IoT application is to use a plurality of communication protocols corresponding to the plurality of device types to perform the one or more workflows;

determine a mapping of at least a subset of the plurality of devices to the associated respective device types of the two or more device models of the IoT application;

deploy a system comprising at least the subset of the plurality of devices and the web service based on the mapping; and

orchestrate interactions between at least the subset of the plurality of devices based on the IoT application to cause the system to perform the one or more workflows based on the interactions defined in the IoT application.

20. The system of claim 19 , wherein the web service is to receive data from or send data to one of the devices mapped to one of the two or more device models to perform the one or more workflows.

21. At least one non-transitory machine-readable storage medium with instructions stored thereon, the instructions executable by a machine to cause the machine to:

cause an IoT application to be identified at a particular device, wherein the particular device is coupled to a plurality of other devices in a local wireless network, the IoT application identifies a plurality of models to be accessed and used in the IoT application and defines interactions between the plurality of models to be applied in one or more workflows of the IoT application, wherein the plurality of models comprise two or more device models and at least one web service model, each of the two or more device models comprise a respective abstract representation of a respective one of a plurality of device types and operational capabilities of the corresponding device type, the at least one web service model comprises an abstract representation of a web service to be accessed from the cloud service to interact with at least one of the devices types associated with the two or more device models to perform the one or more workflows of the IoT application, and the IoT application is to use a plurality of protocols corresponding to the plurality of device types to perform the one or more workflows;

determine a mapping of at least a subset of the plurality of other devices to the associated respective device types of the two or more device models of the IoT application;

deploy a system comprising at least the subset of the plurality of other devices and the web service based on the mapping; and

orchestrate interactions between at least the subset of the plurality of devices based on the IoT application to cause the system to perform the one or more workflows based on the interactions defined in the IoT application.

22. The storage medium of claim 21 , wherein the particular device comprises a gateway device.

23. The storage medium of claim 21 , wherein the particular device is mapped to a particular one of the two or more device of models and deployed with the subset of the plurality of other devices in the system.

24. An apparatus comprising:

communication circuitry to connect to a plurality of devices over a wireless network;

an interface to couple to a remote computing system over a network;

a processor;

an internet of things (IoT) orchestrator executable by the processor to:

identify an IoT application, wherein the IoT application indicates a plurality of models to be accessed and used in the IoT application and defines interactions between the plurality of models to be applied in one or more workflows of the IoT application, wherein the plurality of models comprise two or more device models and at least one web service model, each of the two or more device models comprise a respective abstract representation of a respective one of a plurality of device types and operational capabilities of the corresponding device type, the at least one web service model comprises an abstract representation of a web service to be accessed from the cloud service to interact with at least one of the devices types associated with the two or more device models to perform the one or more workflows of the IoT application, and the IoT application is to use a plurality of protocols corresponding to the plurality of device types to perform the one or more workflows;

determine a mapping of at least a subset of the plurality of devices to the associated respective device types of the two or more device models of the IoT application;

deploy a system comprising at least the subset of the plurality of devices and the web service based on the mapping; and

orchestrate interactions between at least the subset of the plurality of devices based on the IoT application to cause the system to perform the one or more workflows based on the interactions defined in the IoT application.

25. The apparatus of claim 24 , comprising a particular one of the plurality of devices.

Continuity (3)
Continuation 17306304 · May 3, 2021
Continuation 16306559
Related Publication 20230048307A1 · Feb 16, 2023
References Cited (86)
US 8065317B2 · Wang · 2011 [cited by examiner]
US 9462041B1 · Hagins · 2016 [cited by examiner]
US 9531559B1 · Vlaminck · 2016 [cited by examiner]
US 10263841B1 · Stamatakis · 2019 [cited by examiner]
US 10313197B1 · Stamatakis · 2019 [cited by examiner]
US 10423459B1 · Jacques de Kadt · 2019 [cited by examiner]
US 11398952B2 · Petria · 2022 [cited by examiner]
US 11652886B2 · Yang · 2023 [cited by examiner]
US 20050102383A1 · Sutler · 2005 [cited by examiner]
US 20060031248A1 · Vinberg · 2006 [cited by examiner]
US 20070118496A1 · Bornhoevd · 2007 [cited by examiner]
US 20090036750A1 · Weinstein · 2009 [cited by examiner]
US 20090064108A1 · De Atley · 2009 [cited by examiner]
US 20100322258A1 · Dynarski · 2010 [cited by examiner]
US 20120003933A1 · Baker · 2012 [cited by examiner]
US 20120047551A1 · Pattar et al. · 2012 [cited by applicant]
US 20120089726A1 · Doddavula · 2012 [cited by examiner]
US 20120278454A1 · Stewart · 2012 [cited by examiner]
US 20130294285A1 · Zhang · 2013 [cited by examiner]
US 20140122878A1 · Cho et al. · 2014 [cited by applicant]
US 20140136690A1 · Jain · 2014 [cited by examiner]
US 20140351099A1 · Zhu · 2014 [cited by examiner]
US 20150007169A1 · Li · 2015 [cited by examiner]
US 20150172392A1 · Jean · 2015 [cited by examiner]
US 20150223186A1 · Pierrel et al. · 2015 [cited by applicant]
US 20150276925A1 · Scholten · 2015 [cited by examiner]
US 20150281116A1 · Ko · 2015 [cited by examiner]
US 20150334591A1 · Keshavdas et al. · 2015 [cited by applicant]
US 20150373481A1 · Eom · 2015 [cited by examiner]
US 20160007137A1 · Ahn · 2016 [cited by examiner]
US 20160036918A1 · Lee · 2016 [cited by examiner]
US 20160055573A1 · Chen · 2016 [cited by examiner]
US 20160142868A1 · Kulkarni · 2016 [cited by examiner]
US 20160164728A1 · Chakrabarti · 2016 [cited by examiner]
US 20160165651A1 · Pathuri · 2016 [cited by examiner]
US 20160198323A1 · Sakamoto · 2016 [cited by examiner]
US 20160226732A1 · Kim · 2016 [cited by examiner]
US 20160275336A1 · Park · 2016 [cited by examiner]
US 20170261949A1 · Hoffmann · 2017 [cited by examiner]
US 20170331860A1 · Ofversten · 2017 [cited by examiner]
US 20180189667A1 · Tsou · 2018 [cited by examiner]
US 20180198755A1 · Domangue · 2018 [cited by examiner]
US 20180365977A1 · Inoue · 2018 [cited by examiner]
US 20180367616A1 · Yang · 2018 [cited by examiner]
US 20180375720A1 · Yang · 2018 [cited by examiner]
US 20190052993A1 · DiGirolamo · 2019 [cited by examiner]
US 20190104397A1 · Khan · 2019 [cited by examiner]
US 20190138318A1 · Yang · 2019 [cited by examiner]
US 20190149599A1 · Bartfai-Walcott · 2019 [cited by examiner]
US 20190154872A1 · Leduc · 2019 [cited by examiner]
US 20190238662A1 · Guibene · 2019 [cited by examiner]
US 20190296967A1 · Yang · 2019 [cited by examiner]
US 20190306024A1 · Petria · 2019 [cited by examiner]
US 20200036793A1 · Arai · 2020 [cited by examiner]
US 20200296553A1 · Glass · 2020 [cited by examiner]
US 20210141351A1 · Yang · 2021 [cited by examiner]
US 20210174137A1 · Kim · 2021 [cited by examiner]
US 20210266894A1 · Andresky · 2021 [cited by examiner]
US 20220021583A1 · Petria · 2022 [cited by examiner]
US 20220210008A1 · Yang · 2022 [cited by examiner]
US 20230048307A1 · Petria · 2023 [cited by examiner]
CN 102687547A · 2012 [cited by applicant]
CN 102932475A · 2013 [cited by examiner]
CN 205229700U · 2016 [cited by examiner]
WO 2014182706A1 · 2014 [cited by applicant]
WO 2017111828A1 · 2017 [cited by applicant]
WO WO2018004642A1 · 2018 [cited by examiner]
WO WO2018004643A1 · 2018 [cited by examiner]
WO WO2018009205A1 · 2018 [cited by examiner]
WO WO2018182661A1 · 2018 [cited by examiner]
EPO; Extended European Search Report issued in EP Patent Application No. 16907593.4; dated Nov. 13, 2019; 11 pages. [cited by applicant]
EPO; Office Action issued for EP Patent Application No. 16907593.4, dated Dec. 9, 2020; 5 pages. [cited by applicant]
EPO; Office Action issued in EP Patent Application No. 16907593.4, dated Sep. 2, 2021; 4 pages. [cited by applicant]
ETSI; “Machine-to-Machine Communications (M2M); M2M service requirements,” draft ETSI TS 102 689 V0.2.1; dated Nov. 3, 2009; 45 pages. [cited by applicant]
HGI; “Smart Home Architecture and System Requirements,” dated Dec. 2015; retrieved from the internet at www.homegatewayinitiative.org/userfiles/file/downloads/RD036Publication.pdf; 32 pages. [cited by applicant]
International Preliminary Report on Patentability for PCT Application No. PCT/US2016/040644, issued Jan. 1, 2019, 8 pages. [cited by applicant]
International Search Report mailed Mar. 29, 2017 for PCT/US2016/040644, 3 pages. [cited by applicant]
Li, Weihua, et al.; “Update of draft Recommendation ITU-T Y.gw-IoT-reqts, “Common requirements and capabilities of gateway for IoT applications”: output from the Q2IL3 Sep. 16-20, 2013 e-meeting,” International Telecomm… [cited by applicant]
SIPO; First Office Action issued in CN Patent Application No. 201680086360.5, dated Oct. 26, 2020; 5 pages without English translation. [cited by applicant]
Written Opinion of the International Searching Authority mailed Mar. 29, 2017 for PCT/US2016/040644, 6 pages. [cited by applicant]
Young, Joo Jae, et al., “A Design of Integrated Gateway for Variety IoT Devices Management”, Proceedings of Symposium of the Korean Institute of Communications and Information Sciences, Nov. 30, 2015, pp. 234-235. [cited by applicant]
EPO; Office Action issued in EP Patent Application No. 16907593.4, dated Jan. 25, 2023; 4 pages. [cited by applicant]
“IoT application support models; Y.2078 (Feb. 2016)” ITU-T Standard, International Telecommunication Union, Geneva; Ch, No. Y.2078 (Feb. 2016), Feb. 13, 2016 (Feb. 13, 2016), pp. 1-56, XP044163828, [retrieved on Apr. 11… [cited by applicant]
Bauer Martin et al: “IoT Reference Model” 1-20 In: “Enabling Things to Talk”, Jan. 1, 2013 (Jan. 1, 2013), Springer Berlin Heidelberg, Berlin, Heidelberg, XP055812270, ISBN: 978-3-642-40403-0 pp. 113-162, DOI: 10.1007/9… [cited by applicant]
EPO European Extended Search Report in EP Application Serial No. 23187557.6 mailed on Jan. 26, 2024, 14 pages. [cited by applicant]
Weihua Li ZTE Corporation PR China: “Update of draft Recommendation ITU-T Y.gw-IoT-reqts, “Common requirements and capabilities of gateway for IoT applications”: output from the Q2/13 Sep. 16-20, 2013 e- meeting;TDxxx(”… [cited by applicant]