Overview of analysis of existing SDO M2M architectures

Group Name: REQ ARC#2Source: Alcatel-Lucent

• Overview of capabilities based on SDO architecture work• SDO architecture reference point analysis

• Aspects that need clarification and/or further requirements guidance

• Summary of aspects that need clarification/followup

Outline

Introduction

• The purpose of this slide is to encourage discussion and ensure common understanding of existing SDO specification work

Service capabilities listed in SDO specificationsConnectivity support related

Service layer capability Brief description Related requirements (TBC)

Comment / guidelines

Protocol translation Translation between protocols used different reference points of the architecture (HTTP, CoAP, etc.)

HLR-XX

Device triggering Triggering the device through secondary mechanism (e.g. SMS) to establish a connection to the M2M service layer

HLR-XX

Interworking with area network technologies

Interworking aspects towards M2M area network technologies such as ZigBee

HLR-XX

Service capabilities listed in SDO specificationsSecurity related

Service layer capability Brief description Related requirements (TBD)

Comment / guidelines

Key management Generation, exchange, storage, use, and replacement of keys used for security purposes

HLR-190, HLR-212, HLR-XX

Authentication authorisation and accounting

Control over which entities are allowed access to which services, and how much of the resources they have used

HLR-057, HLR-206, HLR-192, HLR-184, HLR-174, HLR-198, HLR-175, HLR-205, HLR-193, HLR-185, HLR-183, HLR-202, HLR-211

M2M service bootstrapping

Secure provisioning of (secret) M2M Root Key in M2M Device/Gateway and M2M Authentication Server;

HLR-XX

API management Authentication and authorization of calls to APIs

HLR-XX

Service capabilities listed in SDO specificationsObject/resource management related

Service layer capability Brief description Related requirements (TBD)

Comment / guidelines

Application and Device Registrations

Making the device and/or device application known to the service layer

HLR-XX

Resource management Create, update, retrieve, disvocer and delete resource objects containing various attributes in the service layer.

HLR-XX

Content push/pull Unicast and multicast datapush to specified devices

HLR-XX

Store and forward of data Store data in intermediate nodes. Forward data subject to permissions and access rights

HLR-XX

Subscribe/notify subscribe to receivenotifications upon certain events or when certain resources are updated.

HLR-XX

Group management group creation, modification etc.

HLR-XX

Service capabilities listed in SDO specificationsRemote management related

Service layer capability Brief description Related requirements (TBD)

Comment / guidelines

Device management Configuration, firmwareupgrades, application lifecycle management, device lock and wipe

HLR-XX Network operators provide already DM functions. Need to articulate how oneM2M service architecture interacts with Network device managementDM sometimes uses specific reference points (#from reference points used for M2M data)

Proxy management Device management of devices behind gateways.

HLR-XX

Monitoring Monitoring of connectivity, application, etc.

HLR-XX Need to articulate how oneM2M service architecture interacts with capabilities already existing in the operator network

Service capabilities listed in SDO specificationsOther

Service layer capability Brief description Related requirements (TBD)

Comment / guidelines

Charging Charging pertaining to the usage of the service layer or network usage

HLR-XX

Data processing Provide e.g. threshold and expression rules setting and execution on the various data collected from the devices. Notifications could be triggered based on the outcome of the rules testing.

HLR-XX

Semantics semantic description of stored data. Such description can be used for the purpose of e.g. data processing

HLR-XX

SDO architecture reference point analysis

DeviceM2M

Applications

M2M ServiceLayer

dIa

DeviceM2M

Applications

M2M ServiceLayer

dIa

B5'

B5

Gateway/NodeM2M

Applications

M2M ServiceLayer

dIa

Gateway/NodeM2M

Applications

M2M ServiceLayer

dIa

DeviceM2M

ApplicationsB3

B9

B3'

B4

B8

M2M NetworkServiceLayer

M2M NetworkApplications

B2

B1

B2', ATIS

Gi/SGi

B7

B6

mIa

mId

mId

ATIS

TSP

AAA

A1

A2

A3'

MAS/MSBF

KEY:

TIA Reference PointsATIS Reference PointsETSI M2M Reference Points3GPP Reference Points

B1B6

mId

mId

B2

B7

B2', ATISATIS

A3

A3

A2

Access / Core

Network

A3'

A1

M2M ServiceLayer

MAS/MSBF

D’ DeviceM2M

ApplicationsdIa

M2M NetworkServiceLayer

mIm

mIa

PoA Device d Device

ASP IFMSP IFNW IF

Reference points analysisTIAATIS ETSI TIA Aspects that needs clarification

no equivalent no equivalentA1, A2, A3/A3': interfaces between applications

(PoA, node, home) and a AAA-SD for the purpose of providing AAA

Clarify if the use of AAA is to allow applications to access the network; AAA ownership

no equivalent no equivalent

B1, B2, B3: provide for interaction between a PoA application and a node application, including bi-directional communication of control information, events and data.

Need to clarify if these are application to application interfaces - without making use of the service layer

Traffic flow (option 2)

no equivalent (in ETSI there is no loopback reference points)

B5/B5'/B9: provides for interaction between the different PoA applications/PoA devices, possibly in different containers, including bi-directional communication of control information, events and data.

Need to clarify if these are application to application interfaces - without making use of the service layer

no equivalent no equivalent

B4: provides for interaction between the different node applications, possibly in different containers, including bi-directional communication of control information, events and data.

no equivalent no equivalentB6/B7/B8: provides for interaction between an

application and a container (node, PoA, server container)

Need to clarify if the container (TIA) and SCL (ETSI) are functionally equivalent

Reference points analysisETSIATIS ETSI TIA Aspects that needs clarification

equivalent to MSP IF

mIa: The mIa reference point offers generic and extendable mechanism for Network Applications interactions with the NSCL. no equivalent

no equivalent

dIa: The dIa reference point offers generic and extendable mechanism for Device Application (DA)/Gateway Application (GA) interactions with the DSCL/GSCL no equivalent

no equivalent (but ATIS shows traffic flows which could be equivalent to ETSI mId)

mId: The mId reference point offers generic and extendable mechanism for SCL interactions. no equivalent

there appears to be no container to container reference point in TIA

no equivalent

mIm: The mIm reference point offers generic and extendable mechanism for NSCL to NSCK interactions. no equivalent

Reference points analysisATISATIS ETSI TIA Aspects that needs clarification

NW IF: This is the interface between the M2M Device and the Network Provider to provision and manage the connection of the device to the network. As indicated in the diagram it may also enforce the network policies Need to clarify what aspects of this reference

points are M2M specific

MSP IF:This is the interface between the Network Provider and the M2M Service Provider to provision, manage service delivery, and define service capability policies on the M2M Devices Need clarify if this reference point is equivalent

to Tsp, Tsms, Gi/SGi, etc.

ASP IF:This is the interface between the M2M Service Provider and the Application Services to Bootstrap, Activate, Provision, Secure, Meter, Manage Application Services delivered on the M2M Devices mIa equivalent

(TBC)Need to confirm if this reference point is equivalent to mIa

Summary of aspects that need clarification/followup

• Link between service capabilities and requirements• Clarify if the PoA device in TIA is equivalent of ETSI d device• Clarify if the ETSI SCL is equivalent to the container in TIA• Seek common understanding on which existing SDO reference points are

within scope of oneM2M (e.g. loopback reference points)