m2m juniper

8/3/2019 M2M Juniper

1/16

WHITE PAPER

Copyright 2011, Juniper Networks, Inc.

MACHINE-T-MACHINE (M2M)

THE RIE f THE MACHINE


2/16

2 Copyright 2011, Juniper Networks, Inc.

WHITE PAPER - Machine-to-Machine (M2M)The Rise o the M achines

TableofContents

Executive ummary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

pportunities or New Business Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

M2M Network A rchitecture Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Present-Day Networks and M2M Challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

M2M tandards tatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

ETI and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3GPP and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3GPP M2M Communication cenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

About Juniper Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

TableofFigures

figure 1: Inonetics Research M2M connections orecast (20092014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

figure 2: Revenue per vertical. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

figure 3: Inverting the pipe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

figure 4: M N and partnership model co-operation or M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

figure 5: ETI M2M network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

figure 6: ETI use case technical reports reerence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

figure 7: E TI T 102 690 system architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

figure 8: tage 3 or ETI M2M Release 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

figure 9: verall 3GPP high-level M2M architecture approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

figure 10: 3GPP M2M communication, scenario 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

figure 11: 3 GPP M2M communication, scenario 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

figure 12: 3GPP M2M communication, scenario 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

ListofTables

Table 1: 3GPP Machine-Type Communication Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Table 2: High-Level Domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Table 3: Dierences Between H2H and M2M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Table 4: tandards, peciication Descriptions and Reerences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Table 5: E TI M2M Network Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Table 6: Major Components o 3GPP M2M Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13


3/16

Copyright 2011, Juniper Networks, Inc. 3

WHITE PAPER - Machine-to-Machine (M2M)The Rise o the M achine

ExecutiveSummary

This paper presents a high- level view o a rekindled market or Machine-to-Machine (M2M) communications. M2M

communication can be agnostic to the access technologies and will uses a broad range o ixed and wireless technologies

(cellular, Wi-fi, wireline, DL, satellite or even serial with gateways). everal key requirements emerge as the industry adopts

the M2M applications toward the Internet o things. Junipers portolio o mobility solutions, such as Juniper Networks

MobileNext, Junos Pulse or security, Junos pace or management and Junos DK position the company or leadership in

this market:

Mobile Broadband Gateway (MBG) and Mobile Control Gateway (MCG) address scaling aspect or M2M endpoints.

Junos Pulse or security expertise helps prevent man-in-the-middle attacks by examining the option o providing

embedded lightweight Junos Pulse or M2M.

Junos DK provides an open API and acilitates third-party development and integration tailored to M2M/MTC.

This paper ocuses 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 ield orce involved with mobile wireless service providers. Through this educational paper,

network administrators are introduced to the growing market need or cellular M2M inrastructure enhancements and

application services.

Introduction

Although cellular M2M communication has existed or some time now, it has been a challenging and niche market.

Existing M2M solutions are ragmented and usually are dedicated to a speciic single application:

There are many dierent incumbent and legacy technical solutions that lack standard homogenization.

There is a need or new revenue models to address generally small volumes o traic rom M2M applications.

According to several market research irms, this market is on an upward path as the M2M market is projected to grow

exponentially in the coming years.

Personal communication has evolved rom traditional phone calls to todays modern text messaging using hort Message

ervice (M) or multimedia content through Multimedia Messaging ervice (MM). Cellular M2M communications or

2G/3G use similar types o mechanisms to send short data bursts o inormation to report residential utility meter readings,

locations or telemetry applications and also or remote upgrades/activations o machines such as parking meters.

Concurrently, advances in wireless technologies, wider availability o application services and the upcoming demands

created by regulatory and policy initiatives or some verticals such as utilities/smart gridthe EU recently issued a mandate

on mart Metering (M/441) to the European tandards Development rganizations (Ds) and the United tates 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 or tremendous

opportunities beyond the traditional M2M market segment.

figure 1 shows the predictions by Inonetics Research or M2M connections.

Figure1:InfoneticsResearchM2Mconnectionsforecast(20092014)

Embedded mobile M2M connections are forecast to reach 428 million by 2014

Infonetics Research, Embedded Mobile M 2M Modem Market Outlook, Oct. 2010

450

ConnectionsinMillions

2009 20140


4/16



furthermore, Harbor Research projects M2M to reach 390 million connections by 2014. Although the projections are slightly

dierent rom each market research irm, it is undeniable that the M2M market is signiicantly growing.

ther markets verticalsbesides utilities/smart grid/energy/telemetryinclude 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.

Figure2:Revenuepervertical

ome o 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 oer an

improved patient experience or those who have limited mobility or remote access by providing vital sign status through

networked monitoring equipment associated with the patients identiication.

There are many dierent MTC applications with distinct characteristics. As such, every optimization eature put orward is

not suitable or all MTC applications. In other words, there is not a unique set o requirements that can be applied to all MTC

applications. Network operators must be able to dierentiate between their MTC devices to provide MTC eatures on a per-

subscription basis. ubscriber database inormation as well as Policy and Charging Rules function (PCRf) will play a key role

in this.

Exhibit: Value-Added Application Services by Venue

2008

$350,000

Millions

$300,000

$250,000

$200,000

$150,000

$100,000

$50,000

$02009 2010 2011 2012 2013

Security/Infrastructure

Healthcare

IT/Networks

Transportation

Retail

Buildings

Energy

Industrial

Source: Harbor Research, Inc.


5/16



Table 1 presents a non-exhaustive list o machine-type communication applications (3GPP TR 22.368).

Table1:3GPPMachine-TypeCommunicationApplications

SERICEAREA MTCAPPLICATIS

ecurity urveillance systems

Backup or landline

Control o physical access

Tracking, Tracing fleet managementrder management

Pay as you drive

Asset tracking

Navigation

Trac Inormation

Road tolling

Road trac optimization/steering

Payment Point o sales

Vending machines

Gaming machines

Health Monitoring vital signs

upporting the aged or handicapped

Web access telemedicine points

Remote diagnostics

Remote Maintenance/Control ensors

Lighting

Pumps

Valves

Elevator control

Vending machine control

Vehicle diagnostics

Metering Power

Gas

Water

Heating

Grid control

Industrial metering

Consumer Devices Digital photo rame

Digital camera

e-book

Table 2 lists ETIs high-level domains with associated examples o possible industry use cases.

Table2:High-LevelDomains

DMAIS EAMPLE

ecurity urveillance application, alarms, tracking (object/person).

Transportation fleet management, emission control, toll payment, road saety.

Healthcare Related to eHealth, personal well-being and security.

mart Energy Measurement, provisioning/billing o utilities, metering.

upply/Provisioning freight supply and distribution monitoring, vending machines.City Automation Public lighting, waste management.

future Many more new domains to be developed.

pportunitiesforewBusinessModels

M2M provides low Average Return Per Device (ARPD) but at the same time oers low churn (i any), making it possible or

operators and executives to design lucrative business models that oer services as the industry shows converging signs that

this market segment can emerge as a serious and signiicant opportunity.


6/16



The current marketplace is extremely ragmented, with many small, vertical and speciic niche applications. Eorts are

underway to bring some level o normalization in the direction o moving away rom the current siloed landscape to a more

horizontal integrated approach. ccasionally, some in the industry reer to this as inverting the pipes and going to mass

market applications, as shown in figure 3.

Figure3:Invertingthepipe

Currently, until new business models develop, mobile network operators have traditionally teamed with partners in

an attempt to beneit rom the M2M market segment. figure 4 (ollowing chart) shows what several operators have

accomplished with partnership models.

Figure4:Mandpartnershipmodelco-operationforM2M

Existing Proprietary

Vertical Applications

ExistingMobile

Infrastructure

SIM basedDedicatedServices

ExistingMobile

Infrastructure


ExistingMobile

Infrastructure


BusinessApplication 1



Applications Share Common Infrastructure,

Environments, and Network Elements




Application Infrastructure

Network Infrastructure

GatewayConcentrators

M2MDevice

M2MDevice

M2MDevice

CONVERGED NETWORK(IP and Mobile Infrastructure)

THE REVENUE OPPORTUNITY FOR MOBILE

CONNECTED DEVICES IN SATURATED MARKETS

TELENORTELIT

VOLVO

New business unit Telenor Objects and co-operationwithTelit and Volvo for in-car SIM card

T-MOBILECELEVOKE

ECHELON

Echelon and T-Mobile alliance to reduce the cost of a securesmart grid network for utilities; also co-operation with Celevoketo sell wholesale data services to M2M clients

VERIZON WIRELESSQUALCOMM

ONSTAR BY GM

Co-operation with OnStar/GM, also Verizon Wireless and Qualcommannounce joint venture to provide advanced M2M solutions (nPhase)

AT&T JASPER WIRELESSEmerging devices business unit launched in October 2008;combined platform with Jasper Wireless

ORANGE

WAVECOM

CINTERION

SECURITAS DIRECT

Orange M2M Connect platform; strategic partnerships withWavecom, Alcatel, and Cinterion, Orange (France and Spain) areco-operating with Securitas Direct to use wireless GSM network

for more advanced surveillance solutions

VODAFONE SECURITAS DIRECTNew M2M platform July 2009, Vodafone Spain also co-operateswith Securitas Direct

TELEFONICA TELITTelefonicas Smart M2M platform in co-operation with Telit

ource: Northstream white paper, february 2010
http://www.google.com/url?sa=t&source=web&cd=1&ved=0CDIQFjAA&url=http%3A%2F%2Fm2m.com%2Fservlet%2FJiveServlet%2FpreviewBody%2F1061-102-1-1042%2FThe-revenue-opportunity-for-mobile-connected-devices-in-saturated-markets.pdf&rct=j&q=Northstream%20M2M%20white%20paper&ei=Np_aTbWrK4f6sAOD3PSFDA&usg=AFQjCNHuv5FWbI_xXiykxZ9rrjvmyOKRVAhttp://www.google.com/url?sa=t&source=web&cd=1&ved=0CDIQFjAA&url=http%3A%2F%2Fm2m.com%2Fservlet%2FJiveServlet%2FpreviewBody%2F1061-102-1-1042%2FThe-revenue-opportunity-for-mobile-connected-devices-in-saturated-markets.pdf&rct=j&q=Northstream%20M2M%20white%20paper&ei=Np_aTbWrK4f6sAOD3PSFDA&usg=AFQjCNHuv5FWbI_xXiykxZ9rrjvmyOKRVA


7/16



M2MetworkArchitectureConsiderations

This section discusses M2M network architecture considerations both in terms o suitability o existing wireless networks in

supporting M2M applications as well as new architectural enhancements as proposed by standards bodies, such as 3GPP, to

eiciently support M2M applications.

Present-DayetworksandM2MChallenges

The current mobile networks (3GPP/2) primarily are designed or human-to-human (H2H) communicationsvoice call

(M/MM) and server-to-human (downloading/streaming). However, these technologies might not be optimal or M2M

application services.

M2M networks are deined as communication without or with limited human end user intervention. Note that the human end

user is not typically the initiator o the input but only occasionally and optionally the recipient or the output.

Table 3 summarizes the dierences between H2H and M2M.

Table3:DierencesBetweenH2HandM2M

TPICS H2H M2M

Density Wireless devices penetration rate is increasing. There

are a lot o us. But maybe not that much compared to

M2M potential.

M2M outnumbers human end users by order o

magnitude. 3GPP A1 requires solutions to cater or

at least two orders o magnitude. Another possible

reason or IPv6. Possible shortage o phone numbers.

Data Volume Most o the trac is downloaded and requires

signicant amounts o bandwidth (le, Web and

video streaming).

Trac is mainly uploaded and most o it requires

small amounts o bandwidth (video surveillance

might require more).

Battery We can buy a new onewe can recharge. It must be capable o auto-generating power or be

sel-sustaining or long periods.

Delay We do have a tolerance or it even when it comes to

voice.

ome applications are mainly or real-time control;

urgent/emergency action would have little tolerance.

ecur ity Worth comes to worth. Instinct tel ls us or we just

know i it has been stolen.

Not so much here. Robust security, even

condentiality 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).

