TS 24.501 v20.0.0 · CT1 — the group that writes what your phone says
The whole document
1340 clauses in the order they appear. The bar shows how much text each part holds. Open one to see what is inside it and which chapter teaches it.
3 Definitions and abbreviations 7,398 words · 2 of 3 clauses taught
4 General 69,642 words · 5 of 136 clauses taught
- 4.1 Overview 1. What CT1 is, and the three names it answers to2. Stage 3 — the difference between a plan and a protocol4. TS 24.501 — two protocols living in one document5. Finding your way around TS 24.50110. Who CT1 writes to, and what the letters count12. The neighbours — and how little the record says about them
- 4.2 Coordination between the protocols for 5GS mobility management and 5GS session management 4. TS 24.501 — two protocols living in one document
- 4.2A Control of UE access technology utilization by 5GS
- 4.3 UE domain selection
- 4.4 NAS security
- 4.5 Unified access control
- 4.6 Network slicing
- 4.7 NAS over non-3GPP access
- 4.8 Interworking with E-UTRAN connected to EPC
- 4.9 Disabling and re-enabling of UE's N1 mode capability
- 4.10 Interworking with ePDG connected to EPC
- 4.11 UE configuration parameter updates
- 4.12 Access traffic steering, switching and splitting (ATSSS)
- 4.13 Support of NAS signalling using wireline access network
- 4.14 Non-public network (NPN)
- 4.15 Time synchronization and time sensitive communication
- 4.16 UE radio capability signalling optimisation
- 4.17 5GS mobility management in NB-N1 mode
- 4.18 5GS session management in NB-N1 mode
- 4.19 5GS mobility management in WB-N1 mode for IoT
- 4.20 5GS session management in WB-N1 mode for IoT
- 4.21 Authentication and key management for applications (AKMA)
- 4.22 Uncrewed aerial vehicle identification, authentication, authorization and operational restrictions
- 4.23 NAS over Non-Terrestrial Network
- 4.24 Minimization of service interruption 11. The work items that fill a CT1 year
- 4.25 Support of MUSIM features
- 4.26 Support for Personal IoT Network service
- 4.27 Mobile base station relay support
- 4.28 NAS-specific aspects of mobile gNB with wireless access backhauling (MWAB)
- 4.29 Support of indirect network sharing
- 4.30 QoS differentiation of traffic for non-3GPP device identifier
5 Elementary procedures for 5GS mobility management 258,044 words · 14 of 236 clauses taught
6 Elementary procedures for 5GS session management 126,272 words · 13 of 137 clauses taught
7 Handling of unknown, unforeseen, and erroneous protocol data 2,905 words · 9 of 28 clauses taught
- 7.1 General 5. Finding your way around TS 24.5017. What a NAS message looks like on the wire
- 7.2 Message too short or too long
- 7.3 Unknown or unforeseen procedure transaction identity or PDU Session identity
- 7.4 Unknown or unforeseen message type 7. What a NAS message looks like on the wire
- 7.5 Non-semantical mandatory information element errors
- 7.6 Unknown and unforeseen IEs in the non-imperative message part
- 7.7 Non-imperative message part errors 7. What a NAS message looks like on the wire
- 7.8 Messages with semantically incorrect contents 7. What a NAS message looks like on the wire
8 Message functional definitions and contents 21,782 words · 3 of 505 clauses taught
9 General message format and information elements coding 76,529 words · 11 of 215 clauses taught
- 9.1 Overview
- 9.2 Extended protocol discriminator 7. What a NAS message looks like on the wire
- 9.3 Security header type 7. What a NAS message looks like on the wire
- 9.4 PDU session identity 7. What a NAS message looks like on the wire
- 9.5 Spare half octet 7. What a NAS message looks like on the wire
- 9.6 Procedure transaction identity 7. What a NAS message looks like on the wire
- 9.7 Message type 2. Stage 3 — the difference between a plan and a protocol7. What a NAS message looks like on the wire
- 9.8 Message authentication code 7. What a NAS message looks like on the wire
- 9.9 Plain 5GS NAS message 7. What a NAS message looks like on the wire
- 9.10 Sequence number 7. What a NAS message looks like on the wire
- 9.11 Other information elements
- 9.12 3GPP specific coding information defined within present document
10 List of system parameters 4,431 words · 2 of 5 clauses taught
Annex A Cause values for 5GS mobility management 2,389 words · 5 of 5 clauses taught
- A.1 Causes related to UE identification 5. Finding your way around TS 24.5017. What a NAS message looks like on the wire
- A.2 Cause related to subscription options 5. Finding your way around TS 24.501
- A.3 Causes related to PLMN or SNPN specific network failures and congestion/authentication failures 5. Finding your way around TS 24.501
- A.4 Causes related to invalid messages 5. Finding your way around TS 24.501
Annex B Cause values for 5GS session management 1,687 words · 3 of 3 clauses taught
Annex C Storage of 5GMM information 3,836 words · 3 of 3 clauses taught
Annex D UE policy delivery service 9,635 words · 58 of 58 clauses taught
- D.1 General 5. Finding your way around TS 24.501
- D.2 Procedures 5. Finding your way around TS 24.501
- D.3 UE policy re-assembly at the UE 5. Finding your way around TS 24.501
- D.4 Void 5. Finding your way around TS 24.501
- D.5 Message functional definition and contents 5. Finding your way around TS 24.501
- D.6 Information elements coding 5. Finding your way around TS 24.501
- D.7 Timers of UE policy delivery service 5. Finding your way around TS 24.501
- D.8 Handling of unknown, unforeseen, and erroneous UPDS data 5. Finding your way around TS 24.501