© 2018 oneM2M

Interworking of oneM2M service layer to underlying 3GPP 4G/5G Networks

Dale Seed

oneM2M Architecture Chair

Convida Wireless

© 2018 oneM2M

Background

• Increasing numbers of cellular IoT devices are starting to hit the market • E.g.- NB-IoT, LTE-M and higher category devices supporting functions such as video surveillance

• 3GPP has been adding IoT features starting in Rel-10 (2011) Rel-15 (2018)

• Features to avoid network congestion from massive numbers of IoT devices

• Features to maximize network resource utilization/efficiency to minimize deployment costs

• Features to keep network secure from the increased threats from IoT devices

• Features to maximize IoT device battery life

• Operators have started deploying support for these features in their networks

© 2018 oneM2M

A Typical Cellular IoT Deployment

3GPP Network

Apps

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT FeaturesIoT FeaturesCOMMAND

COMMAND COMMANDCOMMAND

DATA

DATADATA

DATA

DATA

DATADATA

• Use of 3GPP IoT features requires low-level knowledge of 3GPP and a business relationship with operator

(E.g. Configuration of IoT device sleep times requires intimate knowledge of 3GPP PSM and eDRX)

This presents a high barrier of use and adoption by typical IoT device manufacturers and app developers

• If devices and apps do not properly use these features, cellular IoT deployments are destined to fail

• Inefficient use of network resources higher costs and less scalability for operators

• Shortened battery life of devices inability to deploy cellular IoT devices in many IoT use cases

• Security threats to the network network, devices and application security will be compromised

© 2018 oneM2M

A oneM2M Cellular IoT Deployment

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

Apps

• oneM2M Rel-3 is the first IoT service layer standard to interwork with 3GPP IoT features

• oneM2M provides a complimentary set of value-add services that interwork with 3GPP IoT features

• oneM2M eases the use and adoption of 3GPP IoT features by IoT devices and apps

• oneM2M can be deployed internal or external to an operator’s network

• Enables an operator to move up the value-chain and offer additional value-add IoT services

SCEFT8

© 2018 oneM2M

Some Examples of oneM2M Cellular IoT Value-add Services

© 2018 oneM2M

IoT Device Service Enrollment

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

1. oneM2M app requests that

device enrolls and registers

Trigger

Enrolment Function

2. oneM2M Service Layer

triggers device

4. oneM2M enrolment function enrolls device and

bootstraps it with IDs and credentials

6. Device uses IDs and credentials to securely connect and register to oneM2M Service

Layer

Enrollment Response

3. Device receives trigger that contains

contact info for oneM2M enrollment function and sends it

an enrollment request

5. Device receives enrollment response

containing IDs and credentials

RequestEnrollment

Request

Registration Request

Registration Response

Notification

8. oneM2M Service Layer

notifies app that device is enrolled

and registered

7. oneM2M Service Layer

registers device

© 2018 oneM2M

IoT Device Sleep Schedule Management

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

2. oneM2M app(s) specify their

desired schedules to communicate

with a device

1. Apps on device specify their desired

communication schedule

5. Targeted Device is configured with PSM/eDRX timers

Schedule(s)

Schedule(s)

Notification

6. oneM2M Service Layer notifies app(s) of the

device’s schedule of availability

3. oneM2M Service Layer computes proposed

PSM/eDRX times based on aggregated schedule inputs from device and

app(s)

Proposed PSM/eDRX timers

4. 3GPP network considers proposed

PSM/eDRX timers for device and

determines actual timer values

Actual PSM/eDRX timers

© 2018 oneM2M

IoT Device Message Delivery Handling

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

4. A oneM2M App issues a

request targeting an IoT device

9. Device receives

request and responds

1. oneM2M Service Layer subscribes to 3GPP CN to

receive notifications when a device enters or exits

power savings mode

3. 3GPP CN notifies oneM2M

Service Layer device has

entered power savings mode

7. 3GPP CN notifies

oneM2M Service Layer device has

exited power savings mode

8. oneM2M Service Layer

sends buffered requests to

device now that it is reachable

Notify

5. oneM2M Service Layer buffers request until

device exits power savings mode and

becomes reachable

Subscribe

2. Device enters power savings mode

(PSM/eDRX) to conserve its battery

Request

NotifyRequest

Response

10. oneM2M Service Layer

