Embed Size (px)
Citation preview
I Internet of Things
II Machine Type Communication
III IP based WSN
IV Open Issues
The Internet of Things ?The Internet of Things ?
A new dimension added to ICTsFrom anytime, any place connectivity for anyoney , y p y y
Connectivity for anything
Connect everyday objects and devicesConnect everyday objects and devicesTo large databases and networks
Seamlessly integrated into the Internet
2 KRnet 2010
Seamlessly integrated into the Internet
Source: “ITU Internet Reports 2005: The Internet of Things: Executive Summary,”Nov. 2009
Alphabet Soup for …Alphabet Soup for …M2M : Machine-to-Machine Network
WSN : Wireless Sensor Network
USN : Ubiquitous Sensor NetworkUSN : Ubiquitous Sensor Network
MTC : Machine Type Communication
IoT : Internet of Things
WoT : Web of Things
O2N : Object-to-Object Network
IoTO2N
IoT
M2M
WSN
M2M
3 KRnet 2010
Things ?Things ?
사물 (事物) : Thing, Object, Matter
1. 일과 물건 (物件)을 아울러 이르는 말.
사물 (事物) : Thing, Object, Matter
1. 일과 물건 (物件)을 아울러 이르는 말. ( )
2. 물질 세계에 있는 모든 구체적이며 개별적인 존재를 통틀어 이르는 말.
( )
2. 물질 세계에 있는 모든 구체적이며 개별적인 존재를 통틀어 이르는 말.
사물의 정의구체적이고 개별적인 존재
물리적 존재, 개념적 존재물리적 존재, 개념적 존재
관리 대상 사물의 확장 단계 : Machine Thing Object Matter
Machine : 1. 기계 2. 기구
Thing : 1. (사물을 가리키는) 것 2. (생명이 없는) 물건
Object : 1. 물건, 물체 2. 욕망, 연구, 관심 등의 대상 3. 목적, 목표
Matter : 1. (고려하거나 처리해야 할) 문제 2. 상황, 사태, 사정
사물간 통신Machine, Thing, Object, matter 간 통신
M2M, M2T, T2T, M2O, T2O, O2O, M2m, T2m, O2m, m2m
4 KRnet 2010
사물간사물간 통신통신 관계도관계도
M2M : machine device 간 통신
WSN : sensing device 의 wireless 통신
USN : pervasive sensing device 의 wired/wireless 통신USN : pervasive sensing device 의 wired/wireless 통신
IoT : Internet infra 기반의 thing 간 통신
WoT : thing 관련 data web
Physical device
g
O2N : 개념적 개체간 통신
Logical devicePhysical device
Thing
Logical device
Matter
Machine device Object O2NM2M
IoT
Sensing
deviceUSN
WSN
O2NM2MData
WoT
5 KRnet 2010
사물간 통신사물간 통신
Architecture of Architecture of IoTIoT
ThingsID tags & Readers
NetworksLocal networkg
Barcodes, RFID tags, GPS chips
POS readers, Subway gates
Mobile reader
LAN/WLAN
PLC
IEEE 802 15 4Mobile reader
PDAs, Cameras
Sensors
IEEE 802.15.4
Public network
Telephone Network
Actuators
Logic circuits
Cable network
Cellular Mobile Network
InternetInternet
Routers
Discovery services
M2Mserver
WSNserver
EPCserver
Internet
Data bases
M2MGW
ZigBeeGW
RFIDGW
Mobile Network
6 KRnet 2010
ZigBee
ETSI M2M ETSI M2M 구조구조
ETSI Jan. 2009, Machine-to-Machine Communications Technical Committee
end-to-end view of Machine to Machine standardization needs
M2M DeviceM2M ApplicationM2M Area Network
end to end view of Machine to Machine standardization needs
Capable of transmitting data autonomously
M2M Area Network
M2M Area Network
Service
Capabilities
M2M
Core
UWB, ZigBee, Bluetooth, PLC
M2M GW
M2M
M2M
Gateway
Capabilities
Communications Networks
Access, transport, core network
xDSL W-LAN
Client
Application
xDSL, W-LAN, WiMAX, LTE, GERAN, UTRAN
M2M Application (Server)
7 KRnet 2010 Source: David Boswarthick, “M2M Activities in ETSI, SCS Conference”, Sophia 2nd July 2009
Key Elements of M2M Architecture (I)Key Elements of M2M Architecture (I)
M2M Device
A device that runs application(s) using M2M capabilities and network domain functions. An M2M Device is either connected straight to an Access Network or interfaced to M2M Gateways via an M2M Area NetworkNetwork.
M2M Area Network
A M2M Area Network provides connectivity between M2M Devices and M2M Gateways.
Examples of M2M Area Networks include: Personal Area Network ptechnologies such as IEEE 802.15, SRD, UWB, Zigbee, Bluetooth, etc or local networks such as PLC, M-BUS, Wireless M-BUS.
M2M GatewaysEquipments using M2M Capabilities to ensure M2M Devices interworking and interconnection to the Network and Application
8 KRnet 2010
Domain. The M2M Gateway may also run M2M applications.
Source: David Boswarthick, “M2M Activities in ETSI, SCS Conference”, Sophia 2nd July 2009
Key Elements of M2M Architecture (II)Key Elements of M2M Architecture (II)
M2M Core:
Composed of Core Networks and Service Capabilities
Service CapabilitiesService Capabilities
Provide functions that are shared by different applications. Expose functionalities through a set of open interfaces. Use Core Network functionalities and simplify and optimize applications development and deployment whilst hiding network specificities to applications.
Examples include: Data Storage and Aggregation, Unicast and Multicast message delivery, etc.
M2M Applications (Server)
Applications that run the service logic and use Service Capabilities accessible via open interfaces.
9 KRnet 2010
accessible via open interfaces.
Source: David Boswarthick, “M2M Activities in ETSI, SCS Conference”, Sophia 2nd July 2009
IoTIoT 관련관련 표준화표준화 단체단체
ISO/IEC JTC1ESMIG
EPCGlobalGS1
Capillary
A t k
ITU-TNGN CENELEC
Smart Metering
CENSmart Metering
UWSNESMIGMetering
HGIHome Gateway
Initiative
UtilitiesMetering
Access networks
Service Platform
Wide Area wireless
WOSAOASIS
W3C
IP Network
Network
M2M Gateway
IPSOIPV6
Hardware and
IETF 6LowPANPhy-Mac Over IPV6
IETF ROLL
KNX
W-Mbus
wireline
Protocols Routing over Low Power
Lossy NetworksIEEE
802.xx.xZCL
Application
ZigBee Alliance.ZB Application Profiles 3GPP
SA1, SA3, ,…
OMA GSMASCAG,…
ETSITISPAN, ITS,
10 KRnet 2010 Source: David Boswarthick, “M2M Activities in ETSI, SCS Conference”, Sophia 2nd July 2009
I Internet of Things
II Machine Type Communication
III IP based WSN
IV Open Issues
11 KRnet 2010
M2M M2M 통신통신 서비스서비스
M2M (Machine-to-Machine) 서비스
1990년대 초반 : 원격 조정, 텔레매틱스 개념으로 인식년대 반 원격 정, 텔레매틱 개념 인식
2000년대 초반 : 이동통신망을 활용한 원격 모니터링 서비스
machine-to-server; 1-1, uploading
Bending machine POS OnStar Fleet management AWS …Bending machine, POS, OnStar, Fleet management, AWS,
이동통신망 사업자별, Solution 별 platform
2000년대 후반 : 이동통신망외 무선망 센서망 등을 활용한 전자장치간 통신2000년대 후반 : 이동통신망외 무선망, 센서망 등을 활용한 전자장치간 통신
Ethernet, WiFi, GSM, CDMA, WCDMA, WiBro, Bluetooth, ZigBee 활용M2M access
이동통신망 이외 무선망 유선망 센서망에 의한 M2M 서비스 미성숙이동통신망 이외 무선망, 유선망, 센서망에 의한 M2M 서비스 미성숙
현재 M2M 서비스유럽 : GSM 망을 기반으로 텔레매틱스, 원격 검침, 원격 관리 서비스 활성화
북미 : 텔레매틱스 M2M 기기, 사설 플랫폼 서비스
12 KRnet 2010
M2M M2M 네트워크네트워크
M2M 네트워크
Circuit 음성망, 1x/EVDO 패킷망, SMS 망성망, 망, 망
이동통신망 자원 활용
M2M 플랫폼M2M 플랫폼
M2M 단말, 모뎀 제어/관리
Over the Air
개방형 API 제공
13 KRnet 2010 Source: “LGT M2M Platform 개요”O2N포럼 발표 2010
기존기존 M2M M2M 문제점문제점
기존 M2M solution 은 application-specific : fragmentedk tmarkets
비효율적인 building blocks : 통신망 기술 별 legacy system 별비효율적인 building blocks : 통신망 기술 별, legacy system 별
고 비용 : deployment, maintenance costs, evolution 어려움
Telco, IT provider, Service provider 간 협력이 어려움
이동통신망 이외 무선망, 유선망, 센서망에 의한 M2M 서비스 미성숙
14 KRnet 2010
Standards in ETSI & 3GPPStandards in ETSI & 3GPP
ETSI
TC M2M
3GPP
SA1
TR 22.868 (8.0.0) – Study on facilitating M2MCommunication in 3GPP Systems (~ 2007)
TR 22.368 (1.1.1) – Service requirements
TS 102 689 (0.4.1) – Machine-to-Machinecommunications (M2M); M2M service requirements
TS 102 690 (0.1.1) – Machine-to-Machine
for machine-type communications
SA2
communications (M2M); M2M functional architecture
TS 102 691 (0.3.1) – Machine-to-Machinecommunications (M2M); Smart metering use case
TS 102 725 (0.2.0) – Machine-to-Machine
TR 23.888 (0.1.2) – System improvement formachine-type communications
RAN2
communications (M2M); M2M definitions
TS 102 732 (0.2.1) – Machine-to-Machinecommunications (M2M); use cases for eHealth
TS 102 857 (0.0.1) – Machine-to-Machine RAN2
TR 37.8xx (0.0.2) – RAN improvement formachine-type communications
communications (M2M); use cases for Connected Consumer
TS 102 897 (0.0.2) – Machine-to-Machinecommunications (M2M); use cases for City automation
TS 102 898 (0.0.1) – Machine-to-Machine
15 KRnet 2010
communications (M2M); use cases for Automotive app.
Source: ETRI 신재승 박사
3GPP M2M 3GPP M2M 구조구조
16 KRnet 2010 Source : ETSI TS 102 690 M2M Functional Architecture
M2M M2M MTCMTC
Terminology
Machine-to-Machine (M2M)Machine to Machine (M2M)
TR22.868 v.8.0.0 (in SA1, 2005 ~ 2007)
Definition: A form of data communication between entitiesDefinition A form of data communication between entities
that do not necessarily need human interaction.
Machine Type Communications (MTC)yp ( )
TS22.368 v.1.1.1 (2009)
Definition: A form of data communication which involves one
or more entities that do not necessarily need human
interaction.H
M
H
M
17 KRnet 2010
M MM2M
Source: ETRI 신재승 박사
MTC MTC 특징특징
Present structures that have been optimally designed for H2Hmay be suboptimal for M2M and therefore structures y pdesigned for M2M need to be investigated.
C t bil t k 과 차이점Current mobile network comm. 과 차이점
Machine type communications is different to current mobile network communication services as it involves:network communication services as it involves
different market scenarios,
data communications,
lower costs and effort,
a potentially very large number of communicating terminals
to a large extent little traffic per terminalto a large extent, little traffic per terminal.
18 KRnet 2010
MTC Features (I)MTC Features (I)
Low mobilityThis feature applies for those devices which do not move, move infrequently, or within a limited area.
Time controlledTime controlled devices are those devices which send or receive data during certain defined periods of times. The network needs to be able to let access to these devices at those concrete times.
Ti t l tTime tolerantThe network can be able to allow or restrict access to these devices as well as to limit the data transferred or set load thresholds.
Packet switched onlyThe MTC Feature Packet Switched Only is intended for use with MTC Devices that
l i k t it h d ionly require packet switched services.
Mobile originated only
19 KRnet 2010
The MTC Feature Mobile Originated Only is intended for use with MTC Devices that only utilize mobile originated communications.
MTC Features (II)MTC Features (II)
Online small data transmissionThe MTC Feature Online Small Data Transmissions is intended for use with online or connected MTC Devices that frequently send or receive small amounts of data.
Offline small data transmissionThe MTC Feature Offline Small Data Transmissions is intended for use with offline (i.e. disconnected) MTC Devices that connect, then send and/or receive only pre-defined small amounts of data, and then disconnect from the network.
Infrequent mobile terminatedThe MTC Feature Infrequent Mobile Terminated is intended for use with MTC Devices that mainly utilize mobile originated communications.
MTC monitoringgThe MTC Feature MTC Monitoring is intended for use with MTC Devices that are employed in locations with high risk, e.g. possibility of vandalism or theft. This system optimisation is not intended to protect the MTC Device or prevent theft or vandalism of the MTC Device but is intended to provide functionality to detect
20 KRnet 2010
vandalism of the MTC Device but is intended to provide functionality to detect events that may possibly be the result of theft or vandalism.
MTC Features (III)MTC Features (III)
Offline indicationThe Offline Indication MTC Feature is intended for use with MTC Applications whichThe Offline Indication MTC Feature is intended for use with MTC Applications which require timely notification of when it is no longer possible to establish signalling between the MTC Device and the network.
Jamming indicationThe Jamming Indication MTC Feature is intended for use with MTC Applications which require timely notification of when an MTC Devices is being jammed.
Priority alarm messageMTC Devices issues a priority alarm in the event of e g theft vandalism or otherMTC Devices issues a priority alarm in the event of e.g. theft, vandalism or other needs for immediate attention.
Extra low power consumptionExtra low power consumptionThe MTC Feature Extra Low Power Consumption will result in improving the ability of the system to efficiently service MTC applications that require extra low power consumption.
21 KRnet 2010
MTC Features (IV)MTC Features (IV)
Secure connectionThe MTC Feature Secure Connection is intended for use with MTC Devices that require a secure connection between the MTC Device and MTC Server.
Location specific triggerp ggThe MTC Feature Location Specific Trigger is intended to trigger MTC Devices in a particular area (e.g. to wake up the MTC Device).
Group basedGroup Based is a collection of MTC Features that are intended for use with groups of MTC Devices.
Group based policing - The MTC Feature Group Based Policing is intended for use with a group of MTC Devices belonging to the same MTC Subscriber, for which the network operator wants to enforce a combined QoS policy.
G b d dd i Th MTC F t G B d Add i i i t d dGroup based addressing - The MTC Feature Group Based Addressing is intended for use with a large group of MTC Devices belonging to the same MTC Subscriber, for which the network operator wants to optimize the message volume when many MTC devices need to receive the same message.
22 KRnet 2010
I Internet of Things
II Machine Type Communication
III IP based WSN
IV Open Issues
23 KRnet 2010
IETF IP based WSN Standardization (I)IETF IP based WSN Standardization (I)
Extensive interoperabilityOther wireless embedded 802.15.4 network devices
Devices on any other IP network link (WiFi, Ethernet, GPRS, Serial lines, …)
Established securityAuthentication, access control, and firewall mechanisms
Network design and policy determines access not the technologyNetwork design and policy determines access, not the technology
Established naming, addressing, translation, lookup, discovery
Established proxy architectures for higher-level servicesNAT, load balancing, caching, mobility
Established application level data model and servicesEstablished application level data model and servicesHTTP/HTML/XML/SOAP/REST, Application profiles
Established network management toolsPi T t SNMP O Vi N tM G liPing, Traceroute, SNMP, … OpenView, NetManager, Ganglia, …
Transport protocolsEnd-to-end reliability in addition to link reliability
24 KRnet 2010
y y
Most “industrial” (wired and wireless) standards support an IP option
IETF IP based WSN Standardization (II)IETF IP based WSN Standardization (II)
IETF 6LoWPAN WG
make IEEE802.15.4 link look like an IPv6 link
Fragmentation and Reassembly LayerFragmentation and Reassembly Layer
Header Compression
Address Auto-configuration
Mesh Routing Protocol
Network Management Implementation ConsiderationsNetwork Management, Implementation Considerations
Application and Higher layer Considerations,
Security Considerations
IETF ROLL WG (R ti O L d L t k )IETF ROLL WG (Routing Over Low power and Lossy networks)LLNs (Low power and Lossy Networks)
Low Power : Low Transmission Power, Modest Receive Sensitivity, Short Range, Multi-Hop
Lossy : BER, Small MTU, Embedded in changing, often harsh, environment.
Routing protocol specification for LLNs
IETF CoRE WG (Constrained RESTful Environments )
define a framework for a limited class of applications
to monitor simple sensors (e.g. temperature sensors, light switches, and power meters)
to control actuators (e.g. light switches, heating controllers, and door locks)
to manage devices
25 KRnet 2010
define a Constrained Application Protocol (CoAP) for the manipulation ofResources on a Device
6LoWPANs : Frame Format6LoWPANs : Frame Format
802.15.4 PHY 802.15.4 MAC Payload Frame Check Seq.
Dispatch Header PayloadDispatch Header Payload
6LoWPAN Frame Dispatch-Header
0 Dispatch IPv6, LOWPAN_HC1, LOWPAN_BC0, other 1
IPv6 Dispatch (01000001) IPv6 Header Payload
M h H d
HC1 Dispatch (01000010) HC1 Header Payload
BC0 Dispatch (01010000) Sequence Number
Mesh Header
1 0 O F Hops Originator Address, Final Address
1 0 O F 0xF Originator Address Final AddressHops
1 1 0 dgram tag dgram size
Fragmentation Header
1 0 O F 0xF Originator Address, Final AddressHops
26 KRnet 2010
1 1 0 dgram_tag dgram_size
1 1 1 dgram_tag dgram_size dgram_offset
6LoWPAN : IP HC Encoding6LoWPAN : IP HC Encoding
0 1 1 TF NH HLIM CI SA SAM M DA DAM
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
0 1 1 TF NH HLIM CID
SAC
SAM M DAC
DAM
Dispatch byte LOWPAN_IPHC byte
• TF: Traffic Class, Flow Label
• NH: Next Header
• HLIM: Hop Limit
• CID: Context Identifier Extension
SAC: Source Address Compression• SAC: Source Address Compression
• SAM: Source Address Mode
• M: Multicast CompressionM: Multicast Compression
• DAC: Destination Address Compression
• DAM: Destination Address Mode
27 KRnet 2010
• http://tools.ietf.org/id/draft-ietf-6lowpan-hc-05.txt
6LoWPAN : 6LoWPAN : UnicastUnicast ExamplesExamples
15.4 6Lowpan Mesh H d
Dispt h
IPHC NHC Ports Payload
5 1 1 1 1
Header atch
1 1 1 1
Link Local, Mesh Under (9 bytes)
15.4 Dispatch
IPHC NHC Ports Payload
1 1 1 1
Li k L l R t O (4 b t )
15 4 6Lowpan Mesh Disp IPHC NHC Ports Payload
5 1 1 1 1
Link Local, Route Over (4 bytes)
15.4 6Lowpan Mesh Header
Dispatch
IPHC NHC Ports Payload
Global, Mesh Under (9 bytes)
15.4 Dispatch
IPHC HLIM Src Addr DestAddr
NHC Ports Payload
1 1 1 2 2 1 1
28 KRnet 2010
atch Addr
Global, Route Over (9 bytes)
ROLL : RPL (I)ROLL : RPL (I)
RPL: Routing Protocol for LLNsFirst IETF-Draft released for Low power & Lossy Networks on June 28 2009First IETF Draft released for Low power & Lossy Networks,on June 28, 2009
ARCHROCK & SENSINODE are currently testing & implementing the RPL
RPL Propertiessupporting core set of functionalities corresponding to the intersection of the various application requirements of LLNspp q
customization of RPL to optimize the operation based on application requirements
Path for MP2P & P2MP LLN Traffic flowsPath for MP2P & P2MP LLN Traffic flows
Constraint based routing
Cluster tree based hierarchical Directed Acyclic Graph (DAG)
T ickle ti e fo Ro ti g Ad e t DAG I fo atio Optio (RA DIO)Trickle timer for Routing Advert DAG Information Option (RA-DIO) transmission
29 KRnet 2010
ROLL : RPL (II)ROLL : RPL (II)
LLN Traffics
MP2P is inward traffic towards DAG Root
P2MP is an Outward traffic away from DAG Root from neighborsP2MP is an Outward traffic away from DAG Root from neighbors
RPLRPL RPL
RPL
RPLRPLRPLRPL
RPL
RPL
LBR(LLN Border Router) : DAG Root / Egress point
Any Router / Node
RPLRPL RPL
RPLRPL
RPL
Neighbor Discovery
By hearing the multicast Router Advertisements (RAs)
N4
N1
messages from neighborsN4
N5
N2
Multicasts RAs
Link Layer mechanism
30 KRnet 2010 Source: Claudio Borean, “ROLL: RPL”, WSN over IP, Sep. 2009
N3Multicasts RAs
ROLL : RPL (III)ROLL : RPL (III)
Directed Acyclic Graph
All edges are contained in paths oriented toward & terminated at a root (DAG root or sink)
DAGID :A globally unique identifier for a DAG
DAG ROOT :DAG root is a sink within the DAG graph
DAG PARENT : A parent of a node within DAG is one of the immediate successors of the node on a path towards the DAG root
DAG SIBLING :Any neighboring node which is located at the same depth within a DAG
GROUNDED DAG :If DAG Root offers a default routeGROUNDED DAG :If DAG Root offers a default route
FLOATING DAG : If any node has no parents,
then a node itself is DAG root offering
no ‘default’ route
N11
N22 N23
DAG Root : OCP - Energy,
- Delay
OCP:Reliability
Depth 1
no default route
OCP :Objective Code Point –
indicates which routing metrics ,
optimization objectives
N22
N32
N23
N31
N21
OCP:BW
Depth 2
Depth 3optimization objectives
( BW, energy, delay, etc) are in use in a DAGN41Depth 4
Eg: DAGID#1: N41-N32-N22-N23-N11
31 KRnet 2010 Source: Claudio Borean, “ROLL: RPL”, WSN over IP, Sep. 2009
Eg: DAGID#1: N41-N32-N22-N23-N11
RA from N11 RA from N21 RA from N31
I Internet of Things
II Machine Type Communication
III IP based WSN
IV Open Issues
32 KRnet 2010
IoTIoT 구축구축 방안방안 : : 기존기존 표준표준 기술기술 활용활용
Infra Server
기존 표준 기술 활용 사물통신망 구축기존 표준 기술 활용 사물통신망 구축
WSN ManagerApplication Server
계층 이동통신망 IP ZigBee
PHY/MAC2G/3G, WiBro
IEEE802.15.4 IEEE802.15.4
IP Star ZigBee ProNetwork
IP, Star topology
6LoWPANZigBee-Pro stack
Management
- - ZigBee
InterworkiIP IP
ZigBee Bridge,
WSN gatewayng
IP IPg g ,
ZigBee-IP
Infra - - -
WSN Coordinator문제점
• 망 구성 방식별 적용 서비스 제한
- 서비스를 지원할 수 있는 범용 사물통신망 구성 방식 부재
문제점
• 망 구성 방식별 적용 서비스 제한
- 서비스를 지원할 수 있는 범용 사물통신망 구성 방식 부재
Sensor Node
- 서비스별 특성에 따른 사물통신망 다수개 구성
- 사물통신망 연동으로 운용관리, 인프라 구축에 불리
• 사물통신망 고유 서비스 구현 불가능
- 저전력 무선 센서노드에 의한 사물통신망 구성 불가능
- 서비스별 특성에 따른 사물통신망 다수개 구성
- 사물통신망 연동으로 운용관리, 인프라 구축에 불리
• 사물통신망 고유 서비스 구현 불가능
- 저전력 무선 센서노드에 의한 사물통신망 구성 불가능
33 KRnet 2010
- invisible smart space 지원 서비스 제공 불가능- invisible smart space 지원 서비스 제공 불가능
Networking for Networking for IoTIoT
Infra ServerNetworking : Addressing, Neighbor Discovery
• 표준 프로토콜
- ZigBee : 16bit/64bit addressing
- IEEE 802.15.5 : 64bit addressing, mesh networking
Networking : Addressing, Neighbor Discovery
• 표준 프로토콜
- ZigBee : 16bit/64bit addressing
- IEEE 802.15.5 : 64bit addressing, mesh networking
TN Manager
Application Server
- IETF 6LoWPAN, ROLL : IPv6, 표준 제정 중
• 사물 ID
- ZigBee : service profiling
- IETF 6LoWPAN, ROLL : IPv6, 표준 제정 중
• 사물 ID
- ZigBee : service profilingg p g
- IETF 6LoWPAN : host identification
• 문제점
- Global 사물식별 체계, 주소 체계, 연동 체계 부재
g p g
- IETF 6LoWPAN : host identification
• 문제점
- Global 사물식별 체계, 주소 체계, 연동 체계 부재
TN gateway
Global 사물식별 체계, 주소 체계, 연동 체계 부재
- 기존 6LoWPAN 프로토콜 사물통신망 특성 수용 미비
- 사물통신 표준 액세스 프로토콜 부재
Global 사물식별 체계, 주소 체계, 연동 체계 부재
- 기존 6LoWPAN 프로토콜 사물통신망 특성 수용 미비
- 사물통신 표준 액세스 프로토콜 부재
Interworking : TN-TN TN-BackboneInterworking : TN-TN TN-Backbone
TN Coordinator
Interworking : TN TN, TN Backbone
• TN-TN
- 이더넷/2G/3G/WiBro : IP
- 6LoWPAN : IP
- ZigBee : ZigBee Bridge
Interworking : TN TN, TN Backbone
• TN-TN
- 이더넷/2G/3G/WiBro : IP
- 6LoWPAN : IP
- ZigBee : ZigBee Bridge
Things’ Node
- ZigBee : ZigBee Bridge
• TN (ZigBee)-Backbone
- PHY/MAC : IEEE 802.15.4-이더넷/2G/3G/WiBro
- Network : ZigBee – IP
- ZigBee : ZigBee Bridge
• TN (ZigBee)-Backbone
- PHY/MAC : IEEE 802.15.4-이더넷/2G/3G/WiBro
- Network : ZigBee – IP
34 KRnet 2010
• 문제점
- Scalable, 상호 운용성 지원 표준 프로토콜 부재
• 문제점
- Scalable, 상호 운용성 지원 표준 프로토콜 부재
Open IssuesOpen Issues
Architecture (edge devices, servers, discovery services, security, privacy etc)services, security, privacy etc)
Governance, naming, identity, interfaces
Naming, Addressing and routingNaming, Addressing and routing
Service levels and QoS
Security authentification data integrity privacySecurity, authentification, data integrity, privacy
Interconnect and interworking
SpectrumSpectrum
Standards
35 KRnet 2010
- 세계최고 리더 -
"꿈과 희망이 넘치는 미래사회, ETRI가 만들어 갑니다."
36 KRnet 2010
