Connectivity service level orchestrator and arbitrator in internet of things (iot) platforms
US-2019104437-A1 · Apr 4, 2019 · US
US11296935B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11296935-B2 |
| Application number | US-201716467002-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 28, 2017 |
| Priority date | Dec 30, 2016 |
| Publication date | Apr 5, 2022 |
| Grant date | Apr 5, 2022 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
An Internet of Things (IoT) network includes an orchestrator to issue service management requests, a service coordinator to identify components to participate in the service, and a component to perform a network service element. An IoT network includes an IoT device with service enumerator, contract enumerator, and join contract function. An IoT network apparatus includes permissions guide drafter for discovered peers, and permissions guide action executor. An IoT network apparatus includes floating service permissions guide drafter for discovered hosts, host hardware selector, floating service permissions guide executor, and service wallet value transferor. An IoT network apparatus includes permissions guide drafter for first and second discovered peers, parameter weight calculator, permissions guide term generator, and permissions guide action executor. An IoT network includes an IoT device with resource hardware component identifier, processor to process a received indication of an external module hardware requirement, an external module comparer, and deactivation signal transmitter.
Opening claim text (preview).
What is claimed is: 1. An apparatus for completing service requests, the apparatus comprising: an orchestrator to issue a service management request to form a service; a service coordinator including: a shared virtual repository to store a network service element to be performed, the network service element to execute one or more portions of the service; and a machine learning engine to select a component to participate in the service; and a client to, in response to obtaining a network service overlay from the shared virtual repository, execute the network service overlay on the component to execute the network service element for the service. 2. The apparatus of claim 1 , wherein the orchestrator is to manage a plurality of network service overlays to perform tasks, the plurality of the network service overlays including the network service overlay. 3. The apparatus of claim 2 , wherein the shared virtual repository includes the plurality of the network service overlays. 4. The apparatus of claim 1 , wherein the network service overlay includes a code segment to cause the component to perform execute the network service element. 5. The apparatus of claim 1 , wherein the service coordinator includes a database to store at least one of data from the component or metadata from the component. 6. The apparatus of claim 1 , wherein the shared virtual repository is to store an identity of the component assigned to the network service element. 7. The apparatus of claim 1 , wherein the service includes a plurality of network service elements including the network service element, ones of the plurality of network service elements to be completed by the component. 8. The apparatus of claim 1 , wherein the service includes a fog device, the fog device including a plurality of components, the plurality of components including the component. 9. The apparatus of claim 1 , wherein the service coordinator includes a network domain controller. 10. The apparatus of claim 1 , wherein the component is a device including the client, the client to register the device with the service coordinator. 11. The apparatus of claim 10 , wherein the client is to send a message to the service coordinator, the message including peripheral data corresponding to at least one of attached sensors, actuators, or devices. 12. The apparatus of claim 1 , wherein the machine learning engine is to select the component from one or more domains. 13. A method for completing service requests, the method comprising: in response to receiving an orchestration request to form a service, determining whether the orchestration request is for an existing service; in response to determining that the orchestration request is for the existing service, sending the orchestration request to a service coordinator; identifying a network service element to be performed, the network service element to execute one or more portions of the service; selecting a component with a machine learning engine, the component to participate in the service; and in response to obtaining a network service overlay from a shared virtual repository, executing the network service overlay on the component to execute the network service element for the service. 14. The method of claim 13 , further including, in response to determining that the orchestration request is a new request: preparing a service model including the network service element; preparing the network service element; identifying the component to perform the network service element; and dispatching a subscription request to the component to perform an action for the network service element. 15. The method of claim 14 , further including identifying the service coordinator. 16. The method of claim 14 , wherein identifying the component includes accessing data associated with historic performance of a plurality of components, the plurality of components including the component. 17. The method of claim 14 , further including: validating the subscription request at the component; and sending a confirmation to the service coordinator in response to validating the subscription request. 18. The method of claim 17 , further including sending a denial to the service coordinator in response to not validating the subscription request. 19. The method of claim 17 , wherein validating the subscription request includes determining whether the subscription request is supported by the component. 20. The method of claim 14 , wherein the component downloads the network service overlay from a shared repository in a cloud. 21. The method of claim 13 , further including: performing the network service element in the component; and returning data from the component to the service coordinator. 22. The method of claim 13 , wherein the component downloads the network service overlay from a virtual shared repository. 23. The method of claim 13 , further including sending a message to the service coordinator to register the component, the message including capabilities of the component. 24. A non-transitory machine readable medium comprising instructions that, when executed, direct one or more processors to: issue a service management request to a service coordinator to form a service; identify one or more network service elements to be performed, the one or more network service elements to execute one or more portions of the service; identify one or more service components with a machine learning engine, the one or more service components to participate in the service; send one or more subscription requests to the one or more service components; in response to the one or more subscription service requests, obtain a network service overlay from a shared virtual repository; and execute the network service overlay on a first one of the one or more service components to execute the network service element for the service. 25. The non-transitory machine readable medium of claim 24 , wherein the instructions, when executed, direct the one or more processors to: validate the one or more subscription requests; cause the one or more service components to perform the one or more network service elements for the service; and send data to the service coordinator. 26. The non-transitory machine readable medium of claim 24 , wherein the instructions, when executed, direct the one or more processors to: send a connection request to the service coordinator; and send device peripheral data to the service coordinator. 27. An apparatus for completing service requests, the apparatus comprising: at least one memory; instructions in the apparatus; and at least one processor to execute the instructions to: store a network service element to be performed for a service and a network service overlay to execute the network service element; select a component with a machine learning model to participate in the service; and provide the network service overlay to the component to cause the component to execute the network service overlay to perform a portion of the service. 28. The apparatus of claim 27 , wherein the network service element is a first network service element, the component is a first component, and the at least one processor is to: generate a service model based on a service management request to form the service, the service model including at least one of (i
Discovery or management of network topologies · CPC title
for initial configuration or provisioning, e.g. plug-and-play · CPC title
Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title
using hash chains, e.g. blockchains or hash trees · CPC title
using standardised directories; using standardised directory access protocols · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.