# US 2023/0403320 A1 · Lwm2m server device, lwm2m client device, and methods thereof

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

- Number: US 2023/0403320 A1
- Document ID: US20230403320A1
- Status: Published application
- Kind: A1
- Application number: 18/034,741
- Filed: 2020-11-02
- Published: 2023-12-14
- Earliest claimed: 2020-11-02
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: Telefonaktiebolaget LM Ericsson (publ)
- Inventors: Oscar NOVO DIAZ
- Web page: https://patentgrep.com/patent/US20230403320A1

## CPC

- H04L 67/1044: {Group management mechanisms (management of multicast group membership H04L12/185; reconfiguring of node membership in a computing system to eliminate errors G06F11/1425)}
- H04L 67/125: involving control of end-device applications over a network
- H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)}
- H04L 67/55: Push-based network services
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Group management of LwM2M devices over MQTT A Lightweight Machine to Machine (LwM2M) server device is disclosed that is operable to run a LwM2M server and a Message Queueing Telemetry Transport (MQTT) client. The LwM2M server device comprises processing circuitry configured to cause the LwM2M server device to determine (310) that a LwM2M management operation should be performed on LwM2M clients fulfilling a criterion, and to identify (320) a LwM2M group management topic corresponding to the criterion, a LwM2M group management topic comprising a topic within a LwM2M namespace that is nonspecific to a particular LwM2M endpoint. The processing circuitry is further configured to cause the LwM2M server device to publish (330) a group management message to an MQTT server, the group management message specifying the identified LwM2M group management topic and the management operation to be performed. Also disclosed are a LwM2M client device and associated methods.

## Claims

### Claim at position 1

1-31. (canceled)

### Claim 32

A Lightweight Machine to Machine (LwM2M) server device operable to run a LwM2M server and a Message Queueing Telemetry Transport (MQTT) client, the LwM2M server device comprising processing circuitry configured to cause the LwM2M server device to:
determine that a LwM2M management operation should be performed on LwM2M clients fulfilling a criterion;
identify a LwM2M group management topic corresponding to the criterion wherein the LwM2M group management topic is a Unicode Transformation Format-8-bit (UTF-8) string that an MQTT server uses to filter messages for each connected client, LwM2M group management topic is within a LwM2M namespace and the LwM2M group management topic is nonspecific to a particular LwM2M endpoint, and the criterion provides a link between LwM2M client devices to be managed and the group management topic; and
publish a group management message to the MQTT server, the group management message specifying: the identified LwM2M group management topic and the management operation to be performed.

### Claim 33 (depends on 32)

The LwM2M server device of claim 32, wherein the processing circuitry is further configured to cause the LwM2M server device to:
set a parameter in the group management message to instruct behaviour for any LwM2M clients to which the group management message is forwarded by the MQTT server and which are unable to interpret the group management message; and
if the parameter in the group management message indicates that any LwM2M clients to which the group management message is forwarded by the MQTT server and which are unable to interpret the group management message may not ignore the group management message, receive an error message, forwarded by the MQTT server, from any LwM2M client to which the group management message was forwarded and which was unable to interpret the group management message.

### Claim 34 (depends on 32)

The LwM2M server device of claim 32, wherein the processing circuitry is further configured to cause the LwM2M server device to:
publish an automatic subscribe message to the MQTT server instructing the MQTT server to subscribe a LwM2M client to at least one LwM2M group management topic.

### Claim 35 (depends on 34)

The LwM2M server device of claim 34, wherein the processing circuitry is further configured to cause the LwM2M server device to:
include an identification of the LwM2M client in a topic specified in the automatic subscribe message; and
identify the group management topic or topics to which the LwM2M client is to be subscribed in the payload of the automatic subscribe message.

### Claim 36 (depends on 32)

The LwM2M server device of claim 32, wherein the processing circuitry is further configured to cause the LwM2M server device to:
publish an automatic unsubscribe message to the MQTT server instructing the MQTT server to unsubscribe a LwM2M client from at least one LwM2M group management topic.

### Claim 37 (depends on 36)

The LwM2M server device of claim 36, wherein the processing circuitry is further configured to cause the LwM2M server device to:
include an identification of the LwM2M client in a topic specified in the automatic unsubscribe message; and
identify the group management topic or topics from which the LwM2M client is to be unsubscribed in the payload of the automatic unsubscribe message.

### Claim 38 (depends on 32)

The LwM2M server device of claim 32, wherein the processing circuitry is further configured to cause the LwM2M server device to:
instruct a LwM2M client to subscribe to at least one group management topic with the MQTT server by:
publishing a subscription management message to the MQTT server for forwarding to the LwM2M client, the subscription management message including:
a topic including an identifier of the LwM2M client;
an identification of the “write” management operation; and
a payload including: an identification of an object instance hosted at the LwM2M client on which the write operation is to be performed and the group management topics to be written to the object instance and to which the LwM2M client should subscribe.

### Claim 39 (depends on 38)