Revenue Good. Low ARPD.

Dimensioning Normal business case. High level o endpoints connecting rom time to time

(can be predened) to transmit small amounts o

data. However, control network overload aspects

must be considered.

Value Chain Well dened. To be created/adapted or new opportunities on top

o common inrastructure.

Reachability atisying. Push/pull behavior. Might require much longer

dormant period to minimize signaling on control

plane.

Using Table 3 as a reerence, it is apparent that M2M and H2H traic patterns are quite dierent and accommodations and

optimizations are needed in current networks or M2M while maintaining or at least not disrupting existing H2H services.


8/16



M2MStandardsStatus

The European Telecommunications tandardization Institute (ETI) and 3rd Generation Partnership Project (3GPP) are two

main standard groups that have been investigating M2Ms challenges, issues, gaps, and architectures. To a lesser degree, WiMAX

orum is also looking at M2M. Table 4 summarizes the two standards and associated speciication descriptions and reerences.

Table4:Standards,SpecicationDescriptionsandReferences

STADARDS SPECIFICATIDESCRIPTI SPECIFICATIREFERECE

ETI M2M functional Architecture

M2M ervice Requirements

mart Metering Use Cases

eHealth Use Cases

Automotive Applications Use Cases

City Applications Use Cases

M2M interaces mIa, mId, dIa

