Internet of Things. Machine Type Communication III. IP based WSN. Open Issues

Transcription

1

2 I II III IV Internet of Things Machine Type Communication IP based WSN Open Issues

3 The Internet of Things? A new dimension added to ICTs From anytime,, any yplace connectivity for anyone Connectivity for anything Connect everyday objects and devices To large databases and networks Seamlessly integrated into the Internet Source: ITU Internet Reports 2005: The Internet of Things: Executive Summary, Nov KRnet 2010

4 Alphabet Soup for M2M : Machine-to-Machine Network WSN : Wireless Sensor Network USN : Ubiquitous Sensor Network MTC : Machine Type Communication IoT : Internet of Things WoT : Web of Things O2N : Object-to-Object Network IoT O2N WSN M2M 3 KRnet 2010

5 Things? 사물 ( 事物 ) : Thing, Object, Matter 1. 일과물건 ( 物件 ) 을아울러이르는말. 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

6 사물간통신관계도 M2M : machine device 간통신 WSN : sensing device 의 wireless 통신 USN : pervasive sensing device 의 wired/wireless 통신 IoT : Internet infra 기반의 thing 간통신 WoT : thing 관련 data web O2N : 개념적개체간통신 Physical device Logical device Thing Matter IoT Machine device Object O2N Sensing device M2M USN WSN Data WoT 사물간통신 5 KRnet 2010

7 Architecture of IoT Things ID tags & Readers Barcodes, RFID tags, GPS chips POS readers, Subway gates Mobile reader PDAs, Cameras Sensors Actuators Logic circuits M2M server EPC server Internet Mobile Network WSN server Networks Local network LAN/WLAN PLC IEEE Public network Internet Telephone Network Cable network Cellular Mobile Network Routers Discovery services Data bases M2M GW RFID GW ZigBee GW ZigBee 6 KRnet 2010

8 ETSI M2M 구조 ETSI Jan. 2009, Machine-to-Machine Communications Technical Committee end-to-end view of Machine to Machine standardization needs M2M Application Client Application Service Capabilities M2M Core M2M Gateway M2M Area Network M2M Device Capable of transmitting data autonomously M2M Area Network UWB, ZigBee, Bluetooth, PLC M2M GW M2M Communications Networks Access, transport, core network xdsl, W-LAN, WiMAX, LTE, GERAN, UTRAN M2M Application (Server) Source: David Boswarthick, M2M Activities in ETSI, SCS Conference, Sophia 2nd July KRnet 2010

9 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 Network. M2M Area Network A M2M Area Network provides connectivity between M2M Devices and M2M Gateways. Examples of M2M Area Networks include: Personal Area Network technologies such as IEEE , SRD, UWB, Zigbee, Bluetooth, etc or local networks such as PLC, M-BUS, Wireless M-BUS. M2M Gateways Equipments using M2M Capabilities to ensure M2M Devices interworking and interconnection to the Network and Application Domain. The M2M Gateway may also run M2M applications. Source: David Boswarthick, M2M Activities in ETSI, SCS Conference, Sophia 2nd July KRnet 2010

10 Key Elements of M2M Architecture (II) M2M Core: Composed of Core Networks and Service Capabilities Service 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. Source: David Boswarthick, M2M Activities in ETSI, SCS Conference, Sophia 2nd July KRnet 2010

11 IoT 관련표준화단체 W3C IPSO ITU-T NGN OASIS Service Platform Phy-Mac Over IPV6 IPV6 Hardware and Protocols IETF 6LowPAN IETF ROLL Routing over Low Power Lossy Networks ZCL ZigBee Alliance. ZB Application Profiles CEN Smart Metering Application OMA IP Network ISO/IEC JTC1 UWSN Wide Area Network GSMA SCAG, CENELEC ESMIG Metering EPCGlobal HGI GS1 Home Gateway Smart Metering Capillary Initiative Access networks M2M Gateway wireline wireless 3GPP SA1, SA3,, WOSA KNX Utilities Metering W-Mbus IEEE 802.xx.x ETSI TISPAN, ITS, Source: David Boswarthick, M2M Activities in ETSI, SCS Conference, Sophia 2nd July KRnet 2010

