Tech-invite  3GPPspace  IETFspace
◀  ▶  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

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

3GPP‑Page   fToC↓   Partial Content →
V11.0.0 (Wzip)  2012/09  165 p.
Rapporteur:
Mr. Jain, Puneet
Intel Corporation (UK) Ltd

full Table of Contents for  TR 23.888  Word version:  11.0.0

each clause number in 'red' refers to the equivalent title in the Partial Content
Here   Top
1Scope  p. 12
2References  p. 12
3Definitions and abbreviations  p. 13
3.1Definitions  p. 13
3.2Abbreviations  p. 13
4Architectural Considerations  p. 14
4.1Architectural requirements  p. 14
4.1AArchitecture Principles  p. 14
4.2Architecture Model  p. 14
4.3Architectural Reference Model for MTC  p. 16
4.4Network Elements  p. 19
4.4.1General  p. 19
4.4.2MTC-IWF  p. 19
4.4.3HLR/HSS  p. 20
4.4.4GGSN/PGW  p. 20
4.4.5SGSN/MME  p. 20
4.5Reference Points  p. 20
4.5.1General  p. 20
4.5.2List of Reference Points  p. 21
4.5.3Reference Point Requirements  p. 21
4.5.3.1MTCsp Reference Point Requirements  p. 21
4.5.3.2T4 Reference Point Requirements  p. 21
4.5.3.3T5a/T5b Reference Point Requirements  p. 22
4.5.3.4S6m Reference Point Requirements  p. 22
4.6High Level Functions  p. 22
4.6.1General  p. 22
4.7Authorization and Security  p. 22
4.8Protocol Stacks  p. 23
4.8.1User plane  p. 23
4.8.2Control plane  p. 23
4.8.2.1MTC Server-MTC-IWF MTCsp reference point  p. 23
4.8.2.2MTC Server-SMS SC MTCsms reference point  p. 24
5Description of envisioned System Improvements for Machine Type Communication, use cases  p. 24
5.1Key Issue - Group Based Optimization  p. 24
5.1.1Use case description  p. 24
5.1.2Required Functionality  p. 24
5.1.3Evaluation  p. 24
5.2Key Issue - MTC Devices communicating with one or more MTC Servers  p. 24
5.2.1Use case description  p. 24
5.2.2Required Functionality  p. 25
5.3Key Issue - IP Addressing  p. 25
5.3.1Use case description  p. 25
5.3.2Required Functionality  p. 26
5.3.3Evaluation  p. 26
5.4Key Issue - Small Data Transmission  p. 29
5.4.1Use case description  p. 29
5.4.2Required Functionality  p. 29
5.4.3Evaluation  p. 30
5.5Void  p. …
5.6Key Issue - Low Mobility  p. 30
5.6.1Use case description  p. 30
5.6.2Required Functionality  p. 30
5.6.3Evaluation  p. 30
5.7Key Issue - MTC Subscriptions  p. 30
5.7.1Use case description  p. 30
5.7.2Required Functionality  p. 30
5.8Key Issue - MTC Device Trigger  p. 31
5.8.1Use case description  p. 31
5.8.2Required Functionality  p. 32
5.8.3Evaluation  p. 34
5.8.3.1Comparison of the MTC Device Trigger solutions  p. 34
5.8.3.2Delivery of device trigger information from 3GPP system to UE  p. 35
5.8.3.3Submission of device trigger requests from MTC server to 3GPP system  p. 35
5.8.3.43GPP system internal handling of device triggers  p. 35
5.9Key Issue -Time Controlled  p. 36
5.9.1Use case description  p. 36
5.9.2Required Functionality  p. 37
5.9.3Evaluation  p. 37
5.10Key Issue - MTC Monitoring  p. 37
5.10.1Use case description  p. 37
5.10.2Required Functionality  p. 37
5.11Key Issue - Decoupling MTC Server from 3GPP Architecture  p. 38
5.11.1Use Case Description  p. 38
5.11.2Required Functionality  p. 38
5.12Key Issue - Signalling Congestion Control  p. 38
5.12.1Use Case Description  p. 38
5.12.2Required Functionality  p. 39
5.12.3Evaluation  p. 40
5.12.3.1General  p. 40
5.12.3.2Evaluation for Congestion Control  p. 40
5.12.3.3Evaluation for Overload Control  p. 40
5.12.3.4Comparison of Each Solution  p. 41
5.13Key Issue - MTC Identifiers  p. 43
5.13.1Use Case Description  p. 43
5.13.2Required Functionality  p. 43
5.13.3Evaluation  p. 44
5.14Key Issue - Potential overload issues caused by Roaming MTC devices  p. 44
5.14.1Use Case Description  p. 44
5.14.1.1What is the likelihood of M2M devices being roamers?  p. 44
5.14.1.2What are the consequences if most M2M devices are roaming?  p. 44
5.14.1.2.1Commercial arrangements  p. 44
5.14.1.2.2Devices that only power-up/attach when they need to do something  p. 45
5.14.1.2.3Failure of "M2M partner" network  p. 45
5.14.2Required Functionality  p. 45
5.14.3Evaluation  p. 46
5.14.3.1Evaluation for M2M "access class barring" functionality  p. 46
5.15Key Issue - Low Power Consumption  p. 46
5.15.1Use case description  p. 46
5.15.2Required Functionality  p. 46
5.15.3Evaluation  p. 46
6Solutions  p. 46
6.1Solution - FQDN Identifier Solution  p. 47
6.1.1Problem Solved / Gains Provided  p. 47
6.1.2General  p. 47
6.1.3Impacts on existing nodes or functionality  p. 48
6.1.4Evaluation  p. 48
6.2Solution - Transfer of device trigger or data via SMS  p. 49
6.2.1Problem Solved / Gains Provided  p. 49
6.2.2General  p. 49
6.2.3Impacts on existing nodes or functionality  p. 49
6.2.4Evaluation  p. 49
6.3Solution - Paging within configured area  p. 49
6.3.1Problem Solved / Gains Provided  p. 49
6.3.2General  p. 49
6.3.3Impacts on existing nodes or functionality  p. 50
6.3.4Evaluation  p. 50
6.4Solution - Paging stepwise  p. 50
6.4.1Problem Solved / Gains Provided  p. 50
6.4.2General  p. 50
6.4.3Impacts on existing nodes or functionality  p. 50
6.4.4Evaluation  p. 50
6.5Solution - Paging within reported area  p. 50
6.5.1Problem Solved / Gains Provided  p. 50
6.5.2General  p. 50
6.5.3Impacts on existing nodes or functionality  p. 50
6.5.4Evaluation  p. 50
6.6Solution - Triggering of non-attached MTC Devices based on location information provided by MTC User  p. 51
6.6.1Problem Solved / Gains Provided  p. 51
6.6.2General  p. 51
6.6.3Impacts on existing nodes or functionality  p. 51
6.6.4Evaluation  p. 51
6.7Solution - Network access control by the PLMN  p. 51
6.7.1Problem Solved / Gains Provided  p. 51
6.7.2General  p. 51
6.7.3Impacts on existing nodes or functionality  p. 52
6.7.4Evaluation  p. 53
6.8Solution - Introduction of a 3GPP MTC Service Abstraction Layer  p. 53
6.8.1Problem Solved / Gains Provided  p. 53
6.8.2General  p. 53
6.8.3Impacts on existing nodes or functionality  p. 54
6.8.4Evaluation  p. 54
6.9Solution - MTC Monitoring - General  p. 55
6.9.1Problem Solved / Gains Provided  p. 55
6.9.2General  p. 55
6.10Solution - SGSN/MME based detection  p. 56
6.10.1Problem Solved / Gains Provided  p. 56
6.10.2General  p. 56
6.10.3Impacts on existing nodes or functionality  p. 56
6.10.4Evaluation  p. 56
6.11Solution - HLR/HSS based detection  p. 56
6.11.1Problem Solved / Gains Provided  p. 56
6.11.2General  p. 57
6.11.3Impacts on existing nodes or functionality  p. 57
6.11.4Evaluation  p. 57
6.12Solution - GGSN/P-GW based detection  p. 58
6.12.1Problem Solved / Gains Provided  p. 58
6.12.2General  p. 58
6.12.3Impacts on existing nodes or functionality  p. 58
6.12.4Evaluation  p. 58
6.13Solution - Reporting by SGSN/MME  p. 59
6.13.1Problem Solved / Gains Provided  p. 59
6.13.2General  p. 59
6.13.3Impacts on existing nodes or functionality  p. 59
6.13.4Evaluation  p. 59
6.14Solution - Reporting by HLR/HSS  p. 59
6.14.1Problem Solved / Gains Provided  p. 59
6.14.2General  p. 59
6.14.3Impacts on existing nodes or functionality  p. 60
6.14.4Evaluation  p. 60
6.15Solution - Reporting by GGSN/P-GW  p. 60
6.15.1Problem Solved / Gains Provided  p. 60
6.15.2General  p. 60
6.15.3Impacts on existing nodes or functionality  p. 60
6.15.4Evaluation  p. 61
6.16Solution - Reporting by PCRF  p. 61
6.16.1Problem Solved / Gains Provided  p. 61
6.16.2General  p. 61
6.16.3Impacts on existing nodes or functionality  p. 61
6.16.4Evaluation  p. 61
6.17Solution - Allowed Time Period after TAU/RAU  p. 61
6.17.1Problem Solved / Gains Provided  p. 61
6.17.2General  p. 62
6.17.3Impacts on existing nodes or functionality  p. 62
6.17.4Evaluation  p. 62
6.18Solution - MT Communication with NATTT  p. 62
6.18.1Problem Solved / Gains Provided  p. 62
6.18.2General  p. 62
6.18.3Impacts on existing nodes or functionality  p. 64
6.18.4Evaluation  p. 64
6.19Solution - MT Communication with Micro Port Forwarding  p. 65
6.19.1Problem Solved / Gains Provided  p. 65
6.19.2General  p. 65
6.19.3Impacts on existing nodes or functionality  p. 68
6.19.4Evaluation  p. 68
6.20Solution - Optimizing periodic LAU/RAU/TAU Signalling  p. 69
6.20.1Problem Solved / Gains Provided  p. 69
6.20.2General  p. 69
6.20.3Impacts on existing nodes or functionality  p. 70
6.20.4Evaluation  p. 70
6.21Solution - Randomized triggering of time-controlled MTC operations  p. 71
6.21.1Problem Solved / Gains Provided  p. 71
6.21.2General  p. 71
6.21.3Impacts on existing nodes or functionality  p. 72
6.21.4Evaluation  p. 72
6.22Solution - Rejecting connection requests by the SGSN/MME  p. 72
6.22.1Problem Solved / Gains Provided  p. 72
6.22.2General  p. 72
6.22.3Impacts on existing nodes or functionality  p. 73
6.22.4Evaluation  p. 75
6.23Solution - Low Priority Access Indication  p. 75
6.23.1Problem Solved / Gains Provided  p. 75
6.23.2General  p. 75
6.23.3Impacts on existing nodes or functionality  p. 76
6.23.4Evaluation  p. 77
6.24Solution - Directly Reporting to MTC Server from CN entity  p. 78
6.24.1Problem Solved / Gains Provided  p. 78
6.24.2General  p. 78
6.24.3Impacts on existing nodes or functionality  p. 79
6.24.4Evaluation  p. 79
6.25Solution - Reporting to MTC Server through the intermediate node  p. 79
6.25.1Problem Solved / Gains Provided  p. 79
6.25.2General  p. 79
6.25.3Impacts on existing nodes or functionality  p. 80
6.25.4Evaluation  p. 80
6.26Solution - Rejecting RRC Connection and Channel Requests by the eNodeB/RNC/BSS  p. 80
6.26.1Problem Solved / Gains Provided  p. 80
6.26.2General  p. 80
6.26.3Impacts on existing nodes or functionality  p. 81
6.26.4Evaluation  p. 81
6.27Time Control Solution Summary  p. 83
6.28Solution - Access Control by RAN  p. 85
6.28.1Problem Solved / Gains Provided  p. 85
6.28.2General  p. 85
6.28.3Impacts on existing nodes or functionality  p. 86
6.28.4Evaluation  p. 88
6.29Solution - IP address assignment mechanisms  p. 90
6.29.1Problem Solved / Gains Provided  p. 90
6.29.2General approach based on existing standards  p. 90
6.29.3IP address assignment by the PDN of the MTC server  p. 91
6.29.4IP address assignment by the GGSN/P-GW  p. 91
6.29.5MTC Server located on Internet and public IP addresses for MTC devices  p. 92
6.29.6Impacts on existing nodes or functionality  p. 93
6.29.7Evaluation  p. 93
6.30Solution - MME/SGSN overload control by DL MTC traffic throttling  p. 93
6.30.1Problem Solved / Gains Provided  p. 93
6.30.2General  p. 94
6.30.3Impacts on existing nodes or functionality  p. 95
6.30.4Evaluation  p. 95
6.31Solution - Rejecting connection requests at partial signalling links  p. 95
6.31.1Problem Solved / Gains Provided  p. 95
6.31.2General  p. 95
6.31.3Impacts on existing nodes or functionality  p. 95
6.31.4Evaluation  p. 96
6.32Solution - Rejecting connection requests based on request types  p. 96
6.32.1Problem Solved / Gains Provided  p. 96
6.32.2General  p. 96
6.32.3Impacts on existing nodes or functionality  p. 97
6.32.4Evaluation  p. 97
6.33Solution - UE behaviour changes  p. 97
6.33.1Problem Solved / Gains Provided  p. 97
6.33.2General  p. 97
6.33.3Impacts on existing nodes or functionality  p. 98
6.33.4Evaluation  p. 98
6.34Solution - M2M device indication to network  p. 98
6.34.1Problem Solved / Gains Provided  p. 98
6.34.2General  p. 98
6.34.3Impacts on existing nodes or functionality  p. 98
6.34.4Evaluation  p. 98
6.35Solution - Overload control within an MTC access grant time interval  p. 98
6.35.1Problems solved / Gains provided  p. 98
6.35.2General  p. 98
6.35.3Impacts on existing nodes or functionality  p. 99
6.35.4Evaluation  p. 100
6.36Solution - Time controlled feature via Operator and MTC User Business Agreements  p. 100
6.36.1Problem Solved / Gains Provided  p. 100
6.36.2General  p. 100
6.36.3Impacts on existing nodes or functionality  p. 100
6.36.4Evaluation  p. 100
6.37Solution - Simple Subscription Control  p. 101
6.37.1Problem Solved / Gains Provided  p. 101
6.37.2General  p. 101
6.37.3Impacts on existing nodes or functionality  p. 101
6.37.4Evaluation  p. 101
6.38Solution - Device identifier used over MTCSP  p. 102
6.38.1Problems solved / Gains provided  p. 102
6.38.2General  p. 102
6.38.3Impacts on existing nodes or functionality  p. 104
6.38.4Evaluation  p. 104
6.39Solution - Triggering MTC devices via HSS and NAS signalling  p. 104
6.39.1Problem Solved / Gains Provided  p. 104
6.39.2General  p. 104
6.39.2.1Overview  p. 104
6.39.2.2Detailed solution  p. 104
6.39.3Impacts on existing nodes or functionality  p. 107
6.39.4Evaluation  p. 107
6.40Solution - Information sent to trigger a UE used for MTC  p. 107
6.40.1Problem solved  p. 107
6.40.2Required Functionality  p. 107
6.41Solution - Triggering of attached MTC Devices by reusing Network Requested PDP Context Activation procedure  p. 107
6.41.1Problem Solved / Gains Provided  p. 107
6.41.2General  p. 108
6.41.3Impacts on existing nodes or functionality  p. 109
6.41.4Evaluation  p. 110
6.42Solution - Triggering of attached MTC Device via Pre rel-11 SMS  p. 110
6.42.1Problem Solved / Gains Provided  p. 110
6.42.2General  p. 110
6.42.3Impacts on existing nodes or functionality  p. 110
6.42.4Evaluation  p. 110
6.43Solution - Triggering of attached MTC Device via intermediate node  p. 110
6.43.1Problem Solved / Gains Provided  p. 110
6.43.2General  p. 110
6.43.3Impacts on existing nodes or functionality  p. 111
6.43.4Evaluation  p. 111
6.44Solution - Device Triggering reuse of MT SMS  p. 111
6.44.1Problems solved / Gains provided  p. 111
6.44.2General  p. 111
6.44.3Impacts on existing nodes or functionality  p. 114
6.44.3.1Impacts for MT-SMS device trigger - MSISDN based  p. 114
6.44.3.2Impacts for MT-SMS and MSISDN-less based  p. 114
6.44.3.3Properties of the solution  p. 116
6.44.4Evaluation  p. 116
6.45Solution - Device trigger gateway solution  p. 117
6.45.1Problem Solved / Gains Provided  p. 117
6.45.2General  p. 117
6.45.3Submission of device trigger request from MTC Server to HPLMN  p. 117
6.45.4HPLMN internal handling of device triggers  p. 118
6.45.5Delivery of device trigger from HPLMN to UE  p. 119
6.45.6DT functionality  p. 119
6.45.7Information flows  p. 120
6.45.8Impacts on existing nodes or functionality  p. 121
6.45.9Evaluation  p. 121
6.46Solution - Address resolution via MTC-IWF  p. 121
6.46.1Problem Solved / Gains Provided  p. 121
6.46.2General  p. 121
6.46.3UP MT communications UE current IP address resolution  p. 122
6.46.4CP device triggering assigned MTC-IWF address resolution  p. 123
6.46.5Impacts on existing nodes or functionality  p. 123
6.46.6Evaluation  p. 123
6.47Solution - UE without unique MSISDN using ICCID  p. 124
6.47.1Problem Solved / Gains Provided  p. 124
6.47.2General  p. 124
6.47.3Impacts on existing nodes or functionality  p. 124
6.47.4Evaluation  p. 124
6.48Solution - Transfer data via SMS for MTC Devices sharing one MSISDN  p. 125
6.48.1Problem Solved / Gains Provided  p. 125
6.48.2General  p. 125
6.48.3Impacts on existing nodes or functionality  p. 126
6.48.4Evaluation  p. 126
6.49Solution - UE configured to build its IPv6 address with the provided interface identifier  p. 126
6.49.1Problem Solved / Gains Provided  p. 126
6.49.2General  p. 126
6.50Solution - Use of FQDN Identifier with Dynamic DNS Update  p. 127
6.50.1Problem Solved / Gains Provided  p. 127
6.50.2General  p. 127
6.51Solution- MT Communication with MTCsp/MTCsms signalling  p. 128
6.51.1Problem Solved/ Gains Provided  p. 128
6.51.2General  p. 128
6.51.3Impacts on existing nodes or functionality  p. 129
6.51.4Evaluation  p. 129
6.52Solution - Transfer of device trigger or data via optimised SMS  p. 129
6.52.1Problem Solved / Gains Provided  p. 129
6.52.2General  p. 129
6.52.2.1Overview  p. 129
6.52.2.2Removal of CP protocol layer  p. 130
6.52.2.3Flexible deployment of MSC functionality for SMS over SGs  p. 130
6.52.2.4Stateless SMS IWF  p. 132
6.52.2.5Evolution of the signalling interfaces between MME and HSS/SMSC  p. 133
6.52.2.6Use of pre-established NAS security context to transfer the SMS PDUs as NAS signalling without establishing RRC security  p. 133
6.52.2.7Transfer of Device Trigger as MT SMS or NAS payload without U-plane bearer establishment in E-UTRAN  p. 134
6.52.3Impacts on existing nodes or functionality  p. 135
6.52.4Evaluation  p. 135
6.53Solution - Small Data Transfer (E-UTRAN): Use of pre-established NAS security context to transfer the IP packet as NAS signalling without establishing RRC security  p. 135
6.53.1Problem Solved / Gains Provided  p. 135
6.53.2General  p. 135
6.53.3Impacts on existing nodes or functionality  p. 138
6.53.4Evaluation  p. 138
6.54Solution - NAT Traversal using controlled NAT  p. 138
6.54.1Problem Solved / Gains Provided  p. 138
6.54.2General  p. 138
6.54.3Impacts on existing nodes or functionality  p. 139
6.54.4Evaluation  p. 139
6.55Solution - NAT Traversal using Non-Managed-NAT  p. 140
6.55.1Problem Solved/ Gains Provided  p. 140
6.55.2General  p. 140
6.55.3Non-Managed-NAT for MTC  p. 140
6.55.4Impacts on existing nodes or functionality  p. 141
6.55.5Evaluation  p. 141
6.56Solution - SMS Transfer by SGSN for PS-only  p. 141
6.56.1Problem Solved / Gains Provided  p. 141
6.56.2General  p. 141
6.56.3Impacts on existing nodes or functionality  p. 142
6.56.4Evaluation  p. 142
6.57Solution - Optimised SMS over SGs architecture  p. 142
6.57.1Problem Solved / Gains Provided  p. 142
6.57.2General  p. 143
6.57.3Impacts on existing nodes or functionality  p. 143
6.57.4Evaluation  p. 143
6.58Solution - Triggering using Cell Broadcast  p. 144
6.58.1Problem Solved / Gains Provided  p. 144
6.58.2General  p. 144
6.58.3Impacts on existing nodes or functionality  p. 145
6.58.4Evaluation  p. 145
6.59Solution - Load/Overload Control via MTC-IWF  p. 146
6.59.1Problem Solved / Gains Provided  p. 146
6.59.2General  p. 146
6.59.3MTC-IWF Load Control to MTC servers  p. 146
6.59.4MME/SGSN Overload Control of Trigger Requests to MTC-IWF(s)  p. 147
6.59.5Impacts on existing nodes or functionality  p. 148
6.59.6Evaluation  p. 148
6.60Solution - Device trigger using MT-SMS & direct SGSN/MME delivery  p. 149
6.60.1Problem Solved / Gains Provided  p. 149
6.60.2General  p. 149
6.60.3Impacts on existing nodes or functionality  p. 149
6.60.4Evaluation  p. 150
6.61Solution - Native SMS over NAS for PS-only  p. 150
6.61.1Problem Solved / Gains Provided  p. 150
6.61.2General  p. 150
6.61.3Impacts on existing nodes or functionality  p. 150
6.61.4Evaluation  p. 151
6.62Solution - User plane based device Triggering  p. 151
6.62.1Problem Solved / Gains Provided  p. 151
6.62.2High level information flow for Device Triggering using user plane  p. 151
6.62.3Proposals for MTC-IWF to determine IP address of MTC device  p. 152
6.62.3.1Alternate 1 - Explicit Registration based  p. 152
6.62.3.2Alternate 2 - Mapping Table based  p. 152
6.62.3.2.1MME/HSS based mapping table update  p. 152
6.62.3.2.2PGW/GGSN based mapping table update  p. 153
6.62.4IMS-based trigger delivery over user plane  p. 153
7Conclusions  p. 154
7.1Interim conclusions for release 10 specification work  p. 154
7.2Interim conclusions for release 11 specification work  p. 154
7.2.1IP Addressing - Key Issue 5.3  p. 154
7.2.2MTC Device Triggering - Key Issue 5.8  p. 155
7.2.3MTC Identifiers - Key Issue 5.13  p. 157
7.2.4MTC Feature Control - Key Issue 5.7  p. 157
7.2.5MTC Feature - Packet Switched only  p. 157
8Impacts to normative specifications  p. 158
8.1Related to Interim conclusions for release 10 specification work  p. 158
8.2Related to Interim conclusions for release 11 specification work  p. 158
8.2.1IP addressing  p. 158
8.2.1.1Guiding Principles  p. 158
8.2.1.2Documentation approach  p. 158
8.2.2MTC Identifiers  p. 159
8.2.2.1Guiding Principles  p. 159
8.2.2.2Documentation approach  p. 159
AStage 2 PS Dependencies on MSISDN-based Subscriptions  p. 160
A.1General Considerations  p. 160
A.2PS stage 2 MSISDN dependencies  p. 160
A.2.1General network architecture  p. 160
A.2.2GPRS  p. 160
A.2.3EPS  p. 160
A.2.4WLAN  p. 161
A.2.5SMS  p. 161
A.2.6IMS  p. 162
A.2.7PCC  p. 162
A.2.8LCS  p. 162
A.2.9SIPTO  p. 162
A.2.10CAMEL  p. 163
A.2.11Other services  p. 163
A.3Impact of MSISDN-less subscriptions for PS only MS/UEs  p. 164
$Change history  p. 165

Up   Top