The LwM2M server device of claim 38, wherein the processing circuitry is further configured to cause the LwM2M server device to:
create a new LwM2M object instance to be hosted at the LwM2M client, the new object instance being created for storing group management topics to which the LwM2M client should subscribe.

### Claim 40 (depends on 39)

The LwM2M server device of claim 39, wherein the processing circuitry is further configured to cause the LwM2M server device to create the new LwM2M object instance by:
publishing an object management message to the MQTT server for forwarding to the LwM2M client, the object management message including:
a topic including an identifier of the LwM2M client;
an identification of the “create” management operation; and
a payload including an identification of the LwM2M object instance to be created.

### Claim 41

A Lightweight Machine to Machine (LwM2M) client device operable to run a LwM2M client and a Message Queueing Telemetry Transport (MQTT) client, the LwM2M client device comprising processing circuitry configured to cause the LwM2M client device to:
receive a group management message published by a LwM2M server and forwarded to the LwM2M client device by an MQTT server, the group management message specifying:
a LwM2M group management topic wherein the LwM2M group management topic is a Unicode Transformation Format-8-bit (UTF-8) string that the MQTT server uses to filter messages for each connected client, LwM2M group management topic is within a LwM2M namespace and the LwM2M group management topic is nonspecific to a particular LwM2M endpoint; and
a management operation to be performed by the LwM2M client device; and
initiate performance of the management operation.

### Claim 42 (depends on 41)

The LwM2M client device of claim 41, wherein the processing circuitry is further configured to cause the LwM2M client device to:
if the LwM2M client device is unable to interpret the received group management message, check for a parameter in the received group management message, the parameter instructing behaviour for any LwM2M client that is forwarded the group management message and is unable to interpret the group management message; and
ignore the group management message or send an error message to the MQTT server according to whether or not the parameter is present.

### Claim 43 (depends on 42)

The LwM2M client device of claim 42, wherein the processing circuitry is further configured to cause the LwM2M client device to:
if the LwM2M client device is unable to interpret the received group management message and the parameter is present in the received group management message, ignore the group management message or send an error message to the MQTT server according to a value of the parameter.

### Claim 44

A method performed by a Lightweight Machine to Machine (LwM2M) server device operable to run a LwM2M server and a Message Queueing Telemetry Transport (MQTT) client, the method comprising:
determining that a LwM2M management operation should be performed on LwM2M clients fulfilling a criterion;
identifying a LwM2M group management topic corresponding to the criterion wherein the LwM2M group management topic is a Unicode Transformation Format-8-bit (UTF-8) string that an MQTT server uses to filter messages for each connected client, LwM2M group management topic is within a LwM2M namespace and the LwM2M group management topic is nonspecific to a particular LwM2M endpoint and the criterion provides a link between LwM2M client devices to be managed and the group management topic; and
publishing a group management message to the MQTT server, the group management message specifying: the identified LwM2M group management topic and the management operation to be performed.

### Claim 45 (depends on 44)

The method of claim 44, further comprising:
setting a parameter in the group management message to instruct behaviour for any LwM2M clients to which the group management message is forwarded by the MQTT server and which are unable to interpret the group management message; and if the parameter in the group management message indicates that any LwM2M clients to which the group management message is forwarded by the MQTT server and which are unable to interpret the group management message may not ignore the group management message, receiving an error message, forwarded by the MQTT server, from any LwM2M client to which the group management message was forwarded and which was unable to interpret the group management message.

### Claim 46 (depends on 44)

The method of claim 44, further comprising:
publishing an automatic subscribe message to the MQTT server instructing the MQTT server to subscribe a LwM2M client to at least one LwM2M group management topic.

### Claim 47 (depends on 46)

The method of claim 46, further comprising:
including an identification of the LwM2M client in a topic specified in the automatic subscribe message; and
identifying the group management topic or topics to which the LwM2M client is to be subscribed in the payload of the automatic subscribe message.

### Claim 48 (depends on 44)

The method of claim 44, further comprising:
publishing an automatic unsubscribe message to the MQTT server instructing the MQTT server to unsubscribe a LwM2M client from at least one LwM2M group management topic.

### Claim 49 (depends on 48)

The method of claim 48, further comprising:
including an identification of the LwM2M client in a topic specified in the automatic unsubscribe message; and
identifying the group management topic or topics from which the LwM2M client is to be unsubscribed in the payload of the automatic unsubscribe message.

### Claim 50 (depends on 44)

The method of claim 44, further comprising:
instructing a LwM2M client to subscribe to at least one group management topic with the MQTT server by:
publishing a subscription management message to the MQTT server for forwarding to the LwM2M client, the subscription management message including:
a topic including an identifier of the LwM2M client;
an identification of the “write” management operation; and
a payload including:
an identification of an object instance hosted at the LwM2M client on which the write operation is to be performed; and
the group management topics to be written to the object instance and to which the LwM2M client should subscribe.

### Claim 51 (depends on 44)

A computer program product comprising non-transitory computer readable medium storing a computer program comprising instructions which, when executed by processing circuitry of a Lightweight Machine to Machine (LwM2M) server causes the LwM2M server to perform the method of claim 44.
