Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, [email protected];...

Step by step approachGroup Name: WG2Source: Michael hs. Yang, LG uplus, [email protected]; Jaeseung Song, NEC Europe , [email protected];Meeting Date: 2013-11-29Agenda Item: Contribution

Purpose

• Based on the whole architecture of oneM2M, we need to apply a step-by-step approach and make an achievement (e.g. release number) by considering each layer (e.g. platform, solution/services, network) in terms of CSF, Resources, and attributes.

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

• To satisfy the given R1 timeframe

Background• Different view points about functions, resources, and attributes

in CSE.

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

• What functions, resources, and attributes to implement for providing practical M2M Applications.

• No target M2M Applications yet. e.g. BEMS, FMS, CCTV, AMI, Smart Grid, and etc.

• The meaning of the M2M Applications in Release 1.

※ M2M applications : Applications(including a target M2M application) used in the real market (e.g. FMS, EMS, CCTV, and etc) M2M application-specific Functions, resources, and attributes : used for providing particular M2M applications

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

Application

Application

Solution/Service

Service

Platform

Network

Device


Underlying network


… …

Area Network

Device

Gateway


oneM2M architecture

Mca Reference Point

Mcn Reference Point




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

……


M2M architecture

M2M Core

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


M2M Application-specific Functions vs. Generic Functions.

M2M Application-specific

Functions

Generic

Functions

Issues / Discussion points• Which M2M application can we provide in Release 1?

– The meaning of AE in R1 is practical M2M Application including M2M Application-specific functions? or is a basic M2M Application by utilizing capabilities from CSE?

• Where do M2M application-specific functions, Resources, and attributes belong to? CSE? or AE?– Some functions, resources, and attributes in CSE are related to a

particular type of M2M application.

(1) CSE means, common functions which can be commonly used for providing generic M2M Applications?

(2) or, CSE need to cover M2M Application-specific functions? If (2) is right, do we have enough CSE for providing a practical M2M Application in R1? And, which M2M Application can we provide using current CSE? From time to time, we need to update M2M Application-specific functions and resources to the TS.

Suggestion

• Focus on common functions, common resources, and common attributes to provide generic M2M Services in R1– M2M SP can provide M2M services by mapping their own service

functions and oneM2M APIs utilizing oneM2M architecture, functions, resources, and attributes in R1

• Clean-up and Consistent check for defining functions, resources and attributes in R1

• How to include M2M Application-specific functions, resources, and attributes are FFS.*These functions might be in AE or CSE side.

Application

Solution/Service

Service

Platform

Network

Device


Underlying network


… …

Area Network

Device

Gateway


oneM2M architecture

Mca Reference Point

Mcn Reference Point





Location

Security


Delivery Handling

Registration

Device Management



Discovery


Ex+Triggering

Group Management




……


M2M architecture

M2M Core



Step 1

Step 2? The location of M2M Application-specific functions is FFS

Suggestion

M2M Application-specific Functions

Generic Functions

End of Document

Practical M2M Application

Real-Time Audio/Video

Real-Time & Secure Health Monitoring

1 2 3

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

Application

What is AE in Release1?

Solution/Service

Service

Platform

Network

Device


Underlying network


… …

Area Network

Device

Gateway


oneM2M architecture

Mca Reference Point

Mcn Reference Point





Location

Security


Delivery Handling

Registration

Device Management



Discovery


Ex+Triggering

Group Management




……


M2M architecture

M2M Core



??

Application

M2M Application-specific functions

Solution/Service

Service

Platform

Network

Device


Underlying network


… …

Area Network

Device

Gateway


oneM2M architecture

Mca Reference Point

Mcn Reference Point





Location

Security


Delivery Handling

Registration

Device Management



Discovery


Ex+Triggering

Group Management




……


M2M architecture

M2M Core



Where do M2M Application-specific functions, resources, attributes belong to?

M2M Application-specific attributesAttribute Name Multiplicity

RW/RO/WO

Description

resourceType 1 RO See section 9.6.1 where this common attribute is described.expirationTime 1 RW See section 9.6.1 where this common attribute is described.accessRightID 1..n RW See section 9.6.1 where this common attribute is described.creationTime 1 RO See section 9.6.1 where this common attribute is described.lastModifiedTime 1 RO See section 9.6.1 where this common attribute is described.searchStrings 0..1 RW See section 9.6.1 where this common attribute is described.locationSource 1 RW Indicates the source of location information

Network-Based

GPS-Based

Sharing-BasedlocationUpdatePeriod 0..1 RW Indicates the period for updating location information. If the value is marked ‘0’ or not

defined, location information is updated only when a retrieval request is triggered.locationTargetId 0..1 RW The identifier to be used for retrieving the location information of a remote Node and this

attribute is only used in the case that location information is provided by a location server.locationServer 0..1 RW Indicates the identity of the location server. This attribute is only used in that case location

information is provided by a location server.locationContainerID 0..n RO URI of the <container> resource where the actual location information of a M2M Node is

stored.locationContainerName 0..1 WO Name of the <container> resource where the actual location information of a M2M Node is

store. If it is not assigned, the Hosting CSE automatically assigns a name of the resource.locationZone The identifier to be used for setting the location zone information. This attribute is only

used in the case that values of location marked more than “3”.

Table 9.6.7-1: Attributes of <locationPolicy> resource

• An example of M2M Application-specific attributes “※ LocationZone” attribute is intentionally made to demonstrate one of M2M application-specific attribute

※Source : ARC-2013-0511R02-CR_for_locationPolicy_Resource (LGE)

Definition of AE

• "Application Entity (AE): Application Entity provides Application logic for the end-to-end M2M solutions. Examples of the Application Entities can be fleet tracking application, remote blood sugar monitoring application, or remote power metering

Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, [email protected];...

Documents

Transcript of Step by step approach Group Name: WG2 Source: Michael hs. Yang, LG uplus, [email protected];...