ETI T 102 690

ETI T 102 689

ETI TR 102 692

ETI TR 102 732

ETI TR 102 898

ETI TR 102 897

ETI T 102 921

3GPP A1- M2M tudy Report

A1- MTC ervice Requirements

A2 - ystem Improvements or MTC

A3 - M2M ecurity Aspect or Remote Provisioning and ubscription Change

A3 - ecurity Aspect o MTC

3GPP tudy on RAN Improvements or MTC

3GPP tudy on GERAN Improvements or MTC

3GPP TR 22.868

3GPP T 22.368

3GPP TR 23.888

3GPP TR 33.812

3GPP TR 33.868

3GPP TR 37.868

3GPP TR 43.868

ETSIandM2M

In 2009, ETI created a Technical Committee (TC) whose goal is to develop M2M standards. Release 1 planning stages are

as ollows:

tage 1 (requirements)Q3 2010

Based on several M2M use cases

tage 2 (architecture)Q3 2011

Key capability identiied

Message lows documented

Key interaces identiied or Release 1 tage 3 (detailed speciications)

tage 3 (protocol)Q4 2011

Working on three main interacesmId, dIa and mIa.


9/16



figure 5 depicts the high-level architecture concept that ETI proposes or M2M application support.

Figure5:ETSIM2Mnetwork

