M2M Standardization and its perspectives

Transcription

1 M2M Standardization and its perspectives (ITU-T, ETSI, 3GPP) 윤 주 상 (동의대학교) 1

2 Contents Introduction - General M2M definition, Communication model, Properties of M2M applications ITU-T - Internet of Things Global Standards Initiative(IoT-GSI) - Joint Coordination Activity(JCA) on Internet of Things (JCA-IoT) ETSI TC Machine to Machine(M2M) - Machine- to- Machine communications (M2M);Functional architecture Draft ETSI TS V GPP SA2 SIMTC - System Improvements for Machine-Type Communications (3GPP TR V1.4.0) 2

3 M2M Motivation Mobile market becomes saturated - Market is highly competitive - High investments, and high churn New market - Connected machine market - 50* Billion connectable machines - Market is open to develop - Low investment, high return 3

4 M2M Terminology IoT : Internet of Things M2M : Machine-to-Machine MTC : Machine Type Communication 4

5 Internet of Things IoT - 모든 사물에게까지 네트워크 연결을 제공하는 네트워크의 네트워크 (ITU, 2005). - The networks and services that enable communication among these objects (EU policy Outlook RFID, 2007). - A global network infrastructure, linking physical and virtual objects through the exploitation of data capture and communication capabilities. (CASAGRAS Final Report, 2009). - A world-wide network of interconnected objects uniquely addressable, based on standard communication protocols (EU IoT Workshop, 2009). 5

6 IoT 관련 연구 (1/2) M2M (ETSI TC M2M) - Communication between two or more entities that do not necessarily need any direct human intervention MTC (3GPP SA2 SIMTC) - A form of data communication which involves one or more entities that do not necessarily need human interaction M2M (IEEE p) - Information exchange between a Subscriber station and a Server in the core network (through a base station) or between Subscriber station, which may be carried out without any human interaction 6

7 IoT 관련 연구 (2/2) 사물지능통신 - 사람 對 사물, 사물 對 사물 간 지능통신 서비스를 언제 어디서나 안전하고 편리하게 실시간으로 이용 할 수 있는 미래 방송통신 융합 ICT 인프라. 기계간의 통신 및 사람이 동작하는 디바이스와 기계간의 통신. 통신과 IT기술을 결합하여 원격지의 사물의 상태정보 등을 확인할 수 있는 제반 솔루션을 의미함. - TTA PG 708 / M2M포럼에서 표준화 진행 7

8 General M2M-Networks Environments 8

9 Properties of M2M applications Large number of devices - Typical applications require a lot of devices deployed in the same area leading to high density or distant leading to a large spread. Devices can send and/or receive frequently or infrequently small amounts of data. Low mobility for devices meaning that they don t move, move infrequently or move in a predefined region. Devices may be grouped into Groups. - This is interesting for charging, policing and multicast(toward a group) Time tolerant (generally), since data can be usually delayed. However, real-time transmission should also be considered for some applications. Time controlled as the devices may send and receive data only at certain periods of time. Security of exchanges between the devices and the server. 9

10 Application Fields of M2M (1/2) Track and trace use case: Commonly in automotive applications where M2M embedded modules exist in vehicles Monitoring use case: commonly in monitoring and controlling consumption (power,...),monitoring animals Control use case: Controlling vending machines where embedded M2M modules send data about their status (fill-level, malfunctions...) and can be updated automatically 10

11 Application Fields of M2M (2/2) Health care use case: where persons suffering from heart disease Home automation use case: where the M2M application are very useful for security, health, energy efficiency 11

12 In ITU-T 12

13 IoT Definition ITU Report in IoT adds a new dimension to the ICT world ( 4A Vision ) From traditional anytime, any place connectivity for anyone, The Internet of Things brings connectivity for anything Common understanding at international level ITU Standardization Sector is harmonizing IoT definitions at a global level 13

14 Global Standards ITU s IoT Global Standards Initiative(GSI) - Provides a visible single location for information on and development of global IoT standards - Harmonizes different approaches to the IoT architecture worldwide, e.g. definitions Joint Coordination Activity(JCA) on IoT - Coordinates ITU-T work related to the IoT, network aspects of identification of things and ubiquitous sensor networks (USN), for instance: - Maintains list and roadmap of ITU-T IoT standardization items 14

15 Work Plan The IoT-GSI is working on a new Recommendation IoT- Overview which aims to cover: - High level concept (vision) - Business and social drivers, ecosystem and business models - Essential terminology - Scope (applications/services, networks, M2M, devices, security, enabling technologies, etc.) - Very High Level Requirements - Key features / key areas / key components - High level IoT diagrams Target for approval:

16 In ETSI 16

17 ETSI TC M2M ETSI - The European Telecommunication Standards Institute ETSI Technical Committee(TC) M2M - Focused on M2M systems - Established in Europe, USA, China, Korea and Japan companies 17

