Content for TR 23.888 Word version: 11.0.0
6 Solutions p. 46
6.1 Solution - FQDN Identifier Solution p. 47
6.1.1 Problem Solved / Gains Provided p. 47
6.1.2 General p. 47
6.1.3 Impacts on existing nodes or functionality p. 48
6.1.4 Evaluation p. 48
6.2 Solution - Transfer of device trigger or data via SMS p. 49
6.2.1 Problem Solved / Gains Provided p. 49
6.2.2 General p. 49
6.2.3 Impacts on existing nodes or functionality p. 49
6.2.4 Evaluation p. 49
6.3 Solution - Paging within configured area p. 49
6.3.1 Problem Solved / Gains Provided p. 49
6.3.2 General p. 49
6.3.3 Impacts on existing nodes or functionality p. 50
6.3.4 Evaluation p. 50
6.4 Solution - Paging stepwise p. 50
6.4.1 Problem Solved / Gains Provided p. 50
6.4.2 General p. 50
6.4.3 Impacts on existing nodes or functionality p. 50
6.4.4 Evaluation p. 50
6.5 Solution - Paging within reported area p. 50
6.5.1 Problem Solved / Gains Provided p. 50
6.5.2 General p. 50
6.5.3 Impacts on existing nodes or functionality p. 50
6.5.4 Evaluation p. 50
6.6 Solution - Triggering of non-attached MTC Devices based on location information provided by MTC User p. 51
6.6.1 Problem Solved / Gains Provided p. 51
6.6.2 General p. 51
6.6.3 Impacts on existing nodes or functionality p. 51
6.6.4 Evaluation p. 51
6.7 Solution - Network access control by the PLMN p. 51
6.7.1 Problem Solved / Gains Provided p. 51
6.7.2 General p. 51
6.7.3 Impacts on existing nodes or functionality p. 52
6.7.4 Evaluation p. 53
6.8 Solution - Introduction of a 3GPP MTC Service Abstraction Layer p. 53
6.8.1 Problem Solved / Gains Provided p. 53
6.8.2 General p. 53
6.8.3 Impacts on existing nodes or functionality p. 54
6.8.4 Evaluation p. 54
6.9 Solution - MTC Monitoring - General p. 55
6.9.1 Problem Solved / Gains Provided p. 55
6.9.2 General p. 55
6.10 Solution - SGSN/MME based detection p. 56
6.10.1 Problem Solved / Gains Provided p. 56
6.10.2 General p. 56
6.10.3 Impacts on existing nodes or functionality p. 56
6.10.4 Evaluation p. 56
6.11 Solution - HLR/HSS based detection p. 56
6.11.1 Problem Solved / Gains Provided p. 56
6.11.2 General p. 57
6.11.3 Impacts on existing nodes or functionality p. 57
6.11.4 Evaluation p. 57
6.12 Solution - GGSN/P-GW based detection p. 58
6.12.1 Problem Solved / Gains Provided p. 58
6.12.2 General p. 58
6.12.3 Impacts on existing nodes or functionality p. 58
6.12.4 Evaluation p. 58
6.13 Solution - Reporting by SGSN/MME p. 59
6.13.1 Problem Solved / Gains Provided p. 59
6.13.2 General p. 59
6.13.3 Impacts on existing nodes or functionality p. 59
6.13.4 Evaluation p. 59
6.14 Solution - Reporting by HLR/HSS p. 59
6.14.1 Problem Solved / Gains Provided p. 59
6.14.2 General p. 59
6.14.3 Impacts on existing nodes or functionality p. 60
6.14.4 Evaluation p. 60
6.15 Solution - Reporting by GGSN/P-GW p. 60
6.15.1 Problem Solved / Gains Provided p. 60
6.15.2 General p. 60
6.15.3 Impacts on existing nodes or functionality p. 60
6.15.4 Evaluation p. 61
6.16 Solution - Reporting by PCRF p. 61
6.16.1 Problem Solved / Gains Provided p. 61
6.16.2 General p. 61
6.16.3 Impacts on existing nodes or functionality p. 61
6.16.4 Evaluation p. 61
6.17 Solution - Allowed Time Period after TAU/RAU p. 61
6.17.1 Problem Solved / Gains Provided p. 61
6.17.2 General p. 62
6.17.3 Impacts on existing nodes or functionality p. 62
6.17.4 Evaluation p. 62
6.18 Solution - MT Communication with NATTT p. 62
6.18.1 Problem Solved / Gains Provided p. 62
6.18.2 General p. 62
6.18.3 Impacts on existing nodes or functionality p. 64
6.18.4 Evaluation p. 64
6.19 Solution - MT Communication with Micro Port Forwarding p. 65
6.19.1 Problem Solved / Gains Provided p. 65
6.19.2 General p. 65
6.19.3 Impacts on existing nodes or functionality p. 68
6.19.4 Evaluation p. 68
6.20 Solution - Optimizing periodic LAU/RAU/TAU Signalling p. 69
6.20.1 Problem Solved / Gains Provided p. 69
6.20.2 General p. 69
6.20.3 Impacts on existing nodes or functionality p. 70
6.20.4 Evaluation p. 70
6.21 Solution - Randomized triggering of time-controlled MTC operations p. 71
6.21.1 Problem Solved / Gains Provided p. 71
6.21.2 General p. 71
6.21.3 Impacts on existing nodes or functionality p. 72
6.21.4 Evaluation p. 72
6.22 Solution - Rejecting connection requests by the SGSN/MME p. 72
6.22.1 Problem Solved / Gains Provided p. 72
6.22.2 General p. 72
6.22.3 Impacts on existing nodes or functionality p. 73
6.22.4 Evaluation p. 75
6.23 Solution - Low Priority Access Indication p. 75
6.23.1 Problem Solved / Gains Provided p. 75
6.23.2 General p. 75
6.23.3 Impacts on existing nodes or functionality p. 76
6.23.4 Evaluation p. 77
6.24 Solution - Directly Reporting to MTC Server from CN entity p. 78
6.24.1 Problem Solved / Gains Provided p. 78
6.24.2 General p. 78
6.24.3 Impacts on existing nodes or functionality p. 79
6.24.4 Evaluation p. 79
6.25 Solution - Reporting to MTC Server through the intermediate node p. 79
6.25.1 Problem Solved / Gains Provided p. 79
6.25.2 General p. 79
6.25.3 Impacts on existing nodes or functionality p. 80
6.25.4 Evaluation p. 80
6.26 Solution - Rejecting RRC Connection and Channel Requests by the eNodeB/RNC/BSS p. 80
6.26.1 Problem Solved / Gains Provided p. 80
6.26.2 General p. 80
6.26.3 Impacts on existing nodes or functionality p. 81
6.26.4 Evaluation p. 81
6.27 Time Control Solution Summary p. 83
6.28 Solution - Access Control by RAN p. 85
6.28.1 Problem Solved / Gains Provided p. 85
6.28.2 General p. 85
6.28.3 Impacts on existing nodes or functionality p. 86
6.28.4 Evaluation p. 88
6.29 Solution - IP address assignment mechanisms p. 90
6.29.1 Problem Solved / Gains Provided p. 90
6.29.2 General approach based on existing standards p. 90
6.29.3 IP address assignment by the PDN of the MTC server p. 91
6.29.4 IP address assignment by the GGSN/P-GW p. 91
6.29.5 MTC Server located on Internet and public IP addresses for MTC devices p. 92
6.29.6 Impacts on existing nodes or functionality p. 93
6.29.7 Evaluation p. 93
6.30 Solution - MME/SGSN overload control by DL MTC traffic throttling p. 93
6.30.1 Problem Solved / Gains Provided p. 93
6.30.2 General p. 94
6.30.3 Impacts on existing nodes or functionality p. 95
6.30.4 Evaluation p. 95
6.31 Solution - Rejecting connection requests at partial signalling links p. 95
6.31.1 Problem Solved / Gains Provided p. 95
6.31.2 General p. 95
6.31.3 Impacts on existing nodes or functionality p. 95
6.31.4 Evaluation p. 96
6.32 Solution - Rejecting connection requests based on request types p. 96
6.32.1 Problem Solved / Gains Provided p. 96
6.32.2 General p. 96
6.32.3 Impacts on existing nodes or functionality p. 97
6.32.4 Evaluation p. 97
6.33 Solution - UE behaviour changes p. 97
6.33.1 Problem Solved / Gains Provided p. 97
6.33.2 General p. 97
6.33.3 Impacts on existing nodes or functionality p. 98
6.33.4 Evaluation p. 98
6.34 Solution - M2M device indication to network p. 98
6.34.1 Problem Solved / Gains Provided p. 98
6.34.2 General p. 98
6.34.3 Impacts on existing nodes or functionality p. 98
6.34.4 Evaluation p. 98
6.35 Solution - Overload control within an MTC access grant time interval p. 98
6.35.1 Problems solved / Gains provided p. 98
6.35.2 General p. 98
6.35.3 Impacts on existing nodes or functionality p. 99
6.35.4 Evaluation p. 100
6.36 Solution - Time controlled feature via Operator and MTC User Business Agreements p. 100
6.36.1 Problem Solved / Gains Provided p. 100
6.36.2 General p. 100
6.36.3 Impacts on existing nodes or functionality p. 100
6.36.4 Evaluation p. 100
6.37 Solution - Simple Subscription Control p. 101
6.37.1 Problem Solved / Gains Provided p. 101
6.37.2 General p. 101
6.37.3 Impacts on existing nodes or functionality p. 101
6.37.4 Evaluation p. 101
6.38 Solution - Device identifier used over MTCSP p. 102
6.38.1 Problems solved / Gains provided p. 102
6.38.2 General p. 102
6.38.3 Impacts on existing nodes or functionality p. 104
6.38.4 Evaluation p. 104
6.39 Solution - Triggering MTC devices via HSS and NAS signalling p. 104
6.39.1 Problem Solved / Gains Provided p. 104
6.39.2 General p. 104
6.39.2.1 Overview p. 104
6.39.2.2 Detailed solution p. 104
6.39.3 Impacts on existing nodes or functionality p. 107
6.39.4 Evaluation p. 107
6.40 Solution - Information sent to trigger a UE used for MTC p. 107
6.40.1 Problem solved p. 107
6.40.2 Required Functionality p. 107
6.41 Solution - Triggering of attached MTC Devices by reusing Network Requested PDP Context Activation procedure p. 107
6.41.1 Problem Solved / Gains Provided p. 107
6.41.2 General p. 108
6.41.3 Impacts on existing nodes or functionality p. 109
6.41.4 Evaluation p. 110
6.42 Solution - Triggering of attached MTC Device via Pre rel-11 SMS p. 110
6.42.1 Problem Solved / Gains Provided p. 110
6.42.2 General p. 110
6.42.3 Impacts on existing nodes or functionality p. 110
6.42.4 Evaluation p. 110
6.43 Solution - Triggering of attached MTC Device via intermediate node p. 110
6.43.1 Problem Solved / Gains Provided p. 110
6.43.2 General p. 110
6.43.3 Impacts on existing nodes or functionality p. 111
6.43.4 Evaluation p. 111
6.44 Solution - Device Triggering reuse of MT SMS p. 111
6.44.1 Problems solved / Gains provided p. 111
6.44.2 General p. 111
6.44.3 Impacts on existing nodes or functionality p. 114
6.44.3.1 Impacts for MT-SMS device trigger - MSISDN based p. 114
6.44.3.2 Impacts for MT-SMS and MSISDN-less based p. 114
6.44.3.3 Properties of the solution p. 116
6.44.4 Evaluation p. 116
6.45 Solution - Device trigger gateway solution p. 117
6.45.1 Problem Solved / Gains Provided p. 117
6.45.2 General p. 117
6.45.3 Submission of device trigger request from MTC Server to HPLMN p. 117
6.45.4 HPLMN internal handling of device triggers p. 118
6.45.5 Delivery of device trigger from HPLMN to UE p. 119
6.45.6 DT functionality p. 119
6.45.7 Information flows p. 120
6.45.8 Impacts on existing nodes or functionality p. 121
6.45.9 Evaluation p. 121
6.46 Solution - Address resolution via MTC-IWF p. 121
6.46.1 Problem Solved / Gains Provided p. 121
6.46.2 General p. 121
6.46.3 UP MT communications UE current IP address resolution p. 122
6.46.4 CP device triggering assigned MTC-IWF address resolution p. 123
6.46.5 Impacts on existing nodes or functionality p. 123
6.46.6 Evaluation p. 123
6.47 Solution - UE without unique MSISDN using ICCID p. 124
6.47.1 Problem Solved / Gains Provided p. 124
6.47.2 General p. 124
6.47.3 Impacts on existing nodes or functionality p. 124
6.47.4 Evaluation p. 124
6.48 Solution - Transfer data via SMS for MTC Devices sharing one MSISDN p. 125
6.48.1 Problem Solved / Gains Provided p. 125
6.48.2 General p. 125
6.48.3 Impacts on existing nodes or functionality p. 126
6.48.4 Evaluation p. 126
6.49 Solution - UE configured to build its IPv6 address with the provided interface identifier p. 126
6.49.1 Problem Solved / Gains Provided p. 126
6.49.2 General p. 126
6.50 Solution - Use of FQDN Identifier with Dynamic DNS Update p. 127
6.50.1 Problem Solved / Gains Provided p. 127
6.50.2 General p. 127
6.51 Solution- MT Communication with MTCsp/MTCsms signalling p. 128
6.51.1 Problem Solved/ Gains Provided p. 128
6.51.2 General p. 128
6.51.3 Impacts on existing nodes or functionality p. 129
6.51.4 Evaluation p. 129
6.52 Solution - Transfer of device trigger or data via optimised SMS p. 129
6.52.1 Problem Solved / Gains Provided p. 129
6.52.2 General p. 129
6.52.2.1 Overview p. 129
6.52.2.2 Removal of CP protocol layer p. 130
6.52.2.3 Flexible deployment of MSC functionality for SMS over SGs p. 130
6.52.2.4 Stateless SMS IWF p. 132
6.52.2.5 Evolution of the signalling interfaces between MME and HSS/SMSC p. 133
6.52.2.6 Use of pre-established NAS security context to transfer the SMS PDUs as NAS signalling without establishing RRC security p. 133
6.52.2.7 Transfer of Device Trigger as MT SMS or NAS payload without U-plane bearer establishment in E-UTRAN p. 134
6.52.3 Impacts on existing nodes or functionality p. 135
6.52.4 Evaluation p. 135
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 security p. 135
6.53.1 Problem Solved / Gains Provided p. 135
6.53.2 General p. 135
6.53.3 Impacts on existing nodes or functionality p. 138
6.53.4 Evaluation p. 138
6.54 Solution - NAT Traversal using controlled NAT p. 138
6.54.1 Problem Solved / Gains Provided p. 138
6.54.2 General p. 138
6.54.3 Impacts on existing nodes or functionality p. 139
6.54.4 Evaluation p. 139
6.55 Solution - NAT Traversal using Non-Managed-NAT p. 140
6.55.1 Problem Solved/ Gains Provided p. 140
6.55.2 General p. 140
6.55.3 Non-Managed-NAT for MTC p. 140
6.55.4 Impacts on existing nodes or functionality p. 141
6.55.5 Evaluation p. 141
6.56 Solution - SMS Transfer by SGSN for PS-only p. 141
6.56.1 Problem Solved / Gains Provided p. 141
6.56.2 General p. 141
6.56.3 Impacts on existing nodes or functionality p. 142
6.56.4 Evaluation p. 142
6.57 Solution - Optimised SMS over SGs architecture p. 142
6.57.1 Problem Solved / Gains Provided p. 142
6.57.2 General p. 143
6.57.3 Impacts on existing nodes or functionality p. 143
6.57.4 Evaluation p. 143
6.58 Solution - Triggering using Cell Broadcast p. 144
6.58.1 Problem Solved / Gains Provided p. 144
6.58.2 General p. 144
6.58.3 Impacts on existing nodes or functionality p. 145
6.58.4 Evaluation p. 145
6.59 Solution - Load/Overload Control via MTC-IWF p. 146
6.59.1 Problem Solved / Gains Provided p. 146
6.59.2 General p. 146
6.59.3 MTC-IWF Load Control to MTC servers p. 146
6.59.4 MME/SGSN Overload Control of Trigger Requests to MTC-IWF(s) p. 147
6.59.5 Impacts on existing nodes or functionality p. 148
6.59.6 Evaluation p. 148
6.60 Solution - Device trigger using MT-SMS & direct SGSN/MME delivery p. 149
6.60.1 Problem Solved / Gains Provided p. 149
6.60.2 General p. 149
6.60.3 Impacts on existing nodes or functionality p. 149
6.60.4 Evaluation p. 150
6.61 Solution - Native SMS over NAS for PS-only p. 150
6.61.1 Problem Solved / Gains Provided p. 150
6.61.2 General p. 150
6.61.3 Impacts on existing nodes or functionality p. 150
6.61.4 Evaluation p. 151
6.62 Solution - User plane based device Triggering p. 151
6.62.1 Problem Solved / Gains Provided p. 151
6.62.2 High level information flow for Device Triggering using user plane p. 151
6.62.3 Proposals for MTC-IWF to determine IP address of MTC device p. 152
6.62.3.1 Alternate 1 - Explicit Registration based p. 152
6.62.3.2 Alternate 2 - Mapping Table based p. 152
6.62.4 IMS-based trigger delivery over user plane p. 153
