Presentation is loading. Please wait.

Presentation is loading. Please wait.

Step by step approach Group Name: WG2

Published byBathsheba Randall Modified over 8 years ago

Similar presentations

Presentation on theme: "Step by step approach Group Name: WG2"— Presentation transcript:

1 Step by step approach Group Name: WG2
Source: Michael hs. Yang, LG uplus, Meeting Date: Agenda Item: Contribution

2 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

3 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

4 Architecture comparison
M2M architecture oneM2M architecture current oneM2M scope Car infotainment -FMS, BIS -Car Sharing … FMS BIS Truck mgmt. -… Service C … … Solution/ Service Connected Car Smart Grid … … M2M Core P Platform Underlying network N Network Gateway Area Network D Device Device Device Device Device Device ※ AE and CSE on the device are also in oneM2M scope

5 Service Functions vs. Generic Functions.
M2M architecture oneM2M architecture current oneM2M scope Car infotainment -FMS, BIS -Car Sharing … FMS BIS Truck mgmt. -… Service Service Functions … … Connected Car Smart Grid Solution/ Service OBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc… … … M2M Core Generic Functions Registration, Security, Authentication, Subscription, Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data Platform Underlying network Network Gateway Area Network Device Device Device Device Device Device ※ AE and CSE on the device are also in oneM2M scope

6 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?

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

8 Suggestion Step 2 Step 1 M2M architecture oneM2M architecture
current oneM2M scope Car infotainment -FMS, BIS -Car Sharing … FMS BIS Truck mgmt. -… Service Step 2 … … The location of service-specific functions is FFS Connected Car Smart Grid Solution/ Service OBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc… … … M2M Core Step 1 Registration, Security, Authentication, Subscription, Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data Platform Underlying network Network Gateway Area Network Device Device Device Device Device Device ※ AE and CSE on the device are also in oneM2M scope

9 End of Document

10 Practical Services Real-Time Audio/Video
1 2 3 Real-Time & Secure Health Monitoring ※Source : ARC M2M service Session management CSF (IDCC, LGE, ZTE)

11 Inclusion relation of CSE
<6. Functional Architecture from TS-0001_V0.0.2> 3 1 2 relation of inclusion ∩ _ ∩ _ 1 2 3 Example. Number of CSE 5 (max. 11) 11 (max.12) 12 (max. 14)

12 What is AE? M2M architecture oneM2M architecture Underlying network
current oneM2M scope Car infotainment -FMS, BIS -Car Sharing … FMS BIS Truck mgmt. -… Service … … Connected Car Smart Grid Solution/ Service OBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc… … … M2M Core Registration, Security, Authentication, Subscription, Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data Platform Underlying network Network Gateway Area Network Device Device Device Device Device Device ※ AE and CSE on the device are also in oneM2M scope

13 Service-specific functions
M2M architecture oneM2M architecture current oneM2M scope Car infotainment -FMS, BIS -Car Sharing … FMS BIS Truck mgmt. -… Service Where do service-specific functions belonging to? … … Connected Car Smart Grid Solution/ Service OBD/DTG, Vehicle/Driver registration, Driver sync, Eco Drive, Fuel, Driving distance, etc… … … M2M Core Registration, Security, Authentication, Subscription, Charging, Discovery, Location, Device & Service info., DM mgmt., F/W update, Statistics, Big data Platform Underlying network Network Gateway Area Network Device Device Device Device Device Device ※ AE and CSE on the device are also in oneM2M scope

Download ppt "Step by step approach Group Name: WG2"

Similar presentations

oneM2M and AllJoyn Interworking

oneM2M and AllJoyn Interworking
SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: 2014-05-07 Discussion  Source: OBERTHUR Technologies Information  Contact:

SEC Clarification Group Name: WG4 (SEC-2014-xxxx) Decision  Meeting Date: Discussion  Source: OBERTHUR Technologies Information  Contact:
Is a Node or not Node? ARC-2014-1194-Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.

Is a Node or not Node? ARC Node_resolution Group Name: ARC Source: Barbara Pareglio, NEC, Meeting Date: ARC#9.1 Agenda.
Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.

Problem of Current Notification Group Name: ARC WG Source: Heedong Choi, LG Electronics, Meeting Date: ARC 9.0 Agenda Item: TBD.
Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:

Service Layer Session Management Group Name: WG2-ARC Source: IDCC, LGE, ZTE Meeting Date: TP16 Agenda Item:
TTA Views on Technical Scope of M2M Consolidation 17 August 2011 TTA M2MCons02_16 (Agenda 4.3)

TTA Views on Technical Scope of M2M Consolidation 17 August 2011 TTA M2MCons02_16 (Agenda 4.3)
Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All Consolidated M2M standards boost the industry Li Li (Thomas) CCSA(Huawei) Document No: GSC16-PLEN-73.

Halifax, 31 Oct – 3 Nov 2011ICT Accessibility For All Consolidated M2M standards boost the industry Li Li (Thomas) CCSA(Huawei) Document No: GSC16-PLEN-73.
OneM2M-ARC-2013-0365-Service_examples_and_evolution Service examples and evolution Group Name: WG2 Source: Philip Jacobs, Cisco Systems,

OneM2M-ARC Service_examples_and_evolution Service examples and evolution Group Name: WG2 Source: Philip Jacobs, Cisco Systems,
Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: 2014-03-20 Agenda Item: TBD.

Resource Announcement Procedures Group Name: WG2 Source: Rajesh Bhalla, Hao Wu - ZTE Meeting Date: Agenda Item: TBD.
On Management, Abstraction & Semantics

On Management, Abstraction & Semantics
RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: 2013-10-21 Agenda Item:

RoA and SoA Integration for Message Brokers Group Name: WG2-ARC Source: ALU Meeting Date: Agenda Item:
Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:

Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:
2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.
Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,
oneM2M-OIC Interworking Technical Comparison

oneM2M-OIC Interworking Technical Comparison
Common Service Entities

Common Service Entities
Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: 2013-02-25 Agenda.

Optimized M2M interworking with mobile networks Group Name: oneM2M REQ Source: Takanori Iwai, NEC, Meeting Date: Agenda.
Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: 2015-03-25 Agenda Item:

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:
End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date: 2015-05-18.

End-to-End security definition Group Name: SEC WG4 Source: Phil Hawkes, Qualcomm, Meeting Date:
Geneva, Switzerland, 26-27 April 2012 Introduction to session 7 - “Advancing e-health standards: Roles and responsibilities of stakeholders” ​ Marco Carugi.

Geneva, Switzerland, April 2012 Introduction to session 7 - “Advancing e-health standards: Roles and responsibilities of stakeholders” ​ Marco Carugi.

Similar presentations

Ads by Google