DL - 4G Americas

� Remote MTC device management
Specific service requirements have been defined as MTC features:
� Low Mobility
� Time Controlled
� Time Tolerant
� Packet Switched (PS) Only
� Small Data Transmissions
� Mobile Originated Only
� Infrequent Mobile Terminated
� MTC Monitoring
� Priority Alarm Message (PAM)
� Secure Connection
� Location Specific Trigger
� Network Provided Destination for Uplink Data
� Infrequent Transmission
� Group Based MTC Features
The main MTC functionality specified by 3GPP in Rel-10 provides overload and congestion control
functionality. Considering that some networks already experienced congestion caused by M2M
applications, overload and congestion control was considered with priority during Rel-10. A set of
functions is specified for this. It includes specific Mobility Management features, connection reject and
access class barring for MTC devices and also APN-based congestion control. To a certain extent this
functionality is also available for terminals that are not specifically configured for MTC as applications
already deployed use normal terminals. The full range of MTC congestion and overload control means
becomes available when terminals specifically configured for MTC are used for M2M applications.
The congestion and overload control functions affect the overall system. Their specification implied
considerable efforts. Therefore, other MTC features are transferred to the following release and the 3GPP
architecture, core network and RAN groups will work on it in Rel-11. In addition 3GPP stage 1 continues
to identify new MTC scenarios and MTC features.
7.3.5 SINGLE RADIO VOICE CALL CONTINUITY
As part of Rel-10 study, 3GPP is investigating techniques to improve the performance of Single Radio
Voice Call Continuity (SRVCC) handovers while minimizing impacts on the network architecture for
handovers of IMS voice sessions from 4G to 2G/3G CS, and from HSPA to 2G/3G CS systems.
www.4gamericas.org February 2011 Page 72