# US 2021/0084470 A1 · Enable reliable and distributed m2m/iot services

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0084470 A1
- Document ID: US20210084470A1
- Status: Published application
- Kind: A1
- Application number: 16/611,924
- Filed: 2018-05-11
- Published: 2021-03-18
- Earliest claimed: 2017-05-12
- Assignees: Convida Wireless, LLC
- Applicants: Convida Wireless, LLC
- Inventors: Zhuo CHEN; Dale N. SEED; Quang LY; Catalina Mihaela MLADIN; William Robert FLYNN, IV; Rocco DI GIROLAMO; Shoshana LOEB; Chonggang WANG; Michael F. STARSINIC
- Web page: https://patentgrep.com/patent/US20210084470A1

## CPC

- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- G06F 11/1451: {by selection of backup contents}
- 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
- H04L 69/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)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A registration procedure may allow one active and multiple inactive SL registrations to be created at different service layer entities for an application entity without adding significant overhead and burden to an application entity.

## Claims

### Claim 1

An apparatus that enables backup service layer entities, the apparatus comprising:
a processor; and
a memory coupled with the processor, the memory comprising executable instructions stored thereon that when executed by the processor cause the processor to effectuate operations comprising:
obtaining, from an application entity, a request message to register with the apparatus, wherein the apparatus is a service layer registrar entity;
based on the request message, reporting the request message to a server; and
based on the reported request message, obtaining a list of one or more inactive service layer entities that are used as backup for the application entity, wherein the reported request message comprises a reliability requirement for active service layer entities or inactive service layer entities.

### Claim 2 (depends on 1)

The apparatus of claim 1, the operations further comprising triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional.

### Claim 3 (depends on 1)

The apparatus of claim 1, the operations further comprising triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional, wherein a determination of non-functional is based on the apparatus not meeting the reliability requirement.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the apparatus is an active service layer registrar entity for the application entity, the operations further comprising:
triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional; and
when the apparatus is functional, sending a message to add the apparatus to the list of inactive service layer entities that are used as backup for the application entity.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the request message comprises a minimum number of inactive service layer entities required.

### Claim 6 (depends on 1)

The apparatus of claim 1, the operations further comprising creating an inactive registration using an identifier.

### Claim 7 (depends on 1)

The apparatus of claim 1, the operations further comprising sending an inactive registration request to create an inactive service layer entity for the application entity.

### Claim 8

A method comprising:
obtaining, from an application entity, a request message to register with an apparatus, wherein the apparatus is a service layer registrar entity;
based on the request message, reporting, the request message to a server; and
based on the reported request message, obtaining a list of one or more inactive service layer entities that are used as backup for the application entity, wherein the reported request message comprises a reliability requirement for active service layer entities or inactive service layer entities.

### Claim 9 (depends on 8)

The method of claim 8, further comprising triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional.

### Claim 10 (depends on 8)

The method of claim 8, further comprising triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional, wherein a determination of non-functional is based on the apparatus not meeting the reliability requirement.

### Claim 11 (depends on 8)

The method of claim 8, wherein the request message comprises a minimum number of inactive service layer entities required.

### Claim 12 (depends on 8)

The method of claim 8, further comprising creating an inactive registration using an identifier.

### Claim 13 (depends on 8)

The method of claim 8, further comprising sending an inactive registration request to create an inactive service layer entity for the application entity.

### Claim 14 (depends on 8)

The method of claim 8, wherein the apparatus is an active service layer registrar entity for the application entity, and further comprising:
triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional; and
when the apparatus is functional, adding the apparatus to the list of inactive service layer entities that are used as backup for the application entity.

### Claim 15

A computer-readable storage medium storing computer executable instructions that when executed by a computing device cause said computing device to effectuate operations comprising:
obtaining, from an application entity, a request message to register with an apparatus, wherein the apparatus is a service layer registrar entity;
based on the request message, reporting the request message to a server; and
based on the reported request message, obtaining a list of one or more inactive service layer entities that are used as backup for the application entity, wherein the reported request message comprises a reliability requirement for active service layer entities or inactive service layer entities.

### Claim 16 (depends on 15)

The apparatus of claim 15, the operations further comprising triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional.

### Claim 17 (depends on 15)

The apparatus of claim 15, the operations further comprising triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional, wherein a determination of non-functional is based on the apparatus not meeting the reliability requirement.

### Claim 18 (depends on 15)

The apparatus of claim 15, wherein the apparatus is an active service layer registrar entity for the application entity, the operations further comprising:
triggering a first inactive service layer entity of the list of one or more inactive service layer entities to become active when the apparatus is non-functional; and
when the apparatus is functional, sending a message to add the apparatus to the list of inactive service layer entities that are used as backup for the application entity.

### Claim 19 (depends on 15)

The apparatus of claim 15, wherein the request message comprises a minimum number of inactive service layer entities required.

### Claim 20 (depends on 15)

The apparatus of claim 15, the operations further comprising sending an inactive registration request to create an inactive service layer entity for the application entity.
