Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TR 23.743  Word version:  16.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions and abbreviations  3.1 Definitions  3.3 Abbreviations  4 Architectural Requirements and Assumptions 
...

 

1  Scope  p. 7

With the increase of the size of UE radio capabilities driven by additional bands supported by RAN specifications and UE support of significantly more band combinations, the size of the UE Radio Capabilities has and will significantly grow from Rel-15 onwards, an efficient approach to signal UE Radio Capability information is therefore needed.
This study item shall address two issues:
  • Optimizations of system procedures pertaining to the transfer UE Radio Capabilities related information to RAN.
  • Optimizations of system procedures related to transfer UE Radio Capabilities impacting the Core Network.
The overall goal is to study mechanisms to reduce the signalling over Uu, CN-RAN, CN-CN and RAN-RAN interfaces as well as the processing load in core and RAN (taking into account how frequently those message transfers and corresponding processing occurs) working in collaboration with RAN WGs for the related RAN interfaces and CT WG4 for the CN interfaces and NFs.
At minimum, the study shall consider the UE Radio Capabilities related aspects and any other optimisation which is deemed necessary in collaboration with RAN WGs. The study also considers scenarios where the UE radio capabilities change based on various events triggered in NAS (e.g. when certain services are not supported in one system/access and the UE wants to stay registered in another system/access, the UE may disable the radio capability for accessing the first system).
As part of the study and in coordination with other WGs especially RAN WGs it should be concluded whether to proceed with normative work.
Up

2  References  p. 7

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.502: " Procedures for the 5G System".
[3]
TS 23.501: " System Architecture for the 5G System; Stage 2".
[4]
TS 23.222: "Common API Framework for 3GPP Northbound APIs".
[5]
TS 38.331: "NR; Radio Resource Control (RRC); Protocol specification".
[6]
TS 33.501: "Security architecture and procedures for 5G System".
[7]
TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access".
[8]
TS 29.501: "5G System; Principles and Guidelines for Services Definition; Stage 3".
[9]
TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
Up

3  Definitions and abbreviations  p. 8

3.1  Definitions  p. 8

For the purposes of the present document, the terms and definitions given in TR 21.905 apply.

3.3  Abbreviations  p. 8

For the purposes of the present document, the abbreviations given in TR 21.905 apply.

4  Architectural Requirements and Assumptions  p. 8

4.1  Architectural Requirements  p. 8

The solution for the UE radio capability signaling optimizations shall take the following requirements into account:
  1. Solutions shall support UE Radio Access Capabilities > 65 536 bytes.
  2. Solutions shall provide fast, reliable, low processing complexity mechanisms for frequently used procedures (at least Service Request, RRC Connection Resume, X2&Xn handover, secondary gNB addition).
  3. The "UE Capability ID" should reflect the actual UE capabilities and not rely on parameters that may be faked, modified, or do not reflect the actual capabilities (e.g. IMEI and IMEISV might not fulfil this requirement)
  4. The solution must ensure that malicious implementations (outside of the operator's network) do not update the network with incorrect UE Radio Capabilities that corresponds to UE capability ID that are used by other UE's.
  5. Solution should be flexible enough to cope with additional UE capabilities that might be added by 3GPP in future releases.
  6. Solutions should not require any GTPv2 based interface (e.g. N26, S10) to carry an Information Element of greater than 50 000 octets.
  7. Solutions should not require any HTTP request or response based on TS 29.501 (e.g. for N14) to carry an Information Element of greater than 124 000 octets.
Up

4.2  Architectural Assumptions  p. 8

Up   Top   ToC