Tech-invite   3GPPspecs   RFCs   Search in Tech-invite
Gen  21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Fs  NEs  RPs  SBIs  IDs  Ti+
Top   in Index   Prev   Next

TR 23.720 (SA2) ★
Study on Architecture enhancements
for Cellular Internet of Things

3GPP‑Page   full‑ToC
use "3GPP‑Page" to get the Word version
for a better overview, the Table of Contents (ToC) is reproduced
V13.0.0 (Wzip)  2016/03  94 p.
Rapporteur:  Mr. Jain, Puneet
The present document studies and evaluates the architecture enhancement to support ultra-low complexity, power constrained, and low data-rate 'Internet of Things' devices.

full Table of Contents for  TR 23.720  Word version:   13.0.0

 

Here   Top

 

1 Scope  2 References  3 Definitions and abbreviations  4 Architectural Considerations and Assumptions  5 Key Issues  6 Solutions  7 Overall Evaluation  8 Conclusions  A Change history 

 

1  Scope  Word-p. 8
2  References
3  Definitions and abbreviations  Word-p. 9
3.1  Definitions
3.2  Abbreviations
4  Architectural Considerations and Assumptions
4.1  Architectural Reference Model for Cellular IoT
4.2  Architectural assumptions for Cellular IoT system
4.3  Traffic Models for Cellular IoT  Word-p. 10
5  Key Issues
5.1  Key Issue 1 - Architecture Reference Model for Cellular IoT  Up
5.1.1  Description
5.1.2  Architectural Requirements  Word-p. 11
5.2  Key Issue 2 - Efficient support of infrequent small data transmission for Cellular IoT
5.2.1  Description
5.2.2  Architectural Requirements
5.3  Key Issue 3 - Efficient support of tracking devices using small data transmission for Cellular IoT
5.3.1  Description
5.3.2  Architectural Requirements
5.3.3  Traffic model for efficient support of tracking devices using small data transmission for Cellular IoT  Word-p. 12
5.3.3.1  Mobile Autonomous Reporting (MAR) periodic tracking reports  Up
5.4  Key Issue 4 - Support of efficient Paging area management for Cellular IoT
5.4.1  Description
5.4.2  Architectural Requirements
5.5  Key Issue 5: Selection of CIoT-EPC Dedicated Core Network  Word-p. 13
5.5.1  Description
5.5.2  Architectural Requirements
5.6  Key Issue 6 - Support of Non IP data
5.6.1  Description
5.7  Key Issue 7 - Support of SMS
5.7.1  Description  Up
5.8  Key Issue 8 - Control of small data misuse
5.8.1  Description
5.9  Key Issue 9 - Optimised Support of SMS transmission
5.9.1  Description
5.10  Key Issue 10 - Authorization of use of Coverage Enhancement  Word-p. 14
5.10.1  Description
5.10.2  Architectural Requirements
5.11  Key Issue 11 - Header compression enhancements for CIOT
5.11.1  Description
5.11.2  Architectural Requirements  Up
6  Solutions
6.1  Solution 1: Lightweight CN architecture for CIoT
6.1.1  Description
6.1.1.1  Introduction
6.1.1.2  Architecture basic principles  Word-p. 15
6.1.1.3  Functional Description of new entities  Word-p. 16
6.1.1.3.1  C-SGN
6.1.1.3.2  S1-lite  Word-p. 17
6.1.1.4  Protocol stack
6.1.2  Impacts on existing nodes and functionality  Word-p. 18
6.1.3  Solution Evaluation
6.2  Solution 2: Infrequent small data transmission using pre-established NAS security
6.2.1  Description
6.2.1.1  General
6.2.1.2  CIoT Attach Procedure  Word-p. 19
6.2.1.3  Procedure for MO Small Data Transfer (and response)  Word-p. 21
6.2.1.4  Procedure for MT Small Data Transfer  Word-p. 22
6.2.2  Impacts on existing nodes and functionality  Word-p. 23
6.2.3  Solution Evaluation  Word-p. 24
6.3  Solution 3: Connectionless small data transmission with immediate return to idle  Up
6.3.1  Description
6.3.1.1  General
6.3.1.2  MO small data
6.3.1.3  MT small data  Word-p. 27
6.3.2  Impacts on existing nodes and functionality  Word-p. 28
6.3.3  Solution Evaluation
6.4  Solution 4: Non-IP small data transmission via MTC-IWF
6.4.1  Description
6.4.1.1  General
6.4.1.2  Procedure  Word-p. 29
6.4.1.2.1  MO small data transmission
6.4.1.2.2  MT small data transmission  Word-p. 30
6.4.2  Impacts on existing nodes and functionality  Word-p. 31
6.4.2.1  CIoT UE
6.4.2.2  CIoT RAN
6.4.2.3  C-SGN
6.4.3  Solution Evaluation
6.4a  Solution 4a: non-IP small data transmission via SCEF  Word-p. 32
6.4a.1  Description
6.4a.1.1  General  Up
6.4a.1.2  Procedures
6.4a.1.2.1  MO small data transmission
6.4a.1.2.2  MT small data transmission
6.4a.2  Impacts on existing nodes and functionality
6.4a.3  Solution Evaluation  Word-p. 33
6.4b  Solution 4b: Non-IP small data transmission via SCEF with minimized load to HSS
6.4b.1  Description
6.4b.1.1  General
6.4b.1.2  Procedures
6.4b.1.2.1  Configuration of monitoring event: SDT  Up
6.4b.1.2.2  MO small data transmission  Word-p. 34
6.4b.2  Impacts on existing nodes and functionality  Word-p. 35
6.4b.3  Solution Evaluation
6.5  Solution 5: UE state transition signalling reduction  Word-p. 36
6.5.1  Description
6.5.1.1  General
6.5.1.2  RRC Suspend
6.5.1.3  RRC Resume  Word-p. 38
6.5.1.4  States description and transitions handling  Word-p. 40
6.5.1.5  Further aspects  Word-p. 41
6.5.2  Impacts on existing nodes and functionality
6.5.3  Solution Evaluation  Word-p. 42
6.6  Solution 6: User plane based solution with enhanced ECM-CONNECTED state
6.6.1  Description
6.6.1.1  Underlying assessment
6.6.1.2  Proposed architecture  Word-p. 43
6.6.1.3  Proposed High level Solution attributes
6.6.1.4  Expected RAN dependencies / impacts  Word-p. 44
6.6.1.5  Procedures
6.6.1.5.1  General  Up
6.6.1.5.2  Attach  Word-p. 45
6.6.1.5.3  ECM-IDLE to enhanced ECM-CONNECTED TRANSITION (eNB-m without valid retained context)  Word-p. 46
6.6.1.5.4  ECM-IDLE to enhanced ECM-CONNECTED TRANSITION (eNB-m with retained context)  Word-p. 47
6.6.1.5.5  RRC connection re-establishment in enhanced ECM-CONNECTED state in an eNB-m without valid UE context  Word-p. 48
6.6.1.5.6  RRC connection re-establishment in enhanced ECM-CONNECTED state in an eNB-m with valid UE context  Word-p. 49
6.6.1.5.7  Network initiated Temporary UE ID reallocation and Key refresh  Word-p. 50
6.6.2  Impacts on existing nodes and functionality
6.6.3  Solution Evaluation
6.7  Solution 7: Paging for static and dynamic coverage enhancement (CE) level  Word-p. 51
6.7.1  Description  Up
6.7.1.1  General
6.7.1.2  Design for Static Paging CE level (for scenario 1)
6.7.1.3  Design for Dynamic CE level (for scenario 2)  Word-p. 52
6.7.2  Impacts on existing nodes and functionality  Word-p. 53
6.7.3  Solution Evaluation
6.8  Solution 8: Cell based paging area update for efficient paging area management
6.8.1  Description
6.8.2  Impacts on existing nodes and functionality  Word-p. 54
6.8.3  Solution Evaluation  Word-p. 55
6.9  Solution 9: UE provided indication for selection of CIoT-EPC DCN or EPC DCN  Up
6.9.1  Description
6.10  Solution 10: Support for "non IP" PDN types  Word-p. 56
6.10.1  Description
6.10.1.1  General
6.10.1.2  Non IP PDN connection/PDP Context setup
6.10.2  Impacts on existing nodes and functionality  Word-p. 58
6.10.3  Solution Evaluation
6.11  Solution 11: SMS over PS without combined attach and default PDN connection
6.11.1  Description
6.11.1.1  General  Up
6.11.1.2  Attach with EMM context only
6.11.2  Impacts on existing nodes and functionality  Word-p. 59
6.11.3  Solution Evaluation
6.12  Solution 12: Solution on simplification of MM and SM procedures
6.12.1  Description
6.12.1.1  Simplification of MM and SM messages
6.12.1.2  Simplification of IEs in MM and SM messages  Word-p. 63
6.12.2  Impacts on existing nodes and functionality
6.12.3  Solution Evaluation
6.13  Solution 13: RRC FastConnect for Service Request  Up
6.13.0  Description
6.13.1  Procedures  Word-p. 64
6.13.1.1  Storing UE's AS Context in MME when UE goes idle
6.13.1.2  Service Request Procedure
6.13.2  Impacts on existing nodes and functionality  Word-p. 66
6.14  Solution 14: Setup of CIoT PDN connection with minimum NAS
6.14.1  Description
6.14.1.1  General
6.14.1.2  CIoT PDN connection/PDP Context setup
6.14.1.3  CIoT PDN connection/PDP Context setup for "EMM context only case"  Word-p. 68
6.14.1.4  Affected ESM & GSM messages
6.14.2  Impacts on existing nodes  Word-p. 69
6.14.3  Solution Evaluation
6.15  Solution 15: Support for "non IP" small data by UDP/IP encapsulation over SGi
6.15.1  Description
6.15.1.1  General
6.15.1.2  Non IP PDN connection setup  Word-p. 70
6.15.2  Impacts on existing nodes  Word-p. 71
6.15.3  Solution Evaluation
6.16  Solution 16: Optimised SMS over PS without combined attach and default PDN connection  Up
6.16.1  Description
6.16.1.1  General
6.16.1.2  Attach with MO SMS PDU  Word-p. 72
6.16.1.3  Attach with MT SMS PDU  Word-p. 73
6.16.1.4  Attach with MT SMS PDU - more messages to send  Word-p. 74
6.16.1.5  Attach with MO/MT SMS PDU  Word-p. 75
6.16.2  Impacts on existing nodes and functionality
6.16.3  Solution Evaluation
6.17  Solution 17: Optimized SMS relay for CIoT  Word-p. 76
6.17.1  Description  Up
6.17.1.1  Background
6.17.1.2  Optimized SMS relay  Word-p. 77
6.17.1.2.1  Optimized protocol stack
6.17.1.2.2  Optimized MT SMS  Word-p. 78
6.17.1.2.3  Optimized MO SMS
6.17.2  Impacts on existing nodes  Word-p. 79
6.17.3  Solution Evaluation
6.18  Solution 18: User plane based solution with AS information stored in RAN
6.18.1  Description
6.18.1.1  General  Up
6.18.1.2  Initial connection and AS context setup  Word-p. 80
6.18.1.3  RRC Suspend procedure  Word-p. 81
6.18.1.4  RRC Resume procedure  Word-p. 82
6.18.1.5  Resumption when AS information is not available in the eNB  Word-p. 85
6.18.1.6  MM procedure using user plane based solution  Word-p. 86
6.18.1.7  Further aspects
6.18.2  Impacts on existing nodes and functionality  Word-p. 87
6.18.3  Solution Evaluation
6.19  Solution 19: Header compression at C-SGN
6.19.1  Description  Up
6.19.1.1  General
6.19.1.2  Procedures  Word-p. 88
6.19.1.2.1  Procedure for initial context setup
6.19.1.2.2  Procedure for packet delivery with header compression  Word-p. 89
6.19.3  Impacts on existing nodes  Word-p. 91
6.19.4  Solution Evaluation  Word-p. 92
7  Overall Evaluation
8  Conclusions
A  Change history  Word-p. 94

Up   Top