Using figure 5 as a reerence, Table 5 lists and deines the major components that comprise the ETI M2M network

architecture.

Table5:ETSIM2MetworkArchitecture

MAjRCMPETS DEFIITI

M2M Device Is capable o replying to requests or data contained within those devices or

capable o transmitting data contained within those devices autonomously.

M2M Area Network (device domain) Provides connectivity between M2M devices and M2M gateways wireless

personal area networks (WPANs), Wi-fi, Zigbee/802.15.4, Bluetooth and RfID.

M2M Gateway Uses M2M capabilities to ensure M2M devices are interworking and inter-

connected to the communication network.

M2M Communication Networks (network domain) Involves communications between the M2M gateways and M2M application(3G, LTE, WiMAX, WLAN, and wireline).

M2M Applications Contains the middleware layer where data travels through various application

services and is used by the specic business-processing engines.

APPLICATION

DOMAIN

NETWORK

DOMAIN

M2M CORE

M2M DEVICE

DOMAIN

M2MArea

Network

ClientApplication

M2MApplication

ServiceCapabilities M2MGateway


10/16



figure 6 shows a reerence to the ETI use case technical reports, covering many types o industries rom smart metering and

eHealth to city automation.

ource: ETI MWC Barcelona feb. 2011.

Figure6:ETSIusecasetechnicalreportsreference

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 unctions

M2M management unctions.

