hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.23.1 Configuration for EN-DC | Table 6.23.1-1: DC band combination of LTE 2DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_19A-42A_n77A-n257A
DC_19A-42A_n77A-n257G
DC_19A-42A_n77A-n257H
DC_19A-42A_n77A-n257I
DC_19A-42C_n77A-n257A
DC_19A-42C_n77A-n257G
DC_19A-42C_n77A-n257H
DC_19A-42C_n77A-n257I
DC_19A_n77A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.24 DC_19-42_n78-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.24.1 Configuration for EN-DC | Table 6.24.1-1: DC band combination of LTE 2DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_19A-42A_n78A-n257A
DC_19A-42A_n78A-n257G
DC_19A-42A_n78A-n257H
DC_19A-42A_n78A-n257I
DC_19A-42C_n78A-n257A
DC_19A-42C_n78A-n257G
DC_19A-42C_n78A-n257H
DC_19A-42C_n78A-n257I
DC_19A_n78A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.25 DC_19-42_n79-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.25.1 Configuration for EN-DC | Table 6.25.1-1: DC band combination of LTE 2DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_19A-42A_n79A-n257A
DC_19A-42A_n79A-n257G
DC_19A-42A_n79A-n257H
DC_19A-42A_n79A-n257I
DC_19A-42C_n79A-n257A
DC_19A-42C_n79A-n257G
DC_19A-42C_n79A-n257H
DC_19A-42C_n79A-n257I
DC_19A_n79A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.26 DC_21-42_n77-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.26.1 Configuration for EN-DC | Table 6.26.1-1: DC band combination of LTE 2DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_21A-42A_n77A-n257A
DC_21A-42A_n77A-n257G
DC_21A-42A_n77A-n257H
DC_21A-42A_n77A-n257I
DC_21A-42C_n77A-n257A
DC_21A-42C_n77A-n257G
DC_21A-42C_n77A-n257H
DC_21A-42C_n77A-n257I
DC_21A_n77A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.27 DC_21-42_n78-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.27.1 Configuration for EN-DC | Table 6.27.1-1: DC band combination of LTE 2DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_21A-42A_n78A-n257A
DC_21A-42A_n78A-n257G
DC_21A-42A_n78A-n257H
DC_21A-42A_n78A-n257I
DC_21A-42C_n78A-n257A
DC_21A-42C_n78A-n257G
DC_21A-42C_n78A-n257H
DC_21A-42C_n78A-n257I
DC_21A_n78A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.28 DC_21-42_n79-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 6.28.1 Configuration for EN-DC | Table 6.28.1-1: DC band combination of LTE 2DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_21A-42A_n79A-n257A
DC_21A-42A_n79A-n257G
DC_21A-42A_n79A-n257H
DC_21A-42A_n79A-n257I
DC_21A-42C_n79A-n257A
DC_21A-42C_n79A-n257G
DC_21A-42C_n79A-n257H
DC_21A-42C_n79A-n257I
DC_21A_n79A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7 EN-DC of LTE inter-band CA (3DL/1UL) bands and NR FR1 1DL/1UL band and NR FR2 1DL/1UL band: Specific Band Combination Part | <Editor’s note: The requirements for specific band combinations shall be described according to the same mannter as specified in TS38.101-3.> |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.0 DC_1-2-3_n4-n257 | <Editor’s note: This section is the entry example.> |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.0.1 Configuration for EN-DC | Table 7.x.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-2A-3A_n4A-n257A
DC_1A-2A-3A_n4A-n257G
DC_1A-2A-3A_n4A-n257H
DC_1A-2A-3A_n4A-n257I
DC_1A_n4A-n257A
DC_1A_n4A-n257G
DC_1A_n4A-n257H
DC_1A_n4A-n257I
DC_2A_n4A-n257A
DC_2A_n4A-n257G
DC_2A... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.1 DC_1-3-21_n77-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.1.1 Configuration for EN-DC | Table 7.1.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-3A-21A_n77A-n257A
DC_1A-3A-21A_n77A-n257G
DC_1A-3A-21A_n77A-n257H
DC_1A-3A-21A_n77A-n257I
DC_1A_n77A-n257A
DC_1A_n77A-n257G
DC_1A_n77A-n257H
DC_1A_n77A-n257I
DC_3A_n77A-n257A
DC_3A_n7... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.2 DC_1-3-21_n78-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.2.1 Configuration for EN-DC | Table 7.2.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-3A-21A_n78A-n257A
DC_1A-3A-21A_n78A-n257G
DC_1A-3A-21A_n78A-n257H
DC_1A-3A-21A_n78A-n257I
DC_1A_n78A-n257A
DC_1A_n78A-n257G
DC_1A_n78A-n257H
DC_1A_n78A-n257I
DC_3A_n78A-n257A
DC_3A_n7... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.3 DC_1-3-21_n79-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.3.1 Configuration for EN-DC | Table 7.3.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-3A-21A_n79A-n257A
DC_1A-3A-21A_n79A-n257G
DC_1A-3A-21A_n79A-n257H
DC_1A-3A-21A_n79A-n257I
DC_1A_n79A-n257A
DC_1A_n79A-n257G
DC_1A_n79A-n257H
DC_1A_n79A-n257I
DC_3A_n79A-n257A
DC_3A_n7... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.4 DC_1-19-42_n79-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.4.1 Configuration for EN-DC | Table 7.4.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-19A-42A_n79A-n257A
DC_1A-19A-42A_n79A-n257G
DC_1A-19A-42A_n79A-n257H
DC_1A-19A-42A_n79A-n257I
DC_1A-19A-42C_n79A-n257A
DC_1A-19A-42C_n79A-n257G
DC_1A-19A-42C_n79A-n257H
DC_1A-19A-42C_... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.5 DC_19-21-42_n77-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.5.1 Configuration for EN-DC | Table 7.5.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_19A-21A-42A_n77A-n257A
DC_19A-21A-42A_n77A-n257G
DC_19A-21A-42A_n77A-n257H
DC_19A-21A-42A_n77A-n257I
DC_19A-21A-42C_n77A-n257A
DC_19A-21A-42C_n77A-n257G
DC_19A-21A-42C_n77A-n257H
DC_19A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.6 DC_19-21-42_n78-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.6.1 Configuration for EN-DC | Table 7.6.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_19A-21A-42A_n78A-n257A
DC_19A-21A-42A_n78A-n257G
DC_19A-21A-42A_n78A-n257H
DC_19A-21A-42A_n78A-n257I
DC_19A-21A-42C_n78A-n257A
DC_19A-21A-42C_n78A-n257G
DC_19A-21A-42C_n78A-n257H
DC_19A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.7 DC_19-21-42_n79-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.7.1 Configuration for EN-DC | Table 7.7.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_19A-21A-42A_n79A-n257A
DC_19A-21A-42A_n79A-n257G
DC_19A-21A-42A_n79A-n257H
DC_19A-21A-42A_n79A-n257I
DC_19A-21A-42C_n79A-n257A
DC_19A-21A-42C_n79A-n257G
DC_19A-21A-42C_n79A-n257H
DC_19A-... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.8 DC_1-21-42_n77-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.8.1 Configuration for EN-DC | Table 7.8.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-21A-42A_n77A-n257A
DC_1A-21A-42A_n77A-n257G
DC_1A-21A-42A_n77A-n257H
DC_1A-21A-42A_n77A-n257I
DC_1A-21A-42C_n77A-n257A
DC_1A-21A-42C_n77A-n257G
DC_1A-21A-42C_n77A-n257H
DC_1A-21A-42C_... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.9 DC_1-21-42_n78-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.9.1 Configuration for EN-DC | Table 7.9.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-21A-42A_n78A-n257A
DC_1A-21A-42A_n78A-n257G
DC_1A-21A-42A_n78A-n257H
DC_1A-21A-42A_n78A-n257I
DC_1A-21A-42C_n78A-n257A
DC_1A-21A-42C_n78A-n257G
DC_1A-21A-42C_n78A-n257H
DC_1A-21A-42C_... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.10 DC_1-21-42_n79-n257 | |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 7.10.1 Configuration for EN-DC | Table 7.10.1-1: DC band combination of LTE 3DL/1UL + NR FR1 1DL/1UL + NR FR2 1DL/1UL
EN-DC configuration
Uplink EN-DC configuration
DC_1A-21A-42A_n79A-n257A
DC_1A-21A-42A_n79A-n257G
DC_1A-21A-42A_n79A-n257H
DC_1A-21A-42A_n79A-n257I
DC_1A-21A-42C_n79A-n257A
DC_1A-21A-42C_n79A-n257G
DC_1A-21A-42C_n79A-n257H
DC_1A-21A-42C... |
c23648a17e0e0c0f402d657615f5db9a | 37.716-41-22 | 8 EN-DC of LTE inter-band CA (4DL/1UL) bands and NR FR1 1DL/1UL band and NR FR2 1DL/1UL band: Specific Band Combination Part | <Editor’s note: The requirements for specific band combinations shall be described according to the same mannter as specified in TS38.101-3.>
8.x DC_1-2-3-4_n5-n257
<Editor’s note: This section is the entry example.>
8.x.1 Configuration for EN-DC
Table 8.x.1-1: DC band combination of LTE 4DL/1UL + NR FR1 1DL/1UL + NR F... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 1 Scope | The present document provides descriptions of use cases and solutions with regard to RAN-centric data collection and utilization and analysis of these solutions. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 2 References | 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.
- Fo... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 3 Definitions of terms, symbols and abbreviations | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 3.1 Terms | For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1]. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 3.2 Symbols | Void. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AAS Active Antenna System
ANR Automatic Neighbour Relationship
BF... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 4 General | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5 Use cases and solutions for RAN-centric data collection and utilization | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.1 Capacity and Coverage Optimization | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.1.1 Use case description | Coverage and Capacity Optimization (CCO) is one of the typical operational tasks to optimize the radio access network (RAN). CCO has been identified as a key use case for SON since LTE, which aims to provide the required capacity in the targeted coverage areas and to minimize the interference and maintain an acceptable... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.1.2 Solution description | Solutions for CCO are based on the capability to adapt cell/beam coverage to achieve better system performance. Solutions can be generalized as made of two components:
- Detection of coverage and/or capacity issue
- Action to resolve the issue
Generally, there are two types of network coverage adjustment, i.e. long ter... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.1.2.1 Detection of Coverage and Capacity Issues | To detect coverage and capacity issues not only information about failure cases are needed but also information about successful events. For example, a sub-optimal coverage planning between neighbour cells may not always imply that UEs handing over between these cells are subject to RLFs. Nevertheless, the handover may... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.1.2.2 Possible actions to resolve detected issues | Solution 1:
Once the CCO function has a good understanding of the coverage and capacity status of the cells/beams at its hosting RAN node and possibly at neighbouring nodes, the CCO function can trigger a corrective action to address such issue.
For the disaggregated gNB scenario, the gNB-CU should provide relevant inf... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.1.3 Conclusion | RAN3 has concluded the analysis of the CCO function and agreed that solutions in line with the description in the above clause can be moved to normative phase. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.2 PCI selection | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.2.1 Use case description | Physical Cell Identifier (PCI) is assigned to each cell to help UE distinguish wireless signals of different cells. The selection of PCI is one of the first use cases that have been introduced in SON, in order to ensure that PCI collision does not happen or are minimized. In LTE, the eNB base the selection of its PCI e... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.2.2 Solution description | The NG-RAN node (non-split) bases the selection of its PCI either on a centralized or distributed PCI assignment algorithm.
In the split gNB architecture, there are several options for the PCI selection. A non-exhaustive list of possible option is reported below. Details about which option will be selected for normativ... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.2.3 Conclusion | The following features and solutions are recommended to be specified for NR PCI selection function as part of a Rel.16 RAN-centric DCU WI:
- Centralized PCI assignment and distributed PCI assignment for non-split gNB and split gNB.
- The solution down-selection for split gNB case will be decided in normative phase. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3 Mobility optimization | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.1 Use case description | In LTE, Mobility Robustness Optimization (MRO) aims at detecting and enabling correction of following problems, which will deteriorate user experience and waste network resources:
- Connection failure due to intra-LTE or inter-RAT mobility;
- Unnecessary HO to another RAT (too early IRAT HO with no radio link failure);... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.2 Solution description | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.2.1 Connection failure due to mobility | 1) Connection failure due to intra-system mobility
Failure event definition:
- [Intra-system Too Late Handover] An RLF occurs after the UE has stayed for a long period of time in the cell; the UE attempts to re-establish the radio link connection in a different cell.
- [Intra-system Too Early Handover] An RLF occurs sh... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.2.2 Inter-system Unnecessary HO | Failure events definition
UE is handed over from NG-RAN to other system (e.g. UTRAN) even though quality of the NG-RAN coverage was sufficient for the service used by the UE. The handover may therefore be considered as unnecessary HO to another system (too early Inter-system HO without connection failure)
Detection mec... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.2.3 Inter-system HO ping-pong | Failure events definition
A UE is handed over from a cell in a source system (e.g. NG-RAN) to a cell in a target system different from the source system (e.g. E-UTRAN), then within a predefined limited time the UE is handed over back to a cell in the source system, while the coverage of the source system was sufficient... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.2.4 SN change failure in case of EN-DC, NGEN-DC, NE-DC and NR-DC | In case of MR-DC, e.g. EN-DC, NGEN-DC, NE-DC and NR-DC, the SN can be configured with SRB3, and can trigger the SN change autonomously. According to the specification TS 37.340 [3], the SCG failure includes multiple causes of SCG RLF, SN change failure, SCG configuration failure, SCG RRC integrity check failure, etc. i... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.2.5 Successful HO Report | The MRO function in NR could be enhanced to provide a more robust mobility via reporting failure events observed during successful handovers. A solution to this problem is to configure the UE to compile a report associated to a successful handover comprising a set of measurements collected during the handover phase, i.... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.3.3 Conclusion | RAN3 has studied the mobility optimization function and has converged to the solution principles and description outlined above. RAN3 has concluded its study on mobility optimization and determined that the mobility optimization feature can be moved to normative phase. The details of the solution parts involving UE beh... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.4 Load Sharing and Load Balancing Optimization | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.4.1 Use case description | The objective of load sharing and load balancing is to distribute cell load evenly among cells or to transfer part of the traffic from congested cell, or to offload users from one cell or carrier or RAT to achieve network energy saving, This can be done by means of optimization of cell reselection/handover parameters a... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.4.2 Solution description | There are possible solutions that enable load management over X2, Xn, F1 and E1 interfaces. On X2 and Xn, the reported information should contain at least cell level load (e.g. resource utilization). Likewise, similar information is required from the gNB-DU to gNB-CU over F1 in case of disaggregated architecture. For E... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.4.3 Conclusion | Load sharing and load balancing functions over X2, Xn, F1 and E1 interfaces should be specified in Release 16 normative phase. At least the following load related information should be specified. Whether the reporting mechanism supports both periodic and event-triggered procedures is for further decision during normati... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.5 RACH Optimization | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.5.1 Use case description | The RACH configuration has critical impacts on user experience and overall network performance. The RACH collision probability, and therefore access setup delays, data resuming delays from the UL unsynchronized state, handover delays, transition delays from RRC_INACTIVE, and beam failure recovery delays are all affecte... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.5.2 Solution description | The setting of RACH parameters that can be optimized are:
- RACH configuration (resource unit allocation);
- RACH preamble split (among dedicated, group A, group B);
- RACH backoff parameter value;
- RACH transmission power control parameters.
As a minimum, RACH optimization is realized by UE providing RACH related inf... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.5.3 Conclusion | The following features and solutions are recommended to be specified for NR RACH optimization as part of a potential Rel.16 RAN-centric DCU WI:
- RACH optimization is supported by UE reported information and by PRACH parameters exchange over Xn between gNBs and F1 between gNB-CU and gNB-DU.
- UE RACH report (contents n... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.6 Energy Saving | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.6.1 Use case description | Mobile operators are increasingly aiming at decreasing power consumption in mobile networks to lower their operational expense (OPEX) with energy saving solutions. With the foreseen deployment of more number of network elements in NR, e.g. small base stations with massive MIMO in high-band, energy saving becomes even m... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.6.2 Solution description | There is no further solution needed for intra-system energy saving.
1) Inter-RAT Inter-system energy saving solution:
The solution builds upon the possibility for the NG-RAN node owning a capacity booster cell to autonomously decide to switch-off such cell to dormant state and possibility for the eNB node owning non-ca... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.6.3 Conclusion | Intra-system energy saving was completed in R15.
The following features and solutions are recommended to be specified for Energy Saving as part of a Rel.16 RAN-centric DCU WI:
- Inter-RAT Inter-system energy saving solution
- Solution for calculation of data volumes for the calculation of energy efficiency for a base s... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7 Minimization of Drive Test (MDT) Use Cases | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.1 General | The general principles and requirements guiding the definition of functions for Minimization of drive tests are the following:
MDT mode
There are two modes for the MDT measurements: Logged MDT and Immediate MDT. There are also cases of measurement collection not specified as either immediate or logged MDT, such as Acce... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.2 Use case description | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.2.1 Use case: Coverage Optimization via MDT | The MDT data reported from UEs and the RAN may be used to monitor and detect coverage problems in the network. Coverage optimization use cases in LTE are the baseline for NR.
Some examples of use cases of coverage problem monitoring and detection are described in the following:
- Coverage hole
- Weak coverage
- Pilot P... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.2.2 Use case: QoS verification via MDT | The MDT data reported from UEs and the RAN may be used to verify Quality of Service, assess user experience from RAN perspective, and to assist network capacity extension. QoS verification use cases in LTE are the baseline for NR.
Use cases are described in the following:
- Traffic Location: MDT functionality to obtain... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.2.3 Use case: Indoor MDT improvement | The WLAN/Bluetooth measurement can be collected to improve positioning accuracy for indoor MDT. WLAN/Bluetooth measurement use cases of LTE are the baseline of NR. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.2.4 Use case: Sensor data collection | In addition to location and time information, UE orientation in a global coordinate system can be collected in MDT if the information is available. No additional measurement is required. Further details are in clause 5.7.3.2. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3 Solution description | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.1 Measurements | The following measurements should be supported for MDT performance
- DL signal quantities measurement results for the serving cell and for intra-frequency/Inter-frequency/inter-RAT neighbour cells (logged MDT and immediate MDT)
- PHR (immediate MDT)
- Received Interference Power measurement (immediate MDT)
- Data Volum... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.2 MDT procedures | The procedures of LTE MDT are the baseline of NR MDT.
- For immediate MDT: The network can collect data with/without the UE involvement in RRC_CONNECTED. For example, the UE can report measurements to the RAN via periodical or event-triggered ways.
- For logged MDT: the network sends logged measurement configuration to... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.3 MDT activation in split RAN | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.3.0 General | Note: The solutions in this clause are pending progress in RAN2 and further discussions are needed in RAN3 in normative phase. |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.3.1 Signalling activation | If the MDT measurement is initiated by the AMF, the AMF sends MDT measurement request to the CU-CP. The CU-CP may further decide which DU or which CU-UP to perform the MDT measurement. For some measurement, the CU-CP may need to split the measurement into different measurements performed in different nodes.
Figure 5.7.... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.3.2 Management activation | If the MDT measurement is initiated by the EM, the EM sends MDT measurement activation to the CU-CP. The CU-CP may further decide which DU or which CU-UP to perform the MDT measurement. For some measurement, the CU-CP may need to split the measurement into different measurements performed in different nodes.
Figure 5.7... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.4 MDT reporting in split RAN | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.3.5 MDT for dual connectivity | - Immediate MDT configurations are supported for DC scenario.
- Logged MDT configurations can come from SN node in DC scenario.
- The existing MDT framework is the baseline for the SCG cells related MDT configuration.
- The triggers for MDT measurements associated to MCG and SCG are separate.
- MN-SN coordination is re... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.7.4 Conclusion | This chapter of technical report presents the results of a study on MDT for NR. Multiple use cases for MDT have been identified, including coverage optimization, QoS verification via MDT, indoor MDT improvement and sensor data collection.
To address these use cases, logged MDT, immediate MDT and accessibility measureme... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.8 UE energy saving | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.8.1 Use case description | High-end mobile devices with 5G modem are expected to feature advanced components e.g. display, processors, graphic engine, etc. Added up, these render power management to be very challenging. In other words, power efficiency is critical for every single component, in particular for the modem itself, regardless of the ... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.8.2 Solution description | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.8.3 Conclusion | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.9 Active Antenna System (AAS) Optimization | |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.9.1 Use case description | Active Antenna System (AAS) is a key component of 5G radio access networks, and, through the exploitation of a beam-centric design, it enables extensive usage of beamforming techniques. Monitoring the radiated power of Downlink Control Channels in total and per beam allows operators to in-depth monitoring of radiation ... |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.9.2 Solution description | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 5.9.3 Conclusion | Void |
699ad02187bf647b5eb56590cc3d2f79 | 37.816 | 6 Measurement quantities, events and faults for collection and utilization |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.