• Save
MTC in 3GPP Rel. 12
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

MTC in 3GPP Rel. 12

on

  • 2,645 views

 

Statistics

Views

Total Views
2,645
Views on SlideShare
2,645
Embed Views
0

Actions

Likes
1
Downloads
0
Comments
1

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Who is the author/creator of this document ?
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

MTC in 3GPP Rel. 12 Presentation Transcript

  • 1. MTC in 3GPP Rel. 12
  • 2. Disclaimer The information presented in the following slides is taken from various 3GPP documents. No claim of originality is made for the content of these slides
  • 3. Study on Alternatives to E.164 for MTC MTC services are currently deployed over circuit-switched GSM architectures and require E.164 MSISDNs However, MTC services do not require "dialable" numbers, and communication between devices does not need human interaction There’s a serious threat of number crunch if alternative numbering schemes are not put in place ◊ Impact on M2M services as well the general GSM/UMTS services
  • 4. Study on Alternatives to E.164 for MTC Objective: Determine alternative to identify individual devices and route messages between those devices, including: ◊ Effectively identify addressing method to be used for end point devices ◊ Effectively route messaging between those devices ◊ Support multiple methods for delivering messages, as defined by TS 22.368 ◊ Support land-based and wireless connectivity ◊ Make use of IP-based network architectures ◊ Addressing/identifiers must support mobility and roaming ◊ support on high speed packet-switched networks when available and on circuit-switched networks ◊ Consider if there are security issues associated with any alternatives
  • 5. Study on enhancements for MTC In Rel. 10, the NIMTC Work Item specified requirements to make the network MTC-friendly ◊ MTC Device-to-Device communications was excluded from Rel-10 MTC Device-to-Device communications is expected to become of major importance, especially with consumer devices communicating directly to each other ◊ This study looks at network improvements requirements of MTC Device to MTC Device scenarios A particular aspect of MTC Device-to-Device scenarios is the identification and functionality needed to set up a connection towards a MTC Device ◊ IMS domain may provide a solution for this required functionality ◊ Impacts and requirements of MTC on IMS need to be studied
  • 6. Study on enhancements for MTC MTC Devices may also act as gateway for other MTC Devices or non-3GPP devices ◊ Study is needed to determine to what extent improvements are needed and can be specified by 3GPP for MTC Devices that act as a gateway ◊ Alignment with ETSI TC M2M specifications on this aspect is also needed Further optimisations are possible for co-located MTC Devices ◊ Study is needed to determine to what extent network improvements can be specified for co-located MTC Devices Different characteristics of MTC imply that the optimal network for MTC may not be the same as the optimal network for human to human communications ◊ Need to study optimisations of network selections and steering of roaming
  • 7. Study on enhancements for MTC Many MTC applications rely on some kind of location tracking ◊ E.g. the existing LCS framework could be used to provide location information for these kinds of MTC applications. ◊ Study is needed to determine to what extent improvements are needed for MTC location tracking MTC brings a new concept of a MTC User and MTC Server ◊ Limited attention given so far to service requirements on the communication between the network and the MTC User/MTC Server ◊ Alignment with by ETSI TC M2M specifications on this aspect is needed ◊ Study is needed on what kind of service requirements are needed and can be specified by 3GPP
  • 8. Study on enhancements for MTC Objective: to study additional requirements, use cases and functionality beyond Rel-10 NIMTC on the following: ◊ Network improvements for MTC Device to MTC Device communications via one or more PLMNs. ◊ Possible improvements for MTC Devices that act as a gateway for capillary networks of other devices ◊ Network improvements for groups of MTC Devices that are co-located with other MTC Devices ◊ Improvements on network selection mechanisms and steering of roaming for MTC devices ◊ Possible enhancements to IMS to support MTC ◊ Possible improvements for location tracking of MTC Devices ◊ Service requirements on communications between PLMN and the MTC User/MTC Server ◊ Possible service requirements to optimize MTC Devices ◊ Possible New MTC Features to further improve the network for MTC
  • 9. Machine-Type and other mobile data applicationsCommunications enhancements MTC-related Standardisation on M2M service enablement is on- going in other standardisation bodies ◊ Complementing work is needed on topics that affect existing MTC requirements in the 3GPP system and requirements on the interfaces between the 3GPP system and the M2M service enablement layer Objective: Identify and specify service requirements for the support of interworking of the 3GPP System with M2M service enablement layers as specified by ETSI TC M2M. This includes: ◊ Clarify the relation/mapping between the MTC Server and ETSI TC M2M service capabilities ◊ Requirements for handling subscriber identities across service enablement layers and the 3GPP system ◊ Requirements of interworking and integration of accounting and charging information ◊ Clarify border between 3GPP functionality and M2M service enablement
  • 10. Machine-Type and other mobile data applicationsCommunications enhancements The work will be conducted in separate Building Blocks The following BBs are identified for this work: ◊ Small Data and Triggering Enhancements ◊ Monitoring Enhancements ◊ UE Power Consumptions Optimizations ◊ Group based features