Work Methodology

STAGE 1

STAGE 2

STAGE 3

TR 102 692

SmartMetering

TR 102 857

ConnectedConsumer

TR 102 732

eHealth

TR 102 898

Automotive

TR 102 897

CityAutomation

TR 102 920

Delivery ofM/441 Work

TS 102 689

M2M ServiceRequirements

TR 102 725

M2M Definitions

TS 102 921

M2M Communications;mia, dia, and

mid interfaces

TR 102 935

Smart GridImpacts on M2M

TS 102 690

M2MFunctional

ArchitectureTR 101 531

Re-use of3GPP Nodes

by M2MSC Layer

TR 102 167

Threat Analysis andCounter Measures

to M2M Service Layer

PUBLISHED

PUBLISHED

Source: ETSI MWC Barcelona, February 2011


11/16



figure 7 depicts the high-level system architecture put orward by ETI T 102 690.

Figure7:ETSITS102690systemarchitecture

ETI (T 102 690) M2M service capabilities unctional architecture ramework is progressing to tage 3 to deine identiied

reerence pointsmId, dIa and mIa, as illustrated in figure 8.

Figure8:Stage3forETSIM2MRelease1

PC/DedicatedAppliance

TRANSPORT NETWORK

M2M CORE

M2M AREANETWORK

Based on existing standards3GPP, TISPAN, IETF, etc.

Network andApplications Domain

Based on existing standardsand technologies, e.g.:

DLMS, CEN, CENELEC, PLT,Zigbee, M-BUS, KNX, etc.

M2M Device DomainM2M

Applications

M2MCapabilities

M2M GATEWAY

M2MApplications

M2MCapabilities

M2M DEVICE

M2M Applications

ACCESS NETWORKM2M

Capabilities

M2MCapabilities

Service Capabilities

CORE NETWORK (CN)(include enhancements

to existing CN capabilities)

M2MCapabilities

M2MDevices

M2MManagement

Functions

M2M-specificManagement

Functions

NetworkManagement

Functions

Core network function,based on existing standards(3GPP, ETSI, TISPAN, IETF...)Communication Modules

mla

Stage 3for M2M R1

M2M SERVICE CAPABILITIES

M2M DEVICE/GATEWAY DOMAIN

CORENETWORK A

CORENETWORK B

M2MApplication

M2MService

Capabilities

SC8

SC7

SC6

SC1

SC5

RoutingFunction

SC2

SC3

SC4

M2MApplication

dla

mld


12/16



ervice capabilities can access network core unctions through existing interaces (deined by I.E 3GPP and ETI) and

provide unctions that can be shared among applications. In the ollowing list, X represents N or networks, G or Gateway

and D or Device, as previously described in Table 3.

The ollowing M2M service capabilities (C) include:

Application Enablement (xAE)

Generic Communication (xGC)

Reachability, Addressing and Repository (xRAR)

Communication election (xC)

Remote Entity Management (xREM)

ECurity (xEC)

History and Data Retention (xHDR)

Transaction Management (xTM)

Compensation Broker (xCB)

Telco perator Exposure (xTE)

Interworking Proxy (xIP)

mIaAllows an application to access M2M Cs in the network and applications domain.

dIaAllows an application within an M2M device to access the dierent Cs in the same M2M device or in an M2M gateway.

Allows an application within an M2M gateway to access the dierent service capabilities in the same M2M gateway.

mIdEnables an M2M device or M2M gateway to access M2M Cs in the network and application domain.

3GPPandM2M

In 2007, a 3GPP study item (TR-22.868) on M2M communications titledStudy on Facilitating Machine to Machine

Communication in 3GPP Systems was completed. This particular 3GPP study has shown potential or M2M services beyond

the current premium M2M market segment. In 2010, 3GPP started the process o developing the studys results into a

speciication phaseT 22.368Service Requirements for Machine-Type Communication (MTC) Stage 1 June 2010; TR 23.888

System Improvements for MTC July 2010to address required network system improvements to support MTC.

T 22.368 deines general requirements and speciic MTC eatures, and it generated two additional study items that ocus onalternatives or using E.164 numbering or MTC and enhancements or MTC (TR 22.888).

