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

Top   in Index   Prev   Next

TR 23.724 (SA2)
Study on
CIoT Support and Evolution
for the 5G System

3GPP‑Page   short‑ToC   full‑ToC  
use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V16.1.0 (Wzip)2019/06  274 p.


Rapporteur:  Dr. Speicher, Sebastian

This technical report studies and evaluates architecture enhancements to address the following objectives:
  1. Enable CIoT/MTC functionalities in 5G CN
    The objective is to study how to support identified CioT/MTC functionalities in 5G CN with potential connectivity to WB-EUTRA (eMTC) and/or NB-IoT for 5GS capable devices.
    The following CIoT/MTC functionalities need to be evaluated and studied how to enable them in 5G CN, if needed:
    • Equivalent overall functionalities as provided by SCEF for CIoT/MTC.
    • Monitoring.
    • Small data transmission (infrequent and frequent small data transmission including frequent small data transmission from tracking devices).
    • Additional power saving functions unless those are supported for 5G system in Rel-15.
    • Non-IP Data Delivery.
    • Overload control (as relevant in 5G CN).
    • Support of Coverage enhancement including adaptations in 5G CN required to support latencies.
    • Equivalent to Group communication and messaging.
    • Reliable communication via functionality equivalent to SCEF.
    • Inter-RAT mobility support to/from NB-IoT.
    • High latency communication.
    • Include location services procedures for IoT in 5G location services.
    NOTE:  Attach without PDN connection and non-IP PDN Connection type is already supported in 5G CN. Ensure that regulatory requirements can be fulfilled at the same level as in EPC.
  2. Co-existence and migration from EPC based eMTC/NB-IoT to 5GCN
    Study solutions for coexistence and migration from EPC towards 5G CN for eMTC/NB-IoT.
    This objective will study solutions where the same service is offered to some UEs connected to EPC and some UEs connected to 5G CN e.g. using SCEF and equivalent functionalities in 5GCN. Solutions that assume that 5G CN needs to support EPC NAS signaling for legacy IoT devices access are not considered.
    Any modifications in the EPC-5GC interworking "baseline" specific to CIOT will also be discussed as part of Objective II.
  3. 5G System enhancements to address 5G service requirements
    To study system architecture enhancements to address related service requirements defined in TS 22.261 and RAN requirements defined in TR 38.913 and how to enable them in 5G CN, if needed. At least the following service requirements have been identified:
    • Enable the change of association between subscription and address/number of an IoT device within same operator and in between different operators.
    • Restricted Registration procedure to allow IoT device provisioning.
Any system implications for the RAN will be coordinated with RAN WGs.
This study is not going to study enhancements to EPC.

short Table of Contents for  TR 23.724  Word version:   16.1.0

each title links to the equivalent title in the full ToC

 

Here   Top

 

