The following prerequisites are assumed:

• An initial remote IP end point to be used for SCTP initialisation is provided to the NG-RAN node for each AMF the NG-RAN node is supposed to connect to.

NG-RAN establishes the first SCTP (IETF RFC 4960) using a configured IP address.

Once SCTP connectivity has been established, the NG-RAN node and the AMF shall exchange application level configuration data over NGAP with the NG Setup procedure, which is needed for these two nodes to interwork correctly on the NG interface:

• The NG-RAN node provides the relevant configuration information to the AMF, which includes list of supported TA(s), etc.;
• The AMF provides the relevant configuration information to the NG-RAN node, which includes PLMN ID, etc.;
• When the application layer initialization is successfully concluded, the dynamic configuration procedure is completed and the NG-C interface is operational.

After the application layer initialization is successfully completed, the AMF may add or update or remove SCTP endpoints to be used for NG-C signalling between the AMF and the NG-RAN node pair as specified in TS 23.501.

The following prerequisites are necessary:

• An initial remote IP end point to be used for SCTP initialisation is provided to the NG-RAN node.

NG-RAN establishes the first SCTP (IETF RFC 4960) using a configured IP address.

Once SCTP connectivity has been established, the NG-RAN node and its candidate peer NG-RAN node are in a position to exchange application level configuration data over XnAP needed for the two nodes to interwork correctly on the Xn interface:

• The NG-RAN node provides the relevant configuration information to the candidate NG-RAN node, which includes served cell information;
• The candidate NG-RAN node provides the relevant configuration information to the initiating NG-RAN node, which includes served cell information;
• When the application layer initialization is successfully concluded, the dynamic configuration procedure is completed and the Xn interface is operational;
• The NG-RAN node shall keep neighbouring NG-RAN nodes updated with the complete list of served cells, or, if requested by the peer NG-RAN node, by a limited list of served cells, while the Xn interface is operational.

The purpose of ANR function is to relieve the operator from the burden of manually managing NCRs. Figure 15.3.3.1-1 shows ANR and its environment:

The ANR function resides in the gNB and manages the Neighbour Cell Relation Table (NCRT). Located within ANR, the Neighbour Detection Function finds new neighbours and adds them to the NCRT. ANR also contains the Neighbour Removal Function which removes outdated NCRs. The Neighbour Detection Function and the Neighbour Removal Function are implementation specific. An existing NCR from a source cell to a target cell means that gNB controlling the source cell:

1. Knows the global and physical IDs (e.g. NR CGI/NR PCI, ECGI/PCI) of the target cell; and
2. Has an entry in the NCRT for the source cell identifying the target cell; and
3. Has the attributes in this NCRT entry defined, either by OAM or set to default values.

NCRs are cell-to-cell relations, while an Xn link is set up between two gNBs. Neighbour Cell Relations are unidirectional, while an Xn link is bidirectional. The ANR function also allows OAM to manage the NCRT. OAM can add and delete NCRs. It can also change the attributes of the NCRT. The OAM system is informed about changes in the NCRT.

ANR relies on NCGI (see clause 8.2) and ANR reporting of E-UTRA cells as specified in TS 36.300.

Figure 15.3.3.2-1 depicts an example where the NG-RAN node serving cell A has an ANR function. In RRC_CONNECTED, the NG-RAN node instructs each UE to perform measurements on neighbour cells. The NG-RAN node may use different policies for instructing the UE to do measurements, and when to report them to the NG-RAN node. This measurement procedure is as specified in TS 38.331 and TS 36.331. When the NG-RAN node receives a UE measurement report containing the PCI, the following sequence may be used.

For Inter-system ANR, each cell contains an Inter Frequency Search list. This list contains all frequencies that shall be searched. Figure 15.3.3.5-1 depicts an example where the NG-RAN node serving cell A has an ANR function.

