Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TR 33.824  Word version:  17.0.0

Top   Top   None   None   Next
1…   4…   5…   6.3…   7…

 

1  Scopep. 7

The present document:
  • Describes potential security threats and vulnerabilities that are applicable to the enhanced IAB architecture specified in the TS 38.300, TS 38.331, TS 38.321 and TS 38.340.
  • Identifies potential security requirements for those potential security threats and vulnerabilities.
  • Proposes candidate solutions to ensure that the enhanced IAB architecture specified in the TS 38.300, TS 38.331, TS 38.321 and TS 38.340 does not introduce security vulnerabilities in the 5G system providing a secure connection for the UEs connecting to the NR through IAB node(s).
  • Concludes with the solutions that should be included in a future normative phase.
Up

2  Referencesp. 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]
TR 38.874: "NR; Study on integrated access and backhaul".
[3]
TS 38.300: "NR and NG-RAN Overall Description".
[4]
TS 38.401: "NG-RAN; Architecture description".
[5]
TS 33.501: "Security architecture and procedures for 5G system (Release 15)".
[6]
TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture".
[7]
TS 23.501: "System Architecture for the 5G System".
[8]
TS 38.331: "Radio Resource Control (RRC) protocol specification".
[9]
TS 38.321: "NR; Medium Access Control (MAC) protocol specification".
[10]
TS 38.340: "NR; Backhaul Adaptation Protocol (BAP) specification".
Up

3  Definitions of terms, symbols and abbreviationsp. 7

3.1  Termsp. 7

For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
IAB-donor:
A RAN node that has wired transport to the core network and provides wireless access to UEs and wireless backhauling functionality to IAB-nodes.
IAB-node:
A RAN node that provides wireless access to UEs and wirelessly backhauls the access traffic.
Access-node:
An IAB-node serving an access UE.
Parent-node:
An IAB-node that is serving other IAB-nodes
Child-node:
An IAB-node which is served by another Parent-node.
Access-link:
A link between an access UE and an IAB-node.
Backhaul-link:
A link between a Child-node and a Parent-node.
Up

3.2  Symbolsp. 8

Void.

3.3  Abbreviationsp. 8

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
BAP
Backhaul Adaptation Protocol
IAB
Integrated Access and Backhaul

Up   Top   ToC