Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.300  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   4.7…   5…   5.3…   5.4…   6…   6.2…   6.6…   7…   8…   9…   9.2.2…   9.2.2.5…   9.2.3…   9.2.3.2…   9.2.3.3…   9.2.4…   9.2.6…   9.3…   10…   11…   15…   15.5…   16…   16.2…   16.3…   16.4…   16.8…   16.9…   16.10…   16.12…   16.12.5…   16.12.6…   16.12.6.3   16.12.7   16.13…   16.14…   16.15…   16.18…   16.19…   16.21…   16.22   16.23…   17…   18…   19   20…   21…   22…   A…   B…   C…   G…

 

16.19  Support for Air to Ground Networks |R18|p. 248

16.19.1  Overviewp. 248

In Air-to-ground (ATG) network, an NG-RAN consisting of ground-based gNBs, which provide cell towers that send signals up to an aircraft's antenna(s) of onboard ATG terminal, with typical vertical altitude of around 10,000m and take-off/landing altitudes down to 3000m.
DC is not supported for ATG in this release of the specification.

16.19.2  Timing and Synchronizationp. 248

16.19.2.1  Scheduling and Timingp. 248

To accommodate the propagation delay in ATG, the timing relationship is enhanced by one cell-specific offset Koffset:
  • Koffset is a configured scheduling offset that needs to be larger or equal to the max RTT.
The scheduling offset Koffset is used to allow the UE sufficient processing time between a downlink reception and an uplink transmission, see TS 38.213.

16.19.2.2  Timing Advancep. 248

For the serving cell, the network broadcasts coarse gNB location information. The UE shall have valid GNSS position as well as gNB location before connecting to an ATG cell. To achieve synchronisation, before and during connection to an ATG cell, the UE shall compute the RTT between UE and the gNB based on the GNSS position and the gNB location parameters, and autonomously pre-compensate the TTA for the RTT between the UE and the gNB.
In connected mode, the UE shall be able to continuously update the Timing Advance.
The UE may be configured to report Timing Advance during Random Access procedures or in connected mode. For an RRC_CONNECTED UE, event-triggered reporting of the Timing Advance is supported.
Up

16.19.3  Mobilityp. 248

16.19.3.1  Mobility in RRC_IDLE and RRC_INACTIVEp. 248

The same principles as described in clause 9.2.1 apply to mobility in RRC_IDLE for ATG and the same principles as described in clause 9.2.2 apply to mobility in RRC_INACTIVE for ATG unless hereunder specified. The gNB reference location of the serving cell and neighbour cell(s) provided in SIB22 can be used for the UE to perform the idle/inactive measurement and mobility.
The UE can determine whether a network is for ATG connectivity implicitly by the existence of cellBarredATG in SIB1.
Up

16.19.3.2  Mobility in RRC_CONNECTEDp. 249

16.19.3.2.1  Handoverp. 249
The same principle as described in clause 9.2.3.2 applies to ATG unless hereunder specified.
16.19.3.2.2  Conditional Handoverp. 249
The same principle as described in clause 9.2.3.4 applies to ATG unless hereunder specified.
ATG supports the following additional trigger conditions upon which UE may execute CHO to a candidate cell, as defined in TS 38.331:
  • The RRM measurement-based event A4;
  • A location-based trigger condition.
A location-based trigger condition is always configured together with one of the measurement-based trigger conditions (CHO events A3/A4/A5) as defined in TS 38.331.
Up

16.19.3.3  Measurements |R19|p. 249

A UE in RRC_CONNECTED can skip the neighbour Secondary Cell measurement based on network configuration.

16.20  Support of AI/ML for NG-RAN |R18|p. 249

16.20.1  Generalp. 249

Support of AI/ML for NG-RAN, as a RAN function, is used to facilitate Artificial Intelligence (AI) and Machine Learning (ML) techniques in NG-RAN.
The objective of AI/ML for NG-RAN is to improve network performance and user experience, through analysing the data collected and autonomously processed by the NG-RAN, which can yield further insights, e.g., for Network Energy Saving, Load Balancing, Mobility Optimization, Network Slicing, CCO.

16.20.2  Principlesp. 249

Support of AI/ML for NG-RAN requires inputs from neighbour NG-RAN nodes (e.g., predicted information, feedback information, measurements) and/or UEs (e.g., measurement results).
Signalling procedures used for the exchange of information to support AI/ML for NG-RAN, are use case and data type agnostic, which means that the intended usage (e.g., input, output, feedback) of the data exchanged via these procedures is not indicated.
AI/ML algorithms and models are out of 3GPP scope. Model-specific performance information, e.g. model performance indicators specified in clause 6 of TS 28.105, is not exchanged over NG-RAN interfaces in TS 38.401.
Support of AI/ML for NG-RAN does not apply to ng-eNB.
For the deployment of AI/ML for NG-RAN the following scenarios may be supported:
  • AI/ML Model Training is located in the OAM and AI/ML Model Inference is located in the NG-RAN node;
  • AI/ML Model Training and AI/ML Model Inference are both located in the NG-RAN node.
AI/ML Model Training follows the definition of the "ML model training" as specified in clause 3.1 of TS 28.105. An AI/ML Model needs to be trained, validated and tested before deployment for AI/ML Model Inference.
AI/ML Model Inference follows the definition of the "AI/ML inference" as defined in clause 3.1 of TS 28.105.
Up

16.20.3  Data Collection and Reportingp. 250

The following information can be configured to be reported by an NG-RAN node:
  • Predicted resource status information, including predicted radio resource status per slice;
  • UE performance feedback, including per-slice UE performance;
  • Measured UE trajectory;
  • Energy Cost (EC);
  • Predicted slice available capacity.
The collection and reporting of the above information are configured through the Data Collection Reporting Initiation procedure, while the actual reporting is performed through the Data Collection Reporting procedure.
The collection of measured UE trajectory and UE performance feedback is triggered at successful Handover.
Cell-based UE trajectory prediction, which can be used, e.g., for the Mobility Optimization use case, is transferred to the target NG-RAN node via the Handover Preparation procedure to provide information for, e.g., subsequent mobility decisions. Cell-based UE trajectory prediction is limited to the first-hop target NG-RAN node.
An NG-RAN node may derive predicted CCO issues and the corresponding future coverage states for its affected cells and beams. The NG-RAN node may notify its neighbour NG-RAN nodes, via the NG-RAN Node Configuration Update procedure, about the future coverage state changes together with modification cause and time information. The NG-RAN node may also notify its neighbour NG-RAN nodes that previously notified coverage state changes together with the corresponding modification cause have been cancelled.
At any given point in time, for a list of predicted affected cells and beams, there is only one predicted CCO issue generated by a gNB.
Up

16.20.4  OAM Requirementsp. 250

OAM configures the following for EC reporting:
  • The minimum and maximum energy consumption values corresponding to the minimum and maximum EC index values respectively, based on an implementation-specific mapping rule, which is unified within a defined area; and
  • The recommended time interval within which an NG-RAN node selects an implementation-specific time window for averaging of the measurements of the NG-RAN node's consumed energy.
OAM further configures management-based MDT for continuous MDT towards the NG-RAN. OAM provides specific information to the NG-RAN for the NG-RAN to identify continuous MDT.
Up

Up   Top   ToC