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  TS 38.401  Word version:  18.4.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.1.4   6.1.5…   6.2…   7…   8…   8.2…   8.2.1.4…   8.2.2…   8.2.3…   8.2.4   8.2.5   8.3…   8.4…   8.4.4…   8.5…   8.9…   8.9.4…   8.9.6…   8.9.7…   8.10   8.11…   8.12…   8.13…   8.14…   8.15…   8.15.2…   8.16…   8.17…   8.17.3…   8.17.4   8.18…   8.19…   8.19.2   8.19.3   8.19.4…   8.21…   8.22…   8.23…   8.24…   9…   A… 
8.14 Self-optimisation  8.14.1 Overall procedures for MRO  8.14.1.1 Signalling of RLF information from gNB-CU to gNB-DU  8.14.1.2 Signalling of RACH information from gNB-CU to gNB-DU  8.14.1.3 Reporting of DL LBT failure information from gNB-DU to gNB-CU 
...

 

8.14  Self-optimisation |R16|  p. 100

8.14.1  Overall procedures for MRO  p. 100

The following clauses describe the overall procedures for MRO involving F1.

8.14.1.1  Signalling of RLF information from gNB-CU to gNB-DU  p. 101

The signalling flow for signalling of RLF information from gNB-CU to gNB-DU is shown in Figure 8.14.1.1-1, where the example where NG-RAN nodes exchange the RLF Report via the Xn: FAILURE INDICATION message has been considered.
Reproduction of 3GPP TS 38.401, Fig. 8.14.1.1-1: Example of signalling of RLF information from gNB-CU to gNB-DU in NG RAN
Figure 8.14.1.1-1: Example of signalling of RLF information from gNB-CU to gNB-DU in NG RAN
Up
Step 1.
A UE with a logged RLF Report connects to a cell in gNB2 and it signals the RLF Report to gNB2 by means of the RRC UE Information Request/Response procedures.
Step 2.
The gNB2 sends an Xn: Failure Indication to gNB1-CU where the UE may have previously been connected prior to the connection failure. This includes also the RLF Report.
Step 3.
The gNB1-CU sends the F1: Access and Mobility Indication message to the gNB1-DU, including the RLF Report.
It is also possible for the gNB-CU receiving the RLF Report from the UE to signal it directly to the gNB-DU by means of the F1: Access and Mobility Indication procedure.
Up

8.14.1.2  Signalling of RACH information from gNB-CU to gNB-DU |R17|  p. 101

The signalling flow for signalling of RACH information from gNB-CU to gNB-DU is shown in Figure 8.14.1.2-1, where the example where NG-RAN nodes exchange the RACH Report via the Xn: ACCESS AND MOBILITY INDICATION message has been considered.
Reproduction of 3GPP TS 38.401, Fig. 8.14.1.2-1: Example of signalling of RACH information from gNB-CU to gNB-DU in NG-RAN
Figure 8.14.1.2-1: Example of signalling of RACH information from gNB-CU to gNB-DU in NG-RAN
Up
Step 1.
A UE with a RACH Report concerning cells of gNB1 connects to a cell in gNB2 and it signals the RACH Report to gNB2 by means of the RRC UE Information Request/Response procedures.
Step 2.
GNB2 sends an Xn: Access and Mobility Indication message to gNB1-CU where the UE may have previously been connected. This includes also the RACH Report.
Step 3.
GNB1-CU sends the F1: Access and Mobility Indication message to the gNB1-DU, including the RACH Report.
It is also possible for the gNB-CU receiving the RACH Report from the UE to signal it directly to the gNB-DU by means of the F1: Access and Mobility Indication procedure.
Up

8.14.1.3  Reporting of DL LBT failure information from gNB-DU to gNB-CU |R18|  p. 102

For MRO analysis, a gNB-CU may request to a gNB-DU to collect and report DL LBT failure information related to mobility failures for a UE, as defined in TS 38.300, via the UE CONTEXT SETUP REQUEST message, or the UE CONTEXT MODIFICATION REQUEST message, or to trigger report via the UE CONTEXT RELEASE COMMAND. The gNB-DU may report the information to the gNB-CU via the DU-CU ACCESS AND MOBILITY INDICATION message.

Up   Top   ToC