machine type communications in 3gpp · 3gpp mobile etsi m2m architecture etsi m2m was formed...

Machine Type Communications in 3GPP From Release 10 to Release 12

Andreas Kunz, NEC Laboratories Europe

LaeYoung Kim, LG Electronics

Hyunsook Kim, LG Electronics

Syed S. Husain, NTT DOCOMO

7th December 2012

GLOBECOM 2012 ONIT WS

© NEC Corporation 2012

Outline

▐ Introduction to MTC in 3GPP

▐ MTC in 3GPP Release 10

Congestion and Overload Control

▐ MTC in 3GPP Release 11

MTC Architecture

Addressing and Identification

Device Triggering

▐ Outlook of MTC in 3GPP Release 12


Scope of 3GPP


Introduction to MTC in 3GPP


M2M

Application

Service

Capability

Server

M2M

Gateway

M2M

Devices

Communication

Network

3GPP Mobile

Network

ETSI M2M Architecture

▐ ETSI M2M was formed January 2009 and was one of the first

standardization organizations that developed an end-to-end

architecture for Machine-to-Machine (M2M) systems

▌ ETSI M2M documented two main specifications TS 102 690

(functional architecture) and TS 102 921 (interfaces) that are used

as baseline models in the MTC Service Requirements specification

TS 22.368 from 3GPP


MTC in 3GPP Release 10

▐ MTC focus in Release 10 was

on network improvments to

support M2M communication

in an optimized way

▐ 15 key issues were identified

▐ Due to lack of time and many

contributions it was not

possible to standardize all key

issues, even up to now

(Rel-12)

▐ Most important Rel-10 feature

is Signalling Congestion and

Overload Control


Key Issue Description

Group based

optimization

Grouping of MTC devices for ease of

control, management, charging facilities,

etc., by the operators, and help in reducing

redundant signalling.

MTC devices

communicating with one

or more MTC servers

Common service requirements for

communication between MTC devices and

MTC servers.

IP addressing MTC device using a private non-routable

IPv4 address and thus not reachable by the

MTC server.

Online small data

transmission

MTC devices frequently send or receive

only small amounts of data.

Offline small data

transmission

MTC devices infrequently send or receive


Low mobility MTC device does not move frequently.

MTC subscriptions Activation/deactivation of MTC features.

MTC device trigger MTC server polls data from MTC devices.

Time controlled Data transmission is only performed in a

predefined time period.

MTC monitoring Monitoring of MTC devices in locations

with high risk.

Decoupling MTC server

from 3GPP architecture

MTC server may be deployed outside of the

mobile network.

Signalling congestion

control

MTC related signalling congestion and

overload.

MTC identifiers Addressing issue due to the huge amount of

MTC devices and shortage of MSISDNs.

Potential overload issues

caused by roaming MTC

devices

Imbalance of signalling vs. data traffic in the

Visited Public Land Mobile Network

(VPLMN).

Low Power Consumption Battery power saving for MTC devices.



▐ Signalling Congestion and Overload Control

▐ Two main overload scenarios from a large number of UEs:

Synchronized behavior of an application in the UEs to do something at the same

time.

Roaming UEs moving at the same time to local competing networks once their

serving network fails.

▐ To address the scenarios, the UE can be configured in four different ways:


UE Configurations

be rejected, usage of waiting/back off

UE messages can be rejected, usage of waiting/back-off

timers

UE does not perform TAU with GUTI at PLMN change

between searches for preferred PLMN

Minimum time between searches

for preferred PLMN is increased

lists are kept even PLMN forbidden

lists are kept even if UE is switched

off and on

Low access priority

IMSI at PLMN Attach with

IMSI at PLMN change

Long minimum periodic PLMN Long minimum periodic PLMN

search time limit

handling of the Specific

handling of the invalid USIM

state

This mechanism can be also applied to normal UEs,

e.g. Smartphones from Rel-10 onwards

TAU – Tracking Area Update

GUTI – Globally Unique

Temporary Identifier



▐ MTC focus in Release 11 was

on

IP addressing,

MTC identifiers and

Device triggering



Group based

optimization





MTC devices


or more MTC servers



MTC servers.



MTC server.

Online small data

transmission



Offline small data

transmission









with high risk.




mobile network.


control


overload.





devices



(VPLMN).



New Network

Element and

Reference Points

MTC-IWF: supports device

trigger functionality over Tsp

and T4 reference points, can

generate the Charging Data

Records (CDRs) for the device

trigger

Tsp : delivers a device trigger

request from SCS to MTC-

IWF, and reports the

acceptance/success (or the

non-acceptance/failure) of this

request.

S6m: maps MSISDN or

external identifier to IMSI and

resolves the serving nodes

identities of the MTC UE. HSS

was enhanced to support this

functionality.

T4: transfers the device trigger from

MTC-IWF (acting as a Short

Message Entity (SME)) to SMS-SC,

provides serving node’s information

corresponding to IMSI, and reports

the success or failure of delivering

a device trigger to the MTC UE.