12 I II III IV Internet of Things Machine Type Communication IP based WSN Open Issues 11 KRnet 2010

13 M2M 통신서비스 M2M (Machine-to-Machine) 서비스 1990 년대초반 : 원격조정, 텔레매틱스개념으로인식 2000 년대초반 : 이동통신망을활용한원격모니터링서비스 machine-to-server; 1-1, uploading Bending machine, POS, OnStar, Fleet management, AWS, 이동통신망사업자별, Solution 별 platform 2000 년대후반 : 이동통신망외무선망, 센서망등을활용한전자장치간통신 Ethernet, WiFi, GSM, CDMA, WCDMA, WiBro, Bluetooth, ZigBee M2M access 이동통신망이외무선망, 유선망, 센서망에의한 M2M 서비스미성숙 활용 현재 M2M 서비스 유럽 : GSM 망을기반으로텔레매틱스, 원격검침, 원격관리서비스활성화 북미 : 텔레매틱스 M2M 기기, 사설플랫폼서비스 12 KRnet 2010

14 M2M 네트워크 M2M 네트워크 Circuit 음성망, 1x/EVDO 패킷망, SMS 망 이동통신망자원활용 M2M 플랫폼 M2M 단말, 모뎀제어 / 관리 Over the Air 개방형 API 제공 Source: LGT M2M Platform 개요 O2N 포럼발표 KRnet 2010

15 기존 M2M 문제점 기존 M2M solution 은 application-specific : fragmented markets 비효율적인 building blocks : 통신망기술별, legacy system 별 고비용 : deployment, maintenance costs, evolution 어려움 Telco, IT provider, Service provider 간협력이어려움 이동통신망이외무선망, 유선망, 센서망에의한 M2M 서비스미성숙 14 KRnet 2010

16 Standards in ETSI & 3GPP ETSI TC M2M 3GPP SA1 TS (0.4.1) Machine-to-Machine communications (M2M); M2M service requirements TS (0.1.1) Machine-to-Machine communications (M2M); M2M functional architecture TS (0.3.1) Machine-to-Machine communications (M2M); Smart metering use case TS (0.2.0) Machine-to-Machine communications (M2M); M2M definitions TS (0.2.1) Machine-to-Machine communications (M2M); use cases for ehealth TS (0.0.1) Machine-to-Machine communications (M2M); use cases for Connected Consumer TS (0.0.2) Machine-to-Machine communications (M2M); use cases for City automation TS (0.0.1) Machine-to-Machine communications (M2M); use cases for Automotive app. TR (8.0.0) Study on facilitating M2M Communication in 3GPP Systems (~ 2007) TR (1.1.1) Service requirements for machine-type communications SA2 TR (0.1.2) System improvement for machine-type communications RAN2 TR 37.8xx (0.0.2) RAN improvement for machine-type communications Source: ETRI 신재승박사 15 KRnet 2010

17 3GPP M2M 구조 Source : ETSI TS M2M Functional Architecture 16 KRnet 2010

18 M2M MTC Terminology Machine-to-Machine (M2M) TR v (in SA1, 2005 ~ 2007) Definition: A form of data communication between entities that do not necessarily need human interaction. Machine Type Communications (MTC) TS v (2009) Definition: A form of data communication which involves one or more entities that do not necessarily need human interaction. H H M M2M M Source: ETRI 신재승박사 17 KRnet 2010

19 MTC 특징 Present structures that have been optimally designed for H2H may be suboptimal for M2M and therefore structures designed for M2M need to be investigated. Current mobile network comm. 과차이점 Machine type communications is different to current mobile 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 terminal. 18 KRnet 2010

20 MTC Features (I) Low mobility This feature applies for those devices which do not move, move infrequently, or within a limited area. Time controlled Time 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. Time tolerant t The 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 only The MTC Feature Packet Switched Only is intended for use with MTC Devices that only require packet switched services. Mobile originated only The MTC Feature Mobile Originated Only is intended for use with MTC Devices that only utilize mobile originated communications. 19 KRnet 2010