returns response6. Device exits power savings

mode (PSM/eDRX)

Response

© 2018 oneM2M

IoT Device Location Tracking

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

1. A oneM2M App asks to be

notified if/when device leaves

specified geofenced area

2. oneM2M Service Layer subscribes to 3GPP CN to receive location updates

for specified device

5. 3GPP CN detects device’s current

location has changed and sends a notification

6. oneM2M Service Layer receives device’s current

location, compares it against geofenced area and detects

device has left the area

Notify

Subscribe

4. Device moves to a new location

Request

Notification

7. oneM2M Service Layer notifies device has left geofenced area

3. 3GPP CN monitors the current location of

the device to detect changes

© 2018 oneM2M

3GPP Network Congestion Control

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

3. A oneM2M App sends a

request targeting a device in

congested area of network

1. oneM2M Service Layer subscribes to 3GPP CN to receive

network status notifications

4. Congestion detected in particular location of network and notification is

sent

4. oneM2M Service Layer checks location of targeted device and detects it is in

congested area of network so it buffers the request

Notify

Subscribe

Request

Response

7. oneM2M Service Layer returns

response

2. Congestion detected in particular location of

network and notification is sent

4. Congestion detected in particular location of network and notification is

sent

5. Congestion eventually subsides and

notification is sent

Notify

Request

6. oneM2M Service Layer detects

congestion has subsided and sends

buffered request

Response

© 2018 oneM2M

Non-IP Data Delivery (NIDD)

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

6. A oneM2M App samples

sensor reading

1. oneM2M Service Layer issues NIDD configuration

request for device that enrolls with NIDD

capability

4. oneM2M Service Layer processes request and returns a response

2. 3GPP CN processes NIDD configuration and will know where

to send NIDD data when the UE establishes a PDN connection

NIDD Config

3. Device sends an uplink oneM2M request over

the control plane of 3GPP CN using NIDD

(e.g. sensor reading)

RequestoneM2M

Request via NIDD

Response

7. oneM2M Service Layer returns

response (e.g. sensor reading)

oneM2M Response via NIDD

5. (optional) Device receives an downlink oneM2M response

via NIDD

© 2018 oneM2M

IoT Device Tampering Detection

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

5. A oneM2M app sends request

targeting device that has been

tampered with

1. oneM2M Service Layer subscribes to 3GPP CN to receive device tampering

notifications

4. Congestion detected in particular location of network and notification is

sent

4. oneM2M stops servicing requests to/from tampered

device.

Notify

Subscribe

Request

Response

7. oneM2M Service Layer returns error

response

3. Change in IMSI-IMEI is detected. A notification

is generated

Request

2. A device’s SIM card is tampered with (i.e. removed and swapped out with

another SIM)

X

6. oneM2M stops servicing requests to/from tampered

device

4. The tampered device issues a

request

© 2018 oneM2M

Management of Groups of IoT Devices

3GPP Core Network

Cellular IoT Devices (NB-IoT, LTE-M)

IoT Server

IoT Features

Service Layer

AppsSCEF

1. A oneM2M app sends request to

form a group devices

3. oneM2M Service Layer requests 3GPP

CN to establish a MBMS group with an assigned TMGI

Allocate TMGI

Group Formation

Request

7. A oneM2M app sends request to a group of devices

6. Devices receive unicast request to join MBMS group

2. oneM2M Service Layer

detects if devices are 3GPP MBMS

multicast capable

5. oneM2M Service Layer sends requests to devices

to join MBMS group

Unicast Requests to join

MBMS group

4. 3GPP CN sets up PDU session for group

communication, establishes MBMS group and allocates

and assigns TMGI

Group Fanout

Request

Request to MBMS group

8. oneM2M SL sends group

request to SCEF

9. Devices receive group

request via MBMS

© 2018 oneM2M

Summary

• oneM2M Rel-3 interworks with 3GPP IoT features

• oneM2M provides complimentary value-add services over top of 3GPP IoT features

• oneM2M eases use and adoption of 3GPP IoT features by IoT devices and apps

• oneM2M enables operators to move up the value-chain and offer value-add IoT services

© 2018 oneM2M

Thank You!

Dale Seed

oneM2M Architecture Chair

Principal Engineer, IoT R&D,

Convida Wireless

Seed.Dale@ConvidaWireless.com