Upload
duonglien
View
224
Download
6
Embed Size (px)
Citation preview
2
1 개요
2 IoT 기술 표준
3 M2M 기술 표준
4 기타 관련 표준 등
5 Q&A
목 차
3
M2M/IoT 개념
M2M - Machine to Machine TTA 정보통신용어사전
- 무선 통신을 이용한 기계와 기계 사이의 통신
ETSI TC M2M (TR 102 725 – Definitions) - M2M Communications: refer to physical telecommunication based
interconnection for data exchange between two ETSI M2M compliant entities, like: device, gateways and network infrastructure.
IoT - Internet of Things TTA 정보통신용어사전
- 세상에 존재하는 모든 사물(things)을 네트워크로 연결해 인간과 사물, 사물과 사물 간 언제 어디서나 서로 소통할 수 있게 하는 새로운 정보 통신 기반
- 유비쿼터스 공간을 구현하기 위한 인프라 컴퓨팅 기기들이 환경과 사물에 심겨 환경이나 사물 그 자체가 지능화되는 것부터 사람과 사물, 사물과 사물 간에 지능 통신을 할 수 있는 M2M의 개념을 인터넷으로 확장하여 사물은 물론, 현실과 가상 세계의 모든 정보와 상호 작용하는 개념으로 진화했다.
ITU-T Y.2060 - A global infrastructure for the information society, enabling advanced services by
interconnecting (physical and virtual) things based on, existing and evolving, interoperable information and communication technologies.
- The Internet of things (IoT) can be perceived as a far reaching vision with technological and societal implications.
1. 개요
4
M2M과 IoT 관계
M2M 과 IoT 관계 MACHINE v.s. THING
의미상 차이가 있으나 지향하는 바는 유사
1. 개요
vs. ? < ? > ? = ?
Top Down
과거 미래 Bottom Up
5
M2M/IoT 기술 표준화 방향
M2M/IoT 기술 표준화 관점 표준화 관점에서는 IoT와 M2M의 기술 표준화 방향을 모두 고려하여 기술
적 합의점을 찾는 것이 필요함
1. 개요
Merging Point
시간
표준화 기술 측면
(물리적/구체적)
(가상적/개념적)
M2M
IoT
6
관련 주요 표준화기구 1. 개요
• oneM2M – M2M 기술 표준화를 위한 글로벌 협력체 – 세계 지역별 7개 표준화 기구 참여
• ETSI TC M2M (SmartM2M) – 하위 통신네트워크에 독립적/End-to-End M2M 서비스 대상 – M2M 서비스 요구사항, 기능 구조, 인터페이스 규격 표준화
(구현 참조 가능 표준) – 타 기술/표준 재사용 (IETF, OMA, BBF, 3GPP 등)
• 3GPP SA1/SA2 MTC – 이동통신망 관점 – MTC 서비스 요구사항, 시스템 구조 표준화 진행중
• IEEE 802.16’s M2M Task Group – WirelessMAN에서 M2M을 위한 시스템 요구사항/참조 아키
텍처/Air Interface 규격 정의
• WiMAX Forum – WiMAX 망 관점 – M2M 요구사항에 대한 표준화 진행
• IETF 6LoWPAN/CORE/ROLL – IPv6 over LLN/CoAP/Routing,…
• ITU-T IoT-GSI/JCA-IoT – IoT Reference Model에 대한 표준 작성
• ITU-T FG-M2M – 서비스 계층의 M2M 기술 표준화(e-Health 중심) 진행
• W3C – Semantic Web 기술
*LLN: Low power & Lossy Network
7
관련 주요 표준화 기구 1. 개요
S(C)-P-N-D 별 관련 표준화 기구 예
S(C)
P
N
D
P, D
8
1 개요
2 IoT 기술 표준
3 M2M 기술 표준
4 기타 관련 표준 등
5 Q&A
목 차
9 KRnet 2014
ITU-T NGN • ITU-T Y.2002, “Overview of ubiquitous networking and of its support in NGN”, 2009.10 • Communication Types
– person-to-person communication: • persons communicate with each other using attached devices (e.g., mobile phone, PC)
– person-to-object communication: • persons communicate with a device in order to get specific information (e.g., IPTV content, file transfer)
– object-to-object communication: • an object delivers information (e.g., sensor related information) to another object with or without the
involvement of persons
Source: ITU-T Y.2002, Overview of ubiquitous networking and of its support in NGN
2. IoT 기술 표준
10 KRnet 2014
ITU-T IoT
• ITU-T Y.2060, “Overview of the Internet of things”, 2012.06
Technical overview of the IoT
2. IoT 기술 표준
11 KRnet 2014
ITU-T IoT
• IoT in ITU-T Y.2060
IoT Reference model
2. IoT 기술 표준
12
1 개요
2 IoT 기술 표준
3 M2M 기술 표준
4 기타 관련 표준 등
5 Q&A
목 차
13 KRnet 2014
M2M 관련 표준화 기구
oneM2M
13
M2M Gateway
Client Application
M2M Area Network
Service Capabilities
M2M Core
M2M Application
ZigBee Alliance. ZB Application Profiles
3GPP SA1, SA3, ,…
IETF 6LowPAN Phy-Mac Over IPV6
GSMA SCAG,…
IETF ROLL Routing over Low Power
Lossy Networks
CENELEC Smart Metering
CEN Smart Metering
TC294
IEEE 802.15.4
ESMIG Metering
ISO/IEC JTC 1/SWG5
KNX
HGI Home Gateway
Initiative
W-MBUS ETSI TISPAN
ETSI PLT
ETSI ISG-SMT
IEEE 802.16
ETSI TC M2M
OMA
TC13, TC205
BBF
3. M2M 기술 표준
14 KRnet 2014
ETSI TC M2M
• ETSI M2M overall scenario – 기존의 M2M 서비스 use case들을 기반으로 표준화 작업 시작
M2M Gateway
Client Application
M2M Application M2M Area Network
Service Capabilities
M2M Core
DIRECT CONNEC
T
DIRECT CONNEC
T
3. M2M 기술 표준
(출처: ETSI TC M2M)
15 KRnet 2014
ETSI TC M2M
• Work Items & Deliverables
TR 102 691 Smart Metering
WI-03
TR 102 732 e-Health
WI-05
TR 102 857 Connected consum
er
WI-06
TR 102 897 City Automation
WI-07
TR 102 898 Automotive
WI-08
TR 102 935 Smart Grid impacts
on M2M
WI-11
TS 102 689 M2M Service Require
ments
WI-01
TS 102 690 M2M Functional
Architecture
WI-02
TS 102 921 M2M Comm.
mIa, dIa and mId interfaces
WI-10
TS 101 603 Service Layer
Interworking with 3GPP networks
WI-18 WI-15
TS 103 093 BBF TR-069 Compatible
Management Objects
WI-16
TR 103 167 Threat analysis &
counter measures to M2M service layer
WI-12
TR 102 966 Interworking with
M2M Area Networks
WI-14
TR 101 584 Semantic Support
for M2M Data
WI-17
TR 101 531 Reuse of 3GPP nodes by M2M
SC Layer
WI-13
TR 102 725 M2M Definitions
WI-04
TS 103 092 OMA-DM
Compatible Management Objects
TS 103 107 Service Layer
Interworking with 3GPP2 networks
WI-20
TS 103 104 Interop. Test Spec for CoAP bindings of M2M primitives
WI-19
* * * * *
*
* *
* * *
* *
* * * * *
*
* shall be transferred to oneM2M * shall not be transferred to oneM2M
TR 103 118 Smart Grid Infrastru
ctures Security
WI-21
*
3. M2M 기술 표준
16 KRnet 2014
ETSI TC M2M • M2M Architecture Model
– D/GSCL : Device/Gateway Service Capability Layer – NSCL : Network Service Capability Layer – D/GA : Device/Gateway Application – NA: Network Application – MAS : M2M Authentication Server – MSBF : M2M Service Bootstraping Function
mIa
Device/Gateway Domain
D/GA
D/G M2M Node
Communication modules
dIa
NSCL mId
MSBF MAS
Network M2M Node
Core Network Connection
Core Network A Core Network B
D/GSCL
NA
Network Domain
<ETSI TS 102 690, M2M functional architecture framework>
3. M2M 기술 표준
17 KRnet 2014
ETSI TC M2M
• Functions of Service Capability Layers Function NSCL GSCL DSCL
Ensure that only trusted applications can communicate to the SCL X X X
Registration of applications to the local SCL X X X
Authentication and authorization of SCL communication X X X
Generation of charging records pertaining to the use of the system for purposes of e.g. billing, accounting
X
Provides means to store application data with history X X X
Provides means to share data among applications X X X
Provides M2M service connection establishment and teardown along with security key negotiation
X X X
Selection of communication means for delivery of information based on policies X X X
Analysis and forwarding of methods according to provisioned policies and method metadata X X X
Manages subscriptions and notifications pertaining to changes in data X X X
Support access control for stored data (authorization) X X X
Keeping track of reachability of the M2M Device or M2M Gateway X X X
Support grouping of information pertaining to gateways, devices and applications X X X
Supports remote management of gateways, devices and area network, including performance management, configuration management, fault management and software and firmware upgrading management
X X X
Supports multiple management protocols X X Provides interworking between non ETSI compliant devices or gateways and the SCL X X X
Interworking and using of Core Network services exposed by the Network Operator X
Geographic location support X X X
NAT traversal support X X X
3. M2M 기술 표준
18 KRnet 2014
ETSI TC M2M 3. M2M 기술 표준
• Example set of specific service capabilities
Service capabilities (SC) M2M Server (N : Network)
M2M Gateway (G : Gateway)
M2M Device (D : Device)
1 Application Enablement NAE GAE DAE
2 Generic Communication NGC GGC DGC
3 Reachability, Addressing and Repository
NRAR GRAR DRAR
4 Communication Selection NCS GCS DCS
5 Remote Entity Management NREM GREM DREM
6 SECurity NSEC GSEC DSEC
7 History and Data Retention NHDR GHDR DHDR
8 Transaction Management NTM GTM DTM
9 Interworking Proxy NIP GIP DIP
10 Compensation Brokerage NCB GCB DCB
11 Telco Operator Exposure NTOE - -
19 KRnet 2014
ETSI TC M2M
• Reference Points – mIa/dIa/mId/mIm
• mIm: inter-domain reference point offering generic and extensible mechanisms for NSCL-to-NSCL interactions and communications
3. M2M 기술 표준
20 KRnet 2014
ETSI TC M2M
• ETSI M2M Service Layer & 3GPP Interworking – Architecture models for interworking between 3GPP system and
M2M Service Capability Layer.
GGSN/P-GW GGSN/P-GW
NSCL
D/GSCL
MTC-IWF
SMS-SC/ GMSC/ IWMSC
MME
SGSN
S-GW
MSC RA
N
HSS
IP-SM_GW
CDF/ CGF
M2M Network
Application
M2M Device/Gateway
D/G App
mId (over Gi/SGi)
mId (over S5)
mId (over Gn)
mId (over Iu/Gb)
mId (over S1-U)
mIa
dIa
Comm module
s
mId
mId
3. M2M 기술 표준
Services Capability
Server ( SCS )
Gi / SGi
Tsp Control plane
User plane
Indirect Model
Direct Model
Hybrid Model
GGSN / P - GW
MTC - IWF
SMS - SC / GMSC / IWMSC
2
1
1
T 4
S 6 m Rf / Ga
T 5 c
Um / Uu /
LTE - Uu
MTC UE Application
MME
HPLMN
VPLMN
Gi / SGi
SGSN
S - GW
UE
MSC
RAN
T 5 b T 5 a
HSS
Tsms
Application Server ( AS )
1
Application Server ( AS )
2
IP - SM - GW
CDF / CGF
2 +
SME
ETSI TS 102 690
3GPP TS 23.682
21 KRnet 2014
ETSI SmartM2M
• oneM2M 협의체 발족 이후 ETSI TC M2M SmartM2M 이라는 이름으로 변경하여 활동 시작
• Architecture와 Interface 표준 Release 2 제정 – TS 102 690 v2.2.0 : 2014-5-7 – TS 102 921 v2.2.0 : 2014-5-7
• New Work Items 표준화 작업 중 – M2M communications for Smart Appliances – Common Ontology for Smart Appliances – Smart Appliances ontology and communications testing – Interoperability test specification for the ETSI M2M
primitives – Release 2 maintenance of TS 102 690 (M2M architecture) – Release 2 maintenance of TS 102 921 (M2M Interfaces)
3. M2M 기술 표준
22 KRnet 2014
oneM2M 3. M2M 기술 표준
• Steering Committee – Manages Work Scope and Vision – Develops and Maintains Working
Procedures – Organizational Oversight
• Technical Plenary – Technical Program Management – Technical Oversight – Responsible for standard work
SC
(Steering Committee)
FC
(Finance Committee)
MARCOM
(Marketing & Communications)
LG
(Legal Group)
MP
(Methods & Procedures)
TP
(Technical Plenary)
WG 1 WG 2 WG 4 WG 5 WG 3
(Requirements) (Architecture) (Protocols) (Security) (Management, Abstraction, Semantics)
• oneM2M Structure
23 KRnet 2014
oneM2M • Objectives
– To develop globally agreed-upon M2M end-to-end specifications using common use cases and architecture principles across multiple M2M applications to connect M2M devices with application servers worldwide with an access independent view of end-to-end services
– To define a Service Layer platform with high level and detailed service architecture including protocols/APIs/standard objects
• Scope
3. M2M 기술 표준
No Description
1. Use cases and requirements for a common set of Service Layer capabilities;
2. Service Layer aspects with high level and detailed service architecture, in light of an access independ
ent view of end-to-end services;
3. Protocols/APIs/standard objects based on this architecture (open interfaces & protocols);
4. Security and privacy aspects (authentication, encryption, integrity verification);
5. Reachability and discovery of applications;
6. Interoperability, including test and conformance specifications;
7. Collection of data for charging records (to be used for billing and statistical purposes);
8. Identification and naming of devices and applications;
9. Information models and data management (including store and subscribe/notify functionality);
10. Management aspects (including remote management of entities);
11. Common use cases, terminal/module aspects, including Service Layer interfaces/APIs between: - Application and Service Layers; - Service Layer and communication functions.
24 KRnet 2014
oneM2M
• Work Items WI TS / TR Name WG Rapporteur
0001 TR 0001 oneM2M Use Case collection 1 Cisco
0001 TS 0002 M2M Requirements 1 Huawei
0002 TR 0002
Part 1: Analysis of the architectures proposed for consideration by o
neM2M 2 Telxxis
0002 TR 0003
Part 2 Study for the merging of architectures proposed for considera
tion by oneM2M 2 InterDigital
0002 TS 0001 M2M Architecture 2 ZTE, Ericsson
0003 TR 0004 Definitions and Acronyms 1 Telekom
0003 TR 0005 Roles and Focus Areas 1 Qualcomm
0004 TR 0006
Study of Management Capability Enablement Technologies for Cons
ideration by oneM2M 5 Huawei
0005 TR 0007 oneM2M Abstraction and Semantics Capability Enablement 5 NEC
0006 TR 0010 oneM2M Device / Gateway Classification 2 LGE
0007 TR 0008 Analysis of Security Solutions for the oneM2M System 4 Giesecke & Devrient
0007 TS 0003 oneM2M Security Solutions 4 Giesecke & Devrient
0008 TR 0009 oneM2M Protocol Analysis 3 Telxxis
0009 TS 0004 oneM2M Protocol Technical Specification 3 Fujitsu
0010 TS 0005 oneM2M Management Enablement (OMA) 5 LGE, Huawei
0010 TS 0006 oneM2M Management Enablement (BBF) 5 ALU
0011 TS 0007 oneM2M Service Components 2 ALU
0012 TS 0008 CoAP Protocol Binding Technical Specification 3 LGE
0013 TS 0009 HTTP Protocol Binding Technical Specification 3 LGE
0014 TS 0010 MQTT Protocol Binding Technical Specification 3 IBM
0014 TR 0011 MQTT Protocol Interworking Study 2, 3 IBM
0015 TR 0001V2 Use Case Technical Report 1 Cisco
3. M2M 기술 표준
25 KRnet 2014
oneM2M
• Work Programme Timeline
May-13 Sep-13 Jan-14 May-14 Aug-14 Dec-14 Apr-15 Aug-15
RequirementsTR-0001V2(WG1)
TS-0011(WG1)TR-0005(WG1)
ArchitectureTS-0007(WG2)
TR-0010(WG2)TS-0001(WG2)TR-0011(WG2)
ProtocolsTR-0009(WG3)TS-0004(WG3)TS-0008(WG3)TS-0009(WG3)TS-0010(WG3)
Security0
TS-0003(WG4)Management, Abstraction and Semantics
TR-0007(WG5)TS-0005(WG5)TS-0006(WG5)
oneM2M Work Programme (2014-06-13)
Drafting
Change Control
Freeze
Delay
3. M2M 기술 표준
26 KRnet 2014
oneM2M
• Initial Release - Normative Deliverables – 2014년 7월, TP12 회의 후 Release 1 공개 예정
3. M2M 기술 표준
May-13 Sep-13 Jan-14 May-14 Aug-14 Dec-14 Apr-15 Aug-15
Requirements
TS-0011(WG1)
Architecture
TS-0001(WG2)
Protocols
TS-0004(WG3)
TS-0008(WG3)
TS-0009(WG3)
TS-0010(WG3)
Security
TS-0003(WG4)
Management, Abstraction and Semantics
TS-0005(WG5)
TS-0006(WG5)
oneM2M Work Programme
Drafting
Change Control
Freeze
Delay
Level of completeness
90%
95%
45%
25%
40%
45%
90%
60%
70%
27 KRnet 2014
oneM2M
• oneM2M Use cases collection(1/2)
3. M2M 기술 표준
구분 Use cases
Energy
Wide area Energy related measurement/control system for advanced transmissi
on and distribution automation
Analytics Use Case for M2M
Smart Meter Reading
Environmental Monitoring of Remote Locations to Determine Hydropower
Oil and Gas Pipeline Cellular/Satellite Gateway
Enterprise Smart Building
Healthcare
M2M Healthcare Gateway
Use Case on Wellness Services
Secure remote patient care and monitoring
Public Services
Street Light Automation
Use Case on Devices, Virtual Devices and Things
Car/Bicycle Sharing Services
Smart Parking
Information Delivery service in the devastated area
Transportation
Vehicle Diagnostic & Maintenance Report
Use Case on Remote Maintenance Services
Traffic Accident Information Collection
Fleet Management Service using DTG (Digital Tachograph)
28 KRnet 2014
oneM2M
• oneM2M Use cases collection(2/2)
3. M2M 기술 표준
구분 Use cases
Residential
Home Energy Management
Home Energy Management System (HEMS)
Plug-In Electrical Charging Vehicles and power feed in home scenario
Real-time Audio/Video Communication
Event Triggered Task Execution Use Case
Semantic Home Control
Semantic Device Plug and Play
Other
Extending the M2M Access Network using Satellites
M2M Data Traffic Management by Underlying Network Operator
Optimized M2M interworking with mobile networks (Optimizing connectivity man
agement parameters)
Optimized M2M interworking with mobile networks (Optimizing mobility manage
ment parameters)
Sleepy Node Use Case
Use Case on collection of M2M System data
Leveraging Broadcasting/Multicasting Capabilities of Underlying Networks
Leveraging Service Provisioning for Equipment with Built-in M2M Device
29 KRnet 2014
oneM2M
• oneM2M Requirements(v0.6.2)
3. M2M 기술 표준
구분 Requirement 항목 개수
Functional Requirements
Overall System Requirements 72
Management Requirements 17
Abstraction Requirements 3
Semantics Requirements 7
Security Requirements 26
Charging Requirements 6
Operational Requirements 6
Communication Request Processing Requirements
5
Non-Functional Requirements (non-normative)
- 2
총: 144
OSR-001 The M2M System shall be able to allow communication between M2M Applications by using multiple communication means based on IP Access.
Example:
30 KRnet 2014
oneM2M
• oneM2M Functional Architecture(1/3) – oneM2M Layered Model & Functional Architecture
• AE : Application Entity • CSE : Common Service Entity • NSE : Network Service Entity
Application
Common Services
Underlying Network Services
AE AE
Mca Mca Mca
Mcc
Mcn Mcn
CSE CSE
NSE NSE
Field Domain Infrastructure Domain
To Infrastructure
Domain of other
Service Provider
Mcc’
<oneM2M Layered Model> <oneM2M Functional Architecure>
3. M2M 기술 표준
31 KRnet 2014
oneM2M
• oneM2M Functional Architecture(2/3) – oneM2M System Configuration
3. M2M 기술 표준
32 KRnet 2014
oneM2M
• oneM2M Functional Architecture(3/3) – Commem Service Functions : Service function that is common to the M2M
environment and specified by oneM2M
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
Device
Management
Subscription
Notification
Service Charging &
Accounting
Discovery
Network Service
Exposure/Service
Ex+Triggering
Group
Management
3. M2M 기술 표준
33 KRnet 2014
oneM2M
• Data model – oneM2M 데이터는 resource로 표현 – 32개의 resource type을 정의 : 각 reource 별 attribute 정의
3. M2M 기술 표준
<E>
CSE1
<A>
APP1
<R>
AR1
<C>
CONT1
<C>
CONT1
<C>
CONT2
<C>
CONT3
baseURI
<Topological Resource Structure at a CS>
0..1memory
0..1schedule
nodeID0..1
0..1power
0..1networkTopology
0..nstorage
0..n< subscription>
<Node>
Structure of <node> resource
34 KRnet 2014
oneM2M
• Information Flow – CREATE(C)/RETRIEVE(R)/UPDATE(U)/DELETE(D) – 이벤트 메시지 전송방법으로 NOTIFY(N) 포함
3. M2M 기술 표준
<Procedure for CREATEing a Resource> RETRIEVE/UPDATE/DELETE 도 동일 <Procedure for NOTIFYing Information>
001: CREATE Request
Originator requests creation of a Resource
003: CREATE Response
Receiver responds to creation Request
Originator
(CSE or AE)Receiver CSE
002: Receiver
Processing 002: NOTIFY Request
003: NOTIFY Response
Originator
(CSE)
Receiver
(CSE or AE)
001: Local Processing
(Notification Triggered)
35
1 개요
2 IoT 기술 표준
3 M2M 기술 표준
4 기타 관련 표준 등
5 Q&A
목 차
36 KRnet 2014
ITU-T WoT
• Y.2063 (2012.7), “Framework of the web of things” – WoT의 프레임워크 구조를 제시
• WoT requirements, deployment models, functional architecture, use cases 등
– semantics와 ontology는 다루지 않음
4. 기타 관련 표준 등
. . .
Y.2063(12)_F8-1
. . .
Web of things broker
Controlservice
Sensorservice
Web
Mash-upservice
Mash-upservice
Mash-upservice
Mash-upservice
TV controlservice
Monitoringservice Data cloud
service
Wi-Fidevice
Bluetoothdevice
Constrained devices
Bluetoothagent
Zigbeeagent
Fully-fledged devices
Applications
Agent-n
Light controlservice
IP phoneservice
Mash-upservice
Wi-Fiagent
Monitoringservice
Zigbeedevice
Zigbeedevice
Conceptual model of the web of things
37 KRnet 2014
ITU-T WoT
• Overview of the web of things architecture (Y.2063)
4. 기타 관련 표준 등
Applications
Wo
TB
roke
r
Service Layer
Adaptation Layer
Physical Layer
Mash-up service WoT service WoT Agent
Constrained device
`
Web
Web service
Composite WoT service
Full-fledged device
• WoT Broker – role for integrating and
exposing the devices to the web
• WoT Agent – a role to control and
communicate with physical devices
– role of communicating and translating between the adaptation layer of the WoT broker and the physical devices in a subnetwork
– bridge between the WoT service and the physical devices residing in a subnetwork
38 KRnet 2014
ITU-T FG-M2M
• FG-M2M : Focus Group on Machine-to-Machine Service Layer – 현재 SG11에 최종보고서 제출한 상태임
• FG-M2M structure and deliverables – WG1: Use cases and service models
• (D1.1) “M2M use cases: e-health”
– WG2: Requirements and architectural framework of the M2M Service Layer • (D2.1) “M2M service layer: requirements and architectural framework”
– WG3: API and protocols • Framework of M2M APIs and protocols • M2M APIs and protocols for specific interfaces • (D3.1) “M2M service layer: APIs and protocols overview”
– Cross WGs deliverables • (D0.1) “M2M standardization activities and gap analysis: e-health” • (D0.2) “M2M enabled ecosystems: e-health”
4. 기타 관련 표준 등
39 KRnet 2014
ITU-T FG-M2M
• (D2.1) M2M service layer: requirements and architectural framework
4. 기타 관련 표준 등
ITU-T M2M service layer in the IoT reference model
ETSI M2M SCL in the IoT reference model
40 KRnet 2014
ITU-T FG-M2M
• (D2.1) M2M service layer: requirements and architectural framework
4. 기타 관련 표준 등
Reference points of the ITU-T M2M service layer
41 KRnet 2014
3GPP MTC
• 3GPP는 Rel-8부터 MTC(Machine-type Communication)으로 관련 3GPP network enhancement 관련 규격을 제정 중
Rel-9, SA3
2012
Rel-8, SA1
2007 2008
FS_M2M : Study on Facilitating Machine to Machine Communication in GSM and UMTS TR 22.868
20092005 2006 2010 2011
Rel-11, SA/CT/RAN
2013
Rel-10, SA/CT/RAN
FS_UM2M : Study on Security Aspects of Remote Provisioning and Change of Subscription for M2M Equipment TR 33.812
NIMTC : Network Improvements for Machine-type CommunicationsTS 22.368, 23.401, 24.301, 24.368, 36.331, 44.018, ...
SIMTC : System Improvements for Machine-type CommunicationsTS 22.368, TS 23.682 TS 24.301, etc.
MTCe : Machine-Type and other mobile data applications Communications enhancementsTS 22.368, TS 23.682 TS 24.301, etc.
Rel-12, SA/CT/RAN
2014
Rel-13, SA/CT/RAN
2015
SEES : Service Exposure and Enablement SupportSRMMTC : Service Requirements Maintenance for MTCTS 22.368
4. 기타 관련 표준 등
42 KRnet 2014
3GPP MTC • 3GPP TS 23.682 : Architecture enhancements to facilitate communications with packet data
networks and applications (Release 12)
S6n
Services Capability
Server ( SCS )
Gi / SGi
Tsp Control plane
User plane
Indirect Model
Direct Model
Hybrid Model
GGSN / P - GW
MTC - IWF
SMS - SC / GMSC / IWMSC
2
1
1
T 4
Rf / Ga S 6 m
T 5 c
Um / Uu /
LTE - Uu
MTC UE Application
MME
HPLMN
VPLMN
Gi / SGi
SGSN
S - GW
UE
MSC
RAN
T 5 b T 5 a
CDF / CGF
Tsms
Application Server ( AS )
1
Application Server ( AS )
2
IP - SM - GW
HSS
2 +
SME
MTC AAA
4. 기타 관련 표준 등
43 KRnet 2014
3GPP D2D • ProSe (Proximity-based Services)
– LTE 기반으로 근접거리에 있는 단말끼리 직접 통신하는 D2D 방식 – 단말들 사이의 물리적 접근성을 기반으로 운영되며, 네트워크의 자원 효율성 증대, 단말기 소비전력 감
소, 셀룰러 통신 영역 확대 등의 측면에서 장점 – 2011.6월, 3GPP RAN 계층에서 D2D를 위한 study item 제안 – 2012.12월, Feasibility study for Proximity Services 승인(TR 22.803 R12) – 2014. 2월, Study on architecture enhancements to support Proximity-based Services (ProSe) (TS
23.703) R12 배포 – 유스케이스는 public safety 시나리오를 대상으로 하여 진행
(출처: You Sun Hwang/ETRI)
4. 기타 관련 표준 등
44 KRnet 2014
TIA SDC
core IP
convergence
application
management
device
management
network management
AAA-SD container
authentication, authorization
and accounting
server container
convergence
smart
device
protocol
home
applications
admin
node container
convergence
smart
device
protocol
node
applications
admin
PoA container
smart
device
protocol
PoA
applications
PoA
devices
admin
convergence
application
domain
device
domain
• TIA TR-50 : M2M Smart Device Communications System Architecture(1/3)
– High Level System Architecture
4. 기타 관련 표준 등
45 KRnet 2014
TIA SDC
• TIA TR-50 : M2M Smart Device Communications System Architecture(2/3) – High Level System Architecture
• AAA-SD: provide authentication, authorization and accounting services to other entities in the network to establish and enforce security policies.
• Home Application: The home application is a logical entity that is responsible for the business logic, either directly or via supervision and interaction with node applications and PoA applications and with PoA devices.
• Node Application: The node application is a logical entity that acts as an intermediary between the home application and the PoA application and between the home application and the PoA device.
• PoA Application: PoA application is a logical entity that provides resources to node or home applications or to other PoA applications.
• Container: The container is a logical entity that provides services to the applications that operate within it, and enforce security policies.
– A PoA device is a resource that represents a physical device. The means by which physical devices are interfaced are outside the scope of this document. The combination of services provided by the PoA container and the software that implements a PoA device are responsible for whatever conversion is necessary to represent the physical device as a standardized resource.
4. 기타 관련 표준 등
46 KRnet 2014
TIA SDC
• TIA TR-50 : M2M Smart Device Communications System Architecture(3/3) – Reference architecture
• URL과 RESTful interface를 명시하고 있음
server
node
PoA
AAA-SD
B5/B5'/
B9
B4
home application
B2/B2'
PoA application/PoA device
node application
authentication, authorization and accounting
B1
A3/A3'
A1
B3/B3'
A2
B7
B6
B8
4. 기타 관련 표준 등
47 KRnet 2014
IEEE P2413
• IEEE P2413 Working Group – IoT를 위한 Architectural Framework 표준화 작업 시작(2014.3~)
• Title: Standard for an Architectural Framework for the Internet of Things (IoT)
– Motivation: “Most current standardization activities are confined to very specific verticals and stakeholder groups. ~”
– First Meeting : 10-11 July 2014 Munich, Germany – STMicroelectronics, Marvell, Huawei, Siemens, CISCO 등 참여
• IEEE P2413 Goals – Define an IoT architecture framework that covers the
architectural needs of the various IoT application areas – Promote cross-domain interaction by increasing system
interoperability and functional exchangeability to further fuel the growth of the IoT-based application market
– Increase the transparency of system architectures to support system benchmarking, safety, and security assessments
– Reduce industry fragmentation and create a critical mass of multi-stakeholder activities around the world
4. 기타 관련 표준 등
48 KRnet 2014
Q&A
- 감사합니다 -