Content for TR 23.743 Word version: 16.0.0
5 Key Issues
6 Solutions
7 Evaluation
8 Conclusions
A Maximum supportable information element size
$ Change History
5 Key Issues p. 8
5.1 Key Issue #1: How are the UE Radio Capabilities identified? p. 8
5.1.1 Description p. 8
5.2 Key Issue #2: Where are the UE radio capabilities stored? p. 9
5.2.1 Description p. 9
5.3 Key Issue #3: How are the UE radio capabilities managed? p. 9
5.3.1 Description p. 9
6 Solutions p. 10
6.1 Solution #1: UE manufacturer-specific UE capability ID p. 10
6.1.1 Introduction p. 10
6.1.2 Functional Description p. 10
6.1.3 Procedures p. 10
6.1.4 Impacts on existing entities and interfaces p. 10
6.1.5 Evaluation p. 10
6.2 Solution #2: UE capability ID indicated in Access Stratum and N2 p. 10
6.2.1 Introduction p. 10
6.2.2 Functional Description p. 10
6.2.3 Procedures p. 11
6.2.4 Impacts on existing entities and interfaces p. 11
6.2.4.1 Registration procedure p. 12
6.2.4.2 UE Triggered Service Request p. 14
6.2.4.3 RAN retrieval of UE Radio Capability p. 15
6.2.5 Evaluation p. 15
6.3 Solution #3: Solution using Hash-based Identification of UE radio capabilities p. 15
6.3.1 Introduction p. 15
6.3.2 Functional Description p. 15
6.3.3 Procedures p. 16
6.3.4 Impacts on existing entities and interfaces p. 16
6.3.5 Evaluation p. 16
6.4 Solution #4: Provisioning of UE Radio Capability using UDR p. 17
6.4.1 Introduction p. 17
6.4.2 Functional Description p. 17
6.4.3 Procedures p. 17
6.4.3.1 Provisioning UE Radio Capability Information to UDR p. 17
6.4.3.2 Update and sharing of UE Radio Capability Information using UDR p. 18
6.4.4 Impacts on existing entities and interfaces p. 20
6.4.5 Evaluation p. 20
6.5 Solution #5: UE radio capability reporting and management using UE-capability-ID p. 20
6.5.1 Introduction p. 20
6.5.2 Functional Description p. 21
6.5.3 Procedures p. 21
6.5.4 Impacts on existing entities and interfaces p. 23
6.5.5 Evaluation p. 23
6.6 Solution #6: UE capability ID indicated in Access Stratum and N2 and local RAN Storage p. 23
6.6.1 Introduction p. 23
6.6.2 Functional Description p. 24
6.6.3 Procedures p. 24
6.6.4 Impacts on existing entities and interfaces p. 24
6.6.4.1 Registration procedure p. 25
6.6.4.2 UE Triggered Service Request p. 27
6.6.4.3 RAN retrieval of UE Radio Capability p. 28
6.6.4.4 Local (R)AN Storage of dictionary p. 28
6.6.5 Evaluation p. 29
6.7 Solution #7: Retrieve UE Radio Capability and store it in AMF per UE Capability ID p. 29
6.7.1 Introduction p. 29
6.7.2 Functional Description p. 29
6.7.3 Procedures p. 29
6.7.4 Impacts on existing entities and interfaces p. 31
6.7.5 Evaluation p. 32
6.8 Solution #8: Solution for identifying UE radio capabilities using PLMN-specific UE Capability ID p. 32
6.8.1 Introduction p. 32
6.8.2 Functional Description p. 33
6.8.3 Procedures p. 33
6.8.4 Impacts on existing entities and interfaces p. 33
6.8.5 Evaluation p. 33
6.9 Solution #9: UE Capability ID with delta set of UE Radio Capabilities p. 33
6.9.1 Introduction p. 33
6.9.2 Functional Description p. 34
6.9.3 Procedures p. 34
6.9.4 Impacts on existing entities and interfaces p. 34
6.9.5 Evaluation p. 34
6.10 Solution #10: Solution based on network-controlled capabilities sending and UE Capability ID allocation p. 35
6.10.1 Introduction p. 35
6.10.2 Functional Description p. 36
6.10.3 Procedures p. 36
6.10.4 Impacts on existing entities and interfaces p. 42
6.10.5 Evaluation p. 42
6.11 Solution #11: Standardized UE Capability ID p. 42
6.11.1 Introduction p. 42
6.11.2 Functional Description p. 42
6.11.3 Procedures p. 43
6.11.4 Impacts on existing interfaces and entities p. 43
6.12 Solution #12: Bulk Provisioning of UE Radio Capability from AF p. 43
6.12.1 Introduction p. 43
6.12.2 Functional Description p. 43
6.12.3 Procedures p. 43
6.12.3.1 Bulk provisioning of UE Radio Capability p. 43
6.12.3.2 On-demand UE Radio Capability Information Retrieval from AF p. 45
6.12.4 Impacts on existing entities and interfaces p. 46
6.12.5 Evaluation p. 46
6.13 Solution #13: "Self-learning" logic for progressive building of a dictionary p. 46
6.13.1 Introduction p. 46
6.13.2 Functional Description p. 46
6.13.3 Procedures p. 47
6.13.4 Impacts on existing interfaces and entities p. 47
6.13.5 Evaluation p. 47
6.14 Solution #14: RAN mapping of 'Capability Pointer' to Full UE capability with Backward Compatibility p. 47
6.14.1 Introduction p. 47
6.14.2 Functional Description p. 48
6.14.3 Procedures p. 48
6.14.4 Impacts on existing entities and interfaces p. 48
6.14.5 Evaluation p. 48
6.15 Solution #15: Network assigned capability ID with AMFI and Hash fields p. 49
6.15.1 Introduction p. 49
6.15.2 Functional Description p. 49
6.15.3 Procedures p. 49
6.15.4 Impacts on existing entities and interfaces p. 50
6.15.5 Evaluation p. 51
7 Evaluation p. 51
8 Conclusions p. 51
A Maximum supportable information element size p. 55
$ Change History p. 56
