M2M Juniper
Content
WHITE PAPER
MACHINE-To-MACHINE (M2M)— THE RIsE of THE MACHINEs
Copyright © 2011, Juniper Networks, Inc.
1
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Table of Contents
Executive summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 opportunities for New Business Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 M2M Network Architecture Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Present-Day Networks and M2M Challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 M2M standards status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 ETsI and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3GPP and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3GPP M2M Communication scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 About Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table of Figures
figure 1: Infonetics Research M2M connections forecast (2009–2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 figure 2: Revenue per vertical. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 figure 3: Inverting the pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 4: MNo and partnership model co-operation for M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 5: ETsI M2M network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 6: ETsI use case technical reports reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 7: ETsI Ts 102 690 system architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 8: stage 3 for ETsI M2M Release 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 9: overall 3GPP high-level M2M architecture approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 10: 3GPP M2M communication, scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 11: 3GPP M2M communication, scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 12: 3GPP M2M communication, scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
List of Tables
Table 1: 3GPP Machine-Type Communication Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Table 2: High-Level Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Table 3: Differences Between H2H and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Table 4: standards, specification Descriptions and References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Table 5: ETsI M2M Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Table 6: Major Components of 3GPP M2M Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Executive Summary
This paper presents a high- level view of a rekindled market for Machine-to-Machine (M2M) communications. M2M communication can be agnostic to the access technologies and will uses a broad range of fixed and wireless technologies (cellular, Wi-fi, wireline, DsL, satellite or even serial with gateways). several key requirements emerge as the industry adopts the M2M applications toward the Internet of things. Juniper’s portfolio of mobility solutions, such as Juniper Networks® MobileNext, Junos® Pulse for security, Junos space for management and Junos sDK position the company for leadership in this market: • Mobile Broadband Gateway (MBG) and Mobile Control Gateway (MCG) address scaling aspect for M2M endpoints. • Junos Pulse for security expertise helps prevent man-in-the-middle attacks by examining the option of providing embedded lightweight Junos Pulse for M2M. • Junos sDK provides an open API and facilitates third-party development and integration tailored to M2M/MTC. This paper focuses on cellular M2M/MTC communications and describes current considerations by key standard organizations directly looking into the technical challenges and network enhancements required to address these opportunities. It is directed to the field force involved with mobile wireless service providers. Through this educational paper, network administrators are introduced to the growing market need for cellular M2M infrastructure enhancements and application services.
Introduction
Although cellular M2M communication has existed for some time now, it has been a challenging and niche market. • Existing M2M solutions are fragmented and usually are dedicated to a specific single application: • There are many different incumbent and legacy technical solutions that lack standard homogenization. • There is a need for new revenue models to address generally small volumes of traffic from M2M applications. According to several market research firms, this market is on an upward path as the M2M market is projected to grow exponentially in the coming years. Personal communication has evolved from traditional phone calls to today’s modern text messaging using short Message service (sMs) or multimedia content through Multimedia Messaging service (MMs). Cellular M2M communications for 2G/3G use similar types of mechanisms to send short data bursts of information to report residential utility meter readings, locations for telemetry applications and also for remote upgrades/activations of machines such as parking meters. Concurrently, advances in wireless technologies, wider availability of application services and the upcoming demands created by regulatory and policy initiatives for some verticals such as utilities/smart grid—the EU recently issued a mandate on smart Metering (M/441) to the European standards Development organizations (sDos) and the United states National Broadband Plan (March 2010)—prompted the industry (M2M modem vendors, operators, standards, application providers) to take a second look at this overall segment. The M2M ecosystem is developing and opening the doors for tremendous opportunities beyond the “traditional M2M market segment.” figure 1 shows the predictions by Infonetics Research for M2M connections.
Embedded mobile M2M connections are forecast to reach 428 million by 2014 450 Connections in Millions 0
2009
2014
© Infonetics Research, Embedded Mobile M2M Modem Market Outlook, Oct. 2010
Figure 1: Infonetics Research M2M connections forecast (2009–2014)
Copyright © 2011, Juniper Networks, Inc.
3
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
furthermore, Harbor Research projects M2M to reach 390 million connections by 2014. Although the projections are slightly different from each market research firm, it is undeniable that the M2M market is significantly growing. other markets verticals—besides utilities/smart grid/energy/telemetry—include transportation and logistics, security/ surveillance, healthcare, retail/vending, consumers, and miscellaneous (including environment, education and military). As depicted in figure 2, Harbor Research shows its revenue projections per vertical.
Exhibit: Value-Added Application Services by Venue
$350,000 $300,000 $250,000 Millions $200,000 $150,000 $100,000 $50,000 $0 2008 2009 2010 2011 2012 2013
Source: Harbor Research, Inc.
Security/Infrastructure Healthcare IT/Networks Transportation Retail Buildings Energy Industrial
Figure 2: Revenue per vertical
some of those verticals such as smart metering and healthcare are gaining popularity and are in early deployment stages. They already contribute at changing the economics and user experience perception. for example, gas and electric utility companies can reduce their costs by discontinuing meter readings by their prescribed employees. eHealth can offer an improved patient experience for those who have limited mobility or remote access by providing vital sign status through networked monitoring equipment associated with the patient’s identification. There are many different MTC applications with distinct characteristics. As such, every optimization feature put forward is not suitable for all MTC applications. In other words, there is not a unique set of requirements that can be applied to all MTC applications. Network operators must be able to differentiate between their MTC devices to provide MTC features on a persubscription basis. subscriber database information as well as Policy and Charging Rules function (PCRf) will play a key role in this.
4
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Table 1 presents a non-exhaustive list of machine-type communication applications (3GPP TR 22.368).
Table 1: 3GPP Machine-Type Communication Applications
SERvICE AREA MTC APPLICATIonS
security
surveillance systems Backup for landline Control of physical access fleet management order management Pay as you drive Asset tracking Navigation Traffic Information Road tolling Road traffic optimization/steering Point of sales Vending machines Gaming machines Monitoring vital signs supporting the aged or handicapped Web access telemedicine points Remote diagnostics sensors Lighting Pumps Valves Elevator control Vending machine control Vehicle diagnostics Power Gas Water Heating Grid control Industrial metering Digital photo frame Digital camera e-book
Tracking, Tracing
Payment
Health
Remote Maintenance/Control
Metering
Consumer Devices
Table 2 lists ETsI’s high-level domains with associated examples of possible industry use cases.
Table 2: High-Level Domains
DoMAInS ExAMPLE
security Transportation Healthcare smart Energy supply/Provisioning City Automation future
surveillance application, alarms, tracking (object/person). fleet management, emission control, toll payment, road safety. Related to eHealth, personal well-being and security. Measurement, provisioning/billing of utilities, metering. freight supply and distribution monitoring, vending machines. Public lighting, waste management. Many more new domains to be developed.
opportunities for new Business Models
M2M provides low Average Return Per Device (ARPD) but at the same time offers low churn (if any), making it possible for operators and executives to design lucrative business models that offer services as the industry shows converging signs that this market segment can emerge as a serious and significant opportunity.
Copyright © 2011, Juniper Networks, Inc.
5
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
The current marketplace is extremely fragmented, with many small, vertical and specific niche applications. Efforts are underway to bring some level of normalization in the direction of moving away from the current siloed landscape to a more horizontal integrated approach. occasionally, some in the industry refer to this as “inverting the pipes and going to mass market applications,” as shown in figure 3.
Existing Proprietary Vertical Applications
Business Application 1 Business Application 2 Business Application 3
Applications Share Common Infrastructure, Environments, and Network Elements
Business Application 1 Business Application 2 Business Application 3
Application Infrastructure
Existing Mobile Infrastructure
Existing Mobile Infrastructure
Existing Mobile Infrastructure
Network Infrastructure
CONVERGED NETWORK
(IP and Mobile Infrastructure)
SIM based Dedicated Services
SIM based Dedicated Services
SIM based Dedicated Services
Gateway Concentrators
M2M Device
M2M Device
M2M Device
Figure 3: Inverting the pipe
Currently, until new business models develop, mobile network operators have traditionally teamed with partners in an attempt to benefit from the M2M market segment. figure 4 (following chart) shows what several operators have accomplished with partnership models.
THE REVENUE OPPORTUNITY FOR MOBILE CONNECTED DEVICES IN SATURATED MARKETS
TELENOR
New business unit “Telenor Objects” and co-operation withTelit and Volvo for in-car SIM card
TELIT VOLVO CELEVOKE ECHELON QUALCOMM ONSTAR BY GM JASPER WIRELESS WAVECOM CINTERION SECURITAS DIRECT SECURITAS DIRECT
T-MOBILE
Echelon and T-Mobile alliance to reduce the cost of a secure smart grid network for utilities; also co-operation with Celevoke to sell wholesale data services to M2M clients
VERIZON WIRELESS
Co-operation with OnStar/GM, also Verizon Wireless and Qualcomm announce joint venture to provide advanced M2M solutions (nPhase)
AT&T
Emerging devices business unit launched in October 2008; combined platform with Jasper Wireless “Orange M2M Connect” platform; strategic partnerships with Wavecom, Alcatel, and Cinterion, Orange (France and Spain) are co-operating with Securitas Direct to use wireless GSM network for more advanced surveillance solutions New M2M platform July 2009, Vodafone Spain also co-operates with Securitas Direct
ORANGE
VODAFONE
TELEFONICA
Telefonica’s Smart M2M platform in co-operation with Telit
TELIT
source: Northstream white paper, february 2010
Figure 4: Mno and partnership model co-operation for M2M
6
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
M2M network Architecture Considerations
This section discusses M2M network architecture considerations both in terms of suitability of existing wireless networks in supporting M2M applications as well as new architectural enhancements as proposed by standards bodies, such as 3GPP, to efficiently support M2M applications.
Present-Day networks and M2M Challenges
The current mobile networks (3GPP/2) primarily are designed for human-to-human (H2H) communications—voice call (sMs/MMs) and server-to-human (downloading/streaming). However, these technologies might not be optimal for M2M application services. M2M networks are defined as communication without or with limited human end user intervention. Note that the human end user is not typically the initiator of the input but only occasionally and optionally the recipient for the output. Table 3 summarizes the differences between H2H and M2M.
Table 3: Differences Between H2H and M2M
ToPICS H2H M2M
Density
Wireless devices’ penetration rate is increasing. There are a lot of us. But maybe not that much compared to M2M potential. Most of the traffic is downloaded and requires significant amounts of bandwidth (file, Web and video streaming). We can buy a new one—we can recharge. We do have a tolerance for it even when it comes to voice. Worth comes to worth. Instinct tells us or we just know if it has been stolen.
M2M outnumbers human end users by order of magnitude. 3GPP sA1 requires solutions to cater for at least two orders of magnitude. Another possible reason for IPv6. Possible shortage of phone numbers. Traffic is mainly uploaded and most of it requires small amounts of bandwidth (video surveillance might require more). It must be capable of auto-generating power or be self-sustaining for long periods. some applications are mainly for real-time control; urgent/emergency action would have little tolerance. Not so much here. Robust security, even confidentiality ought to be available. New considerations are being made regarding Machine Communication Identity Module (MCIM) in Universal Integrated Circuit Card (UICC) or Trusted Environment (TRE). Low ARPD. High level of endpoints connecting from time to time (can be predefined) to transmit small amounts of data. However, control network overload aspects must be considered. To be created/adapted for new opportunities on top of common infrastructure. Push/pull behavior. Might require much longer dormant period to minimize signaling on control plane.
Data Volume
Battery Delay security
Revenue Dimensioning
Good. Normal business case.
Value Chain Reachability
Well defined. satisfying.
Using Table 3 as a reference, it is apparent that M2M and H2H traffic patterns are quite different and accommodations and optimizations are needed in current networks for M2M while maintaining or at least not disrupting existing H2H services.
Copyright © 2011, Juniper Networks, Inc.
7
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
M2M Standards Status
The European Telecommunications standardization Institute (ETsI) and 3rd Generation Partnership Project (3GPP) are two main standard groups that have been investigating M2M’s challenges, issues, gaps, and architectures. To a lesser degree, WiMAX forum is also looking at M2M. Table 4 summarizes the two standards and associated specification descriptions and references.
Table 4: Standards, Specification Descriptions and References
STAnDARDS SPECIFICATIon DESCRIPTIon SPECIFICATIon REFEREnCE
ETsI
M2M functional Architecture M2M service Requirements smart Metering Use Cases eHealth Use Cases Automotive Applications Use Cases City Applications Use Cases M2M interfaces mIa, mId, dIa
ETsI Ts 102 690 ETsI Ts 102 689 ETsI TR 102 692 ETsI TR 102 732 ETsI TR 102 898 ETsI TR 102 897 ETsI Ts 102 921 3GPP TR 22.868 3GPP Ts 22.368 3GPP TR 23.888 3GPP TR 33.812 3GPP TR 33.868 3GPP TR 37.868 3GPP TR 43.868
3GPP
sA1- M2M study Report sA1- MTC service Requirements sA2 - system Improvements for MTC sA3 - M2M security Aspect for Remote Provisioning and subscription Change sA3 - security Aspect of MTC 3GPP study on RAN Improvements for MTC 3GPP study on GERAN Improvements for MTC
ETSI and M2M
In 2009, ETsI created a Technical Committee (TC) whose goal is to develop M2M standards. Release 1 planning stages are as follows: stage 1 (requirements)—Q3 2010 • Based on several M2M use cases stage 2 (architecture)—Q3 2011 • Key capability identified • Message flows documented • Key interfaces identified for Release 1 stage 3 (detailed specifications) stage 3 (protocol)—Q4 2011 • Working on three main interfaces—mId, dIa and mIa.
8
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 5 depicts the high-level architecture concept that ETsI proposes for M2M application support.
M2M Application
M2M Area Network
Service Capabilities
M2M Gateway
Client Application
M2M CORE
APPLICATION DOMAIN
NETWORK DOMAIN
M2M DEVICE DOMAIN
Figure 5: ETSI M2M network
Using figure 5 as a reference, Table 5 lists and defines the major components that comprise the ETsI M2M network architecture.
Table 5: ETSI M2M network Architecture
MAjoR CoMPonEnTS DEFInITIon
M2M Device M2M Area Network (device domain) M2M Gateway M2M Communication Networks (network domain) M2M Applications
Is capable of replying to requests for data contained within those devices or capable of transmitting data contained within those devices autonomously. Provides connectivity between M2M devices and M2M gateways— wireless personal area networks (WPANs), Wi-fi, Zigbee/802.15.4, Bluetooth and RfID. Uses M2M capabilities to ensure M2M devices are interworking and interconnected to the communication network. Involves communications between the M2M gateways and M2M application (3G, LTE, WiMAX, WLAN, and wireline). Contains the middleware layer where data travels through various application services and is used by the specific business-processing engines.
Copyright © 2011, Juniper Networks, Inc.
9
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 6 shows a reference to the ETsI use case technical reports, covering many types of industries from smart metering and eHealth to city automation.
source: ETsI MWC Barcelona feb. 2011.
Work Methodology
TR 102 692 Smart Metering
PUBLISHED
TR 102 732 eHealth
TR 102 857 Connected Consumer
TR 102 898 Automotive
TR 102 897 City Automation
TR 102 920 Delivery of M/441 Work
STAGE 1
TS 102 689 M2M Service Requirements
PUBLISHED
TR 102 725 M2M Definitions
TR 102 935 Smart Grid Impacts on M2M
STAGE 2
TS 102 690 M2M Functional Architecture
TR 101 531 Re-use of 3GPP Nodes by M2MSC Layer
TR 102 167 Threat Analysis and Counter Measures to M2M Service Layer
STAGE 3
TS 102 921 M2M Communications; mia, dia, and mid interfaces
Source: ETSI MWC Barcelona, February 2011
Figure 6: ETSI use case technical reports reference
The M2M device domain includes: • M2M device • M2M area network • M2M gateway. The network and application domain includes: • Access network • Transport network • M2M core • M2M applications • Network management functions • M2M management functions.
10
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 7 depicts the high-level system architecture put forward by ETsI Ts 102 690.
PC/Dedicated Appliance
M2M Applications
M2M CORE
M2M Management Functions
Service Capabilities
M2M Capabilities
(include enhancements to existing CN capabilities)
CORE NETWORK (CN) M2M-specific Management Functions
M2M Capabilities Network Management Functions M2M Capabilities TRANSPORT NETWORK ACCESS NETWORK Network and Applications Domain
Based on existing standards 3GPP, TISPAN, IETF, etc.
M2M Device Domain M2M Applications M2M Capabilities M2M GATEWAY M2M Applications M2M Capabilities M2M DEVICE
Based on existing standards and technologies, e.g.: DLMS, CEN, CENELEC, PLT, Zigbee, M-BUS, KNX, etc.
M2M Devices
M2M AREA NETWORK
Figure 7: ETSI TS 102 690 system architecture
ETsI (Ts 102 690) M2M service capabilities functional architecture framework is progressing to stage 3 to define identified reference points—mId, dIa and mIa, as illustrated in figure 8.
M2M Application M2M Application
Stage 3 for M2M R1
mla dla
SC1 M2M Service Capabilities SC8 SC2
SC7
Routing Function
SC3
SC6 SC5 mld
SC4
M2M SERVICE CAPABILITIES
Core network function, based on existing standards (3GPP, ETSI, TISPAN, IETF...)
Communication Modules
M2M DEVICE/ GATEWAY DOMAIN
CORE NETWORK A
CORE NETWORK B
Figure 8: Stage 3 for ETSI M2M Release 1
Copyright © 2011, Juniper Networks, Inc.
11
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
service capabilities can access network core functions through existing interfaces (defined by I.E 3GPP and ETsI) and provide functions that can be shared among applications. In the following list, X represents N for networks, G for Gateway and D for Device, as previously described in Table 3. The following M2M service capabilities (sC) include: • Application Enablement (xAE) • Generic Communication (xGC) • Reachability, Addressing and Repository (xRAR) • Communication selection (xCs) • Remote Entity Management (xREM) • sECurity (xsEC) • History and Data Retention (xHDR) • Transaction Management (xTM) • Compensation Broker (xCB) • Telco operator Exposure (xToE) • Interworking Proxy (xIP) mIa—Allows an application to access M2M sCs in the network and applications domain. dIa—Allows an application within an M2M device to access the different sCs in the same M2M device or in an M2M gateway. Allows an application within an M2M gateway to access the different service capabilities in the same M2M gateway. mId—Enables an M2M device or M2M gateway to access M2M sCs in the network and application domain.
3GPP and M2M
In 2007, a 3GPP study item (TR-22.868) on M2M communications titled Study on Facilitating Machine to Machine Communication in 3GPP Systems was completed. This particular 3GPP study has shown potential for M2M services beyond the current “premium M2M market segment.” In 2010, 3GPP started the process of developing the study’s results into a specification phase—Ts 22.368 Service Requirements for Machine-Type Communication (MTC) Stage 1 June 2010; TR 23.888 System Improvements for MTC July 2010—to address required network system improvements to support MTC. Ts 22.368 defines general requirements and specific MTC features, and it generated two additional study items that focus on alternatives for using E.164 numbering for MTC and enhancements for MTC (TR 22.888). TR 23.888 identifies key issues and proposes corresponding possible solutions. 3GPP Release 10 addresses change requests related to congestion and overload control while other remaining items are deferred to later releases. TR 33.812 is a feasibility study on the security aspects of remote provisioning and change of subscription for M2M equipment. TR 33.868 focuses on the security aspect of MTC and is expected to be delayed until 3GPP Release 11 as a new work item. 3GPP Radio Access Network (RAN) and GsM Edge Radio Access Network (GERAN) groups are also active and are working on the improvements for MTC with TR 37.868 and TR 43.868.
12
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 9 depicts the high-level 3GPP architecture (3GPP Ts 23.888).
MTC Device MTCu
MTCsms 3GPP Bearer Services/ SMS/IMS MTCi 3GPP PLMN-MTC SERVER IWK Function
MTC Server
MTC Server
Figure 9: overall 3GPP high-level M2M architecture approach
The MTC server can be located either inside or outside of the operator domain. Reference points MTCi and MTCsms can be part of the interworking function itself that could facilitate access to the MTC server using non-3GPP interfaces. Roaming scenarios are considered and the MTC devices would connect using MTCu from visited public land mobile Network (PLMN) to access home services. Table 6 identifies the major components of the 3GPP M2M architecture.
Table 6: Major Components of 3GPP M2M Architecture
CoMPonEnTS/TERMInoLoGy DEFInITIon
MTC MTCu MTCi MTCsms MTC User MTC Device MTC server
Machine-Type Communication. Reference point providing MTC devices access to 3GPP network for transporting user traffic. Reference point for MTC server to connect 3GPP network using 3GPP bearer service. Reference point for MTC server to connect 3GPP network using 3GPP sMs. Legal entity that uses MTC terminals (usually the contractual partner for the operator). User equipment for MTC communicating with MTC server or device. An entity that can communicate with MTC devices and connects to the PLMN.
3GPP M2M Communication Scenarios
Three scenarios have been defined in 3GPP Ts 22.368 pertaining to the communication between MTC devices and the MTC server: • scenario 1 (Located in the operator domain) • scenario 2 (Located outside the operator domain) • scenario 3 (Communication directly with each other without an intermediate MTC server).
Scenario 1
scenario 1 represents MTC devices communicating with the MTC server located in the operator domain. The network operator domain offers an API on its MTC server, and the MTC user accesses the MTC server through this API.
MTC User MTC Server MTC Device API
OPERATOR DOMAIN
Figure 10: 3GPP M2M communication, scenario 1
Copyright © 2011, Juniper Networks, Inc.
13
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Scenario 2
scenario 2 represents MTC devices communicating with the MTC server located outside the operator domain. In this case, the network operator offers network connectivity to the MTC server outside of its domain.
MTC Server/ MTC User MTC Device
OPERATOR DOMAIN
Figure 11: 3GPP M2M communication, scenario 2
Scenario 3
scenario 3 represents MTC devices communicating directly with each other without an intermediate MTC server.
MTC Device
OPERATOR DOMAIN A
OPERATOR DOMAIN B
MTC Device
Figure 12: 3GPP M2M communication, scenario 3
3GPP Release 10 Feature Requirements for M2M
overall, approximately 14 specific feature service requirements have been identified in 22.368 Release 10. Low Mobility • MTC devices are static, nomadic and move only within a predefined region. • There is a reduction in mobility signaling and reporting frequency. Time Controlled • Data can be sent or received only during certain predefined periods. • signaling outside of these predefined time windows can be minimized. Time Tolerant • Data application can support delay. Packet switched only • Network access allows for services to be obtained, and triggering should be possible with or without a Mobile station International subscriber Directory Number (MsIsDN). small Data Transmissions • Most MTC devices send small amounts of data uplink. Mobile originated only • The network should provide mechanisms to reduce control signaling originated by MTC devices Infrequent Mobile Terminated
14
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
MTC Monitoring • It is not intended to prevent theft. • Detection functionality of events such as unexpected behaviors and loss of connectivity is provided. • The end user is notified and predetermined action is taken. Priority Alarm Message (PAM) • There is a need for immediate attention. • It is used in case of theft, urgency or emergency. secure Connection • MTC devices connect through a roaming operator. Location specific Trigger • operator stores location information and can wake up and trigger the MTC device in a particular area. Network Provided Destination for Uplink Data • The ability to transmit to a specific address is available. Infrequent Transmission • Network resources are allocated only when needed. Group Based MTC features • It should be possible to broadcast to a specific group of devices. • Combined policy, charging, addressing and Qos for a specific group should be possible. 3GPP Release 10 will focus on the following general functionalities required to support the above-listed features: • overload control • Addressing • Identifiers • Triggering • Remote management • subscription control • Charging • security.
Conclusion
The current mobile network is optimized for H2H traffic patterns and not necessarily for M2M. Enhancements and optimizations are needed for MTC to address issues such as scalability, IP addresses shortages and telephone numbers to protect against control network overload, to differentiate between MTC applications that have different characteristics, to help secure connectivity between M2M devices and the network as well as with the application servers, and to lower costs to align with lower ARPD for MTC. We like to talk about killer applications for wireless cellular. Many people think the next killer application is video streaming, which is estimated to represent up to 60 percent of data volume. Today, M2M might not be perceived as a killer application segment. However, even though M2M is expected to have applications predominately for low data usage (some might generate higher traffic in the case of video surveillance), the order of magnitude for M2M endpoints that will connect to the network is significant. Current forecasts indicate a large market for MTC. We have seen a first phase of fragmented, niche M2M vertical applications. Currently, a second phase is occurring, driven by regulatory and policies initiatives. A third phase is expected to follow, with the Internet of things made possible through the advent of technologies such as 6lowpan from IETf. M2M communications bring the opportunity to use mobile networks in a new way. We probably cannot foresee today what
Copyright © 2011, Juniper Networks, Inc.
15
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
impact the rise that machines might have on mobile data usage. However, it definitely opens up the possibility to create new businesses. Juniper Networks can facilitate mobile network operators to start addressing M2M segment opportunities with its MobileNext product portfolio (MobileNext Broadband Gateway, MobileNext Control Gateway)—offering unprecedented subscriber density, call setup capability and PCRf partnerships (MobileNext Policy Manager) to help translate these new business rules into profitable services. Juniper Networks is in a unique position to leverage its security expertise with Junos Pulse and Junos sDK by providing open APIs for partnership development and integration.
About juniper networks
Juniper Networks is in the business of network innovation. from devices to data centers, from consumers to cloud providers, Juniper Networks delivers the software, silicon and systems that transform the experience and economics of networking. The company serves customers and partners worldwide. Additional information can be found at www.juniper.net.
Corporate and Sales Headquarters Juniper Networks, Inc. 1194 North Mathilda Avenue sunnyvale, CA 94089 UsA Phone: 888.JUNIPER (888.586.4737) or 408.745.2000 fax: 408.745.2100 www.juniper.net
APAC Headquarters Juniper Networks (Hong Kong) 26/f, Cityplaza one 1111 King’s Road Taikoo shing, Hong Kong Phone: 852.2332.3636 fax: 852.2574.7803
EMEA Headquarters Juniper Networks Ireland Airside Business Park swords, County Dublin, Ireland Phone: 35.31.8903.600 EMEA sales: 00800.4586.4737 fax: 35.31.8903.601
To purchase Juniper Networks solutions, please contact your Juniper Networks representative at 1-866-298-6428 or authorized reseller.
Copyright 2011 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, Netscreen, and screenos are registered trademarks of Juniper Networks, Inc. in the United states and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
2000416-001-EN
May 2011
Printed on recycled paper
16
Copyright © 2011, Juniper Networks, Inc.
MACHINE-To-MACHINE (M2M)— THE RIsE of THE MACHINEs
Copyright © 2011, Juniper Networks, Inc.
1
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Table of Contents
Executive summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 opportunities for New Business Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 M2M Network Architecture Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Present-Day Networks and M2M Challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 M2M standards status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 ETsI and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 3GPP and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3GPP M2M Communication scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 About Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Table of Figures
figure 1: Infonetics Research M2M connections forecast (2009–2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 figure 2: Revenue per vertical. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 figure 3: Inverting the pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 4: MNo and partnership model co-operation for M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 figure 5: ETsI M2M network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 figure 6: ETsI use case technical reports reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 figure 7: ETsI Ts 102 690 system architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 8: stage 3 for ETsI M2M Release 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 figure 9: overall 3GPP high-level M2M architecture approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 10: 3GPP M2M communication, scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 figure 11: 3GPP M2M communication, scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 figure 12: 3GPP M2M communication, scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
List of Tables
Table 1: 3GPP Machine-Type Communication Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Table 2: High-Level Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Table 3: Differences Between H2H and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Table 4: standards, specification Descriptions and References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Table 5: ETsI M2M Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Table 6: Major Components of 3GPP M2M Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Executive Summary
This paper presents a high- level view of a rekindled market for Machine-to-Machine (M2M) communications. M2M communication can be agnostic to the access technologies and will uses a broad range of fixed and wireless technologies (cellular, Wi-fi, wireline, DsL, satellite or even serial with gateways). several key requirements emerge as the industry adopts the M2M applications toward the Internet of things. Juniper’s portfolio of mobility solutions, such as Juniper Networks® MobileNext, Junos® Pulse for security, Junos space for management and Junos sDK position the company for leadership in this market: • Mobile Broadband Gateway (MBG) and Mobile Control Gateway (MCG) address scaling aspect for M2M endpoints. • Junos Pulse for security expertise helps prevent man-in-the-middle attacks by examining the option of providing embedded lightweight Junos Pulse for M2M. • Junos sDK provides an open API and facilitates third-party development and integration tailored to M2M/MTC. This paper focuses on cellular M2M/MTC communications and describes current considerations by key standard organizations directly looking into the technical challenges and network enhancements required to address these opportunities. It is directed to the field force involved with mobile wireless service providers. Through this educational paper, network administrators are introduced to the growing market need for cellular M2M infrastructure enhancements and application services.
Introduction
Although cellular M2M communication has existed for some time now, it has been a challenging and niche market. • Existing M2M solutions are fragmented and usually are dedicated to a specific single application: • There are many different incumbent and legacy technical solutions that lack standard homogenization. • There is a need for new revenue models to address generally small volumes of traffic from M2M applications. According to several market research firms, this market is on an upward path as the M2M market is projected to grow exponentially in the coming years. Personal communication has evolved from traditional phone calls to today’s modern text messaging using short Message service (sMs) or multimedia content through Multimedia Messaging service (MMs). Cellular M2M communications for 2G/3G use similar types of mechanisms to send short data bursts of information to report residential utility meter readings, locations for telemetry applications and also for remote upgrades/activations of machines such as parking meters. Concurrently, advances in wireless technologies, wider availability of application services and the upcoming demands created by regulatory and policy initiatives for some verticals such as utilities/smart grid—the EU recently issued a mandate on smart Metering (M/441) to the European standards Development organizations (sDos) and the United states National Broadband Plan (March 2010)—prompted the industry (M2M modem vendors, operators, standards, application providers) to take a second look at this overall segment. The M2M ecosystem is developing and opening the doors for tremendous opportunities beyond the “traditional M2M market segment.” figure 1 shows the predictions by Infonetics Research for M2M connections.
Embedded mobile M2M connections are forecast to reach 428 million by 2014 450 Connections in Millions 0
2009
2014
© Infonetics Research, Embedded Mobile M2M Modem Market Outlook, Oct. 2010
Figure 1: Infonetics Research M2M connections forecast (2009–2014)
Copyright © 2011, Juniper Networks, Inc.
3
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
furthermore, Harbor Research projects M2M to reach 390 million connections by 2014. Although the projections are slightly different from each market research firm, it is undeniable that the M2M market is significantly growing. other markets verticals—besides utilities/smart grid/energy/telemetry—include transportation and logistics, security/ surveillance, healthcare, retail/vending, consumers, and miscellaneous (including environment, education and military). As depicted in figure 2, Harbor Research shows its revenue projections per vertical.
Exhibit: Value-Added Application Services by Venue
$350,000 $300,000 $250,000 Millions $200,000 $150,000 $100,000 $50,000 $0 2008 2009 2010 2011 2012 2013
Source: Harbor Research, Inc.
Security/Infrastructure Healthcare IT/Networks Transportation Retail Buildings Energy Industrial
Figure 2: Revenue per vertical
some of those verticals such as smart metering and healthcare are gaining popularity and are in early deployment stages. They already contribute at changing the economics and user experience perception. for example, gas and electric utility companies can reduce their costs by discontinuing meter readings by their prescribed employees. eHealth can offer an improved patient experience for those who have limited mobility or remote access by providing vital sign status through networked monitoring equipment associated with the patient’s identification. There are many different MTC applications with distinct characteristics. As such, every optimization feature put forward is not suitable for all MTC applications. In other words, there is not a unique set of requirements that can be applied to all MTC applications. Network operators must be able to differentiate between their MTC devices to provide MTC features on a persubscription basis. subscriber database information as well as Policy and Charging Rules function (PCRf) will play a key role in this.
4
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Table 1 presents a non-exhaustive list of machine-type communication applications (3GPP TR 22.368).
Table 1: 3GPP Machine-Type Communication Applications
SERvICE AREA MTC APPLICATIonS
security
surveillance systems Backup for landline Control of physical access fleet management order management Pay as you drive Asset tracking Navigation Traffic Information Road tolling Road traffic optimization/steering Point of sales Vending machines Gaming machines Monitoring vital signs supporting the aged or handicapped Web access telemedicine points Remote diagnostics sensors Lighting Pumps Valves Elevator control Vending machine control Vehicle diagnostics Power Gas Water Heating Grid control Industrial metering Digital photo frame Digital camera e-book
Tracking, Tracing
Payment
Health
Remote Maintenance/Control
Metering
Consumer Devices
Table 2 lists ETsI’s high-level domains with associated examples of possible industry use cases.
Table 2: High-Level Domains
DoMAInS ExAMPLE
security Transportation Healthcare smart Energy supply/Provisioning City Automation future
surveillance application, alarms, tracking (object/person). fleet management, emission control, toll payment, road safety. Related to eHealth, personal well-being and security. Measurement, provisioning/billing of utilities, metering. freight supply and distribution monitoring, vending machines. Public lighting, waste management. Many more new domains to be developed.
opportunities for new Business Models
M2M provides low Average Return Per Device (ARPD) but at the same time offers low churn (if any), making it possible for operators and executives to design lucrative business models that offer services as the industry shows converging signs that this market segment can emerge as a serious and significant opportunity.
Copyright © 2011, Juniper Networks, Inc.
5
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
The current marketplace is extremely fragmented, with many small, vertical and specific niche applications. Efforts are underway to bring some level of normalization in the direction of moving away from the current siloed landscape to a more horizontal integrated approach. occasionally, some in the industry refer to this as “inverting the pipes and going to mass market applications,” as shown in figure 3.
Existing Proprietary Vertical Applications
Business Application 1 Business Application 2 Business Application 3
Applications Share Common Infrastructure, Environments, and Network Elements
Business Application 1 Business Application 2 Business Application 3
Application Infrastructure
Existing Mobile Infrastructure
Existing Mobile Infrastructure
Existing Mobile Infrastructure
Network Infrastructure
CONVERGED NETWORK
(IP and Mobile Infrastructure)
SIM based Dedicated Services
SIM based Dedicated Services
SIM based Dedicated Services
Gateway Concentrators
M2M Device
M2M Device
M2M Device
Figure 3: Inverting the pipe
Currently, until new business models develop, mobile network operators have traditionally teamed with partners in an attempt to benefit from the M2M market segment. figure 4 (following chart) shows what several operators have accomplished with partnership models.
THE REVENUE OPPORTUNITY FOR MOBILE CONNECTED DEVICES IN SATURATED MARKETS
TELENOR
New business unit “Telenor Objects” and co-operation withTelit and Volvo for in-car SIM card
TELIT VOLVO CELEVOKE ECHELON QUALCOMM ONSTAR BY GM JASPER WIRELESS WAVECOM CINTERION SECURITAS DIRECT SECURITAS DIRECT
T-MOBILE
Echelon and T-Mobile alliance to reduce the cost of a secure smart grid network for utilities; also co-operation with Celevoke to sell wholesale data services to M2M clients
VERIZON WIRELESS
Co-operation with OnStar/GM, also Verizon Wireless and Qualcomm announce joint venture to provide advanced M2M solutions (nPhase)
AT&T
Emerging devices business unit launched in October 2008; combined platform with Jasper Wireless “Orange M2M Connect” platform; strategic partnerships with Wavecom, Alcatel, and Cinterion, Orange (France and Spain) are co-operating with Securitas Direct to use wireless GSM network for more advanced surveillance solutions New M2M platform July 2009, Vodafone Spain also co-operates with Securitas Direct
ORANGE
VODAFONE
TELEFONICA
Telefonica’s Smart M2M platform in co-operation with Telit
TELIT
source: Northstream white paper, february 2010
Figure 4: Mno and partnership model co-operation for M2M
6
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
M2M network Architecture Considerations
This section discusses M2M network architecture considerations both in terms of suitability of existing wireless networks in supporting M2M applications as well as new architectural enhancements as proposed by standards bodies, such as 3GPP, to efficiently support M2M applications.
Present-Day networks and M2M Challenges
The current mobile networks (3GPP/2) primarily are designed for human-to-human (H2H) communications—voice call (sMs/MMs) and server-to-human (downloading/streaming). However, these technologies might not be optimal for M2M application services. M2M networks are defined as communication without or with limited human end user intervention. Note that the human end user is not typically the initiator of the input but only occasionally and optionally the recipient for the output. Table 3 summarizes the differences between H2H and M2M.
Table 3: Differences Between H2H and M2M
ToPICS H2H M2M
Density
Wireless devices’ penetration rate is increasing. There are a lot of us. But maybe not that much compared to M2M potential. Most of the traffic is downloaded and requires significant amounts of bandwidth (file, Web and video streaming). We can buy a new one—we can recharge. We do have a tolerance for it even when it comes to voice. Worth comes to worth. Instinct tells us or we just know if it has been stolen.
M2M outnumbers human end users by order of magnitude. 3GPP sA1 requires solutions to cater for at least two orders of magnitude. Another possible reason for IPv6. Possible shortage of phone numbers. Traffic is mainly uploaded and most of it requires small amounts of bandwidth (video surveillance might require more). It must be capable of auto-generating power or be self-sustaining for long periods. some applications are mainly for real-time control; urgent/emergency action would have little tolerance. Not so much here. Robust security, even confidentiality ought to be available. New considerations are being made regarding Machine Communication Identity Module (MCIM) in Universal Integrated Circuit Card (UICC) or Trusted Environment (TRE). Low ARPD. High level of endpoints connecting from time to time (can be predefined) to transmit small amounts of data. However, control network overload aspects must be considered. To be created/adapted for new opportunities on top of common infrastructure. Push/pull behavior. Might require much longer dormant period to minimize signaling on control plane.
Data Volume
Battery Delay security
Revenue Dimensioning
Good. Normal business case.
Value Chain Reachability
Well defined. satisfying.
Using Table 3 as a reference, it is apparent that M2M and H2H traffic patterns are quite different and accommodations and optimizations are needed in current networks for M2M while maintaining or at least not disrupting existing H2H services.
Copyright © 2011, Juniper Networks, Inc.
7
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
M2M Standards Status
The European Telecommunications standardization Institute (ETsI) and 3rd Generation Partnership Project (3GPP) are two main standard groups that have been investigating M2M’s challenges, issues, gaps, and architectures. To a lesser degree, WiMAX forum is also looking at M2M. Table 4 summarizes the two standards and associated specification descriptions and references.
Table 4: Standards, Specification Descriptions and References
STAnDARDS SPECIFICATIon DESCRIPTIon SPECIFICATIon REFEREnCE
ETsI
M2M functional Architecture M2M service Requirements smart Metering Use Cases eHealth Use Cases Automotive Applications Use Cases City Applications Use Cases M2M interfaces mIa, mId, dIa
ETsI Ts 102 690 ETsI Ts 102 689 ETsI TR 102 692 ETsI TR 102 732 ETsI TR 102 898 ETsI TR 102 897 ETsI Ts 102 921 3GPP TR 22.868 3GPP Ts 22.368 3GPP TR 23.888 3GPP TR 33.812 3GPP TR 33.868 3GPP TR 37.868 3GPP TR 43.868
3GPP
sA1- M2M study Report sA1- MTC service Requirements sA2 - system Improvements for MTC sA3 - M2M security Aspect for Remote Provisioning and subscription Change sA3 - security Aspect of MTC 3GPP study on RAN Improvements for MTC 3GPP study on GERAN Improvements for MTC
ETSI and M2M
In 2009, ETsI created a Technical Committee (TC) whose goal is to develop M2M standards. Release 1 planning stages are as follows: stage 1 (requirements)—Q3 2010 • Based on several M2M use cases stage 2 (architecture)—Q3 2011 • Key capability identified • Message flows documented • Key interfaces identified for Release 1 stage 3 (detailed specifications) stage 3 (protocol)—Q4 2011 • Working on three main interfaces—mId, dIa and mIa.
8
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 5 depicts the high-level architecture concept that ETsI proposes for M2M application support.
M2M Application
M2M Area Network
Service Capabilities
M2M Gateway
Client Application
M2M CORE
APPLICATION DOMAIN
NETWORK DOMAIN
M2M DEVICE DOMAIN
Figure 5: ETSI M2M network
Using figure 5 as a reference, Table 5 lists and defines the major components that comprise the ETsI M2M network architecture.
Table 5: ETSI M2M network Architecture
MAjoR CoMPonEnTS DEFInITIon
M2M Device M2M Area Network (device domain) M2M Gateway M2M Communication Networks (network domain) M2M Applications
Is capable of replying to requests for data contained within those devices or capable of transmitting data contained within those devices autonomously. Provides connectivity between M2M devices and M2M gateways— wireless personal area networks (WPANs), Wi-fi, Zigbee/802.15.4, Bluetooth and RfID. Uses M2M capabilities to ensure M2M devices are interworking and interconnected to the communication network. Involves communications between the M2M gateways and M2M application (3G, LTE, WiMAX, WLAN, and wireline). Contains the middleware layer where data travels through various application services and is used by the specific business-processing engines.
Copyright © 2011, Juniper Networks, Inc.
9
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 6 shows a reference to the ETsI use case technical reports, covering many types of industries from smart metering and eHealth to city automation.
source: ETsI MWC Barcelona feb. 2011.
Work Methodology
TR 102 692 Smart Metering
PUBLISHED
TR 102 732 eHealth
TR 102 857 Connected Consumer
TR 102 898 Automotive
TR 102 897 City Automation
TR 102 920 Delivery of M/441 Work
STAGE 1
TS 102 689 M2M Service Requirements
PUBLISHED
TR 102 725 M2M Definitions
TR 102 935 Smart Grid Impacts on M2M
STAGE 2
TS 102 690 M2M Functional Architecture
TR 101 531 Re-use of 3GPP Nodes by M2MSC Layer
TR 102 167 Threat Analysis and Counter Measures to M2M Service Layer
STAGE 3
TS 102 921 M2M Communications; mia, dia, and mid interfaces
Source: ETSI MWC Barcelona, February 2011
Figure 6: ETSI use case technical reports reference
The M2M device domain includes: • M2M device • M2M area network • M2M gateway. The network and application domain includes: • Access network • Transport network • M2M core • M2M applications • Network management functions • M2M management functions.
10
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 7 depicts the high-level system architecture put forward by ETsI Ts 102 690.
PC/Dedicated Appliance
M2M Applications
M2M CORE
M2M Management Functions
Service Capabilities
M2M Capabilities
(include enhancements to existing CN capabilities)
CORE NETWORK (CN) M2M-specific Management Functions
M2M Capabilities Network Management Functions M2M Capabilities TRANSPORT NETWORK ACCESS NETWORK Network and Applications Domain
Based on existing standards 3GPP, TISPAN, IETF, etc.
M2M Device Domain M2M Applications M2M Capabilities M2M GATEWAY M2M Applications M2M Capabilities M2M DEVICE
Based on existing standards and technologies, e.g.: DLMS, CEN, CENELEC, PLT, Zigbee, M-BUS, KNX, etc.
M2M Devices
M2M AREA NETWORK
Figure 7: ETSI TS 102 690 system architecture
ETsI (Ts 102 690) M2M service capabilities functional architecture framework is progressing to stage 3 to define identified reference points—mId, dIa and mIa, as illustrated in figure 8.
M2M Application M2M Application
Stage 3 for M2M R1
mla dla
SC1 M2M Service Capabilities SC8 SC2
SC7
Routing Function
SC3
SC6 SC5 mld
SC4
M2M SERVICE CAPABILITIES
Core network function, based on existing standards (3GPP, ETSI, TISPAN, IETF...)
Communication Modules
M2M DEVICE/ GATEWAY DOMAIN
CORE NETWORK A
CORE NETWORK B
Figure 8: Stage 3 for ETSI M2M Release 1
Copyright © 2011, Juniper Networks, Inc.
11
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
service capabilities can access network core functions through existing interfaces (defined by I.E 3GPP and ETsI) and provide functions that can be shared among applications. In the following list, X represents N for networks, G for Gateway and D for Device, as previously described in Table 3. The following M2M service capabilities (sC) include: • Application Enablement (xAE) • Generic Communication (xGC) • Reachability, Addressing and Repository (xRAR) • Communication selection (xCs) • Remote Entity Management (xREM) • sECurity (xsEC) • History and Data Retention (xHDR) • Transaction Management (xTM) • Compensation Broker (xCB) • Telco operator Exposure (xToE) • Interworking Proxy (xIP) mIa—Allows an application to access M2M sCs in the network and applications domain. dIa—Allows an application within an M2M device to access the different sCs in the same M2M device or in an M2M gateway. Allows an application within an M2M gateway to access the different service capabilities in the same M2M gateway. mId—Enables an M2M device or M2M gateway to access M2M sCs in the network and application domain.
3GPP and M2M
In 2007, a 3GPP study item (TR-22.868) on M2M communications titled Study on Facilitating Machine to Machine Communication in 3GPP Systems was completed. This particular 3GPP study has shown potential for M2M services beyond the current “premium M2M market segment.” In 2010, 3GPP started the process of developing the study’s results into a specification phase—Ts 22.368 Service Requirements for Machine-Type Communication (MTC) Stage 1 June 2010; TR 23.888 System Improvements for MTC July 2010—to address required network system improvements to support MTC. Ts 22.368 defines general requirements and specific MTC features, and it generated two additional study items that focus on alternatives for using E.164 numbering for MTC and enhancements for MTC (TR 22.888). TR 23.888 identifies key issues and proposes corresponding possible solutions. 3GPP Release 10 addresses change requests related to congestion and overload control while other remaining items are deferred to later releases. TR 33.812 is a feasibility study on the security aspects of remote provisioning and change of subscription for M2M equipment. TR 33.868 focuses on the security aspect of MTC and is expected to be delayed until 3GPP Release 11 as a new work item. 3GPP Radio Access Network (RAN) and GsM Edge Radio Access Network (GERAN) groups are also active and are working on the improvements for MTC with TR 37.868 and TR 43.868.
12
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
figure 9 depicts the high-level 3GPP architecture (3GPP Ts 23.888).
MTC Device MTCu
MTCsms 3GPP Bearer Services/ SMS/IMS MTCi 3GPP PLMN-MTC SERVER IWK Function
MTC Server
MTC Server
Figure 9: overall 3GPP high-level M2M architecture approach
The MTC server can be located either inside or outside of the operator domain. Reference points MTCi and MTCsms can be part of the interworking function itself that could facilitate access to the MTC server using non-3GPP interfaces. Roaming scenarios are considered and the MTC devices would connect using MTCu from visited public land mobile Network (PLMN) to access home services. Table 6 identifies the major components of the 3GPP M2M architecture.
Table 6: Major Components of 3GPP M2M Architecture
CoMPonEnTS/TERMInoLoGy DEFInITIon
MTC MTCu MTCi MTCsms MTC User MTC Device MTC server
Machine-Type Communication. Reference point providing MTC devices access to 3GPP network for transporting user traffic. Reference point for MTC server to connect 3GPP network using 3GPP bearer service. Reference point for MTC server to connect 3GPP network using 3GPP sMs. Legal entity that uses MTC terminals (usually the contractual partner for the operator). User equipment for MTC communicating with MTC server or device. An entity that can communicate with MTC devices and connects to the PLMN.
3GPP M2M Communication Scenarios
Three scenarios have been defined in 3GPP Ts 22.368 pertaining to the communication between MTC devices and the MTC server: • scenario 1 (Located in the operator domain) • scenario 2 (Located outside the operator domain) • scenario 3 (Communication directly with each other without an intermediate MTC server).
Scenario 1
scenario 1 represents MTC devices communicating with the MTC server located in the operator domain. The network operator domain offers an API on its MTC server, and the MTC user accesses the MTC server through this API.
MTC User MTC Server MTC Device API
OPERATOR DOMAIN
Figure 10: 3GPP M2M communication, scenario 1
Copyright © 2011, Juniper Networks, Inc.
13
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
Scenario 2
scenario 2 represents MTC devices communicating with the MTC server located outside the operator domain. In this case, the network operator offers network connectivity to the MTC server outside of its domain.
MTC Server/ MTC User MTC Device
OPERATOR DOMAIN
Figure 11: 3GPP M2M communication, scenario 2
Scenario 3
scenario 3 represents MTC devices communicating directly with each other without an intermediate MTC server.
MTC Device
OPERATOR DOMAIN A
OPERATOR DOMAIN B
MTC Device
Figure 12: 3GPP M2M communication, scenario 3
3GPP Release 10 Feature Requirements for M2M
overall, approximately 14 specific feature service requirements have been identified in 22.368 Release 10. Low Mobility • MTC devices are static, nomadic and move only within a predefined region. • There is a reduction in mobility signaling and reporting frequency. Time Controlled • Data can be sent or received only during certain predefined periods. • signaling outside of these predefined time windows can be minimized. Time Tolerant • Data application can support delay. Packet switched only • Network access allows for services to be obtained, and triggering should be possible with or without a Mobile station International subscriber Directory Number (MsIsDN). small Data Transmissions • Most MTC devices send small amounts of data uplink. Mobile originated only • The network should provide mechanisms to reduce control signaling originated by MTC devices Infrequent Mobile Terminated
14
Copyright © 2011, Juniper Networks, Inc.
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
MTC Monitoring • It is not intended to prevent theft. • Detection functionality of events such as unexpected behaviors and loss of connectivity is provided. • The end user is notified and predetermined action is taken. Priority Alarm Message (PAM) • There is a need for immediate attention. • It is used in case of theft, urgency or emergency. secure Connection • MTC devices connect through a roaming operator. Location specific Trigger • operator stores location information and can wake up and trigger the MTC device in a particular area. Network Provided Destination for Uplink Data • The ability to transmit to a specific address is available. Infrequent Transmission • Network resources are allocated only when needed. Group Based MTC features • It should be possible to broadcast to a specific group of devices. • Combined policy, charging, addressing and Qos for a specific group should be possible. 3GPP Release 10 will focus on the following general functionalities required to support the above-listed features: • overload control • Addressing • Identifiers • Triggering • Remote management • subscription control • Charging • security.
Conclusion
The current mobile network is optimized for H2H traffic patterns and not necessarily for M2M. Enhancements and optimizations are needed for MTC to address issues such as scalability, IP addresses shortages and telephone numbers to protect against control network overload, to differentiate between MTC applications that have different characteristics, to help secure connectivity between M2M devices and the network as well as with the application servers, and to lower costs to align with lower ARPD for MTC. We like to talk about killer applications for wireless cellular. Many people think the next killer application is video streaming, which is estimated to represent up to 60 percent of data volume. Today, M2M might not be perceived as a killer application segment. However, even though M2M is expected to have applications predominately for low data usage (some might generate higher traffic in the case of video surveillance), the order of magnitude for M2M endpoints that will connect to the network is significant. Current forecasts indicate a large market for MTC. We have seen a first phase of fragmented, niche M2M vertical applications. Currently, a second phase is occurring, driven by regulatory and policies initiatives. A third phase is expected to follow, with the Internet of things made possible through the advent of technologies such as 6lowpan from IETf. M2M communications bring the opportunity to use mobile networks in a new way. We probably cannot foresee today what
Copyright © 2011, Juniper Networks, Inc.
15
WHITE PAPER - Machine-to-Machine (M2M)—The Rise of the Machines
impact the rise that machines might have on mobile data usage. However, it definitely opens up the possibility to create new businesses. Juniper Networks can facilitate mobile network operators to start addressing M2M segment opportunities with its MobileNext product portfolio (MobileNext Broadband Gateway, MobileNext Control Gateway)—offering unprecedented subscriber density, call setup capability and PCRf partnerships (MobileNext Policy Manager) to help translate these new business rules into profitable services. Juniper Networks is in a unique position to leverage its security expertise with Junos Pulse and Junos sDK by providing open APIs for partnership development and integration.
About juniper networks
Juniper Networks is in the business of network innovation. from devices to data centers, from consumers to cloud providers, Juniper Networks delivers the software, silicon and systems that transform the experience and economics of networking. The company serves customers and partners worldwide. Additional information can be found at www.juniper.net.
Corporate and Sales Headquarters Juniper Networks, Inc. 1194 North Mathilda Avenue sunnyvale, CA 94089 UsA Phone: 888.JUNIPER (888.586.4737) or 408.745.2000 fax: 408.745.2100 www.juniper.net
APAC Headquarters Juniper Networks (Hong Kong) 26/f, Cityplaza one 1111 King’s Road Taikoo shing, Hong Kong Phone: 852.2332.3636 fax: 852.2574.7803
EMEA Headquarters Juniper Networks Ireland Airside Business Park swords, County Dublin, Ireland Phone: 35.31.8903.600 EMEA sales: 00800.4586.4737 fax: 35.31.8903.601
To purchase Juniper Networks solutions, please contact your Juniper Networks representative at 1-866-298-6428 or authorized reseller.
Copyright 2011 Juniper Networks, Inc. All rights reserved. Juniper Networks, the Juniper Networks logo, Junos, Netscreen, and screenos are registered trademarks of Juniper Networks, Inc. in the United states and other countries. All other trademarks, service marks, registered marks, or registered service marks are the property of their respective owners. Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.
2000416-001-EN
May 2011
Printed on recycled paper
16
Copyright © 2011, Juniper Networks, Inc.