In RRC_CONNECTED, the NG-RAN node instructs a UE to perform measurements and detect E-UTRA cells connected to EPC.: When the NG-RAN node receives the UE reports containing PCIs of cell(s), the following sequence may be used:

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 lower energy consumption (inactive state). The decision is typically based on cell load information, consistently with configured information. The switch-off decision may also be taken by O&M. The NG-RAN node may initiate handover actions in order to off-load the cell being switched off and may indicate the reason for handover with an appropriate cause value to support the target node in taking subsequent actions, e.g. when selecting the target cell for subsequent handovers. All neighbour NG-RAN nodes are informed by the NG-RAN node owning the concerned cell about the switch-off actions over the Xn interface, by means of the NG-RAN node Configuration Update procedure. All informed nodes maintain the cell configuration data, e.g., neighbour relationship configuration, also when a certain cell is inactive. If basic coverage is ensured by NG-RAN node cells, NG-RAN node owning non-capacity boosting cells may request a re-activation over the Xn interface if capacity needs in such cells demand to do so. This is achieved via the Cell Activation procedure. During switch off time period of the boost cell, the NG-RAN node may prevent idle mode UEs from camping on this cell and may prevent incoming handovers to the same cell. The NG-RAN node receiving a request should act accordingly. The switch-on decision may also be taken by O&M. All peer NG-RAN nodes are informed by the NG-RAN node owning the concerned cell about the re-activation by an indication on the Xn interface. The solution also builds upon the possibility for the NG-RAN node owning a coverage cell to request neighbouring NG-RAN node(s) owning a capacity booster cell to switch on some SSB beams within the cell which are deactivated. The receiving NG-RAN node should act accordingly. The solution also builds upon the possibility for an NG-RAN node to page certain UEs (e.g., stationary UEs) in RRC_INACTIVE state on a limited set of beams, instead of paging on all the beams within the cell. It is up to the gNB's implementation to select the UEs in RRC_INACTIVE for which paging in limited set of beams applies. If the paging over the limited set of beams fails, the gNB performs subsequent paging by implementation, e.g., by ensuring the same paging message is repeated in all the transmitted SSB beams.

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. The decision is typically based on cell load information, consistently with configured information. The switch-off decision may also be taken by O&M. The NG-RAN node indicates the switch-off action to the eNB over NG interface and S1 interface. The NG-RAN node could also indicate the switch-on action to the eNB over NG interface and S1 interface. The eNB providing basic coverage may request a NG-RAN node's cell re-activation based on its own cell load information or neighbour cell load information, the switch-on decision may also be taken by O&M. The eNB requests a NG-RAN node's cell re-activation and receives the NG-RAN node's cell re-activation reply from the NG-RAN node over the S1 interface and NG interface. Upon reception of the re-activation request, the NG-RAN node's cell should remain switched on at least until expiration of the minimum activation time. The minimum activation time may be configured by O&M or be left to the NG-RAN node's implementation.

To facilitate reducing gNB downlink transmission/uplink reception active time, UE can be configured with a periodic cell DTX/DRX pattern (i.e. active and non-active periods). The pattern configuration for cell DTX/DRX is common for the UEs configured with this feature in the cell. The cell DTX and cell DRX patterns can be configured and activated separately. A maximum of two cell DTX/DRX patterns can be configured per MAC entity for different serving cells. When cell DTX is configured and activated for the concerned cell, the UE may not monitor PDCCH in selected cases or does not monitor SPS occasions during cell DTX non-active duration. When cell DRX is configured and activated for the concerned cell, the UE does not transmit on CG resources or does not transmit a SR during cell DRX non-active duration. This feature is only applicable to UEs in RRC_CONNECTED state and it does not impact Random Access procedure, SSB transmission, paging, and system information broadcasting. Cell DTX/DRX operation is only supported for single TRP scenario. Cell DTX/DRX can be activated/deactivated by RRC signalling or L1 group common signalling. Cell DTX/DRX is characterized by the following:

• active duration: duration that the UE waits for to receive PDCCHs or SPS occasions, and transmit SR or CG. In this duration, the gNB transmission/reception of PDCCH, SPS, SR, CG, periodic and semi-persistent CSI report are not impacted for the purpose of network energy saving;
• cycle: specifies the periodic repetition of the active-duration followed by a period of non-active duration.

Active duration and cycle parameters are common between cell DTX and cell DRX, when both are configured; Once the gNB recognizes there is an emergency call or public safety related service, the network should ensure that there is no impact to that service (e.g. it may release or deactivate cell DTX/DRX configuration). The network should also ensure that there is at least partial overlapping between UE's connected mode DRX on-duration and cell DTX/DRX active duration, i.e. the UE's connected mode DRX periodicity is a multiple of cell DTX/DRX periodicity or vice versa.

The same principle as described in clause 9.2.3.4 applies to conditional handover in case the source cell is using a network energy saving solution (e.g., the cell is activating cell DTX/DRX or turning off), unless hereunder specified. In this case, the following additional triggering conditions are supported, upon which UE may use NES-specific CHO event for executing CHO to a candidate cell, as defined in TS 38.331:

• The UE may be notified via DCI to enable CHO conditions(s) configured with NES event indication.

If a cell is activating or going to activate NES cell DTX/DRX, the cell can allow the access of UEs capable of NES cell DTX/DRX via a single bit in SIB1 but prevent the access of UEs not capable of cell DTX/DRX using barring mechanisms described in clause 7.4.

For an intra-band or inter-band CA SCell, a UE may obtain timing reference and AGC source from another serving cell in case the UE is not provided with SSB nor SMTC configuration for this SCell, as described in TS 38.331.

To assist the gNB on muting transceivers and/or adapting transmission power, the UE can be configured to report multiple CSI entries in a CSI report based on two or more sub-configurations, as specified in clause 5.2.1.6 of TS 38.214. Each sub-configuration corresponds to a spatial domain adaptation pattern (subsets of available spatial elements) and/or a power offset between PDSCH and CSI-RS.