More detailed explanation about LWM2M Gateway ?

[sbernard31]

I see there is a new concept introduce in LWM2M 1.2 : LWM2M Gateway.

Support for LwM2M gateway functionality; this allows non-LwM2M IoT devices as well as LwM2M devices behind a gateway to be connected to the LwM2M ecosystem and to manage those devices remotely.

but I can find details explanation and so I'm not sure to understand how it works. The only thing I found is object descriptions :

• LwM2M-Gateway
• LwM2M-Gateway-Routing

I looked at this because of this leshan question : eclipse-leshan/leshan#974

[hannestschofenig]

We actually made a mistake in the publication of the specification and did not include the description on how to use the gateway-related objects. We will obviously publish them as soon as possible. In the interim we will make the missing text available on the OMA website. I will discuss the procedures with the group at the weekly conference call.

[jpradocueva]

@hannestschofenig keep us in the loop if there is something to rectify in the current publication. Thanks

[jbuckAI]

Hi! Any chance that link for gateway usage is live?

[lodup29]

Any news on this? I still can’t find anything on the OMA website describing how those 2 objects shall be used.

Assuming that the end device is a LwM2M client, my best guess is that a gateway behaves as a server on one side, accepting registrations from end devices, then turns back and establish a new registration, specific to each end device, with its own server where the registration ID is build using a prefix (25//1, RW, by default could be the registration ID of the gateway itself) and the end device ID (25//0, registration ID of the end device when the later is a LwM2M client).

So, the added value of a Gateway over a simple proxy (LwM2M only context) would be to have a formal and automatic mean to identify the site (the ID of the gateway) of the end device through its connexion ID?

In this context, the gateway object would only be used by the main server to change the prefix of the registration ID for an end device, or for information purposes only. Unless the prefix extraction is performed by the server, the later wouldn’t care about the fact that a gateway is involved.

If the end device is not a LwM2M client, then I guess that the device ID wound typically rather be fixed by the configuration of the gateway itself.

But I can hardly put together the pieces of the Gateway Routing object. Basically, it’s a table where each entry combines an Object ID (referred to as the “source of the mapping”) and mapping information which basically points to a single resource (referred to as the “destination of the mapping”) using the Corelnk type (ex.: <3303/0/9002>;rt=“oma.lwm2m”) .
Referencing an entry from the routing table is optional for an instance (device) of the Gateway object, but if it does, it can only reference a single entry (Objlnk type cannot reference multiple instances).

I can’t think of a context where it would make sense to publish the mapping info of at most one object ID per device and have that object ID associated with a single resource.

[sbernard31]

@lodup29, @jbuckAI the specification is released at : http://www.openmobilealliance.org/release/LwM2M_Gateway/

[hannestschofenig]

Since there are no further questions about the gateway specification I will close this issue.