21 MTC Features (II) Online small data transmission The 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 transmission The 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 predefined small amounts of data, and then disconnect from the network. Infrequent mobile terminated The MTC Feature Infrequent Mobile Terminated is intended for use with MTC Devices that mainly utilize mobile originated communications. MTC monitoring The 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 events that may possibly be the result of theft or vandalism. 20 KRnet 2010

22 MTC Features (III) Offline indication The 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 indication The 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 message MTC Devices issues a priority alarm in the event of e.g. theft, vandalism or other needs for immediate attention. Extra low power consumption The 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

23 MTC Features (IV) Secure connection The 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 trigger The MTC Feature Location Specific Trigger is intended to trigger MTC Devices in a particular area (e.g. to wake up the MTC Device). Group based Group 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. Group based addressing - The MTC Feature Group Based Addressing is intended d 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

24 I II III IV Internet of Things Machine Type Communication IP based WSN Open Issues 23 KRnet 2010

25 IETF IP based WSN Standardization (I) Extensive interoperability Other wireless embedded network devices Devices on any other IP network link (WiFi, Ethernet, GPRS, Serial lines, ) Established security Authentication, access control, and firewall mechanisms Network design and policy determines access, not the technology Established naming, addressing, translation, lookup, discovery Established proxy architectures for higher-level services NAT, load balancing, caching, mobility Established application level data model and services HTTP/HTML/XML/SOAP/REST, Application profiles Established network management tools Ping, Traceroute, SNMP, OpenView, NetManager, Ganglia, Transport protocols End-to-end reliability in addition to link reliability Most industrial (wired and wireless) standards support an IP option 24 KRnet 2010

26 IETF IP based WSN Standardization (II) IETF 6LoWPAN WG make IEEE link look like an IPv6 link Fragmentation and Reassembly Layer Header Compression Address Auto-configuration Mesh Routing Protocol Network Management, Implementation Considerations Application and Higher layer Considerations, Security Considerations 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 define a Constrained Application Protocol (CoAP) for the manipulation of Resources on a Device 25 KRnet 2010

27 6LoWPANs : Frame Format PHY MAC Payload Frame Check Seq. Dispatch Header Payload 6LoWPAN Frame Dispatch-Header 0 1 Dispatch IPv6, LOWPAN_HC1, LOWPAN_BC0, other IPv6 Dispatch ( ) IPv6 Header Payload HC1 Dispatch ( ) HC1 Header Payload BC0 Dispatch ( ) Sequence Number Mesh Header 1 0 O F Hops Originator Address, Final Address 1 0 O F 0xF Hops Originator Address, Final Address Fragmentation Header dgram_tag dgram_size dgram_tag dgram_size dgram_offset 26 KRnet 2010

28 6LoWPAN : IP HC Encoding TF NH HLIM CI SA SAM M DA DAM D C C Dispatch byte LOWPAN_IPHC byte TF: Traffic Class, Flow Label NH: Next Header HLIM: Hop Limit CID: Context Identifier Extension SAC: Source Address Compression SAM: Source Address Mode M: Multicast Compression DAC: Destination Address Compression DAM: Destination Address Mode 27 KRnet 2010

29 6LoWPAN : Unicast Examples Lowpan Mesh Header Disp atch IPHC NHC Ports Payload 15.4 Disp atch Link Local, Mesh Under (9 bytes) IPHC NHC Ports Payload Link Local, Route Over (4 bytes) Lowpan Mesh Disp IPHC NHC Ports Payload Header atch Global, Mesh Under (9 bytes) Disp atch IPHC HLIM Src Addr Dest Addr NHC Ports Payload Global, Route Over (9 bytes) 28 KRnet 2010

