# US 10,771,335 B2 · Generating and sharing models for Internet-of-Things data > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,771,335 B2 - Document ID: US10771335B2 - Status: Granted - Kind: B2 - Application number: 15/657,716 - Filed: 2017-07-24 - Published: 2019-01-24 - Granted: 2020-09-08 - Earliest claimed: 2017-07-24 - Assignees: Verizon Patent and Licensing Inc. - Applicants: Verizon Patent and Licensing Inc. - Inventors: Ming Chen; Ira C. Stevens, III; Zhong Chen; Matthew J. Threefoot - Web page: https://patentgrep.com/patent/US10771335B2 ## CPC - H04L 41/0866: Checking the configuration - H04L 41/0856: {by backing up or archiving configuration information} - H04L 41/145: {involving simulating, designing, planning or modelling of a network} - G06Q 10/067: Enterprise or organisation modelling - H04L 61/5007: Internet protocol [IP] addresses - 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 ## Abstract A network device stores capability designations associated with Internet-of-Things (IoT) devices and receives, from a customer device, one or more of the capability designations associated with a first type of IoT device. The network device receives event data generated by the first type of IoT device and maps the event data to the one or more of the capability designations. The mapping produces normalized IoT data for the first type of IoT device. The network device generates semantic information for the normalized IoT data and assembles a device model for the first type of IoT device. The device model includes the one or more of the capability designations and the semantic information. ## Claims ### Claim 1 A method, comprising: storing, by a network device, a catalog of capability designations for different types of Internet-of-Things (IoT) devices; receiving, by the network device and from a customer device, selection from the catalog of one or more of the capability designations, associated with a first type of IoT device; receiving, by the network device and after receiving the selection of the capability designations, event data generated by the first type of IoT device; mapping, by the network device, the event data to the one or more of the capability designations, wherein the mapping produces normalized IoT data for the first type of IoT device; generating, by the network device, semantic information for the normalized IoT data; assembling, by the network device, a data model for the first type of IoT device, wherein the data model includes the one or more of the capability designations and the semantic information and wherein the data model governs how data for the first type of IoT device is at least one of collected, stored, or presented; storing, by the network device and in a memory, the data model; receiving, by the network device and from a service or organization, an approval indication for the data model; and converting, by the network device and after receiving the approval indication, the data model to a public model that is accessible to other customers. ### Claim 2 (depends on 1) The method of claim 1, wherein the converting comprises disassembling the data model to various data fields and mapping the various data fields to capabilities that correspond to the capability designations. ### Claim 3 (depends on 1) The method of claim 1, further comprising: adding, by the network device, the public model to a catalog listing. ### Claim 4 (depends on 1) The method of claim 1, further comprising: assigning a network address for the normalized IoT data, wherein the network address includes access restrictions. ### Claim 5 (depends on 1) The method of claim 1, further comprising: receiving, by the network device, additional event data generated by the first type of IoT device; mapping, by the network device, the additional event data to the one or more of the capability designations; generating, by the network device, updated semantic information for the normalized IoT data; and revising, by the network device, the data model based on the updated semantic information. ### Claim 6 (depends on 1) The method of claim 1, wherein the event data generated by the first type of IoT device includes the one or more of the capability designations. ### Claim 7 (depends on 1) The method of claim 1, wherein storing the data model further includes storing the data model to a customer account accessible to only a customer. ### Claim 8 (depends on 1) The method of claim 1, further comprising: receiving, by the network device and from the customer device, another selection from the catalog of one or more of the capability designations associated with a second type of IoT device; receiving, by the network device, event data generated by the second type of IoT device; mapping, by the network device, the event data to the one or more of the capability designations associated with the second type of IoT device, wherein the mapping produces normalized IoT data for the second type of IoT device; generating, by the network device, other semantic information for the normalized IoT data for the second type of IoT device; assembling, by the network device, another data model for the second type of IoT device, wherein the other data model includes the one or more of the capability designations associated with the second type of IoT device and the other semantic information; and storing, by the network device, the other data model associated with the second type of IoT device. ### Claim 9 (depends on 8) The method of claim 8, wherein at least one of the capability designations associated with the first type of IoT device and the capability designations associated with the second type of IoT device are the same. ### Claim 10 One or more network devices, comprising: a memory for storing instructions; and one or more processors configured to execute the instructions to: store a catalog of capability designations for different types of Internet-of-Things (IoT) devices; receive, from a customer device, selection from the catalog of one or more of the capability designations, associated with a first type of IoT device; receive, after receiving the selection of the capability designations, event data generated by the first type of IoT device; map the event data to the one or more of the capability designations, wherein the mapping produces normalized IoT data for the first type of IoT device; generate semantic information for the normalized IoT data; assemble a data model for the first type of IoT device, wherein the data model includes the one or more of the capability designations and at least some of the semantic information and wherein the data model governs how data for the first type of IoT device is at least one of collected, stored, or presented; store in the memory the data model; receive, from a service or organization, an approval indication for the data model; and convert, after receiving the approval indication, the data model to a public model that is accessible to other customers. ### Claim 11 (depends on 10) The one or more network devices of claim 10, wherein, when converting the data model, the one or more processors are further configured to execute the instructions to: disassemble the data model to various data fields and map the various data fields to capabilities that correspond to the capability designations. ### Claim 12 (depends on 10) The one or more network devices of claim 10, wherein the one or more processors are further configured to execute the instructions to: add the public model to a catalog listing. ### Claim 13 (depends on 10) The one or more network devices of claim 10, wherein the one or more processors are further configured to execute the instructions to: assign a network address for the normalized IoT data, wherein the network address includes access restrictions. ### Claim 14 (depends on 10) The one or more network devices of claim 10, wherein the one or more processors are further configured to execute the instructions to: receive additional event data generated by the first type of IoT device; map the additional event data to the one or more of the capability designations; generate updated semantic information for the normalized IoT data; and revise the data model based on the updated semantic information. ### Claim 15 (depends on 10) The one or more network devices of claim 10, wherein the event data generated by the first type of IoT device includes one or more of the capability designations. ### Claim 16 A non-transitory computer-readable medium containing instructions executable by at least one processor, the computer-readable medium comprising one or more instructions to cause the at least one processor to: store a catalog of capability designations for different types of Internet-of-Things (IoT) devices; receive, from a customer device, selection from the catalog of one or more of the capability designations, associated with a first type of IoT device; receive, after receiving the selection of the capability designations, event data generated by the first type of IoT device; map the event data to the one or more of the capability designations, wherein the mapping produces normalized IoT data for the first type of IoT device; generate semantic information for the normalized IoT data; assemble a data model for the first type of IoT device, wherein the data model includes the one or more of the capability designations and the semantic information and wherein the data model governs how data for the first type of IoT device is at least one of collected, stored, or presented; store in a memory the data model; receive, from a service or organization, an approval indication for the data model; and convert, after receiving the approval indication, the data model to a public model that is accessible to other customers. ### Claim 17 (depends on 16) The non-transitory computer-readable medium claim 16, further comprising one or more instructions to cause the at least one processor to: add the public model to a catalog listing. ### Claim 18 (depends on 16) The non-transitory computer-readable medium claim 16, wherein the instructions to store the data model further include instructions to store the data model to a customer account. ### Claim 19 (depends on 16) The non-transitory computer-readable medium claim 16, further comprising one or more instructions to cause the at least one processor to: receive, from the customer device, selection from the catalog of one or more of the capability designations associated with a second type of IoT device; receive event data generated by the second type of IoT device; map the event data to the one or more of the capability designations associated with the second type of IoT device, wherein the mapping produces normalized IoT data for the second type of IoT device; generate other semantic information for the normalized IoT data for the second type of IoT device; assemble another data model for the second type of IoT device, wherein the other data model includes the one or more of the capability designations associated with the second type of IoT device and the other semantic information; and storing the other data model associated with the second type of IoT device. ### Claim 20 (depends on 19) The non-transitory computer-readable medium claim 19, wherein at least one of the capability designations associated with a first type of IoT device and the capability designations associated with the second type of IoT device are the same.