Service Provision To IoT Devices

• US 20190349254A1
• Filed: 12/28/2017
• Published: 11/14/2019
• Est. Priority Date: 12/30/2016
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Nolan, Keith, Kelly, Mark, Nolan, Michael, Carboni, Davide, Ni Scanaill, Cliodhna, Ryan, Eugene, Davies, Richard, Brady, John
• Granted Patent: US 11,296,935 B2
• Time in Patent Office: Days
• CPC Class Codes: G06F 16/1824 implemented using Network-attached Storage [NAS] architecture distributed or networked storage systems G06F3/067; protocols for distributed storage of data in a network H04L67/1097
• CPC Class Codes: G06F 16/1834 implemented based on peer-to-peer networks, e.g. gnutella p2p communication protocols H04L67/104
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 45/20 Hop count for routing purposes, e.g. TTL
• CPC Class Codes: H04L 61/3025 Domain name generation or assignment
• CPC Class Codes: H04L 61/4505 using standardised directories; using standardised directory access protocols
• CPC Class Codes: H04L 61/5069 for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04L 61/5092 by self-assignment, e.g. picking addresses at random and testing if they are already in use
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/1046 Joining mechanisms
• CPC Class Codes: H04L 67/1093 Some peer nodes performing special functions
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/562 Brokering proxy services
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 9/0825 using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates
• CPC Class Codes: H04L 9/3239 : involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/50 : using hash chains, e.g. blockchains or hash trees
• CPC Class Codes: H04W 12/106 : Packet or message integrity
• CPC Class Codes: H04W 12/69 : Identity-dependent
• CPC Class Codes: H04W 12/76 : Group identity
• CPC Class Codes: H04W 4/08 : User group management
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 84/18 : Self-organising networks, e.g. ad-hoc networks or sensor networks
• CPC Class Codes: H04W 84/22 : with access to wired networks

Abstract

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.

Claims

1-37. -37. (canceled)

38. An apparatus, comprising an Internet-of-Things (IoT) network, wherein the IoT network comprises devices comprising:

an orchestrator to issue service management requests to a service coordinator to form a service;

the service coordinator to identify a plurality of components to participate in the service; and

a component to perform a network service element for the service.

39. The apparatus of claim 38, wherein the orchestrator manages a plurality of network service overlays to perform tasks.

40. The apparatus of claim 39, comprising a shared repository comprising the plurality of network service overlays.

41. The apparatus of claim 39, wherein a network service overlay comprises a code segment to allow the component to perform the network service element.

42. The apparatus of claim 38, wherein the service coordinator comprises:

a database to store data or metadata or both from a component;

a shared virtual repository to hold a network service element needing completion; and

a machine learning engine to select the component to complete the network service element.

43. The apparatus of claim 42, wherein the shared virtual repository stores an identity of the component assigned to the network service element.

44. The apparatus of claim 38, wherein the service comprises a plurality of network service elements, and wherein the network service elements are completed by the plurality of components.

45. The apparatus of claim 38, wherein the service comprises a fog device comprising a plurality of internet-of-things (IoT) devices.

46. The apparatus of claim 38, wherein the service coordinator comprises a network domain controller.

47. The apparatus of claim 38, wherein the component is a device comprising a client, and wherein the client registers the device with the service coordinator.

48. The apparatus of claim 47, wherein the client sends a message comprising attached sensors, actuators, or devices, or any combinations thereof, the service coordinator.

49. The apparatus of claim 38, wherein the plurality of components is selected from multiple domains.

50. A method for completing service requests, comprising:

receiving an orchestration request at a network domain controller;

determining if the orchestration request is for an existing service; and

if the orchestration request is for an existing service, sending the orchestration request to a service coordinator.

51. The method of claim 50, comprising, if the orchestration request is a new request:

preparing a service model comprising a network service element;

preparing the network service element;

identifying a service component to perform the network service element; and

dispatching a subscription request to the service component to perform an action for the network service element.

52. The method of claim 51, comprising identifying a service coordinator.

53. The method of claim 51, wherein identifying a service component comprises:

accessing data on historic performance of a plurality of service components; and

using a machine learning technique to select the service component.

54. The method of claim 51, comprising:

validating the subscription request at the service component; and

sending a confirmation to the service coordinator if the subscription request is valid.

55. The method of claim 54, comprising sending a denial to the service coordinator if the subscription request is not valid.

56. The method of claim 54, wherein a subscription request is valid if it is supported by the service component.

57. The method of claim 50, comprising:

performing the network service element in the service component; and

returning data from the service component to the service coordinator.

58. The method of claim 50, wherein the service component downloads a network service overlay from a virtual shared repository to perform the network service element.

59. The method of claim 51, wherein the service component downloads a network service overlay from a shared repository in a cloud.

60. The method of claim 50, comprising sending a message comprising capabilities of a service component to a service coordinator to register the service component.

61. A non-transitory, machine readable medium comprising instructions that, when executed, direct one or more processors to:

identify a service coordinator;

prepare network elements;

identify service components; and

send subscription requests to service components.

62. The non-transitory, machine readable medium of claim 61, comprising instructions that, when executed, direct the one or more processors to:

validate a subscription request;

perform and action for a network service element; and

send data to the service coordinator.

63. The non-transitory, machine readable medium of claim 61, comprising instructions that, 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.