Tech-invite   3GPPspecs   IETFRFCs   SIP   Search in Tech-invite

Top   in Index   Prev   Next

TR 23.888 (SA2)
System improvements for
Machine-Type Communications (MTC)

3GPP‑Page   full‑ToC  
use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V11.0.0 (Wzip)  2012/09  165 p.


Rapporteur:  Mr. Jain, Puneet

This TR studies and evaluates architectural aspects of the System Improvements for Machine Type Communications requirements specified in TS 22.368.

full Table of Contents for  TR 23.888  Word version:   11.0.0

 

Here   Top

 

1  ScopeWord-p. 12
2  References
3  Definitions and abbreviationsWord-p. 13
4  Architectural ConsiderationsWord-p. 14
5  Description of envisioned System Improvements for Machine Type Communication, use cases
5.1  Key Issue - Group Based Optimization
5.2  Key Issue - MTC Devices communicating with one or more MTC Servers
5.3  Key Issue - IP AddressingUp
5.4  Key Issue - Small Data TransmissionWord-p. 29
5.5Void
5.6  Key Issue - Low Mobility
5.7  Key Issue - MTC Subscriptions
5.8  Key Issue - MTC Device TriggerWord-p. 31
5.9  Key Issue -Time ControlledWord-p. 36
5.10  Key Issue - MTC Monitoring
5.11  Key Issue - Decoupling MTC Server from 3GPP ArchitectureWord-p. 38
5.12  Key Issue - Signalling Congestion Control
5.13  Key Issue - MTC IdentifiersWord-p. 43
5.14  Key Issue - Potential overload issues caused by Roaming MTC devices
5.15  Key Issue - Low Power Consumption
6  Solutions
6.1  Solution - FQDN Identifier SolutionWord-p. 47
6.2  Solution - Transfer of device trigger or data via SMSWord-p. 49
6.3  Solution - Paging within configured areaUp
6.4  Solution - Paging stepwise
6.5  Solution - Paging within reported areaUp
6.6  Solution - Triggering of non-attached MTC Devices based on location information provided by MTC UserWord-p. 51
6.7  Solution - Network access control by the PLMNUp
6.8  Solution - Introduction of a 3GPP MTC Service Abstraction Layer
6.9  Solution - MTC Monitoring - GeneralWord-p. 55
6.10  Solution - SGSN/MME based detectionWord-p. 56
6.11  Solution - HLR/HSS based detection
6.12  Solution - GGSN/P-GW based detectionWord-p. 58
6.13  Solution - Reporting by SGSN/MMEWord-p. 59
6.14  Solution - Reporting by HLR/HSS
6.15  Solution - Reporting by GGSN/P-GW
6.16  Solution - Reporting by PCRF
6.17  Solution - Allowed Time Period after TAU/RAU
6.18  Solution - MT Communication with NATTT
6.19  Solution - MT Communication with Micro Port ForwardingWord-p. 65
6.20  Solution - Optimizing periodic LAU/RAU/TAU SignallingWord-p. 69
6.21  Solution - Randomized triggering of time-controlled MTC operationsWord-p. 71
6.22  Solution - Rejecting connection requests by the SGSN/MME
6.23  Solution - Low Priority Access Indication
6.24  Solution - Directly Reporting to MTC Server from CN entityWord-p. 78
6.25  Solution - Reporting to MTC Server through the intermediate node
6.26  Solution - Rejecting RRC Connection and Channel Requests by the eNodeB/RNC/BSS
6.27  Time Control Solution SummaryWord-p. 83
6.28  Solution - Access Control by RANWord-p. 85
6.29  Solution - IP address assignment mechanismsWord-p. 90
6.30  Solution - MME/SGSN overload control by DL MTC traffic throttling
6.31  Solution - Rejecting connection requests at partial signalling links
6.32  Solution - Rejecting connection requests based on request types
6.33  Solution - UE behaviour changes
6.34  Solution - M2M device indication to network
6.35  Solution - Overload control within an MTC access grant time interval
6.36  Solution - Time controlled feature via Operator and MTC User Business Agreements
6.37  Solution - Simple Subscription ControlWord-p. 101
6.38  Solution - Device identifier used over MTCSPWord-p. 102
6.39  Solution - Triggering MTC devices via HSS and NAS signalling
6.40  Solution - Information sent to trigger a UE used for MTC
6.41  Solution - Triggering of attached MTC Devices by reusing Network Requested PDP Context Activation procedure
6.42  Solution - Triggering of attached MTC Device via Pre rel-11 SMS
6.43  Solution - Triggering of attached MTC Device via intermediate node
6.44  Solution - Device Triggering reuse of MT SMS
6.45  Solution - Device trigger gateway solutionWord-p. 117
6.46  Solution - Address resolution via MTC-IWFUp
6.47  Solution - UE without unique MSISDN using ICCIDWord-p. 124
6.48  Solution - Transfer data via SMS for MTC Devices sharing one MSISDNWord-p. 125
6.49  Solution - UE configured to build its IPv6 address with the provided interface identifier
6.50  Solution - Use of FQDN Identifier with Dynamic DNS UpdateWord-p. 127
6.51  Solution- MT Communication with MTCsp/MTCsms signallingWord-p. 128
6.52  Solution - Transfer of device trigger or data via optimised SMS
6.53  Solution - Small Data Transfer (E-UTRAN): Use of pre-established NAS security context to transfer the IP packet as NAS signalling without establishing RRC securityUp
6.54  Solution - NAT Traversal using controlled NAT
6.55  Solution - NAT Traversal using Non-Managed-NATWord-p. 140
6.56  Solution - SMS Transfer by SGSN for PS-only
6.57  Solution - Optimised SMS over SGs architecture
6.58  Solution - Triggering using Cell BroadcastWord-p. 144
6.59  Solution - Load/Overload Control via MTC-IWFWord-p. 146
6.60  Solution - Device trigger using MT-SMS & direct SGSN/MME deliveryWord-p. 149
6.61  Solution - Native SMS over NAS for PS-only
6.62  Solution - User plane based device Triggering
7  ConclusionsWord-p. 154
8  Impacts to normative specificationsWord-p. 158
A  Stage 2 PS Dependencies on MSISDN-based SubscriptionsWord-p. 160
B  Change historyWord-p. 165

Up   Top