30 ROLL : RPL (I) RPL: Routing Protocol for LLNs First IETF-Draft released for Low power & Lossy Networks,onon June 28, 2009 ARCHROCK & SENSINODE are currently testing & implementing the RPL RPL Properties supporting core set of functionalities corresponding to the intersection of the various application requirements of LLNs customization of RPL to optimize the operation based on application requirements Path for MP2P & P2MP LLN Traffic flows Constraint based routing Cluster tree based hierarchical Directed Acyclic Graph (DAG) Trickle timer for Routing Advert DAG Information Option (RA-DIO) transmission 29 KRnet 2010

31 ROLL : RPL (II) LLN Traffics MP2P is inward traffic towards DAG Root P2MP is an Outward traffic away from DAG Root from neighbors RPL RPL RPL RPL RPL RPL RPL RPL RPL RPL LBR(LLN Border Router) : DAG Root / Egress point Any Router / Node RPL RPL RPL RPL RPL RPL Neighbor Discovery By hearing the multicast Router Advertisements (RAs) messages from neighbors N1 N5 N4 N2 Link Layer mechanism N3 Multicasts RAs Source: Claudio Borean, ROLL: RPL, WSN over IP, Sep KRnet 2010

32 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 route FLOATING DAG : If any node has no parents, then a node itself is DAG root offering no default route OCP :Objective Code Point indicates which routing metrics, optimization objectives ( BW, energy, delay, etc) are in use in a DAG Depth 2 Depth 1 OCP:Reliability N21 OCP:BW N31 Depth 3 Depth 4 N11 N22 N32 DAG Root : OCP - Energy, -Delay N41 N23 Eg: DAGID#1: N41-N32-N22-N23-N11 RA from N11 RA from N21 RA from N31 Source: Claudio Borean, ROLL: RPL, WSN over IP, Sep KRnet 2010

33 I II III IV Internet of Things Machine Type Communication IP based WSN Open Issues 32 KRnet 2010

34 IoT 구축방안 : 기존표준기술활용 Infra Server 기존표준기술활용사물통신망구축 Application Server WSN Manager WSN gateway 계층이동통신망 IP ZigBee PHY/MAC Network Manage ment Interworki ng 2G/3G, WiBro IEEE IEEE IP, Star ZigBee-Pro 6LoWPAN topology stack - - ZigBee IP IP Infra ZigBee Bridge, ZigBee-IP WSN Coordinator Sensor Node 문제점 망구성방식별적용서비스제한 - 서비스를지원할수있는범용사물통신망구성방식부재 - 서비스별특성에따른사물통신망다수개구성 - 사물통신망연동으로운용관리, 인프라구축에불리 사물통신망고유서비스구현불가능 - 저전력무선센서노드에의한사물통신망구성불가능 - invisible smart space 지원서비스제공불가능 33 KRnet 2010

35 Networking for IoT Application Server Infra Server TN Manager Networking : Addressing, Neighbor Discovery 표준프로토콜 - ZigBee : 16bit/64bit addressing - IEEE : 64bit addressing, mesh networking - IETF 6LoWPAN, ROLL : IPv6, 표준제정중 사물 ID - ZigBee : service profiling - IETF 6LoWPAN : host identification TN gateway 문제점 - Global 사물식별체계, 주소체계, 연동체계부재 - 기존 6LoWPAN 프로토콜사물통신망특성수용미비 - 사물통신표준액세스프로토콜부재 TN Coordinator Things Node Interworking : TN-TN TN, TN-Backbone TN-TN - 이더넷 /2G/3G/WiBro : IP - 6LoWPAN : IP - ZigBee : ZigBee Bridge TN (ZigBee)-Backbone - PHY/MAC : IEEE 이더넷 /2G/3G/WiBro - Network : ZigBee IP 문제점 - Scalable, 상호운용성지원표준프로토콜부재 34 KRnet 2010

36 Open Issues Architecture (edge devices, servers, discovery services, security, privacy etc) Governance, naming, identity, interfaces Naming, Addressing and routing Service levels and QoS Security, authentification, data integrity, privacy Interconnect and interworking Spectrum Standards 35 KRnet 2010

37 - 세계최고리더 - " 꿈과희망이넘치는미래사회, ETRI 가만들어갑니다." 36 KRnet 2010