SMS-SC was enhanced for T4.

Tsms: can be used to send a

trigger to a MTC UE encapsulated

in a Mobile Terminating-SMS (MT-

SMS) as an over-the-top

application by any network entity

(e.g., SCS) acting as a SME.



▌MTC Architecture

GW S-GW

MSC

HSS CDF/

CGF

CDF/

CGF

IP-SM-GW

SME SMS-SC/ SMS-SC/

GMSC/

IWMSC

RAN

UE

Application MTC UE

Application SGSN

MTC-IWF

GGSN/

P-GW

HPLMN

VPLMN

(Application AS

(Application Server)

(Application AS


MME MME

Capability

SCS (Services Capability

Server)

Control plane

User plane

Um/Uu/LTE-Uu

Tsms

Tsp

Gi/SGi

Gi/SGi

Rf/Ga S6m

T4

Not in Scope of

3GPP




GW S-GW

MSC

CDF/

CGF

CDF/

CGF

IP-SM-GW

SME SMS-SC/ SMS-SC/

GMSC/

IWMSC

RAN

SGSN

GGSN/

P-GW

HPLMN

VPLMN

(Application AS


(Application AS


MME MME

Capability


Server)

Control plane

User plane

Um/Uu/LTE-Uu

Tsms

Tsp

Gi/SGi

Gi/SGi

Rf/Ga

T4

▌Addressing and Identification

HSS

S6m

MTC-IWF

UE

Application MTC UE

Application

Addressing: lack of IPv4

addresses is predicted by the

mass amounts of MTC UEs

on the networks. Therefore,

IPv6 addressing should be the

primary mechanism for

addressing.

Identification: MTC UEs are

identified by the external

network with an external

identifier, which is globally

unique and composed of a

domain identifier and a local

identifier.

Identification: the local

identifier is used for service

identification and to obtain the

IMSI. IMSI and MSISDN could

also be used as an external

identifier.



▌Device Triggering


GW S-GW

MSC

HSS CDF/

CGF

CDF/

CGF

IP-SM-GW

SME SMS-SC/ SMS-SC/

GMSC/

IWMSC

RAN

UE

Application MTC UE

Application SGSN

MTC-IWF

GGSN/

P-GW

HPLMN

VPLMN

(Application AS


(Application AS


MME MME

1

Capability


Server)

2

Control plane

User plane

Um/Uu/LTE-Uu

Tsms

Tsp

Gi/SGi

Gi/SGi

Rf/Ga S6m

T4

There are three different

deployment models:

Indirect Model:

Direct Model:

Hybrid Model:

1

2

1 2 +

1. AS sends device

trigger request to MTC-

IWF via the SCS with

the external identifier or

MSISDN of the MTC

UE. The interaction

between AS and SCS is

out of scope of 3GPP

2. MTC-IWF checks if the

SCS is authorized to

send trigger requests.

3. MTC-IWF interacts

with HSS and gets the

resolved IMSI, and the

identifiers of the MTC

UE’s serving nodes.

4. MTC-IWF sends a submit

trigger message to the SMS-

SC. SMS-SC confirms that the

submission of the SMS by the

MTC-IWF has been accepted.

5. MTC-IWF confirms the

device trigger request to

the SCS

6. SMS delivery via MSC,

MME or SGSN to the UE

and Delivery Report

7. SMS-SC performs

CDR generation

8. SMS-SC sends a message

delivery report to the MTC-IWF

9. MTC-IWF sends a device

trigger report to the SCS

indicating whether the trigger

delivery succeeded or failed.

10. MTC UE takes the

intended actions, e.g., the

initiation of the communication

with the SCS or AS



▐ MTC focus in Release 12 is

on

Small data transmission,

Triggering enhancements,

Monitoring,

UE power consumptions

optimizations,

Group based features



Group based

optimization





MTC devices


or more MTC servers



MTC servers.



MTC server.

Online small data

transmission



Offline small data

transmission









with high risk.




mobile network.


control


overload.





devices



(VPLMN).



Outlook of MTC in 3GPP Release 12

▌Currently work on MTC in 3GPP Release 12 is ongoing and subject for

prioritization within a 3GPP workshop held at the same time to this

conference

▌The following building blocks are under discussion:

Small data transmission: intended for use with MTC UEs that send or

receive small amounts of data. Also, frequent small data transmission

will be considered.

Triggering enhancements: intended for device triggering by using

reference points between MTC-IWF and serving nodes (i.e., SGSN,

MME, and MSC), as well as triggering efficiency optimizations.

Monitoring: intended for monitoring MTC UE related events such as

loss of connectivity, change of the location of MTC UE, etc.

UE power consumptions optimizations: intended for optimizations to

prevent battery drain of MTC UEs.

Group based features: optimizations to a group of MTC UEs that share

one or more MTC features.



NEC Group Vision 2017

To be a leading global company

leveraging the power of innovation

to realize an information society

friendly to humans and the earth

machine type communications in 3gpp · 3gpp mobile etsi m2m architecture etsi m2m was formed...

Documents