1. Overview of analysis of existing SDO M2M architectures Group Name: REQ ARC#2 Source: Alcatel-Lucent

2. 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

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

4. Service capabilities listed in SDO specifications Connectivity support related Service layer capabilityBrief descriptionRelated requirements (TBC) Comment / guidelines Protocol translationTranslation between protocols used different reference points of the architecture (HTTP, CoAP, etc.) HLR-XX Device triggeringTriggering 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

5. Service capabilities listed in SDO specifications Security related Service layer capabilityBrief descriptionRelated requirements (TBD) Comment / guidelines Key managementGeneration, 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 managementAuthentication and authorization of calls to APIs HLR-XX

6. Service capabilities listed in SDO specifications Object/resource management related Service layer capabilityBrief descriptionRelated requirements (TBD) Comment / guidelines Application and Device Registrations Making the device and/or device application known to the service layer HLR-XX Resource managementCreate, update, retrieve, disvocer and delete resource objects containing various attributes in the service layer. HLR-XX Content push/pullUnicast and multicast data push to specified devices HLR-XX Store and forward of dataStore data in intermediate nodes. Forward data subject to permissions and access rights HLR-XX Subscribe/notifysubscribe to receive notifications upon certain events or when certain resources are updated. HLR-XX Group managementgroup creation, modification etc. HLR-XX

7. Service capabilities listed in SDO specifications Remote management related Service layer capabilityBrief descriptionRelated requirements (TBD) Comment / guidelines Device managementConfiguration, firmware upgrades, 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 management DM sometimes uses specific reference points (#from reference points used for M2M data) Proxy managementDevice management of devices behind gateways. HLR-XX MonitoringMonitoring of connectivity, application, etc. HLR-XX Need to articulate how oneM2M service architecture interacts with capabilities already existing in the operator network

8. Service capabilities listed in SDO specifications Other Service layer capabilityBrief descriptionRelated requirements (TBD) Comment / guidelines ChargingCharging pertaining to the usage of the service layer or network usage HLR-XX Data processingProvide 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 Semanticssemantic description of stored data. Such description can be used for the purpose of e.g. data processing HLR-XX

9. SDO architecture reference point analysis

10. Reference points analysis TIA ATISETSITIAAspects that needs clarification no equivalent A1, 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 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 referenc e 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 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 B6/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

11. Reference points analysis ETSI ATISETSITIAAspects 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 dIa: The dIa reference point offers generic and extendable mechanism for Device Application (DA)/Gateway Application (GA) interactions with the DSCL/GSCLno 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

12. Reference points analysis ATIS ATISETSITIAAspects 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

13. 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)