18 Connecting Things Cluster Home for Future Internet activities in ETSI M2M is the key ehealth (domain) CLOUD (enabler) Wireless Factory (application) RFID (identification) All things SMART (domain 18

19 ETSI M2M Vision Connecting Things 19 출처: ETSI M2M workshop 2011

20 ETSI M2M Challenge Existing M2M solutions are highly fragmented and technology is typically dedicated to a single application (e.g. fleet management, meter reading, vending machines). Multitude of technical solutions and dispersed standardization activities result in the slow development of the global M2M market. Standardization is a key enabler to remove the technical barriers and ensure interoperable M2M services and networks, that may deployed worldwide. 20

21 M2M is inverting the pipes 21

22 Simple M2M Architecture 22 출처: ETSI TC M2M Presentation

23 ... based on existing Technologies 23 출처: ETSI TC M2M Presentation

24 Release 1 Specifications 24

25 M2M Service Requirement (TS V1.1.1) 4. General requirements 5. Management 25

26 M2M Service Requirement 6. Functional requirement for M2M services 7. Security 8. Naming, numbering and addressing M2M Application Identifier M2M Service Device Level M2M Service SUB Identifier M2M Service HW Identifier M2M Transport Device Level M2M Access Network SUB Identifier M2M Access Network HW Identifier M2M Access Network Address 26

27 M2M Functional Architecture Why ETSI M2M? - Provide an M2M architecture with a generic set of capabilities for M2M services - Provide a framework for developing services independently of the underlying network - Facilitate deployment of vertical applications - Facilitate innovation across industries by exposing data and information and providing services. 27

28 M2M high level system 28 출처: ETSI TC M2M Presentation

29 Example, Connected Home 29

30 In 3GPP 30

31 3GPP MTC Specifications Release 10 - Focus on overload and congestion control Extended Access Barring Low priority access APN based congestion control Downlink throttling Release 11 - High Priority assigned to: Numbers and addressing (including no E.164 and PS only) Improvements of device triggering Interfaces between MTC Server and mobile network - Low Priority assigned to: Small Data Transmission Signaling Congestion Control Low Power Consumption Low Mobility Group Based Optimization 31

32 Network Improvements for MTC Current mobile network is optimized for H2H traffic not for Machine Type Communications Optimizations for MTC are necessary Lower costs to reflect lower MTC ARPUs Optimized support for triggering Prepare for E.164 number shortages Interface for external M2M Server 32

33 How to optimize efficiency of connections 33

34 MTC Communication Models Multiple MTC Applications using Diverse Communication Models 34

35 Architectural Reference Model 3GPP Architecture for Machine-Type Communication - MTCsp: new control interface for interactions with MTC Server - MTC-IWF: interworking function between (external) MTC Server and operator core network Security, Authorisation, Authentication, Charging 35

36 Protocol Stacks User plane Control plane 36

37 MTC Addressing Use Case Description - 3GPP Release 11 specifications should be developed in the following areas: IPv6 as the primary solution for IP addressing of UEs used for MTC. IPv4 based solutions are considered transition solutions and are deprecated. 37

38 MTC Identifiers Use Case Description - The identifiers can be categorized into: Internal Identifiers - Used within the 3GPP system to identify a UE using a subscription (or the subscription itself e.g. when the UE is not registered). External Identifiers - Used from outside the 3GPP system (e.g. at the MTCsp interface), to refer to a UE using a subscription (or the subscription itself e.g. when the UE is not registered). 38

39 MTC Identifiers Solutions IMSI is the internal identifier. The existing 3GPP identifiers are not modified, Alternative identifier(s) to MSISDN shall be supported on the MTCsp as the external identifier(s) External identifier - Domain-Identifier that identifies a domain that is under the control of a Mobile Network Operator (MNO) - Local-Identifier that is assigned by the mobile network operator. This identifier is used to derive or obtain internal identifier by the network operator Multiple external identifiers can map to single internal identifier (i.e. IMSI) 39

40 Example of MTC Identifiers External Identifier = <Local-Identifier> <MNO-Identifier> - The 2-tuple (local-identifier, MNO-Identifier) becomes globally unique Example Formats: - As NAI: local-identifier@mno-domain-name - As FQDN: local-identifier.mno-domain-name 40

41 MTC Device Trigger Wake up the device by the network, e.g. to initiate communications Network initiated communications in the following use cases - Device is not attached - Device has no connection - NAT association is lost - Network failure (e.g. context for device is lost Result may be connection establishment or small data (e.g. SMS). Device may also initiate other activities prior to initiation of communication 41

42 Device Triggering Solutions (1/2) Trigger initiation via MTCsms based on existing large account SMS interface Trigger initiation via new MTCsp interface - E.164 MSISDN-less triggering - MTC-IWF can determine optimal trigger delivery method 42

43 Device Triggering Solutions (2/2) Trigger optimisations - SMS delivery via Evolved Packet Core needs optimization There is no native SMS support in Evolved Packet Core, two existing options for SMS delivery over EPC are not ideal for MTC - SMS over IMS requires IMS registration which is not cost efficient for MTC devices - SMS over SGs relies on the CS domain, where PS-only MTC subscriptions are desired - Optimizations are needed to enable authenticity of trigger messages Unauthorized triggering of MTC Devices shall be prevented - SMS relies on E.164 MSISDNs; triggering needs to be supported without MSISDNs 43

44 Conclusions 44 출처: ETSI M2M workshop 2011, Ericsson