TR 23.888 identiies key issues and proposes corresponding possible solutions. 3GPP Release 10 addresses change requests

related to congestion and overload control while other remaining items are deerred to later releases.

TR 33.812 is a easibility study on the security aspects o remote provisioning and change o subscription or M2M equipment.

TR 33.868 ocuses on the security aspect o MTC and is expected to be delayed until 3GPP Release 11 as a new work item.

3GPP Radio Access Network (RAN) and GM Edge Radio Access Network (GERAN) groups are also active and are working

on the improvements or MTC with TR 37.868 and TR 43.868.


13/16



figure 9 depicts the high-level 3GPP architecture (3GPP T 23.888).

Figure9:verall3GPPhigh-levelM2Marchitectureapproach

The MTC server can be located either inside or outside o the operator domain. Reerence points MTCi and MTCsms can be

part o the interworking unction itsel that could acilitate access to the MTC server using non-3GPP interaces. Roaming

scenarios are considered and the MTC devices would connect using MTCu rom visited public land mobile Network (PLMN)

to access home services.

Table 6 identiies the major components o the 3GPP M2M architecture.

Table6:MaorComponentsof3GPPM2MArchitecture

CMPETS/TERMILG DEFIITI

MTC Machine-Type Communication.

MTCu Reerence point providing MTC devices access to 3GPP network or

transporting user trac.

MTCi Reerence point or MTC server to connect 3GPP network using 3GPP bearer

service.

MTCsms Reerence point or MTC server to connect 3GPP network using 3GPP M.

MTC User Legal entity that uses MTC terminals (usually the contractual partner or the

operator).

MTC Device User equipment or MTC communicating with MTC server or device.

MTC erver An entity that can communicate with MTC devices and connects to the PLMN.

3GPPM2MCommunicationScenarios

Three scenarios have been deined in 3GPP T 22.368 pertaining to the communication between MTC devices and the

MTC server:

cenario 1 (Located in the operator domain)

cenario 2 (Located outside the operator domain)

cenario 3 (Communication directly with each other without an intermediate MTC server).

Scenario1

cenario 1 represents MTC devices communicating with the MTC server located in the operator domain. The network

operator domain oers an API on its MTC server, and the MTC user accesses the MTC server through this API.

Figure10:3GPPM2Mcommunication,scenario1

3GPP

PLMN-MTC SERVER

IWK Function

MTC Device

MTC Server

MTC Server

MTCsms

MTCu

MTCi

3GPP Bearer Services/

SMS/IMS

MTC User

MTC Device

OPERATOR DOMAIN

APIMTC Server


14/16



Scenario2

cenario 2 represents MTC devices communicating with the MTC server located outside the operator domain. In this case,

the network operator oers network connectivity to the MTC server outside o its domain.


Scenario3

cenario 3 represents MTC devices communicating directly with each other without an intermediate MTC server.


3GPPRelease10FeatureRequirementsforM2M

verall, approximately 14 speciic eature service requirements have been identiied in 22.368 Release 10.

Low Mobility

MTC devices are static, nomadic and move only within a predeined region.

There is a reduction in mobility signaling and reporting requency.

Time Controlled

Data can be sent or received only during certain predeined periods.

ignaling outside o these predeined time windows can be minimized.

Time Tolerant

Data application can support delay.

Packet witched nly

Network access allows or services to be obtained, and triggering should be possible with or without a Mobile tation

International ubscriber Directory Number (MIDN).

mall Data Transmissions

Most MTC devices send small amounts o data uplink.

Mobile riginated nly

The network should provide mechanisms to reduce control signaling originated by MTC devices

Inrequent Mobile Terminated

MTC Server/

MTC User

MTC Device OPERATOR DOMAIN

MTC Device MTC DeviceOPERATOR DOMAIN A OPERATOR DOMAIN B


15/16



MTC Monitoring

It is not intended to prevent thet.

Detection unctionality o events such as unexpected behaviors and loss o connectivity is provided.

The end user is notiied and predetermined action is taken.