1  ScopeWord-p. 16
2  ReferencesWord-p. 17
3  Definitions, symbols and abbreviationsWord-p. 18
4  Architectural Assumptions and PrinciplesWord-p. 18
5  Key IssuesWord-p. 19
5.1  Key Issue 1: Support for infrequent small data transmissionWord-p. 19
5.2  Key Issue 2: Frequent small data communicationWord-p. 20
5.3  Key Issue 3: High latency communicationWord-p. 21
5.4  Key Issue 4: Power Saving FunctionsWord-p. 22
5.5  Key Issue 5: UE TX Power Saving FunctionsWord-p. 23
5.6  Key Issue 6: Management of Enhanced CoverageWord-p. 24
5.7  Key Issue 7: Overload Control for small dataWord-p. 25
5.8  Key Issue 8: Support of the Reliable Data ServiceWord-p. 26
5.9  Key Issue 9: Support of common north-bound APIs for EPC-5GC InterworkingWord-p. 26
5.10  Key Issue 10: Network Parameter Configuration API via NEFWord-p. 27
5.11  Key Issue 11: MonitoringWord-p. 28
5.12  Key Issue 12: Inter-RAT mobility support to/from NB-IoTWord-p. 29
5.13  Key Issue 13: Support for Expected UE BehaviourWord-p. 30
5.14  Key Issue 14: QoS Support for NB-IoTWord-p. 31
5.15  Key Issue 15: Core Network selection for Cellular IoTWord-p. 31
5.16  Key Issue 16: Support of Group communication and messagingWord-p. 32
5.17  Key Issue 17: MSISDN-less MO SMSWord-p. 33
6  SolutionsWord-p. 34
6.1  Solution 1: Infrequent small data transfer via NAS-SM and N6Word-p. 34
6.2  Solution 2: Infrequent small data transfer through NAS and a direct interface between AMF and UPFWord-p. 45
6.3  Solution 3: Infrequent small data transmission with no PDU session availableWord-p. 51
6.4  Solution 4: Reliable Data Service SupportWord-p. 55
6.5  Solution 5: Small Data Fast Path communicationWord-p. 62
6.6  Solution 6: Small Data Communication based on Data PDU routed over the User Plane.UpWord-p. 70
6.7  Solution 7: Small data frequent communicationWord-p. 82
6.8  Solution 8: Enhancing MICO for Mobile terminated data/signalingWord-p. 88
6.9  Solution 9: Enhanced MICO mode with Active TimeWord-p. 90
6.10  Solution 10: Solution for supporting High Latency CommunicationWord-p. 92
6.11  Solution 11: Extended buffering in SMF and NEFWord-p. 95
6.12  Solution 12: Solution for Management of Enhanced Coverage for 5GCUpWord-p. 97
6.13  Solution 13: SCEF+NEF NodeWord-p. 101
6.14  Solution 14: APISupportCapability serviceUpWord-p. 103
6.15  Solution 15: External parameter provisioning in the 5GCWord-p. 109
6.16  Solution 16: UE assisted Inter-UE QoS Support for Data over NASWord-p. 112
6.17  Solution 17: UE-Driven Packet ClassificationWord-p. 115
6.18  Solution 18: QoS control for unstructured PDU sessionsWord-p. 118
6.19  Solution 19: 5GS UP Optimization for Infrequent Small Data TransmissionWord-p. 122
6.20  Solution 20: NIDD API support by SMF for infrequent small data transfer via NAS-SMWord-p. 133
6.21  Solution 21: NIDD service activationWord-p. 142
6.22  Solution 22: eDRX for CM-IDLE state in 5GSWord-p. 147
6.23  Solution 23: MICO Mode Management for Expected Application BehaviourWord-p. 148
6.24  Solution 24: High latency communication with extended buffering and event notificationsWord-p. 151
6.25  Solution 25: HLCom buffering and event notification support for CM-IDLEWord-p. 165
6.26  Solution 26: Expected UE Behaviour provisioning for CIoTUpWord-p. 172
6.27  Solution 27: Reuse of EPS Overload Control MechanismsWord-p. 175
6.28  Solution 28: SMF assisted NG-RAN informationWord-p. 178
6.29  Solution 29: User Plane data transmission with ConnectionLess signallingWord-p. 182
6.30  Solution 30: NEF based infrequent small data transfer via NAS-SMWord-p. 194
6.31  Solution 31: Deferring of Periodic Registration UpdateWord-p. 202
6.32  Solution 32: MO Data Buffering in the UEUpWord-p. 204
6.33  Solution 33: Delayed Paging ResponseWord-p. 205
6.34  Solution 34: Provisioning of UE TX power saving parametersWord-p. 208
6.35  Solution 35: Small data deliveryWord-p. 209
6.36  Solution 36: CM-CONNECTED with RRC Inactive state for frequent small data transmissionWord-p. 215
6.37  Solution 37: MonitoringWord-p. 219
6.38  Solution 38: eDRX RRC_INACTIVE STATE in 5GSWord-p. 222
6.39  Solution 39: UE availability after DDN failure for multiple AFsWord-p. 224
6.40  Solution 40: Infrequent small data transmission with temporary PDU sessionWord-p. 228
6.41  Solution 41: Combining RRC-INACTIVE and 5G UP optimizationWord-p. 231
6.42  Solution 42: NAS based Redirection between Core NetworksWord-p. 232
6.43  Solution 43: RRC based Redirection between Core networksWord-p. 235
6.44  Solution 44: C-IoT UE Core Network selection based on S-NSSAIsUpWord-p. 238
6.45  Solution 45: Core Network Type and Node Selection for CIoT UE Using Explicit IndicationsWord-p. 241
6.46  Solution 46: Network controlled UL data transmission delayWord-p. 243
6.47  Solution 47: Improved Signalling/Data plane separation for Data over NAS small data solutionsWord-p. 245
6.48  Solution 48: NB-IoT idle mode inter-RAT mobility reusing EPS featuresWord-p. 247
6.49  Solution 49: Support for RDS with infrequent small data transmission solutions #1, 2, 3Word-p. 250
6.50  Solution 50: AF Notifications after DDN failureWord-p. 252
6.51  Solution 51: Core Network steering via CN type selection rules configuration/reconfigurationWord-p. 256
6.52  Solution 52: Inter-UE QoS differentiation based on retrieval of UE ContextUpWord-p. 258
7  EvaluationWord-p. 261
8  ConclusionsWord-p. 270
A  Change historyWord-p. 274

Up   Top