step by step approach group name: wg2 source: michael hs. yang, lg uplus,...

Step by step approach

Group Name: WG2Source: Michael hs. Yang, LG uplus, hsyang@lguplus.co.kr Meeting Date: 2013-11-29Agenda Item: Contribution

Purpose• Based on the whole architecture of oneM2M,

To make a step-by-step approach and achievement (e.g. release number) considering each layer (e.g. platform, solution/services, network)

• To know and focus what we need to do in each step

Background• Different view points about functions, resources(including

attributes).• What resources(including attributes) and functions to implement

for providing practical services. • No target service yet.

e.g. BEMS, FMS, Smart Grid, and etc.

• Limited for covering all the M2M services by using current CSEs, resources, and its attributes.

• The meaning of the service in Release 1.

※ Practical services : Services(including a target service) used in the real market (e.g. FMS, EMS, CCTV, and etc) Service-specific functions : Functions used for providing practical services

Architecture comparison

Mca Reference Point

Mcn Reference Point

Application Entity (AE)

Common Services Entity (CSE)

Underlying Network Service Entity (NSE)

Solution/Service

Service

Platform

Network

Device

-Car infotainment-FMS, BIS-Car Sharing-…

Underlying network

Connected Car

-FMS-BIS-Truck mgmt.-…

Smart Grid

… …

Area Network

Device

Gateway

Device Device Device Device

M2M Core

……

M2M architecture oneM2M architecture

current oneM2M scope

※ AE and CSE on the device are also in oneM2M scope

C

P

N

D

Solution/Service

Service

Platform

Network

Device

-Car infotainment-FMS, BIS-Car Sharing-…

Underlying network

-FMS-BIS-Truck mgmt.-…

… …

Area Network

Device

Gateway

Device Device Device Device

oneM2M architecture

Mca Reference Point

Mcn Reference Point

Application Entity (AE)

Underlying Network Service Entity (NSE)

Common Services Entity (CSE)

Data Management & Repository

Location

Security

Communication Management/

Delivery Handling

Registration

Device Management

Subscription Notification

Service Charging & Accounting

Discovery

Network Service Exposure/Service

Ex+Triggering

Group Management

Application and Service Layer Management

Service Session ManagementRegistration, Security, Authentication, Subscription,

Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data

……

current oneM2M scope

M2M architecture

M2M Core

Connected Car Smart GridOBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc…

※ AE and CSE on the device are also in oneM2M scope

Service Functions vs. Generic Functions.

Service

Functions

Generic

Functions

Issues / Discussion points• How can we provide a practical service in Release 1? • The meaning of AE is practical services including service-specific

functions? or is a basic application by utilizing capabilities from CSE?• Where do service-specific functions belong to? CSE? or …

1) CSE need to cover service-specific functions? If it is right, do we have enough CSE for providing a practical services in release 1? And, which services can we provide using current CSE? From time to time, we need to add service-specific functions and resources for providing practical services.2) Or CSE means, the only common function which can be commonly used for providing generic M2M services?

Suggestion• Narrow down and focus on common functions, common

resources, and common attributes to provide a generic service in R1*Using functions and architecture in release 1, M2M SP can provide practical services by mapping their own service functions and oneM2M APIs.

• Defining requisites of CSE, Resources and attributes in R1• How to include service-specific functions is FFS.

*These functions might be in AE or CSE side.

Solution/Service

Service

Platform

Network

Device

-Car infotainment-FMS, BIS-Car Sharing-…

Underlying network

-FMS-BIS-Truck mgmt.-…

… …

Area Network

Device

Gateway

Device Device Device Device

oneM2M architecture

Mca Reference Point

Mcn Reference Point

Application Entity (AE)

Underlying Network Service Entity (NSE)

Common Services Entity (CSE)

Data Management & Repository

Location

Security

Communication Management/

Delivery Handling

Registration

Device Management

Subscription Notification

Service Charging & Accounting

Discovery

Network Service Exposure/Service

Ex+Triggering

Group Management

Application and Service Layer Management

Service Session ManagementRegistration, Security, Authentication, Subscription,

Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data

……

current oneM2M scope

M2M architecture

M2M Core

Connected Car Smart GridOBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc…

※ AE and CSE on the device are also in oneM2M scope

Step 1

Step 2 The location of service-specific functions is FFS

Suggestion

End of Document

Practical ServicesReal-Time Audio/Video

Real-Time & Secure Health Monitoring

1 2 3

※Source : ARC-2013-0498-M2M service Session management CSF (IDCC, LGE, ZTE)

Inclusion relation of CSE

AE

CSEApplication

Service NodeMiddleNode

CSE

InfrastructureNode

CSE

To the Infrastructure Node of other M2M Service

Providers

AE

AEAE

MccMca

Mcn Mcn

Mca Mcc

Mcn

Mcc’McaMca

relation of inclusion 1 2 3∩ ∩_ _

1 2 3

Example.Number of CSE

<6. Functional Architecture from TS-0001_V0.0.2>

12 (max. 14)

11(max.12)

5(max. 11)

What is AE?

Solution/Service

Service

Platform

Network

Device

-Car infotainment-FMS, BIS-Car Sharing-…

Underlying network

-FMS-BIS-Truck mgmt.-…

… …

Area Network

Device

Gateway

Device Device Device Device

oneM2M architecture

Mca Reference Point

Mcn Reference Point

Application Entity (AE)

Underlying Network Service Entity (NSE)

Common Services Entity (CSE)

Data Management & Repository

Location

Security

Communication Management/

Delivery Handling

Registration

Device Management

Subscription Notification

Service Charging & Accounting

Discovery

Network Service Exposure/Service

Ex+Triggering

Group Management

Application and Service Layer Management

Service Session ManagementRegistration, Security, Authentication, Subscription,

Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data

……

current oneM2M scope

M2M architecture

M2M Core

Connected Car Smart GridOBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc…

※ AE and CSE on the device are also in oneM2M scope

Service-specific functions

Solution/Service

Service

Platform

Network

Device

-Car infotainment-FMS, BIS-Car Sharing-…

Underlying network

-FMS-BIS-Truck mgmt.-…

… …

Area Network

Device

Gateway

Device Device Device Device

oneM2M architecture

Mca Reference Point

Mcn Reference Point

Application Entity (AE)

Underlying Network Service Entity (NSE)

Common Services Entity (CSE)

Data Management & Repository

Location

Security

Communication Management/

Delivery Handling

Registration

Device Management

Subscription Notification

Service Charging & Accounting

Discovery

Network Service Exposure/Service

Ex+Triggering

Group Management

Application and Service Layer Management

Service Session ManagementRegistration, Security, Authentication, Subscription,

Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data

……

current oneM2M scope

M2M architecture

M2M Core

Connected Car Smart GridOBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc…

※ AE and CSE on the device are also in oneM2M scope

Where do service-specific functions belonging to?