Priority Alarm Message (PAM)

There is a need or immediate attention.

It is used in case o thet, urgency or emergency.

ecure Connection

MTC devices connect through a roaming operator.

Location peciic Trigger

perator stores location inormation and can wake up and trigger the MTC device in a particular area.

Network Provided Destination or Uplink Data

The ability to transmit to a speciic address is available.

Inrequent Transmission

Network resources are allocated only when needed.

Group Based MTC features

It should be possible to broadcast to a speciic group o devices.

Combined policy, charging, addressing and Qo or a speciic group should be possible.

3GPP Release 10 will ocus on the ollowing general unctionalities required to support the above-listed eatures:

verload control

Addressing

Identiiers

Triggering

Remote management

ubscription control

Charging

ecurity.

Conclusion

The current mobile network is optimized or H2H traic patterns and not necessarily or M2M. Enhancements and

optimizations are needed or MTC to address issues such as scalability, IP addresses shortages and telephone numbers to

protect against control network overload, to dierentiate between MTC applications that have dierent 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 or MTC.

We like to talk about killer applications or wireless cellular. Many people think the next killer application is video streaming,

which is estimated to represent up to 60 percent o data volume. Today, M2M might not be perceived as a k iller application

segment.

However, even though M2M is expected to have applications predominately or low data usage (some might generate higher

traic in the case o video surveillance), the order o magnitude or M2M endpoints that will connect to the network is signiicant.

Current orecasts indicate a large market or MTC. We have seen a irst phase o ragmented, niche M2M vertical applications

Currently, a second phase is occurring, driven by regulatory and policies initiatives. A third phase is expected to ollow, with

the Internet o things made possible through the advent o technologies such as 6lowpan rom IETf.

M2M communications bring the opportunity to use mobile networks in a new way. We probably cannot oresee today what


16/16



2000416-001-EN May 2011

Copyright 2011 Juniper Networks, Inc. All rights res erved. Juniper Networks, the Juniper Networks logo, Junos,

Netcreen, and creen are registered trademarks o Juniper Networks, Inc. in the United tates and other

countries. All other trademarks, service marks, registered marks, or registered ser vice marks are the property o

their respective owners. Juniper Networks assumes no responsibility or any inaccuracies in this document. Juniper

Networks reserves the right to change, modiy, transer, or otherwise revise this publication without notice.

EMEAHeadquarters

Juniper Networks Ireland

Airside Business Park

words, County Dublin, Ireland

Phone: 35.31.8903.600

EMEA ales: 00800.4586.4737

fax: 35.31.8903.601

APACHeadquarters

Juniper Networks (Hong Kong)

26/f, Cityplaza ne

1111 Kings Road

Taikoo hing, Hong Kong

Phone: 852.2332.3636

fax: 852. 2574.7803

CorporateandSalesHeadquarters

Juniper Networks, Inc.

1194 North Mathilda Avenue

unnyvale, CA 94089 UA

Phone: 888.JUNIPER (888.586.4737)

or 408.745.2000

fax: 408.745.2100

www.juniper.net

Printed on recycled paper

To purchase Juniper Networks solutions,

please contact your Juniper Networks

representative at 1-866-298-6428 or

authorized reseller.

impact the rise that machines might have on mobile data usage. However, it deinitely opens up the possibility to create

new businesses.

Juniper Networks can acilitate mobile network operators to start addressing M2M segment opportunities with its MobileNext

product portolio (MobileNext Broadband Gateway, MobileNext Control Gateway)oering unprecedented subscriber

density, call setup capability and PCRf partnerships (MobileNext Policy Manager) to help translate these new business rules

into proitable services. Juniper Networks is in a unique position to leverage its security expertise with Junos Pulse and Junos

DK by providing open APIs or partnership development and integration.

Aboutjuniperetworks

Juniper Networks is in the business o network innovation. from devices to data centers, rom consumers to cloud providers,

Juniper Networks delivers the sotware, silicon and systems that transorm the experience and economics o networking.

The company serves customers and partners worldwide. Additional inormation can be ound at www.uniper.net .

m2m juniper

Documents