Introduction to Service Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP8 Agenda Item:

Outline © 2013 oneM2M Partners oneM2M-ARC-0397R01 2 M2M Service Session Requirements Definition of M2M Service Session M2M Service Session Use Case Examples M2M Service Session Value-add

Requirements OSR-003The M2M System shall support the ability to maintain M2M Session in coordination with application session for those M2M Applications that require it. OSR-004M2M System shall support the ability to support session-less application communications for those M2M Applications that require it. CRPR-005The M2M System shall be able to maintain context associated with M2M sessions (e.g. security context or network connectivity context during the interruption of the session). Source: oneM2M-TS-0002-Requirements-V0_6_2

Definition Source: oneM2M-TR-0004-Definitions_and_Acronyms-V oneM2M-TP “M2M Session: A service layer communication relationship between endpoints managed via M2M Common Services consisting of session authentication, connection establishment/termination, transmission of information, and establishment termination of Underlying Network services” Note - At TP7, ARC WG recommended that ‘M2M Session’ be referred to as ‘M2M Service Session’. Definitions TR should be updated to reflect this name change.

Session-Based M2M Request M2M-Session-ID = S1M2M-Request-ID = R1 … M2M Request #1 M2M-Session-ID = S1M2M-Request-ID = R2 … M2M Request # M2M-Session-ID used to associate M2M requests with a particular M2M service session.

M2M Service Session Benefit #1 M2M service session enables CSE with method of organizing M2M AE traffic into flows M2M service layer is well positioned to provide underlying networks with value-add information about AE flows E.g. Required QoS, traffic pattern/schedule, device state, priority Underlying networks can use this information to better optimize AE traffic flows through their network E.g. Info from CSE can be used by underlying network to more efficiently configure network policies

M2M service sessions are persistent with respect to underlying network connections – M2M service sessions can dynamically and intelligently initiate tear- down and re-establishment of underlying network connections on a as-needed basis – M2M service sessions can help select between multiple underlying networks based on session requirements – M2M service sessions can maintain/provide value-add info (context) to underlying networks – M2M service session can help coordinate end-to-end configuration of policies for each underlying network/connection – M2M session can enable additional end-to-end services not supported by underlying networks (e.g. service session security, collection of service session context, service session analytics, service session event generation, etc M2M Service Session Benefit #1 (con’t)

Cellular NW Broadband NW Use Case – Video Monitoring Mcc Infrastructure Node Middle Node ASN CSE2 CSE3 Mcc CSE1 Mca AE1 AE1 and AE2 establish E2E service session to exchange media data such as real-time audio/video (E.g. Home security video monitoring, etc) M2M service session can help coordinate E2E underlying network policy configuration E.g. CSE can provide input about AEs that can be factored into underlying network policies (e.g. type of service, bit rate requirement, priority, etc) AE2 Mca Service Session Media Data Service Session Control PCRF Packet Network Nodes Mcn (Rx) Mcn BPCF Packet Network Nodes SSM CSF Service session media data flows through underlying network. Underlying network policies configured by CSEs Service session control flows through CSE SSM CSF Other CSFs CMDH CSF SSM CSF Other CSFs CMDH CSF SSM CSF Other CSFs CMDH CSF

M2M Service Session Benefit #2 M2M service layer is well-positioned to offload M2M AEs of some of the burden of E2E ‘over-the-top’ application-based sessions. Today, many AEs are establishing end-to-end (E2E) sessions in an ‘over- the-top’ manner using application-based sessions. E.g. To support secure and reliable exchange of small data (e.g. events, notifications, commands) Much of the burden of establishing and managing these ‘over-the-top’ application sessions rests completely on AEs and humans E.g. AEs must handle session management messaging themselves E.g. Humans must enter end-to-end session login and password For M2M, many devices will be un-manned and resource constrained. E2E application-based session establishment will need to be lighter weight and more automated

Use Case – In-Home Patient Monitoring © 2013 oneM2M Partners oneM2M-ARC-0498R01 10 AE1 and AE2 establish E2E session with one another using M2M service session E.g. Used by AEs to establish/manage efficient, robust and secure E2E exchange of small data (measurements, events, notifications, etc) M2M service session provides AEs with E2E session credential management, authentication of new session participants, session-based request handling, etc. Mcc Infrastructure Node Middle Node Application Dedicated Node CSE1CSE2 Mca AE1 AE2 Mca Patient Alert! Service Session Small Data Service Session Control Both service session control and small data can flow through CSE SSM CSF Other CSFs … CMDH CSF SSM CSF Other CSFs … CMDH CSF M2M-Session-ID = S1M2M-Request-ID = R1 … M2M Service Session Request

M2M service sessions are persistent with respect to M2M requests – Allows AEs to configure CSEs with policies applicable to M2M requests having same M2M-Session-ID  This can streamline the individual M2M requests – Allows AEs to configure CSEs to collect context for M2M requests having same M2M-Session-ID M2M Service Session Benefit #3

M2M Service Session Benefit #4 Support for M2M service session can enable additional value- added services to be supported in M2M service layer Collect M2M service context information in a session based manner E.g. Track number or rate of M2M requests for a given M2M service session (i.e. session-based analytics!) Generation of M2M service events in a session based manner E.g. Detect when number of requests for a given M2M service session exceeds a defined threshold, etc.