Service Layer Session Management

Group Name: WG2-ARCSource: IDCC, LGE, ZTEMeeting Date: TP16Agenda Item:

Outline

• Definition of M2M Service Layer Session• M2M Service Layer Session Requirements• M2M Service Layer Session Use Case

Examples• M2M Service Layer Session Value-Add• Previous work at ARC on Service Layer

Session

Overview of Sessions at Different Layers

MAC/PHY Protocol Layer(E.g. Ethernet, WiFi, etc)

IP Protocol Layer(E.g. IPv4, IPv6, etc)

Transport Protocol Layer (E.g TCP)

Application Protocol Layer (E.g HTTP, CoAP, SIP, etc)

oneM2M Service Layer

Applications(E.g. E-Health, Home Automation, etc)

MAC/PHY Protocol Layer(E.g. Ethernet, WiFi, etc)

IP Protocol Layer(E.g. IPv4, IPv6, etc)

Transport Protocol Layer (E.g TCP)

Application Protocol Layer (E.g HTTP, CoAP, SIP, etc)

oneM2M Service Layer

Applications(E.g. E-Health, Home Automation, etc)

Transport Layer Sessions

Application Protocol Layer Sessions

Service Layer Sessions

Network Node #1 Network Node #2

Application Sessions

At oneM2M, our scope is “Service Layer Session”

Definition of M2M Session TS 0011 (TS 0011 Common Terminology V1.2.1)

• M2M session: 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

M2M Requirements Related to Service Session(oneM2M-TS-0002-Requirements-V1.0.1 )

OSR-003 The oneM2M System shall support the ability to maintain peer-to-peer M2M Session in coordination with application session for those M2M Applications that require it.

Partially implemented in

Rel-1

(see note 21)NOTE 21: No

support for peer-to-peer service layer session.

OSR-004 The oneM2M System shall support session-less application communications for those M2M Applications that require it.

Implemented in Rel-1

CRPR-005 The oneM2M 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).

Partially implemented

in Rel-1(see note 1)

NOTE 1: Long lived security context and

registration is covered, M2M

Sessions are not covered.

Current Status

• What are supported today– Single hop “session” associated with registration

• What are not supported today– End-to-end service layer session

Use Cases Requiring Sessions

• Not all M2M use cases require end-to-end sessions, many use cases do, for example: – use cases requiring end-to-end security and

privacy such as eHealth, banking and military

– use cases requiring end-to-end quality of service such as video surveillance, patient monitoring, and emergency services

Use Case 1 – Real Time Audio/Video Communication (section 9.4 TR 0001 Use Case Collections V 1.4.0)

Mcc

Infrastructure Node

Middle Node

ASN

CSE2 CSE3MccCSE1

McaAE1

• AE1 and AE2 establish End-to-End service session to exchange control information, for example, a user via AE2 can adjust parameters on the surveillance camera

AE2Mca

Service Session Media DataService Layer Session Control

Service session media data flows through transport network.

Service session control flows through CSE

High Level Illustration of Real-time Audio/Video Communication(section 9.4 TR 0001 Use Case Collections V 1.4.0)

oneM2M system

DeviceDevice Device

Smart Phone/Service Centre

session control for audio/video communication

audio/video data packet

Potential Requirements(section 9.4 TR 0001 Use Case Collections V 1.4.0)

• The oneM2M system shall provide a capability to allocate unique identifiers to devices for identification and session routing in oneM2M system.

• The oneM2M system shall support to establish and terminate real-time audio/video session between M2M applications.

• The oneM2M system shall provide a capability for a device to be registered in the system.

• The oneM2M system shall support authorization if a request to and from the device for real-time audio/video call establishment is allowed.

• The oneM2M system shall provide a capability for routing a request for real-time audio/video call establishment from or to the device.

• The oneM2M system shall provide a capability for media control (e.g. negotiation of transcoding, QoS) between the M2M applications for real-time audio/video data packet transmission.

Use Case 2 – Secure remote patient care and monitoring(section 9.4 TR 0001 Use Case Collections V 1.4.0)

• AE1 and AE2 establish secure End-to-End session with one another using M2M service layer session

• E.g. Used by AEs to establish/manage efficient, robust and secure E2E exchange of small data (measurements, events, notifications, etc)

• M2M service layer session provides AEs with E2E session credential management, authentication of new session participants, session-based request handling, etc.

Mcc

Infrastructure NodeMiddle NodeApplication Dedicated Node

CSE1 CSE2

McaAE1 AE2Mca

Patient Alert!

Service Session Small DataService Session Control

Potential Requirements(section 7.3 TR 0001 Use Case Collections V 1.4.0)

• The M2M system shall support M2M applications with establishing a security context for protecting the privacy of application data from the underlying M2M service.

• The M2M system must support mechanisms for binding identities used at service layer and/or application layer to the tamper proof identities that are available within the device secured Environment.

• The M2M service layer must be able to accommodate delay requirements for the application based on the tagging applied to the application data. For instance, data that is marked critical must create notifications for first-level responders.

• … … (didn’t include specific security requirements)

M2M Service Session Benefits

• M2M service layer session enables end-to-end security

• M2M service layer 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 Session Benefits• 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

Previous Discussions and Texts on Service Layer Session (Annex I TS 0001 V1.2.0)

• An M2M service session is an end-to-end Service Layer connection managed by the Service Session Management (SSM) CSF. The SSM CSF manages M2M service sessions between AEs, between an AE and a CSE, or between CSEs.

• The management of a M2M service session includes capabilities such as the management of session state, session authentication and establishment, management of Underlying Network connections and services related to the session, coordination of sessions spanning multiple hops of CSEs, exchange of information between session endpoints, and session termination.

Previous Discussions and Texts on Service Layer Session (Annex I TS 0001 V1.2.0)

Mca Reference Point

Mcn Reference Point

Application Entity (AE)

Underlying Network Service Entity (NSE)

Common Services Entity (CSE)

Mcc Reference Point

Addressing and Identification

Data Management & Repository

Location

Security

Communication Management/

Delivery Handling

Registration

Session Management

Device Management

Subscription Notification

Service Charging & Accounting

Discovery

Network Service Exposure/Service

Ex+Triggering

Group Management

Asking Input from ARC• Agree on the need to support service layer

session and related parameters and management procedures

• Work out solutions