Method and apparatus of interworking M2M and IoT devices and applications with different service layers

Patent metadata

Field	Value
Publication number	US-10999380-B2
Application number	US-201615579711-A
Country	US
Kind code	B2
Filing date	Jun 3, 2016
Priority date	Jun 5, 2015
Publication date	May 4, 2021
Grant date	May 4, 2021

Abstract

Methods and procedures allow devices interwork with various types of service layers by updating the device to support the protocol of the M2M/IoT service layer that is being communicated with. Devices can coordinate/initiate download of a service layer API that is compatible with the service layer the device is attempting to use. A service layer can coordinate the autonomous update of a device with the proper service layer API which allows the device to then communicate and use services supported by the service layer component to the device. A service layer can detect a device or application lacking proper service layer functionality and can trigger a management entity to update the device or application with the service layer API required such that the device can then register to the service layer and use its services. A device or application can be customized or optimized to the service layer that it is registered to and using.

First claim

What is claimed:

1. A first apparatus comprising a processor, a memory, and communication circuitry, the first apparatus being connected to a network via the communication circuitry, the first apparatus further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the first apparatus to:
send, to a second apparatus, a service layer registration request;
receive, from the second apparatus, a service layer registration response, the service layer registration response indicating that no compatible service layer is available at the second apparatus; and
send, to a third apparatus and based on the service layer registration response, the third apparatus being a device management service, an update request, the update request requesting that the third apparatus update the software of the first apparatus to be compatible with a service layer of the second apparatus.

2. The apparatus of claim 1 , wherein the service layer registration response comprises a service layer type.

3. The apparatus of claim 2 , wherein the instructions further cause the first apparatus to analyze the service layer registration response using service layer detection.

4. A second apparatus comprising a processor, a memory, and communication circuitry, the second apparatus being connected to a network via the communication circuitry, the second apparatus further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the second apparatus to:
receive, from a first apparatus, a service layer registration request, the service layer registration request comprising an indication of a device manager type;
determine, based upon the service layer registration request, whether a compatible service layer is available at the second apparatus;
if a compatible service layer is not available at the second apparatus, send to a third apparatus, the third apparatus being a device management service, an update request, the update request comprising an indication of the device manager type indicated in the service layer registration request; and
receive, from the third apparatus, a software update to the second apparatus's service layer to be compatible with the service layer of the first apparatus in accordance with the update request.

5. The second apparatus of claim 4 , wherein the service layer registration request comprises a list of compatible service layers.

6. The second apparatus of claim 4 , wherein the service layer registration request comprises a list of compatible device management devices.

7. The second apparatus of claim 4 , wherein the instructions further cause the second apparatus to send, to the first apparatus, a service layer registration response, the service layer registration response indicating at least one compatible service layer.

8. A second apparatus comprising a processor, a memory, and communication circuitry, the second apparatus being connected to a network via the communication circuitry, the second apparatus further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the second apparatus to:
receive, from a first apparatus, a service layer registration request, the service layer registration request comprising an indication of a device manager type;
determine, based upon the service layer registration request, whether a compatible service layer is available at the second apparatus; and
if a compatible service layer is not available at the second apparatus, send to a third apparatus, the third apparatus being a device management service, an update request, the update request requesting that the third apparatus update the service layer of the first apparatus to be compatible with the service layer of the second apparatus.

9. The apparatus of claim 8 , wherein the service layer registration request comprises a list of compatible service layers.

10. The apparatus of claim 8 , wherein the service layer registration request comprises a list of compatible device management devices.

11. The apparatus of claim 8 , wherein the instructions further cause the second apparatus to send, to the first apparatus, a service layer registration response, the service layer registration response indicating at least one compatible service layer.

Assignees

• Convida Wireless LLC

Inventors

• Flynn Iv William Robert
• Seed Dale N
• Russell Jr Paul L
• Starsinic Michael F
• Lu Guang
• Ly Quang
• Li Qing
• Rahman Shamim Akbar
• Brown Phillip
• Chen Zhuo
• Li Xu
• Choyi Vinod Kumar
• Dong Lijun
• Mladin Catalina M
• Wang Chonggang
• Li Hongkun

Classifications

• H04L67/34 Primary

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• H04L67/51 Primary

  Discovery or management thereof, e.g. service location protocol [SLP] or web services · CPC title

• H04W4/70

  Services for machine-to-machine communication [M2M] or machine type communication [MTC] · CPC title

• H04W4/50

  Service provisioning or reconfiguring · CPC title

• H04L69/40

  for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection (management of faults, events, alarms or notifications in data switching networks H04L41/06) · CPC title