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.700-58  Word version:  18.1.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions of terms and abbreviations  4 Architectural Assumptions and Principles 
...

 

1  Scope  p. 7

This study item shall address the following system enablers for 5GS and EPS to support additional scenarios and requirements for UAV (Uncrewed Aerial Vehicles) and UAM (Urban Air Mobility) by identifying how and whether existing mechanisms can be re-used, and identifying architectural and functional modifications required:
  • a mechanism to transport Broadcast Remote Identification and C2 communications via the 3GPP system;
  • a mechanism to support aviation applications such as Detect And Avoid (DAA).

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.501: "System architecture for the 5G System (5GS)".
[3]
TS 23.502: "Procedures for the 5G System (5GS)".
[4]
TS 22.125: "Uncrewed Aerial System (UAS) support in 3GPP".
[5]
TS 23.256: "Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking".
[6]
DEPARTMENT OF TRANSPORTATION Federal Aviation Administration 14 CFR Parts 1, 11, 47, 48, 89, 91, and 107 [Docket No.: FAA-2019-1100; Amdt. Nos. 1-75, 11-63, 47-31, 48-3, 89-1, 91-361, and 107-7] RIN 2120-AL31 Remote Identification of Unmanned Aircraft.
[7]
EASA NPA 2021-14: "Notice of Proposed Amendment 2021-14".
[8]
TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[9]
TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[10]
TR 23.754: "Study on supporting Unmanned Aerial Systems (UAS) connectivity, Identification and tracking".
[11]
TS 23.273: "5G System (5GS) Location Services (LCS)".
[12]
ASTM F3411.19: "Standard Specification for Remote ID and Tracking".
[13]
ASD-STAN prEN 4709-002:2022-03: "Aerospace series - Unmanned Aircraft Systems - Part 002: Direct Remote Identification".
[14]
TS 23.303: "Proximity-based services (ProSe)".
[15]
TS 23.247: "Architectural enhancements for 5G multicast-broadcast services".
[16]
TS 33.536: "Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services".
[17]
TS 23.285: "Architecture enhancements for V2X services".
[18]
TS 23.700-33: "Study on System enhancement for Proximity based Services (ProSe) in the 5G System (5GS); Phase 2".
[19]
TR 36.885: "Study on LTE-based V2X Services".
[20]
TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[21]
TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[22]
TR 37.985: "Overall description of Radio Access Network (RAN) aspects for Vehicle-to-everything (V2X) based on LTE and NR".
Up

3  Definitions of terms and abbreviations  p. 8

3.1  Terms  p. 8

For the purposes of the present document, the terms given in TR 21.905, TS 23.256 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 or TS 23.256.
U2X communication:
A communication to support UAV-to-Everything (U2X) services leveraging Uu and / or PC5 reference points. U2X services are realized by various types of U2X applications, i.e. UAV-to-UAV (U2U) and UAV-to-Network (U2N).
U2X message
A dedicated messaging type of U2X service, for example Broadcast Remote ID messages.
U2X service type:
A type of U2X service, which is identified by e.g. ITS-AID (ITS Application Identifier), PSID (Provider Service Identifier) or AID (Application Identifier).
Up

3.2  Abbreviations  p. 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.
AAM
Area Airspace Manager
BRID
Broadcast Remote Identification
C2
Command and Control
DAA
Detect And Avoid
RID
Remote Identification
TPAE
Third Party Authorized Entity
UAS
Uncrewed Aerial System
UAV
Uncrewed Aerial Vehicle
U2X
UAV to everything
U2XP
U2X Policy
Up

4  Architectural Assumptions and Principles  p. 8

4.1  Architectural Requirements  p. 8

  • When applicable, existing UAV authentication and authorization procedures specified in TS 23.256 should be reused as much as possible for solutions.
  • When applicable, solutions that involve UAV to UAV communications should apply to UAVs of different PLMNs.
  • Solutions should consider both UAVs in coverage and UAVs out of coverage, though different solutions may apply to the two cases.
  • When applicable, solutions should be backward compatible with mechanisms specified in TS 23.256.
Up

4.2  Architectural Assumptions  p. 9

The following architectural assumptions apply:
  • Solutions for transport of broadcast remote identification shall support existing regulations for remote identification, including FAA regulations [6] and U-Space regulations EASA NPA 2021-14 [7].
  • For solutions using PC5, the use of relay communications is not considered in this study.
  • A UAV shall obtain authorization from 3GPP system and USS to perform direct C2 communication as defined in TS 22.125.
Up

Up   Top   ToC