WO2023132764A1

WO2023132764A1 - Coordinated coverage updates for radio access network nodes with distributed architecture

Info

Publication number: WO2023132764A1
Application number: PCT/SE2022/051113
Authority: WO
Inventors: Luca LUNARDI; Angelo Centonza
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-01-06
Filing date: 2022-11-29
Publication date: 2023-07-13

Abstract

Embodiments include methods for coverage and capacity optimization (CCO) for a first unit or function of a first radio access network (RAN) node. Such methods include receiving, from one or more second RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the second RAN nodes. Such methods include sending, to one or more second units or functions of the first RAN node, indications of the one or more cells and/or beams,served by the second RAN nodes, that are affected by the updated coverage. Such methods include receiving, from the second units or functions, respective indications of corresponding coverage updates to one or more cells and/or beams served by the second units or functions. Other embodiments include complementary methods for a second unit or function and a second RAN node, as well as RAN nodes (or units/functions thereof) configured to perform such methods.Figure 7 is selected for publication.

Description

COORDINATED COVERAGE UPDATES FOR RADIO ACCESS NETWORK NODES WITH DISTRIBUTED ARCHITECTURE

TECHNICAL FIELD

The present disclosure relates generally to wireless networks, and more specifically to techniques for improved resource management by a network node based on predictions of data traffic, including by the network node, by UEs served by the network node, and/or by network nodes serving neighboring coverage areas.

BACKGROUND

Currently the fifth generation (“5G”) of cellular systems, also referred to as New Radio (NR), is being standardized within the Third-Generation Partnership Project (3GPP). NR is developed for maximum flexibility to support multiple and substantially different use cases. These include enhanced mobile broadband (eMBB), machine type communications (MTC), ultra-reliable low latency communications (URLLC), side-link device-to-device (D2D), and several other use cases.

Figure 1 illustrates an exemplary high-level view of the 5G network architecture, consisting of a Next Generation RAN (NG-RAN) 199 and a 5G Core (5GC) 198. NG-RAN 199 can include a set of gNodeB’s (gNBs) connected to the 5GC via one or more NG interfaces, such as gNBs 100, 150 connected via interfaces 102, 152, respectively. In addition, the gNBs can be connected to each other via one or more Xn interfaces, such as Xn interface 140 between gNBs 100 and 150. With respect the NR interface to UEs, each of the gNBs can support frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof.

NG-RAN 199 is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, /.< ., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (e.g., NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport.

The NG RAN logical nodes shown in Figure 1 include a central (or centralized) unit (CU or gNB-CU) and one or more distributed (or decentralized) units (DU or gNB-DU). For example, gNB 100 includes gNB-CU 110 and gNB-DUs 120 and 130. CUs (e.g., gNB-CU 110) are logical nodes that host higher-layer protocols and perform various gNB functions such controlling the operation of DUs. Each DU is a logical node that hosts lower-layer protocols and can include, depending on the functional split, various subsets of the gNB functions. As such, each of the CUs and DUs can include various circuitry needed to perform their respective functions, including processing circuitry, transceiver circuitry (e.g., for communication), and power supply circuitry. A gNB-CU connects to gNB-DUs over respective Fl logical interfaces, such as interfaces 122 and 132 shown in Figure 1. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. In other words, the Fl interface is not visible beyond gNB-CU.

Centralized control plane (CP) protocols (e.g., PDCP-C and RRC) can be hosted in a different CU than centralized user plane (UP) protocols (e.g., PDCP-U). For example, a gNB-CU can be divided logically into a CU-CP function (including RRC and PDCP for signaling radio bearers) and CU-UP function (including PDCP for UP). A single CU-CP can be associated with multiple CU-UPs in a gNB. The CU-CP and CU-UP communicate with each other using the El- AP protocol over the El interface, as specified in 3GPP TS 38.463 (vl5.4.0). Furthermore, the Fl interface between CU and DU (see Figure 1) is functionally split into Fl-C between DU and CU- CP and Fl -U between DU and CU-UP. Three deployment scenarios for the split gNB architecture shown in Figure 1 are CU-CP and CU-UP centralized, CU-CP distributed/CU-UP centralized, and CU-CP centralized/CU-UP distributed.

Self-optimization is a process in which UE and network measurements are used to autotune the RAN. This occurs when RAN nodes are in an operational state, which generally refers to the time when the RAN node’s RF transmitter interface switched on. Self-configuration and selfoptimization features for LTE networks are described in 3GPP TS 36.300 (vl6.5.0) section 22.2. Self-configuration and self-optimization features for NR networks are described in 3 GPP TS 38.300 (vl6.5.0) section 15. These include dynamic configuration, automatic neighbor relations (ANR), mobility load balancing (MLB), mobility robustness optimization (MRO), RACH optimization, capacity and coverage optimization (CCO), and mobility settings change.

MLB involves coordination between two or more network nodes to optimize the traffic loads of their respective cells, thereby enabling a better use of radio resources available in a geographic area among served UEs. MLB involves load-based handover of UEs between cells served by different nodes, thereby achieving “load balancing”. CCO involves coordination between two or more network nodes to optimize the coverage and/or capacity offered by their respective cells. For example, a reduced coverage and/or capacity in a cell served by a first RAN node can be compensated by an increase in the coverage and/or capacity of neighboring cell served by a second RAN node.

CCO use cases can be divided into ones related to coverage problems and others related to capacity problems. For example, coverage problems generally related to scenarios where the coverage of network-transmitted reference signals (RS) is sub-optimal (e.g., a coverage hole or UL/DL disparity), which leaves the UE exposed to risk of failure or reduced performance. In contrast, capacity problems generally relate to scenarios where capacity of a cell or beam is saturated, which also leaves one or more UEs exposed to risk of failure or reduced performance. There are various reasons for these capacity problems, such as demand of services exceeding available resources in the cell/beam, poor radio conditions affecting a large portion of served UEs (e.g., a large portion of UEs are at cell edge, causing high interference to other UEs and consuming large amounts of resources), etc.

MLB addresses excess load (re)distribution via mobility operations, primarily via interfrequency mobility where cross cell interference is not an issue. In contrast, CCO should address cases where the root cause of the capacity problem is serving UEs near edge of a cell/beam adjacent to another cell/beam that uses the same (or at least overlapping) resources.

SUMMARY

However, CCO can encounter various problems, issues, and/or difficulties when used with RAN nodes having a distributed architecture, such as described above. For example, a second RAN node can send CCO-related information to a first RAN node, which has a first unit or function (e.g., CU) that communicates with other RAN nodes and a second unit or function (e.g., DU) that determines and/or provides the beam/cell coverage (and thus is affected by the CCO- related information). As another example, if the first RAN node has multiple second units or functions (e.g., DUs), there is currently no way to inform other of the second functions about CCO-related actions taken by one of the second functions. This can cause various problems, issues, and/or difficulties.

Embodiments of the present disclosure provide specific improvements to CCO in a RAN, such as by providing, enabling, and/or facilitating solutions to exemplary problems summarized above and described in more detail below.

Embodiments include methods (e.g., procedures) for CCO performed by a first unit or function (e.g., CU or CU-CP) of a first RAN node (e.g., gNB).

These exemplary methods can include receiving, from one or more second RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the respective second RAN nodes. These exemplary methods can also include sending, to one or more second units or functions (e.g., DUs) of the first RAN node, indications of the one or more cells and/or beams, served by the respective second RAN nodes, that are affected by the updated coverage. These exemplary methods can also include receiving, from the one or more second units or functions, respective indications of corresponding coverage updates to one or more cells and/or beams served by the respective second units or functions.

In some embodiments, the neighbor information about updated coverage received from each of the second RAN nodes includes one or more of the following:

• information about updated neighbor cells; • information about updated neighbor beams;

• indication of one or more second RAN node coverage states that are independent of specific neighbor cells or neighbor beams;

• an identifier of the second RAN node;

• indication of one or more actions that produced the updated coverage by the second RAN node; and

• one or more cause values indicating corresponding reasons for the one or more actions.

In some of these embodiments, the information about updated neighbor cells includes a list of neighbor cell identifiers and one or more of the following associated with each identified neighbor cell: an updated cell coverage state, or an updated cell coverage index. In some of these embodiments, the information about updated neighbor beams includes a list of neighbor beam identifiers and one or more of the following associated with each identified neighbor beam: an updated beam coverage state, or an updated beam coverage index.

In some of these embodiments, the indicated one or more actions include any of the following: CCO issue detection, CCO issue resolution, network energy savings, mobility optimization, quality-of-service (QoS) optimization, and quality-of-experience (QoE) optimization. In some of these embodiments, the indicated one or more cause values include any of the following: CCO issue detection, CCO issue resolution, poor coverage, cell edge capacity, uplink-downlink imbalance, energy-saving, cell deactivation, coverage reduction, cell reactivation, and cell modification.

In some of these embodiments, these exemplary methods can also include determine each indication sent to the one or more second units or functions based on neighbor information about updated coverage received from one of the second RAN nodes.

In some embodiments, each indication of corresponding coverage updates includes one or more of the following in relation to the corresponding second unit or function:

• an indication of whether a corresponding coverage update was applied by the second unit or function;

• an indication of one or more corresponding coverage updates that were applied by the second unit or function;

• an indication that the second unit or function determined that no corresponding coverage update was necessary;

• an indication that the second unit or function determined that no corresponding coverage update was feasible; and

• a cause value indicating a reason why a corresponding coverage update was not applied by the second unit or function. In some embodiments, the indications of corresponding coverage updates are received from a plurality of second units or functions and these exemplary methods also include sending each indication of corresponding coverage updates received from one of the second units or functions to all other of the second units or functions.

In some embodiments, these exemplary methods can also include sending, to the one or more second RAN nodes, respective indications of corresponding coverage updates made by the first RAN node based on the neighbor information about updated coverage received from the respective second RAN nodes. In some of these embodiments, each indication of corresponding coverage updates made by the first RAN node includes one or more of the following:

• an indication of whether a corresponding coverage update was applied by the first RAN node;

• an indication of one or more corresponding coverage updates that were applied by the first RAN node;

• an indication that no corresponding coverage updates are necessary for cells and/or beams served by the first RAN node;

• an indication that no corresponding coverage updates are feasible for cells and/or beams served by the first RAN node; and

• a cause value indicating a reason why a corresponding coverage update was not applied.

Other embodiments include additional methods (e.g., procedures) for CCO performed by a second unit or function (e.g, DU) of a first RAN node (e.g., gNB).

These exemplary methods can include receiving, from a first unit or function (e.g., CU or CU-CP) of the first RAN node, indications of one or more cells and/or beams, served by one or more second RAN nodes, that are affected by updated coverage. These exemplary methods can also include, based on the indications of the one or more cells and/or beams affected by updated coverage, selectively applying corresponding coverage updates to one or more cells and/or beams served by the second unit or function. These exemplary methods can also include sending, to the first unit or function, an indication of corresponding coverage updates to one or more cells and/or beams served by the second unit or function.

In some embodiments, selectively applying can include the following operations:

• determining whether corresponding coverage updates to one or more cells and/or beams served by the second unit or function are necessary;

• determining whether corresponding coverage updates to one or more cells and/or beams served by the second unit or function are feasible; and • when at least one corresponding coverage update is determined to be necessary and feasible, applying a necessary and feasible corresponding coverage update to one or more cells and/or beams served by the second unit or function.

In some of these embodiments, selectively applying can also include refraining from applying corresponding coverage updates to the one or more cells and/or beams served by the second unit or function, when no corresponding coverage updates are determined to be necessary and feasible.

In various embodiments, each indication received can include any of the information summarized above in relation to such indications sent by the first unit or function of the first RAN node.

In some embodiments, the indication of corresponding coverage updates can include any of the information summarized above in relation to such indications received by the first unit or function of the first RAN node. Such indications can be based on results of the determinations made during selective application of corresponding coverage updates.

In some embodiments, these exemplary methods can also include receive, from the first unit or function, respective indications of corresponding coverage updates by one or more other second units or functions of the first RAN node. In some variants, the second unit or function can consider these indications during selective application of its own coverage updates.

Other embodiments include additional methods (e.g., procedures) for CCO performed by a second RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.).

These exemplary methods can include sending, to respective first units or functions (e.g., CU or CU-CP) of one or more first RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the second RAN node. These exemplary methods can also include receiving, from the respective first units or functions, indications of corresponding coverage updates made by the respective first RAN nodes based on the neighbor information about updated coverage.

In various embodiments, the neighbor information about updated coverage can include any of the information and/or contents summarized above in relation such neighbor information being received by the first unit or function of the first RAN node. In various embodiments, each indication of corresponding coverage updates made by a first RAN node can include any of the information and/or contents summarized above in relation to such indications being sent by the first unit or function of the first RAN node.

Other embodiments include RAN nodes (e.g, base stations, eNBs, gNBs, ng-eNBs, TRPs, etc. and units/functions thereof, such as CUs, CU-CPs, and/or DUs) configured to perform operations corresponding to any of the exemplary methods described herein. Other embodiments include non-transitory, computer-readable media storing program instructions that, when executed by processing circuitry, configure such RAN nodes (or units/functions thereof) to perform operations corresponding to any of the exemplary methods described herein.

These and other embodiments described herein can enable multiple RAN nodes to coordinate cell and/or beam coverage to facilitate improved and/or optimal coverage and capacity in their overall coverage area. In this manner, embodiments facilitate a RAN distributed architecture solution wherein coverage updates for one or more cells and/or beams of different RAN nodes can be coordinated. In this manner, embodiments can improve various RAN optimization scenarios or use cases such as CCO, network energy saving, QoS optimization, QoE optimization, etc.

These and other objects, features, and advantages of embodiments of the present disclosure will become apparent upon reading the following Detailed Description in view of the Drawings briefly described below.

BRIEF DESCRIPTION OF THE DRAWINGS

Figures 1-2 illustrate two high-level views of an exemplary 5G/NR network architecture.

Figure 3 shows exemplary NR user plane (UP) and control plane (CP) protocol stacks.

Figure 4 is a signal flow diagram that illustrates various aspects of CCO detection and CCO resolution in NG-RAN.

Figures 5-6 are a signal flow diagrams that illustrate various embodiments of the present disclosure.

Figure 7 shows a flow diagram of an exemplary method (e.g., procedure) for a first unit or function (e.g., CU or CU-CP) of a first RAN node (e.g., base station, eNB, gNB), according to various embodiments of the present disclosure.

Figure 8 shows a flow diagram of an exemplary method (e.g., procedure) for a second unit or function (e.g., DU) of a first RAN node (e.g., base station, eNB, gNB), according to various embodiments of the present disclosure.

Figure 9 shows a flow diagram of an exemplary method (e.g., procedure) for a second RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.), according to various embodiments of the present disclosure.

Figure 10 shows a communication system according to various embodiments of the present disclosure.

Figure 11 shows a UE according to various embodiments of the present disclosure.

Figure 12 shows a network node according to various embodiments of the present disclosure. Figure 13 shows host computing system according to various embodiments of the present disclosure.

Figure 14 is a block diagram of a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.

Figure 15 illustrates communication between a host computing system, a network node, and a UE via multiple connections, at least one of which is wireless, according to various embodiments of the present disclosure.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods and/or procedures disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein can be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments can apply to any other embodiments, and vice versa. Other objects, features, and advantages of the enclosed embodiments will be apparent from the following description.

Furthermore, the following terms are used throughout the description given below:

• Radio Access Node: As used herein, a “radio access node” (or equivalently “radio network node,” “radio access network node,” or “RAN node”) can be any node in a radio access network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a gNB in a 3GPP 5G/NR network or eNB in a 3GPP LTE network), base station distributed components (e.g., CU and DU), a high-power or macro base station, a low-power base station (e.g., micro, pico, femto, or home base station, or the like), an integrated access backhaul (IAB) node (or component thereof such as MT or DU), a transmission point, a remote radio unit (RRU or RRH), and a relay node. • Core Network Node: As used herein, a “core network node” is any type of node in a core network. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a serving gateway (SGW), a Packet Data Network Gateway (P-GW), etc. A core network node can also be a node that implements a particular core network function (NF), such as an access and mobility management function (AMF), a session management function (SMF), a user plane function (UPF), a Service Capability Exposure Function (SCEF), or the like.

• Wireless Device: As used herein, a “wireless device” (or “WD” for short) is any type of device that is capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Communicating wirelessly can involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. Unless otherwise noted, the term “wireless device” is used interchangeably herein with the term “user equipment” (or “UE” for short), with both of these terms having a different meaning than the term “network node”.

• Radio Node: As used herein, a “radio node” can be either a “radio access node” (or equivalent term) or a “wireless device.”

• Network Node: As used herein, a “network node” is any node that is either part of the radio access network (e.g., a radio access node or equivalent term) or of the core network (e.g., a core network node discussed above) of a cellular communications network. Functionally, a network node is equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the cellular communications network, to enable and/or provide wireless access to the wireless device, and/or to perform other functions (e.g., administration) in the cellular communications network.

• Node: As used herein, the term “node” (without any prefix) can be any type of node that is capable of operating in or with a wireless network (including a RAN and/or a core network), including a radio access node (or equivalent term), core network node, or wireless device. However, the term “node” may be limited to a particular type of node (e.g., radio access node) based on its particular characteristics in any context of use.

• Base station: As used herein, a “base station” may comprise a physical or a logical node transmitting or controlling the transmission of radio signals, e.g., eNB, gNB, ng-eNB, en- gNB, centralized unit (CU)/distributed unit (DU), transmitting radio network node, transmission point (TP), transmission reception point (TRP), remote radio head (RRH), remote radio unit (RRU), Distributed Antenna System (DAS), relay, etc. The above definitions are not meant to be exclusive. In other words, various ones of the above terms may be explained and/or described elsewhere in the present disclosure using the same or similar terminology. Nevertheless, to the extent that such other explanations and/or descriptions conflict with the above definitions, the above definitions should control.

Note that the description given herein focuses on a 3 GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. Furthermore, although the term “cell” is used herein, it should be understood that (particularly with respect to 5G NR) beams may be used instead of cells and, as such, concepts described herein apply equally to both cells and beams.

5G/NR technology shares many similarities with LTE. For example, NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in the DL and both CP-OFDM and DFT-spread OFDM (DFT-S-OFDM) in the UL. As another example, in the time domain, NR DL and UL physical resources are organized into equal-sized 1-ms subframes. A subframe is further divided into multiple slots of equal duration, with each slot including multiple OFDM-based symbols. However, time-frequency resources can be configured much more flexibly for an NR cell than for an LTE cell. For example, rather than a fixed 15-kHz OFDM sub-carrier spacing (SCS) as in LTE, NR SCS can range from 15 to 240 kHz, with even greater SCS considered for future NR releases.

Figure 2 shows another high-level view of an exemplary 5G network architecture, including a NG-RAN 299 and 5GC 298. As shown in the figure, NG-RAN 299 can include gNBs (e.g, 210a,b) and ng-eNBs (e.g, 220a, b) that are interconnected with each other via respective Xn interfaces. The gNBs and ng-eNBs are also connected via the NG interfaces to 5GC, more specifically to Access and Mobility Management Functions (AMFs, e.g., 230a, b) via respective NG-C interfaces and to User Plane Functions (UPFs, e.g., 240a, b) via respective NG-U interfaces. Moreover, the AMFs can communicate with one or more policy control functions (PCFs, e.g., 250a, b) and network exposure functions (NEFs, e.g., 260a, b).

Each of the gNBs 210 can support the NR radio interface including frequency division duplexing (FDD), time division duplexing (TDD), or a combination thereof. Each of ng-eNBs 220 can support the fourth generation (4G) Long-Term Evolution (LTE) radio interface. Unlike conventional LTE eNBs, however, ng-eNBs 220 connect to the 5GC via the NG interface. Each of the gNBs and ng-eNBs can serve a geographic coverage area including one more cells, such as cells 21 la-b and 221a-b shown in Figure 2. Depending on the cell in which it is located, a UE 205 can communicate with the gNB or ng-eNB serving that cell via the NR or LTE radio interface, respectively. Although Figure 2 shows gNBs and ng-eNBs separately, it is also possible that a single NG-RAN node provides both types of functionality.

In addition to providing coverage via cells as in LTE, NR networks also provide coverage via “beams.” In general, a downlink (DL, i.e., network to UE) “beam” is a coverage area of a network-transmitted reference signal (RS) that may be measured or monitored by a UE. In NR, RS can include any of the following: synchronization signal/PBCH block (SSB), channel state information RS (CSI-RS), tertiary reference signals (or any other sync signal), positioning RS (PRS), demodulation RS (DMRS), phase-tracking reference signals (PTRS), etc. In general, SSB is available to all UEs regardless of the state of their connection with the network, while other RS (e.g., CSI-RS, DM-RS, PTRS) are associated with specific UEs that have a network connection.

Figure 3 shows an exemplary configuration of NR user plane (UP) and control plane (CP) protocol stacks between a UE, a gNB, and an AMF, such as those shown in Figures 1-2. The Physical (PHY), Medium Access Control (MAC), Radio Link Control (RLC), and Packet Data Convergence Protocol (PDCP) layers between the UE and the gNB are common to UP and CP. The PDCP layer provides ciphering/deciphering, integrity protection, sequence numbering, reordering, and duplicate detection for both CP and UP. In addition, PDCP provides header compression and retransmission for UP data.

On the UP side, Internet protocol (IP) packets arrive to the PDCP layer as service data units (SDUs), and PDCP creates protocol data units (PDUs) to deliver to RLC. The Service Data Adaptation Protocol (SDAP) layer handles quality-of-service (QoS) including mapping between QoS flows and Data Radio Bearers (DRBs) and marking QoS flow identifiers (QFI) in UL and DL packets. The RLC layer transfers PDCP PDUs to the MAC through logical channels (LCH). RLC provides error detection/correction, concatenation, segmentation/reassembly, sequence numbering, reordering of data transferred to/from the upper layers. The MAC layer provides mapping between LCHs and PHY transport channels, LCH prioritization, multiplexing into or demultiplexing from transport blocks (TBs), hybrid ARQ (HARQ) error correction, and dynamic scheduling (on gNB side). The PHY layer provides transport channel services to the MAC layer and handles transfer over the NR radio interface, e.g., via modulation, coding, antenna mapping, and beam forming.

On CP side, the non-access stratum (NAS) layer is between UE and AMF and handles UE/gNB authentication, mobility management, and security control. The RRC layer sits below NAS in the UE but terminates in the gNB rather than the AMF. RRC controls communications between UE and gNB at the radio interface as well as the mobility of a UE between cells in the NG-RAN. RRC also broadcasts system information (SI) and performs establishment, configuration, maintenance, and release of DRBs and Signaling Radio Bearers (SRBs) and used by UEs. Additionally, RRC controls addition, modification, and release of carrier aggregation (CA) and dual -connectivity (DC) configurations for UEs. RRC also performs various security functions such as key management.

.After a UE is powered ON it will be in the RRC IDLE state until an RRC connection is established with the network, at which time the UE will transition to RRC CONNECTED state (e.g., where data transfer can occur). The UE returns to RRC_IDLE after the connection with the network is released. In RRC IDLE state, the UE’s radio is active on a discontinuous reception (DRX) schedule configured by upper layers. During DRX active periods (also referred to as “DRX On durations”), an RRC__IDLE UE receives SI broadcast in the cell where the UE is camping, performs measurements of neighbor cells to support cell reselection, and monitors a paging channel on PDCCH for pages from 5GC via gNB. An NR UE in RRC IDLE state is not known to the gNB serving the cell where the UE is camping. However, NR RRC includes an RRC_INACTIVE state in which a UE is known (e.g., via UE context) by the serving gNB. RRC INACTIVE has some properties similar to a “suspended” condition used in LTE.

As briefly mentioned above, RAN coverage and capacity optimization (CCO) use cases can be divided into ones related to coverage problems and others related to capacity problems. For example, coverage problems generally related to scenarios where the coverage of RS is sub- optimal (e.g., a coverage hole or UL/DL disparity), which leaves the UE exposed to risk of failure or reduced performance. In contrast, capacity problems generally relate to scenarios where capacity of a cell or beam is saturated, which also leaves one or more UEs exposed to risk of failure or reduced performance. There are various reasons for these capacity problems, such as demand of services exceeding available resources in the cell/beam, poor radio conditions affecting a large portion of served UEs (e.g., a large portion of UEs are at cell edge, causing high interference to other UEs and consuming large amounts of resources), etc.

In the following description, the terms “CCO issue” and “CCO-related issue” refer to a problem that belongs to a use case for CCO. A phase during which a CCO issue is recognized or detected is called “CCO detection” or “CCO issue detection” and a phase during which a detected CCO issue is resolved (or attempted to be resolved) is called “CCO resolution” or “CCO issue resolution”.

During CCO resolution, a first RAN node will take various actions including updating its configuration, e.g., of one or more cells and/or beams (e.g., SSB beams, CSI-RS beams, etc.). After these actions, the coverage envelopes of the one or more cells and/or beams have been updated. For example, the updates in the coverage envelope(s) by the first RAN nod can result in any of the following:

• two or more cells have been merged into one cell, • at least one cell has been split in two or more cells,

• the indexes identifying the cells have been changed

• a set of cells have been replaced by a different set of cells,

• one or more cells may have been deactivated,

• two or more SSB beams have been merged into one SSB beam,

• at least one SSB beam has been split in two or more SSB beams,

• the indexes identifying the SSB beams have been changed

• a set of SSB beams have been replaced by a different set of SSB beams, and

• one or more cells or SSB beams may have been deactivated.

The first RAN node can inform a second RAN node - serving a coverage area neighboring (e.g., adjacent to) the coverage area served by the first RAN node - about the detected CCO issue, the CCO resolution actions taken, and information about the first RAN node’s updated configuration that resulted in the updated coverage envelope.

Figure 4 is a signal flow diagram that illustrates various aspects of CCO detection and CCO resolution in an NG-RAN. The operations shown in Figure 4 are between NG-RAN node 1 (410, an example of the first RAN node discussed above) and NG-RAN node 2 (420, an example of the second RAN node discussed above). NG-RAN node 1 is a gNB that includes a gNB-CU (412) and a gNB-DU (414), such as shown in Figure 1. Although the signaling and operations in Figure 4 are given numerical labels, this is intended to facilitate explanation rather than to require or imply any specific order.

Operation 1 involves intra-gNB CCO issue detection by NG-RAN node 1. In operation la, the gNB-CU indicates to the gNB-DU the presence of a CCO issue and the affected cells and beams by sending an F1AP message that includes CCO assistance information. In operation lb, the gNB-DU acknowledges the CCO issue identified by the CCO assistance information.

Operation 2 involves intra-gNB CCO issue resolution by NG-RAN node 1. In operation 2a, the gNB-DU informs the gNB-CU of a coverage configuration selected by the gNB-DU to resolve the CCO issue identified in operation 1. This is done by sending an F1AP message with a Coverage Modification Notification. In operation lb, the gNB-CU acknowledges the coverage configuration identified by the Coverage Modification Notification.

Operation 3 involves an inter-gNB CCO request. In operation 3a, the gNB-CU of NG- RAN node 1 sends to NG-RAN node 2 an XnAP message that includes a Coverage Modification List identifying updated coverage to one or more cells and/or beams provided by NG-RAN node 1. In operation 4, NG-RAN node 2 takes corresponding actions to update coverage of one or more of its cells and/or beams based on the Coverage Modification List received from the gNB- CU in operation 3. In operation 5a, NG-RAN node 2 sends an XnAP message that includes a Coverage Modification List identifying updated coverage to one or more cells and/or beams provided by NG-RAN node 2, i.e., responsive to the updated coverage by NG-RAN node 1.

The following proposed 3GPP specification text illustrates an implementation of the F1AP signaling shown in Figure 4. *** Begin proposed 3GPP specification text ***

9.3.1.x! CCO Assistance Information

This IE indicates the Capacity and Coverage (CCO) issue detected.

9..1.x2 Affected Cells and Beams This IE includes a list of cells and/or SS/PBCH block indexes affected by the detected CCO issue.

9.3.1 ,x3 Coverage Modification Notification

This IE includes a list of cells and/or SS/PBCH block indexes with the corresponding coverage configuration selected by the gNB-DU.

*** End proposed 3 GPP specification text ***

However, CCO can encounter various problems, issues, and/or difficulties when used with RAN nodes having a distributed architecture, such as described above. Consider the opposite example as shown in Figure 4, specifically that a second RAN node (e.g., NG-RAN node 2) sends CCO-related information to a first RAN node (e.g., NG-RAN node 1), which includes a first unit or function (e.g., CU) that communicates with other RAN nodes and a second unit or function (e.g., DU) that determines and/or provides cell/beam coverage and thus is affected by the CCO-related information. In other words, the second RAN node informs the first RAN node about the detected CCO issue, the CCO resolution actions taken, and the second RAN node’s updated configuration that resulted in an updated coverage envelope.

Currently, 3GPP specifications neither specify nor describe signaling and mechanisms of communication between the first and second units or functions of the first RAN node in response to receiving such information from the second RAN node. As such, it is unclear how the second unit or function can obtain this information and perform its own CCO-related actions responsive and/or corresponding to the second RAN node's actions. Failure to take corresponding actions may result in coverage mismatch (e.g., overlapping coverage or noncoverage) between cells served by the first RAN node and cells served by the second RAN node.

As another example, if the first RAN node has multiple second units or functions (e.g., DUs), there is currently no way to inform other of the second functions about CCO-related actions taken by a first one of the second functions. This can cause coverage mismatches (e.g., overlapping coverage or non-coverage) between cells served by the first second function and cells served by the other second functions of the first RAN node.

Accordingly, embodiments of the present disclosure provide flexible and efficient techniques that coordinate resolution of one or more CCO issues between first and second RAN nodes, where CCO actions are initially taken by a second RAN node and corresponding actions need to be taken by a neighboring first RAN node that is arranged in a distributed architecture. In this arrangement, a first unit or function of the first RAN node has a signaling connection towards the second RAN node(s) and a second unit or function of the first RAN node determines updated coverage or one or more cells and/or beams in response to updated coverage of cells and/or beams served by the second RAN nodes.

For example, embodiments provide techniques for a first unit or function of the first RAN node, after receiving information about CCO actions taken by the second RAN node, to determine indications of coverage updates relevant for the coordination of coverage of cells and/or beams of the first and second RAN nodes. After determining this information, the first unit or function sends it to one or more second units or functions that are responsible for providing coverage for cells and/or beams of the first RAN node. Upon receiving this information, the second unit(s) or function(s) can determine whether corresponding cell and/or beam coverage updates are feasible and apply such updates when feasible. The second unit(s) or function(s) can inform the first unit or function about any positive or negative outcome of coverage updates, which the first unit or function can inform the second RAN node about any corresponding coverage updates that the second unit(s) or function(s) have made.

In this manner, the first and second RAN nodes can enable multiple RAN nodes to coordinate cell/beam coverage to facilitate improved and/or optimal coverage and capacity in their overall coverage area. In this manner, embodiments facilitate a RAN distributed architecture solution wherein coverage updates for one or more cells and/or beams of different RAN nodes can be coordinated. In this manner, embodiments can improve various RAN optimization scenarios or use cases such as CCO, network energy saving, QoS optimization, QoE optimization, etc.

Figure 5 is a signal flow diagrams that illustrates various embodiments of the present disclosure. Specifically, Figure 5 shows signaling between a second RAN node (590) and a first RAN node (580) that includes a first unit or function (582) and a second unit or function (584) arranged in a distributed architecture, with the first function performing signaling with the second RAN node (as well as other network nodes) and the second unit or function providing coverage for cells and/or beams of the first RAN node. As one example, the first unit or function can be a CU or a CU-CP and the second unit or function can be a DU.

Some embodiments are applicable to a scenario where the first RAN node includes one instance of a first unit or function and a plurality of instances of a second unit or function of the first RAN node. For example, a gNB can comprise one gNB-CU-CP controlling multiple gNB- DUs. Other embodiments are applicable to a scenario involving multiple second RAN nodes sending the first unit or function of the first RAN node indications of coverage updates for their respective cells and/or beams.

The second RAN node has a direct or indirect signaling connection with the first RAN node. The second RAN node is a neighbor node of the first RAN node, in the sense that the second RAN node controls, serves, and/or provides cells that are adjacent (or neighboring) to cells served or provided by the first RAN node. When the second RAN node is also deployed in distributed architecture, a first function of the second RAN node can have a direct or indirect signaling connection with the first RAN node or the first unit or function of the first RAN node.

As such, the first unit or function of the first RAN node may communicate (receive information or transmit information) to one or more second RAN nodes or a first function of one or more second RAN node. Hereinafter, reference to the first of these arrangements should be understood as referring to both.

Figure 6 is a signal flow diagrams that illustrates more specific embodiments of the present disclosure. Specifically, Figure 6 shows signaling between NG-RAN node 2 (690, e.g., gNB or ng-eNB) and NG-RAN node 1 (680) that includes a gNB-CU (682) and a gNB-DU (684) in a distributed architecture, with the gNB-CU performing signaling with NG-RAN node 2 (as well as other network nodes) and the gNB-DU providing coverage for cells and/or beams of NG-RAN node 1.

In some embodiments, the first unit or function of the first RAN node receives from one or more second RAN nodes neighbor information about updated coverage (e.g., in block 500 of Figure 5 or block 600 of Figure 6), which can include one or more of the following (i.e., from each second RAN node):

• neighbor cells information, e.g., in the form of a list, comprising identifiers of one or more cells served by the second RAN node and associated per-cell information, such as a new/updated per-cell coverage index or a new/updated per-cell coverage state. For example, a new/updated per-cell coverage index and/or a new/updated per-cell coverage state can be associated with deactivation of one or more cells, activation of one or more cells, change in coverage shape of one or more cells, splitting a cell into multiple cells, merging multiple cells into one cell, replacing a first set of cells with a second set of cells, etc.

• neighbor beams information, e.g., in the form of a list, comprising identifiers of one or more beams (e.g., SSB Area Index) of the second RAN node and associated per-beam information, such as a new/updated per-beam coverage index or a new/updated per-beam coverage state. For example, a new/updated per-beam coverage index and/or a new/updated per-beam coverage state can be associated with deactivation of one or more beams, activation of one or more beams, change in coverage shape of one or more beams, splitting a beam into multiple beams, merging multiple beams into one beam, replacing a first set of beams with a second set of beams, etc. • one or more second RAN node coverage states, namely independent from specific cells or beams at the second RAN node, but where each coverage state represents a coverage configuration adopted by the second RAN node.

• a node identifier of the second RAN node

• indication of one or more actions motivating the updated coverage, or of issue(s) detected and/or resolved by the updated coverage by the second RAN node (e.g., CCO issue detection, CCO issue resolution, network energy saving, mobility optimization, QoS optimization, QoE optimization, etc.). As an example, an action (e.g., CCO issue detection, CCO issue resolution, or network energy saving) can be associated with one or more cells and/or beams served by the second RAN node. As another example, an action or issue indicated by the second RAN node can refer to an action already executed, an action to be performed or initiated, a proposed action, an issue detected, an issue resolved, an issue being resolved, etc.

• one or more cause values associated with an action or an issue of the second RAN node and indicating a reason for the second RAN node for sending neighbor cells information, neighbor beams information, and/or node coverage states. Some example cause values include “CCO issue detection”, “CCO issue resolution”, “poor coverage”, “cell edge capacity”, “uplink-downlink imbalance”, “energy-saving”, “cell deactivation”, “coverage reduction”, “cell reactivation”, and “cell modification”.

In some embodiments, the first unit or function of the first RAN node forwards to the second unit or function of the first RAN node at least part of the received neighbor information about updated coverage. In some embodiments, the first unit or function of the first RAN node determines one or more indications of neighbor coverage update, related to the updated coverage in the one or more cells and/or beams of each of the one or more second RAN nodes (e.g., in block 510 of Figure 5 or block 610 of Figure 6). The first unit or function of the first RAN node sends to the second unit or function of the first RAN node the one or more indications of neighbor coverage update (e.g., in block 520 of Figure 5 or block 620 of Figure 6). For example, the first unit or function can send this information in a Neighbor Node CCO Assistance Information List IE, with example contents discussed below.

In various embodiments, each indication of neighbor coverage update can include one or more of the following:

• cell identifiers for one or more cells served by the second RAN node (e.g., a list of Global NG-RAN Cell Identities) that are affected by the CCO changes at the second RAN node

• beam identifier for one or more beams served by the second RAN node (e.g., a list of SSB Beam Index) that are affected by the CCO changes at the second RAN node • one or more per-cell coverage states for cells served by the second RAN node, which can be a pointer to a more detailed coverage characteristic (e.g., a cell shape). As nonlimiting examples, a per-cell coverage state can be expressed as an integer or as one of an enumerated set of values.

• one or more per-beam coverage state for beam of the second RAN node, which can be a pointer to a more detailed coverage characteristic (e.g., a beam shape). As non-limiting examples, a per-beam coverage state can be expressed as an integer or as one of an enumerated set of values.

• one or more second RAN node coverage states, namely independent from specific cells or beams at the second RAN node, but where each node coverage state represents a coverage configuration adopted by the second RAN node.

• a node identifier associated with the second RAN node.

• number or portion of cells affected by the action(s) of the second RAN node

• number or portion of beams affected by the action(s) of the second RAN node

• number of second RAN nodes from which the first unit or function of the first RAN node received neighbor information about updated coverage

• one or more per-cell indices for cells of the second RAN node, and/or one or more per- beam indexes, wherein a per-cell index and/or a per-beam index is obtained as a function of one or more of any of the indications listed above. • one or more per-node coverage states or indices for cells and/or beams served by the second RAN node, wherein each per node coverage state or index is obtained as a function of one or more of any of the neighbor information about updated coverage listed above (e.g., received from the second RAN node).

A function of the one or more of the indications listed above can be realized in various ways. Some non-limiting examples include:

• as a concatenation of one or more of the indications of neighbor coverage update, e.g., concatenation of a cell identity (e.g., an NR CGI), and a per-cell coverage state (e.g., an integer value in a range from 0 to 32);

• a generated random number associated with one or more of the indications of neighbor coverage update; and

• a hash function with one or more of the indications of neighbor coverage update as input. In some embodiments, the first unit or function of the first RAN node may send the second function of the second RAN node information about neighbor cell measurements, such as measurements that reveal coverage level of cells of the second RAN node adjacent to cells provided by the second unit or function of the first RAN node. Such measurements may include one or more of the following:

• neighbor cell identifiers (e.g., PCIs) and/or beam identifiers (e.g., SSB indices) of the second RAN node;

• RSRP, RSRQ, and/or SINR associated with a specific cell and/or beam of the second RAN node;

• RACH-related measurements associated with a specific cell and/or beam of the second RAN node; and

• Any other L3 measurements that may be used at the second function to derive the coverage and/or capacity of neighbor cells.

For example, the first unit or function of the first RAN node may receive such measurements from one or more UEs connected to the first RAN node. Based on this information, the second function can determine how the coverage of neighbor cells/beams has changed due to the CCO- related actions performed by the second RAN node.

In some embodiments, the first unit or function of the first RAN node receives from a second unit or function of the first RAN node one or more of the following (e.g., in block 540 of Figure 5 or block 640 of Figure 6):

• an indication of whether a second unit or function of the first RAN node successfully applied or failed to apply one or more coverage updates for one or more cells and/or beams of the first RAN node in response to (i.e., as a match of) coverage updates of one or more cells and/or beams served by one or more second RAN nodes.

• one or more coverage updates for one or more cells and/or beams served by the first RAN node determined by a second unit or function of the first RAN node in response to (i.e., to match) coverage updates of one or more cells and/or beams served by one or more second RAN nodes.

• an indication of cause, indicating a reason for which it was not possible to positively respond to (i.e., to match) coverage updates of one or more cells and/or beams of one or more second RAN nodes with corresponding coverage updates of one or more cells and/or beams served by the first RAN node.

• an indication that the second unit or function of the first RAN node has determined that coverage updates are unnecessary for cells and/or beams served by the first RAN node under the control of the second unit or function of the first RAN node.

• an indication that the second unit or function of the first RAN node has determined that coverage updates are infeasible for cells and/or beams served by the first RAN node under the control of the second unit or function of the first RAN node.

In some embodiments, the first unit or function of the first RAN node can send to the second RAN node one or more of the following (e.g., in block 550 of Figure 5 or block 650 of Figure 6):

• an indication of whether the first RAN node successfully applied or failed to apply one or more coverage updates for one or more cells and/or beams served by the first RAN node in response to (i.e., as a match of) coverage updates of one or more cells and/or beams served by the second RAN node.

• one or more coverage updates for one or more cells and/or beams served by the first RAN node determined in response to (i.e., to match) coverage updates of one or more cells and/or beams served by the second RAN node.

• an indication of cause, indicating a reason for which it was not possible to positively respond to (i.e., to match) coverage updates of one or more cells and/or beams served by one or more second RAN nodes with corresponding coverage updates of one or more cells and/or beams served by the first RAN node.

• an indication that no coverage updates are determined for any cells and/or beams served by the first RAN node in response to (i.e., to match) coverage updates of one or more cells and/or beams served by the second RAN node. • an indication that no coverage updates are possible for any cells and/or beams served by the first RAN node in response to (i.e., to match) coverage updates of one or more cells and/or beams served by the second RAN node.

The second unit or function of the first RAN node receives from the first unit or function of the first RAN node one or more indications of neighbor coverage update, according to the above description of that information. Based on this received information, the second unit or function of the first RAN node can determine what corresponding action is needed (e.g., in block 540 of Figure 5 or block 640 of Figure 6). Some illustrative examples are discussed below.

In some embodiments, the second unit or function of the first RAN node may be configured by a different system (e.g., 0AM) with specific CCO actions to be taken if neighbor nodes and/or cells and/or beams apply specific CCO configuration changes.

In some embodiments, the second unit or function of the first RAN node may learn over time more details of the CCO configurations adopted by the second RAN node, as indicated by the first function of the first RAN node based on summary information such as configuration indexes. Such learning may occur, for example, by UE measurements of neighbor cells or beams, UE measurements revealing coverage and capacity issues (e.g., high cross cell interference), UE or RAN node measurements revealing performance degradation in UL and/or DL, etc.

The second unit or function of the first RAN node uses indications of neighbor coverage update associated with or more cells and/or beams of a second RAN node(s) to determine whether it is feasible to make corresponding coverage updates of one or more its own cells and/or beams. If corresponding coverage updates are determined to be feasible, the second unit or function applies the corresponding coverage updates to one or more its own cells and/or beams.

In some embodiments, the second unit or function of the first RAN node sends to the first unit or function of the first RAN node (e.g., in block 540 of Figure 5 or block 640 of Figure 6) one or more of the following:

• an indication of whether the second unit or function of the first RAN node successfully applied or failed to apply one or more coverage updates for one or more cells and/or beams served by the second unit or function of the first RAN node corresponding to the coverage updates by one or more second RAN nodes.

• an indication of the coverage updates applied.

• an indication of a cause for failure to apply corresponding coverage updates.

• an indication that the second unit or function of the first RAN node determined that no corresponding coverage update is needed (i.e., that the current coverage is sufficient). In some embodiments, the first RAN node (e.g., gNB) includes one first unit or function (e.g., CU-CP) and a plurality of second units or functions (e.g., gNB-DUs). In this scenario, the embodiments described above are applicable when the first unit or function determines and sends indications of neighbor coverage update for each of the second units or function. For example, in a gNB that includes a gNB-CU-CP and two gNB-DUs, gNB-DUl and gNB-DU2, gNB-CU-CP sends to gNB-DUl indications of neighbor coverage update related to gNB-DU2 (or vice versa). In addition, gNB-DUl determines coverage updates for one or more of its cells and/or beams in response to indicated coverage updates of cells and/or beams of gNB-DU2.

Some details are provided below in order to further clarify embodiments described above for when the first RAN node has a plurality of second units or functions (e.g., DUs). In this scenario, the first unit or function of the first RAN node determines one or more indications of neighbor coverage update. The first unit or function of the first RAN node sends to each (or at least one) of the second units or functions one or more indications of neighbor coverage update related to the other second units or functions of the first RAN node. For example, the first unit or function can send one or more an Inter-DU CCO Assistance Information List IES via Fl AP, with example contents discussed below.

Based on this received information, each second unit or function determines whether it is feasible to make corresponding coverage updates of one or more its own cells and/or beams. If corresponding coverage updates are determined to be feasible, the second unit or function applies the corresponding coverage updates to one or more its own cells and/or beams. The second unit or function then sends to the first unit or function any of the same indications related to coverage update as discussed above.

The table below shows the contents of an example Fl AP GNB-CU CONFIGURATION UPDATE message defined in 3GPP TS 38.473 (vl6.8.0), with updates according to some embodiments of the present disclosure. This message is sent by the gNB-CU to transfer updated information associated to an Fl-C interface instance, such as shown in Figure 4. Certain unchanged parts have been omitted for brevity.

The table below shows exemplary contents of an example Neighbor node CCO Assistance Information Item IE, such as listed in the table above. This IE indicates the CCO actions for specific CCO issues detected in a peer NG-RAN node.

The table below shows exemplary contents of an example Inter-DU CCO Assistance Information Item IE, such as listed in the table above. This IE indicates the CCO actions for specific CCO issues detected in another DU of the same NG-RAN node.

The table below shows exemplary contents of an example Affected Cells and Beams IE, such as listed in the two IES immediately above. This IE includes a list of cells and/or SSB indices affected by the detected CCO issue.

The table below shows the contents of another example F1AP GNB-CU CONFIGURATION UPDATE message defined in 3GPP TS 38.473 (v!6.8.0), with updates according to some embodiments of the present disclosure. This message is sent by the gNB-CU to transfer updated information associated to an Fl-C interface instance, such as shown in Figure

4. Certain unchanged parts have been omitted for brevity.

The table below shows exemplary contents of an example Neighbor Node Assistance

Information Item IE, such as listed in the table above. This IE indicates the CCO actions for specific CCO issues detected.

The table below shows exemplary contents of an example Neighbor Node Configuration IE, such as listed in the table above. This IE indicates a list of cells and/or SSB indices affected by the detected CCO issue.

Various features of the embodiments described above correspond to various operations illustrated in Figures 7-9, which show exemplary methods (e.g., procedures) for a first function or unit of a first RAN node, a second function or unit of the first RAN node, and a second RAN node, respectively. In other words, various features of the operations described below correspond to various embodiments described above. Furthermore, the exemplary methods shown in Figures 7- 9 can be used cooperatively to provide various benefits, advantages, and/or solutions to problems described herein. Although Figures 7-9 show specific blocks in particular orders, the operations of the exemplary methods can be performed in different orders than shown and can be combined and/or divided into blocks having different functionality than shown. Optional blocks or operations are indicated by dashed lines.

In particular, Figure 7 shows an exemplary method (e.g., procedure) for CCO in a RAN, according to various embodiments of the present disclosure. The exemplary method can be performed by a first unit or function (e.g., CU or CU-CP) of a first RAN node (e.g., gNB) such as described elsewhere herein.

The exemplary method can include the operations of block 710, where the first unit or function can receive, from one or more second RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the respective second RAN nodes. The exemplary method can also include the operations of block 730, where the first unit or function can send, to one or more second units or functions of the first RAN node, indications of the one or more cells and/or beams, served by the respective second RAN nodes, that are affected by the updated coverage. The exemplary method can also include the operations of block 740, where the first unit or function can receive, from the one or more second units or functions, respective indications of corresponding coverage updates to one or more cells and/or beams served by the respective second units or functions.

• information about updated neighbor cells;

• information about updated neighbor beams;

• an identifier of the second RAN node;

In some of these embodiments, the information about updated neighbor cells includes a list of neighbor cell identifiers and one or more of the following associated with each identified neighbor cell: an updated cell coverage state, or an updated cell coverage index. In some of these embodiments, the information about updated neighbor beams includes a list of neighbor beam identifiers and one or more of the following associated with each identified neighbor beam: an updated beam coverage state, or an updated beam coverage index. In some of these embodiments, the indicated one or more actions include any of the following: CCO issue detection, CCO issue resolution, network energy savings, mobility optimization, quality-of-service (QoS) optimization, and quality-of-experience (QoE) optimization. In some of these embodiments, the indicated one or more cause values include any of the following: CCO issue detection, CCO issue resolution, poor coverage, cell edge capacity, uplink-downlink imbalance, energy-saving, cell deactivation, coverage reduction, cell reactivation, and cell modification.

In some of these embodiments, the exemplary method can also include the operations of block 720, where the first unit or function can determine each indication sent to the one or more second units or functions (e.g., in block 730) based on neighbor information about updated coverage received from one of the second RAN nodes (e.g., in block 710).

In some variants of these embodiments, each indication sent in block 730 can include one or more of the following, determined based on neighbor information about updated coverage received from one of the second RAN nodes:

• at least a portion of the information about updated neighbor cells;

• a result of a function of the information about updated neighbor cells;

• at least a portion of the information about updated neighbor beams;

• a result of a function of the information about updated neighbor beams;

• the indication of one or more second RAN node coverage states;

• the identifier of the second RAN node;

• the indication of one or more actions that produced the updated coverage by the second RAN node;

• the one or more cause values;

• number or portion of cells affected by the actions of the second RAN node; and

• number or portion of beams affected by the actions of the second RAN node.

In some further variants of these embodiments, each indication sent to a second unit or function in block 730 also includes a number (i.e., quantity) of second RAN nodes from which the first unit or function received neighbor information about updated coverage.

In some embodiments, each indication of corresponding coverage updates (e.g., received in block 740) includes one or more of the following in relation to the corresponding second unit or function: an indication of whether a corresponding coverage update was applied by the second unit or function; • an indication of one or more corresponding coverage updates that were applied by the second unit or function;

• a cause value indicating a reason why a corresponding coverage update was not applied by the second unit or function.

In some embodiments, the indications of corresponding coverage updates are received from a plurality of second units or functions and the exemplary method also include the operations of block 760, where the first unit or function sends each indication of corresponding coverage updates received from one of the second units or functions to all other of the second units or functions.

In some embodiments, the exemplary method can also include the operations of block 750, where the first unit or function can send, to the one or more second RAN nodes, respective indications of corresponding coverage updates made by the first RAN node based on the neighbor information about updated coverage received from the respective second RAN nodes. In some of these embodiments, each indication of corresponding coverage updates made by the first RAN node includes one or more of the following:

In some embodiments, the second unit or function is a DU and first unit or function is a CU or a CU-CP.

In addition, Figure 8 shows another exemplary method (e.g., procedure) for CCO in a RAN, according to various embodiments of the present disclosure. The exemplary method can be performed by a second unit or function (e.g., DU) of a first RAN node (e.g., gNB) such as described elsewhere herein. The exemplary method can include the operations of block 810, where the second unit or function can receive, from a first unit or function of the first RAN node, indications of one or more cells and/or beams, served by one or more second RAN nodes, that are affected by updated coverage. The exemplary method can also include the operations of block 820, where based on the indications of the one or more cells and/or beams affected by updated coverage, the second unit or function can selectively apply corresponding coverage updates to one or more cells and/or beams served by the second unit or function. The exemplary method can also include the operations of block 830, where the second unit can send, to the first unit or function, an indication of corresponding coverage updates to one or more cells and/or beams served by the second unit or function.

In some embodiments, the selectively applying operations of block 820 can include the following operations labelled with corresponding sub-block numbers:

• (821) determining whether corresponding coverage updates to one or more cells and/or beams served by the second unit or function are necessary;

• (822) determining whether corresponding coverage updates to one or more cells and/or beams served by the second unit or function are feasible; and

• (823) when at least one corresponding coverage update is determined to be necessary and feasible, applying a necessary and feasible corresponding coverage update to one or more cells and/or beams served by the second unit or function.

In some of these embodiments, the selectively applying operations of block 820 can also include the operations of sub-block 824, where the second unit or function can refrain from applying corresponding coverage updates to the one or more cells and/or beams served by the second unit or function, when no corresponding coverage updates are determined to be necessary and feasible (e.g., in sub-blocks 821-822).

In various embodiments, each indication received in block 810 can include any of the information discussed above in relation to embodiments of the first unit or function of the first RAN node.

In some embodiments, the indication of corresponding coverage updates (e.g., sent in block 830) includes one or more of the following:

• an indication that the second unit or function determined that no corresponding coverage update was necessary; • an indication that the second unit or function determined that no corresponding coverage update was feasible; and

For example, these indications and cause values can be based on the result of the determinations made during selective application of corresponding coverage updates in block 820.

In some embodiments, the exemplary method can also include the operations of block 840, where the second unit or function can receive, from the first unit or function, respective indications of corresponding coverage updates by one or more other second units or functions of the first RAN node. In some variants, the second unit or function can consider these indications during selective application of its own coverage updates (e.g., in block 820).

In addition, Figure 9 shows another exemplary method (e.g., procedure) for CCO in a RAN, according to various embodiments of the present disclosure. The exemplary method can be performed by a second RAN node (e.g., base station, eNB, gNB, ng-eNB, etc.) such as described elsewhere herein.

The exemplary method can include the operations of block 910, where the second RAN node can send, to respective first units or functions of one or more first RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the second RAN node. The exemplary method can also include the operations of block 920, where the second RAN node can receive, from the respective first units or functions, indications of corresponding coverage updates made by the respective first RAN nodes based on the neighbor information about updated coverage.

In various embodiments, the neighbor information about updated coverage (e.g., sent in block 910) can include any of the information and/or contents discussed above in relation to embodiments of the first unit or function of the first RAN node. In various embodiments, each indication of corresponding coverage updates made by a first RAN node (e.g., received in block 920) can include any of the information and/or contents discussed above in relation to embodiments of the first unit or function of the first RAN node.

In some embodiments, each first unit or function is a CU or a CU-CP.

Although various embodiments are described above in terms of methods, techniques, and/or procedures, the person of ordinary skill will readily comprehend that such methods, techniques, and/or procedures can be embodied by various combinations of hardware and software in various systems, communication devices, computing devices, control devices, apparatuses, non-transitory computer-readable media, computer program products, etc.

Figure 10 shows an example of a communication system 1000 in accordance with some embodiments. In this example, communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a radio access network (RAN), and a core network 1006, which includes one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes lOlOa-b (one or more of which may be generally referred to as network nodes 1010), or any other similar 3 GPP access node or non-3GPP access point. The network nodes 1010 facilitate direct or indirect connection of UEs, such as by connecting UEs 1012a-d (one or more of which may be generally referred to as UEs 1012) to core network 1006 over one or more wireless connections.

Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1000 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1000 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

UEs 1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1010 and other communication devices. Similarly, network nodes 1010 are arranged, capable, configured, and/or operable to communicate directly or indirectly with UEs 1012 and/or with other network nodes or equipment in telecommunication network 1002 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in telecommunication network 1002.

In the depicted example, core network 1006 connects network nodes 1010 to one or more hosts, such as host 1016. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. Core network 1006 includes one more core network nodes (e.g., core network node 1008) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1008. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

Host 1016 may be under the ownership or control of a service provider other than an operator or provider of access network 1004 and/or telecommunication network 1002, and may be operated by the service provider or on behalf of the service provider. Host 1016 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

As a whole, communication system 1000 of Figure 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

In some examples, telecommunication network 1002 is a cellular network that implements 3GPP standardized features. Accordingly, telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to telecommunication network 1002. For example, telecommunications network 1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

In some examples, UEs 1012 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to access network 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from access network 1004. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example, hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012c and/or 1012d) and network nodes (e.g., network node 1010b). In some examples, the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs. As another example, hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1010, or by executable code, script, process, or other instructions in hub 1014. As another example, hub 1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, hub 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which hub 1014 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, hub 1014 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

Hub 1014 may have a constant/persistent or intermittent connection to the network node 1010b. Hub 1014 may also allow for a different communication scheme and/or schedule between hub 1014 and UEs (e.g., UE 1012c and/or 1012d), and between hub 1014 and core network 1006. In other examples, hub 1014 is connected to core network 1006 and/or one or more UEs via a wired connection. Moreover, hub 1014 may be configured to connect to an M2M service provider over access network 1004 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with network nodes 1010 while still connected via hub 1014 via a wired or wireless connection. In some embodiments, hub 1014 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to network node 1010b. In other embodiments, hub 1014 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between UEs and network node 1010b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 11 shows a UE 1100 in accordance with some embodiments. Examples of UEs include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by 3 GPP, including a narrow band internet of things (NB-IoT) LIE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

UE 1100 includes processing circuitry 1102 that is operatively coupled via bus 1104 to input/output interface 1106, power source 1108, memory 1110, communication interface 1112, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

Processing circuitry 1102 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in memory 1110. Processing circuitry 1102 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general -purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, processing circuitry 1102 may include multiple central processing units (CPUs).

In the example, input/output interface 1106 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into UE 1100. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, power source 1108 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. Power source 1108 may further include power circuitry for delivering power from power source 1108 itself, and/or an external power source, to the various parts of UE 1100 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of power source 1108. Power circuitry may perform any formatting, converting, or other modification to the power from power source 1108 to make the power suitable for the respective components of UE 1100 to which power is supplied.

Memory 1110 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, memory 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116. Memory 1110 may store, for use by UE 1100, any of a variety of various operating systems or combinations of operating systems.

Memory 1110 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ Memory 1110 may allow the UE 1100 to access instructions, application programs and the like, stored on transitory or non- transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in memory 1110, which may be or comprise a device-readable storage medium.

Processing circuitry 1102 may be configured to communicate with an access network or other network using communication interface 1112. Communication interface 1112 may comprise one or more communication subsystems and may include or be communicatively coupled to antenna 1122. Communication interface 1112 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include transmitter 1118 and/or receiver 1120 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, transmitter 1118 and receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of communication interface 1112 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1112, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., an alert is sent when moisture is detected), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 1100 shown in Figure 11.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and/or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. Figure 12 shows a network node 1200 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).

Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and/or Minimization of Drive Tests (MDTs).

Network node 1200 includes processing circuitry 1202, memory 1204, communication interface 1206, and power source 1208. Network node 1200 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 1200 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1200 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., same antenna may be shared by different RATs). Network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1200.

Processing circuitry 1202 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1200 components, such as memory 1204, to provide network node 1200 functionality.

In some embodiments, processing circuitry 1202 includes a system on a chip (SOC). In some embodiments, processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214. In some embodiments, RF transceiver circuitry 1212 and baseband processing circuitry 1214 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1212 and baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units.

Memory 1204 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 1202. Memory 1204 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions (collectively denoted computer program product 1204a) capable of being executed by processing circuitry 1202 and utilized by network node 1200. Memory 1204 may be used to store any calculations made by processing circuitry 1202 and/or any data received via communication interface 1206. In some embodiments, processing circuitry 1202 and memory 1204 are integrated.

Communication interface 1206 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1206 comprises port(s)/terminal(s) 1216 to send and receive data, for example to and from a network over a wired connection. Communication interface 1206 also includes radio front-end circuitry 1218 that may be coupled to, or in certain embodiments a part of, the antenna 1210. Radio front-end circuitry 1218 comprises filters 1220 and amplifiers 1222. Radio front-end circuitry 1218 may be connected to antenna 1210 and processing circuitry 1202. Radio front-end circuitry may be configured to condition signals communicated between antenna 1210 and processing circuitry 1202. Radio front-end circuitry 1218 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1218 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1220 and/or amplifiers 1222. The radio signal may then be transmitted via antenna 1210. Similarly, when receiving data, antenna 1210 may collect radio signals which are then converted into digital data by radio front-end circuitry 1218. The digital data may be passed to processing circuitry 1202. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 1200 does not include separate radio front-end circuitry 1218, instead, processing circuitry 1202 includes radio front-end circuitry and is connected to antenna 1210. Similarly, in some embodiments, all or some of RF transceiver circuitry 1212 is part of communication interface 1206. In still other embodiments, communication interface 1206 includes one or more ports or terminals 1216, radio front-end circuitry 1218, and RF transceiver circuitry 1212, as part of a radio unit (not shown), and communication interface 1206 communicates with baseband processing circuitry 1214, which is part of a digital unit (not shown).

Antenna 1210 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 1210 may be coupled to radio front-end circuitry 1218 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, antenna 1210 is separate from the network node 1200 and connectable to network node 1200 through an interface or port.

Antenna 1210, communication interface 1206, and/or processing circuitry 1202 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, antenna 1210, communication interface 1206, and/or processing circuitry 1202 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

Power source 1208 provides power to the various components of network node 1200 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 1208 may further comprise, or be coupled to, power management circuitry to supply the components of network node 1200 with power for performing the functionality described herein. For example, network node 1200 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of power source 1208. As a further example, the power source 1208 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of network node 1200 may include additional components beyond those shown in Figure 12 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 1200 may include user interface equipment to allow input of information into network node 1200 and to allow output of information from network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 1200.

Figure 13 is a block diagram of a host 1300, which may be an embodiment of host 1016 of Figure 10, in accordance with various aspects described herein. As used herein, host 1300 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. Host 1300 may provide one or more services to one or more UEs.

Host 1300ncludes processing circuitry 1302 that is operatively coupled via bus 1304 to input/ output interface 1306, network interface 1308, power source 1310, and memory 1312. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host 1300.

Memory 1312 may include one or more computer programs including one or more host application programs 1314 and data 1316, which may include user data, e.g., data generated by a UE for host 1300 or data generated by host 1300 for a UE. Embodiments of host 1300 may utilize only a subset or all of the components shown. Host application programs 1314 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). Host application programs 1314 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, host 1300 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1314 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

Figure 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

Applications 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 1404 includes processing circuitry, memory that stores software and/or instructions (collectively denoted computer program product 1404a) executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408a and 1408b (one or more of which may be generally referred to as VMs 1408), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. Virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to VMs 1408.

VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each VM 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1408 on top of hardware 1404 and corresponds to application 1402.

Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402. In some embodiments, hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of control system 1412 which may alternatively be used for communication between hardware nodes and radio units.

Figure 15 shows a communication diagram of a host 1502 communicating via a network node 1504 with a UE 1506 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1012a of Figure 10 and/or UE 1100 of Figure 11), network node (such as network node 1010a of Figure 10 and/or network node 1200 of Figure 12), and host (such as host 1016 of Figure 10 and/or host 1300 of Figure 13) discussed in the preceding paragraphs will now be described with reference to Figure 15.

Like host 1300, embodiments of host 1502 include hardware, such as a communication interface, processing circuitry, and memory. Host 1502 also includes software, which is stored in or accessible by host 1502 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as UE 1506 connecting via an over-the-top (OTT) connection 1550 extending between UE 1506 and host 1502. In providing the service to the remote user, a host application may provide user data which is transmitted using OTT connection 1550.

Network node 1504 includes hardware enabling it to communicate with the host 1502 and UE 1506. Connection 1560 may be direct or pass through a core network (like core network 1006 of Figure 10) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

UE 1506 includes hardware and software, which is stored in or accessible by UE 1506 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1506 with the support of host 1502. In host 1502, an executing host application may communicate with the executing client application via OTT connection 1550 terminating at UE 1506 and host 1502. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. OTT connection 1550 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through OTT connection 1550.

OTT connection 1550 may extend via a connection 1560 between host 1502 and network node 1504 and via a wireless connection 1570 between network node 1504 and UE 1506 to provide the connection between host 1502 and UE 1506. Connection 1560 and wireless connection 1570, over which OTT connection 1550 may be provided, have been drawn abstractly to illustrate the communication between host 1502 and UE 1506 via network node 1504, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via OTT connection 1550, in step 1508, host 1502 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with UE 1506. In other embodiments, the user data is associated with a UE 1506 that shares data with host 1502 without explicit human interaction. In step 1510, host 1502 initiates a transmission carrying the user data towards UE 1506. Host 1502 may initiate the transmission responsive to a request transmitted by UE 1506. The request may be caused by human interaction with UE 1506 or by operation of the client application executing on UE 1506. The transmission may pass via network node 1504, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1512, network node 1504 transmits to UE 1506 the user data that was carried in the transmission that host 1502 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1514, UE 1506 receives the user data carried in the transmission, which may be performed by a client application executed on UE 1506 associated with the host application executed by host 1502.

In some examples, UE 1506 executes a client application which provides user data to host 1502. The user data may be provided in reaction or response to the data received from host 1502. Accordingly, in step 1516, UE 1506 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of UE 1506. Regardless of the specific manner in which the user data was provided, UE 1506 initiates, in step 1518, transmission of the user data towards host 1502 via network node 1504. In step 1520, in accordance with the teachings of the embodiments described throughout this disclosure, network node 1504 receives user data from UE 1506 and initiates transmission of the received user data towards the host 1502. In step 1522, host 1502 receives the user data carried in the transmission initiated by UE 1506.

One or more of the various embodiments improve the performance of OTT services provided to the 1506 using OTT connection 1550, in which wireless connection 1570 forms the last segment. More precisely, embodiments can enable multiple RAN nodes to coordinate cell/beam coverage to facilitate improved and/or optimal coverage and capacity in their overall coverage area. In this manner, embodiments facilitate a RAN distributed architecture solution wherein coverage updates for one or more cells and/or beams of different RAN nodes can be coordinated. In this manner, embodiments can improve various RAN optimization scenarios or use cases such as CCO, network energy saving, QoS optimization, QoE optimization, etc. Accordingly, OTT services will experience improved performance when using a RAN optimized in this manner, which increases the value of such OTT services to end users and service providers.

In an example scenario, factory status information may be collected and analyzed by host 1502. As another example, host 1502 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, host 1502 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, host 1502 may store surveillance video uploaded by a UE. As another example, host 1502 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, host 1502 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 1550 between host 1502 and UE 1506, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of host 1502 and/or UE 1506. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which OTT connection 1550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above or by supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of OTT connection 1550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of network node 1504. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by host 1502. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 1550 while monitoring propagation times, errors, etc.

The foregoing merely illustrates the principles of the disclosure. Various modifications and alterations to the described embodiments will be apparent to those skilled in the art in view of the teachings herein. It will thus be appreciated that those skilled in the art will be able to devise numerous systems, arrangements, and procedures that, although not explicitly shown or described herein, embody the principles of the disclosure and can be thus within the spirit and scope of the disclosure. Various embodiments can be used together with one another, as well as interchangeably therewith, as should be understood by those having ordinary skill in the art.

The term unit, as used herein, can have conventional meaning in the field of electronics, electrical devices and/or electronic devices and can include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

As described herein, device and/or apparatus can be represented by a semiconductor chip, a chipset, or a (hardware) module comprising such chip or chipset; this, however, does not exclude the possibility that a functionality of a device or apparatus, instead of being hardware implemented, be implemented as a software module such as a computer program or a computer program product comprising executable software code portions for execution or being run on a processor. Furthermore, functionality of a device or apparatus can be implemented by any combination of hardware and software. A device or apparatus can also be regarded as an assembly of multiple devices and/or apparatuses, whether functionally in cooperation with or independently of each other. Moreover, devices and apparatuses can be implemented in a distributed fashion throughout a system, so long as the functionality of the device or apparatus is preserved. Such and similar principles are considered as known to a skilled person.

Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

In addition, certain terms used in the present disclosure, including the specification and drawings, can be used synonymously in certain instances (e.g., “data” and “information”). It should be understood, that although these terms (and/or other terms that can be synonymous to one another) can be used synonymously herein, there can be instances when such words can be intended to not be used synonymously. Further, to the extent that the prior art knowledge has not been explicitly incorporated by reference herein above, it is explicitly incorporated herein in its entirety. All publications referenced are incorporated herein by reference in their entireties. Embodiments of the techniques and apparatus described herein also include, but are not limited to, the following enumerated examples:

Al . A method for coverage and capacity optimization (CCO) in a radio access network (RAN), the method being performed by a first unit or function of a first RAN node and comprising: receiving, from one or more second RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the respective second RAN nodes; sending, to one or more second units or functions of the first RAN node, indications of neighbor coverage update, related to the updated coverage in the one or more cells and/or beams served by the respective second RAN nodes; and receiving, from the one or more second units or functions, respective indications of corresponding coverage updates to one or more cells and/or beams served by the respective second units or functions.

A2. The method of embodiment Al, further comprising determining the indications of neighbor coverage update, sent to the respective second units, based on the neighbor information about updated coverage received from the respective second RAN nodes.

A3. The method of any of embodiments A1-A2, wherein the neighbor information about updated coverage received from each of the second RAN nodes includes one or more of the following: information about updated neighbor cells; information about updated neighbor beams; indication of one or more second RAN node coverage states that are independent of specific neighbor cells or neighbor beams; an identifier of the second RAN node; indication of one or more actions that produced the updated coverage by the second RAN node; and one or more cause values indicating corresponding reasons for the one or more actions.

A4. The method of embodiment A3, wherein the information about updated neighbor cells includes a list of neighbor cell identifiers and one or more of the following associated with each identified neighbor cell: an updated cell coverage state, or an updated cell coverage index.

A5. The method of any of embodiments A3-A4, wherein the information about updated neighbor beams includes a list of neighbor beam identifiers and one or more of the following associated with each identified neighbor beam: an updated beam coverage state, or an updated beam coverage index.

A6. The method of any of embodiments A3-A5, wherein the indicated one or more actions include any of the following: CCO issue detection, CCO issue resolution, network energy savings, mobility optimization, quality-of-service (QoS) optimization, and quality-of- experience (QoE) optimization.

A7. The method of any of embodiments A3-A6, wherein the indicated one or more cause values include any of the following: CCO issue detection, CCO issue resolution, poor coverage, cell edge capacity, uplink-downlink imbalance, energy-saving, cell deactivation, coverage reduction, cell reactivation, and cell modification.

A8. The method of any of embodiment A3-A7, wherein each indication of neighbor coverage update includes one or more of the following relating to the corresponding second RAN node: at least a portion of the information about updated neighbor cells; a result of a function of the information about updated neighbor cells; at least a portion of the information about updated neighbor beams; a result of a function of the information about updated neighbor beams; the indication of one or more second RAN node coverage states; the identifier of the second RAN node; the indication of one or more actions that produced the updated coverage by the second RAN node; the one or more cause values; number or portion of cells affected by the actions of the second RAN node; and number or portion of beams affected by the actions of the second RAN node.

A9. The method of embodiment A8, wherein the indications of neighbor coverage update also includes a number of second RAN nodes from which the first unit or function received neighbor information about updated coverage. A10. The method of any of embodiments A1-A9, wherein each indication of corresponding coverage updates includes one or more of the following in relation to the corresponding second unit or function: an indication of whether a corresponding coverage update was applied by the second unit or function; an indication of one or more corresponding coverage updates that were applied by the second unit or function; an indication that no corresponding coverage updates by the second unit or function are needed; an indication that no corresponding coverage update was feasible; and a cause value indicating a reason why a corresponding coverage update was not applied by the second unit or function.

Al l. The method of any of embodiments A1-A10, wherein: the indications of corresponding coverage updates are received from a plurality of second units or functions; and the method further comprises sending each indication of corresponding coverage updates received one of the second units or functions to all others of the second units or functions.

A12. The method of any of embodiments Al-Al l, further comprising sending, to the one or more second RAN nodes, respective indications of corresponding coverage updates made by the first RAN node based on the neighbor information about updated coverage received from the respective second RAN nodes.

A13. The method of any of embodiments A1-A12, wherein each indication of corresponding coverage updates made by the first RAN node includes one or more of the following: an indication of whether a corresponding coverage update was applied by the first RAN node; an indication of one or more corresponding coverage updates that were applied by the first RAN node; an indication that no corresponding coverage updates are needed to any cells and/or beams of the first RAN node; an indication that no corresponding coverage update was feasible to any cells and/or beams of the first RAN node; and a cause value indicating a reason why a corresponding coverage update was not applied.

A14. The method of any of embodiments A1-A13, wherein the second unit or function is a distributed unit (DU) and first unit or function is one of the following: a centralized unit (CU) or a centralized unit control plane (CU-CP).

Bl. A method for coverage and capacity optimization (CCO) in a radio access network (RAN), the method being performed by a second unit or function of a first RAN node and comprising: receiving, from a first unit or function of the first RAN node, indications of neighbor coverage updates related to the updated coverage in the one or more cells and/or beams served by one or more second RAN nodes; based on the indications of neighbor cell coverage updates, selectively applying corresponding coverage updates to one or more cells and/or beams served by the second unit or function; sending, to the first unit or function, an indication of corresponding coverage updates to one or more cells and/or beams served by the second unit or function.

B2. The method of embodiment Bl, wherein selectively applying corresponding coverage updates comprises: determining whether corresponding coverage updates to one or more cells and/or beams served by the second unit or function are necessary; when determined to be necessary, determining whether one or more corresponding coverage updates are feasible; and when determined to be feasible, applying one of the corresponding coverage updates to one or more cells and/or beams served by the second unit or function.

B3. The method of any of embodiments B1-B2, wherein each indication of neighbor coverage update includes one or more of the following relating to the corresponding second RAN node: information about updated neighbor cells; information about updated neighbor beams; indication of one or more second RAN node coverage states that are independent of specific neighbor cells or neighbor beams; an identifier of the second RAN node; indication of one or more actions that produced the updated coverage by the second RAN node; and one or more cause values indicating corresponding reasons for the one or more actions.

B4. The method of embodiment B3, wherein the information about updated neighbor cells includes a list of neighbor cell identifiers and one or more of the following associated with each identified neighbor cell: an updated cell coverage state, or an updated cell coverage index.

B5. The method of any of embodiments B3-B4, wherein the information about updated neighbor beams includes a list of neighbor beam identifiers and one or more of the following associated with each identified neighbor beam: an updated beam coverage state, or an updated beam coverage index.

B6. The method of any of embodiments B3-B5, wherein the indicated one or more actions include any of the following: CCO issue detection, CCO issue resolution, network energy savings, mobility optimization, quality-of-service (QoS) optimization, and quality-of- experience (QoE) optimization.

B7. The method of any of embodiments B3-B6, wherein the indicated one or more cause values include any of the following: CCO issue detection, CCO issue resolution, poor coverage, cell edge capacity, uplink-downlink imbalance, energy-saving, cell deactivation, coverage reduction, cell reactivation, and cell modification.

B8. The method of any of embodiment B3-B7, wherein each indication of neighbor coverage update also includes one or more of the following relating to the corresponding second RAN node: a result of a function of the information about updated neighbor cells; a result of a function of the information about updated neighbor beams; number or portion of cells affected by the actions of the second RAN node; and number or portion of beams affected by the actions of the second RAN node. B9. The method of embodiment B8, wherein the indications of neighbor coverage update also includes a number of second RAN nodes from which the first unit or function received neighbor information about updated coverage

BIO. The method of any of embodiments B1-B9, wherein the indication of corresponding coverage updates includes one or more of the following: an indication of whether a corresponding coverage update was applied by the second unit or function; an indication of one or more corresponding coverage updates that were applied by the second unit or function; an indication that no corresponding coverage updates by the second unit or function are needed; an indication that no corresponding coverage update was feasible; and a cause value indicating a reason why a corresponding coverage update was not applied by the second unit or function.

Bl 1. The method of any of embodiments Bl -BIO, further comprising receiving, from the first unit or function, respective indications of corresponding coverage updates by one or more other second units or functions of the first RAN node.

B12. The method of any of embodiments Bl-Bl 1, wherein the second unit or function is a distributed unit (DU) and first unit or function is one of the following: a centralized unit (CU) or a centralized unit control plane (CU-CP).

Cl . A method for coverage and capacity optimization (CCO) in a radio access network

(RAN), the method being performed by a second RAN node and comprising: sending, to one or more first units or functions of respective first RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the second RAN node; and receiving, from the respective first units or functions, indications of corresponding coverage updates made by the respective first RAN nodes based on the neighbor information about updated coverage.

C2. The method of embodiment Cl, wherein the neighbor information about updated coverage includes one or more of the following: information about updated neighbor cells; information about updated neighbor beams; indication of one or more second RAN node coverage states that are independent of specific neighbor cells or neighbor beams; an identifier of the second RAN node; indication of one or more actions that produced the updated coverage by the second RAN node; and one or more cause values indicating corresponding reasons for the one or more actions.

C3. The method of embodiment C2, wherein the information about updated neighbor cells includes a list of neighbor cell identifiers and one or more of the following associated with each identified neighbor cell: an updated cell coverage state, or an updated cell coverage index.

C4. The method of any of embodiments C2-C3, wherein the information about updated neighbor beams includes a list of neighbor beam identifiers and one or more of the following associated with each identified neighbor beam: an updated beam coverage state, or an updated beam coverage index.

C5. The method of any of embodiments C2-C4, wherein the indicated one or more actions include any of the following: CCO issue detection, CCO issue resolution, network energy savings, mobility optimization, quality-of-service (QoS) optimization, and quality-of- experience (QoE) optimization.

C6. The method of any of embodiments C2-C5, wherein the indicated one or more cause values include any of the following: CCO issue detection, CCO issue resolution, poor coverage, cell edge capacity, uplink-downlink imbalance, energy-saving, cell deactivation, coverage reduction, cell reactivation, and cell modification.

C7. The method of any of embodiments C1-C6, wherein each indication of corresponding coverage update includes one or more of the following related to the corresponding first RAN node: an indication of whether a corresponding coverage update was applied by the first RAN node; an indication of one or more corresponding coverage updates that were applied by the first RAN node; an indication that no corresponding coverage updates are needed to any cells and/or beams of the first RAN node; an indication that no corresponding coverage update was feasible to any cells and/or beams of the first RAN node; and a cause value indicating a reason why a corresponding coverage update was not applied.

C8. The method of any of embodiments C1-C7, wherein each first unit or function is one of the following: a centralized unit (CU) or a centralized unit control plane (CU-CP).

DI . A first unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), the first unit or function comprising: communication interface circuitry configured to communicate with one or more second RAN nodes and with one or more second units or functions of the first RAN node; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments A1-A14.

D2. A first unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), the first unit or function being further configured to perform operations corresponding to any of the methods of embodiments A1-A14.

D3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a first unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), configure the first unit or function to perform operations corresponding to any of the methods of embodiments A1-A14.

D4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a first unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), configure the first unit or function to perform operations corresponding to any of the methods of embodiments A1-A14. El . A second unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), the second unit or function comprising: communication interface circuitry configured to communicate with a first unit or function of the first RAN node; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments B1-B12.

E2. A second unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), the second unit or function being further configured to perform operations corresponding to any of the methods of embodiments B1-B12.

E3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a second unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), configure the second unit or function to perform operations corresponding to any of the methods of embodiments B1-B12.

E4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a second unit or function of a first radio access network (RAN) node configured for coverage and capacity optimization (CCO), configure the second unit or function to perform operations corresponding to any of the methods of embodiments Bl- B12.

Fl. A second radio access network (RAN) node configured for coverage and capacity optimization (CCO), the second RAN node comprising: communication interface circuitry configured to communicate with a first unit or function of a first RAN node; and processing circuitry operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to perform operations corresponding to any of the methods of embodiments C1-C8. F2. A second radio access network (RAN) node configured for coverage and capacity optimization (CCO), the second RAN node being further configured to perform operations corresponding to any of the methods of embodiments C1-C8. F3. A non-transitory, computer-readable medium storing computer-executable instructions that, when executed by processing circuitry of a second radio access network (RAN) node configured for coverage and capacity optimization (CCO), configure the second RAN node to perform operations corresponding to any of the methods of embodiments C1-C8. F4. A computer program product comprising computer-executable instructions that, when executed by processing circuitry of a second radio access network (RAN) node configured for coverage and capacity optimization (CCO), configure the second RAN node to perform operations corresponding to any of the methods of embodiments C1-C8.

Claims

1. A method for coverage and capacity optimization, CCO, in a radio access network, RAN, the method being performed by a first unit or function of a first RAN node and comprising: receiving (710), from one or more second RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the respective second RAN nodes; sending (730), to one or more second units or functions of the first RAN node, indications of the one or more cells and/or beams, served by the respective second RAN nodes, that are affected by the updated coverage; and receiving (740), from the one or more second units or functions, respective indications of corresponding coverage updates to one or more cells and/or beams served by the respective second units or functions.

2. The method of claim 1, wherein the neighbor information about updated coverage, received from each of the second RAN nodes, includes one or more of the following: information about updated neighbor cells; information about updated neighbor beams; indication of one or more second RAN node coverage states that are independent of specific neighbor cells or neighbor beams; an identifier of the second RAN node; indication of one or more actions that produced the updated coverage by the second RAN node; and one or more cause values indicating corresponding reasons for the one or more actions.

3. The method of claim 2, wherein: the information about updated neighbor cells includes a list of neighbor cell identifiers and one or more of the following associated with each identified neighbor cell: an updated cell coverage state, or an updated cell coverage index; and the information about updated neighbor beams includes a list of neighbor beam identifiers and one or more of the following associated with each identified neighbor beam: an updated beam coverage state, or an updated beam coverage index.

58

4. The method of any of claims 2-3, wherein: the indicated one or more actions include any of the following: CCO issue detection;

CCO issue resolution; network energy savings; mobility optimization; quality- of-service, QoS, optimization; and quality-of-experience, QoE, optimization; and the indicated one or more cause values include any of the following: CCO issue detection; CCO issue resolution; poor coverage; cell edge capacity; uplinkdownlink imbalance; energy-saving; cell deactivation; coverage reduction; cell reactivation; and cell modification.

5. The method of any of claims 2-4, further comprising determining (720) each indication sent to the one or more second units or functions based on neighbor information about updated coverage received from one of the second RAN nodes.

6. The method of any of claims 1-5, wherein each indication of corresponding coverage updates includes one or more of the following in relation to the corresponding second unit or function: an indication of whether a corresponding coverage update was applied by the second unit or function; an indication of one or more corresponding coverage updates that were applied by the second unit or function; an indication that the second unit or function determined that no corresponding coverage update was necessary; an indication that the second unit or function determined that no corresponding coverage update was feasible; and a cause value indicating a reason why a corresponding coverage update was not applied by the second unit or function.

7. The method of any of claims 1-6, wherein: the indications of corresponding coverage updates are received from a plurality of second units or functions; and the method further comprises sending (760) each indication of corresponding coverage updates received from one of the second units or functions to all other of the second units or functions.

59

8. The method of any of claims 1-7, further comprising sending (750), to the one or more second RAN nodes, respective indications of corresponding coverage updates made by the first RAN node based on the neighbor information about updated coverage received from the respective second RAN nodes.

9. The method of claim 8, wherein each indication of corresponding coverage updates made by the first RAN node includes one or more of the following: an indication of whether a corresponding coverage update was applied by the first RAN node; an indication of one or more corresponding coverage updates that were applied by the first RAN node; an indication that no corresponding coverage updates are necessary for cells and/or beams served by the first RAN node; an indication that no corresponding coverage updates are feasible for cells and/or beams served by the first RAN node; and a cause value indicating a reason why a corresponding coverage update was not applied.

10. The method of any of claims 1-9, wherein each second unit or function is a distributed unit, DU, and the first unit or function is one of the following: a centralized unit, CU, or a centralized unit control plane function, CU-CP.

11. A method for coverage and capacity optimization, CCO, in a radio access network, RAN, the method being performed by a second unit or function of a first RAN node and comprising: receiving (810), from a first unit or function of the first RAN node, indications of one or more cells and/or beams, served by one or more second RAN nodes, that are affected by updated coverage; based on the indications of the one or more cells and/or beams affected by updated coverage, selectively applying (820) corresponding coverage updates to one or more cells and/or beams served by the second unit or function; sending (830), to the first unit or function, an indication of corresponding coverage updates to one or more cells and/or beams served by the second unit or function.

12. The method of claim 11, wherein selectively applying (820) corresponding coverage updates comprises:

60 determining (821) whether corresponding coverage updates to one or more cells and/or beams served by the second unit or function are necessary; determining (822) whether corresponding coverage updates to one or more cells and/or beams served by the second unit or function are feasible; and when at least one corresponding coverage update is determined to be necessary and feasible, applying (823) a necessary and feasible corresponding coverage update to one or more cells and/or beams served by the second unit or function.

13. The method of claim 12, wherein selectively applying (820) corresponding coverage updates further comprises refraining (824) from applying corresponding coverage updates to the one or more cells and/or beams served by the second unit or function, when no corresponding coverage updates are determined to be necessary and feasible.

14. The method of any of claims 11-13, wherein the indication of corresponding coverage updates includes one or more of the following: an indication of whether a corresponding coverage update was applied by the second unit or function; an indication of one or more corresponding coverage updates that were applied by the second unit or function; an indication that the second unit or function determined that no corresponding coverage update was necessary; an indication that the second unit or function determined that no corresponding coverage update was feasible; and a cause value indicating a reason why a corresponding coverage update was not applied by the second unit or function.

15. The method of any of claims 11-14, further comprising receiving (840), from the first unit or function, respective indications of corresponding coverage updates by one or more other second units or functions of the first RAN node.

16. The method of any of claims 11-15, wherein the second unit or function is a distributed unit, DU, and the first unit or function is one of the following: a centralized unit, CU, or a centralized unit control plane function, CU-CP.

61

17. A method for coverage and capacity optimization, CCO, in a radio access network, RAN, the method being performed by a second RAN node and comprising: sending (910), to respective first units or functions of one or more first RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the second RAN node; and receiving (920), from the respective first units or functions, indications of corresponding coverage updates made by the respective first RAN nodes based on the neighbor information about updated coverage.

18. The method of claim 17, wherein the neighbor information about updated coverage includes one or more of the following: information about updated neighbor cells; information about updated neighbor beams; indication of one or more second RAN node coverage states that are independent of specific neighbor cells or neighbor beams; an identifier of the second RAN node; indication of one or more actions that produced the updated coverage by the second RAN node; and one or more cause values indicating corresponding reasons for the one or more actions.

19. The method of claim 18, wherein: the information about updated neighbor cells includes a list of neighbor cell identifiers and one or more of the following associated with each identified neighbor cell: an updated cell coverage state, or an updated cell coverage index; and the information about updated neighbor beams includes a list of neighbor beam identifiers and one or more of the following associated with each identified neighbor beam: an updated beam coverage state, or an updated beam coverage index.

20. The method of any of claims 18-19, wherein: the indicated one or more actions include any of the following: CCO issue detection; CCO issue resolution; network energy savings; mobility optimization; quality- of-service, QoS, optimization, and quality-of-experience, QoE, optimization; and

62 the indicated one or more cause values include any of the following: CCO issue detection; CCO issue resolution; poor coverage; cell edge capacity; uplinkdownlink imbalance; energy-saving; cell deactivation; coverage reduction; cell reactivation; and cell modification.

21. The method of any of claims 17-20, wherein each indication of corresponding coverage update includes one or more of the following related to the corresponding first RAN node: an indication of whether a corresponding coverage update was applied by the first RAN node; an indication of one or more corresponding coverage updates that were applied by the first RAN node; an indication that no corresponding coverage updates are necessary for cells and/or beams served by the first RAN node; an indication that no corresponding coverage updates are feasible for cells and/or beams served by the first RAN node; and a cause value indicating a reason why a corresponding coverage update was not applied.

22. The method of any of claims 17-21, wherein each first unit or function is one of the following: a centralized unit, CU, or a centralized unit control plane function, CU-CP.

23. A first unit or function (110, 482, 582, 682) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, the first unit or function comprising: communication interface circuitry (1206, 1404) configured to communicate with one or more second RAN nodes (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504) and with one or more second units or functions (120, 130, 484, 584, 684) of the first RAN node; and processing circuitry (1202, 1404) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: receive, from the one or more second RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the respective second RAN nodes; send, to the one or more second units or functions of the first RAN node, indications of the one or more cells and/or beams, served by the respective second RAN nodes, that are affected by the updated coverage; and receive, from the one or more second units or functions, respective indications of corresponding coverage updates to one or more cells and/or beams served by the respective second units or functions.

24. The first unit or function of claim 23, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 2-10.

25. A first unit or function (110, 482, 582, 682) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, the first unit or function being further configured to: receive, from one or more second RAN nodes (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504), neighbor information about updated coverage in one or more cells and/or beams served by the respective second RAN nodes; send, to the one or more second units or functions (120, 130, 484, 584, 684) of the first RAN node, indications of the one or more cells and/or beams, served by the respective second RAN nodes, that are affected by the updated coverage; and receive, from the one or more second units or functions, respective indications of corresponding coverage updates to one or more cells and/or beams served by the respective second units or functions.

26. The first unit or function of claim 25, being further configured to perform operations corresponding to any of the methods of claims 2-10.

27. A non-transitory, computer-readable medium (1204, 1404) storing computer-executable instructions that, when executed by processing circuitry (1202, 1404) of a first unit or function (110, 482, 582, 682) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, configure the first unit or function to perform operations corresponding to any of the methods of claims 1-10.

28. A computer program product (1204a, 1404a) comprising computer-executable instructions that, when executed by processing circuitry (1202, 1404) of a first unit or function (110, 482, 582, 682) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, configure the first unit or function to perform operations corresponding to any of the methods of claims 1-10.

29. A second unit or function (120, 130, 484, 584, 684) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, the second unit or function comprising: communication interface circuitry (1206, 1404) configured to communicate with a first unit or function (110, 482, 582, 682) of the first RAN node; and processing circuitry (1202, 1404) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: receive, from the first unit or function, indications of one or more cells and/or beams, served by one or more second RAN nodes (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504), that are affected by updated coverage; based on the indications of the one or more cells and/or beams affected by updated coverage, selectively apply corresponding coverage updates to one or more cells and/or beams served by the second unit or function; send, to the first unit or function, an indication of corresponding coverage updates to one or more cells and/or beams served by the second unit or function.

30. The second unit or function of claim 29, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 12-16.

31. A second unit or function (120, 130, 484, 584, 684) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, the second unit or function being further configured to: receive, from a first unit or function (110, 482, 582, 682) of the first RAN node, indications of one or more cells and/or beams, served by one or more second RAN nodes (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504), that are affected by updated coverage;

65 based on the indications of the one or more cells and/or beams affected by updated coverage, selectively apply corresponding coverage updates to one or more cells and/or beams served by the second unit or function; send, to the first unit or function, an indication of corresponding coverage updates to one or more cells and/or beams served by the second unit or function.

32. The second unit or function of claim 31, being further configured to perform operations corresponding to any of the methods of claims 12-16.

33. A non-transitory, computer-readable medium (1204, 1404) storing computer-executable instructions that, when executed by processing circuitry (1202, 1404) of a second unit or function (120, 130, 484, 584, 684) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, configure the second unit or function to perform operations corresponding to any of the methods of claims 11-16.

34. A computer program product (1204a, 1404a) comprising computer-executable instructions that, when executed by processing circuitry (1202, 1404) of a second unit or function (120, 130, 484, 584, 684) of a first radio access network, RAN, node (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, configure the second unit or function to perform operations corresponding to any of the methods of claims 11-16.

35. A second radio access network, RAN, node (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, the second RAN node comprising: communication interface circuitry (1206, 1404) configured to communicate with respective first units or functions (110, 482, 582, 682) of one or more first RAN nodes (100, 150, 210, 220, 320, 480, 580, 680, 1010, 1200, 1402, 1504); and processing circuitry (1202, 1404) operatively coupled to the communication interface circuitry, whereby the processing circuitry and the communication interface circuitry are configured to: send, to the respective first units or functions, neighbor information about updated coverage in one or more cells and/or beams served by the second RAN node; and

66 receive, from the respective first units or functions, indications of corresponding coverage updates made by the respective first RAN nodes based on the neighbor information about updated coverage.

36. The second RAN node of claim 35, wherein the processing circuitry and the communication interface circuitry are further configured to perform operations corresponding to any of the methods of claims 18-22.

37. A second radio access network, RAN, node (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, the second RAN node being further configured to: send, to respective first units or functions of one or more first RAN nodes, neighbor information about updated coverage in one or more cells and/or beams served by the second RAN node; and receive, from the respective first units or functions, indications of corresponding coverage updates made by the respective first RAN nodes based on the neighbor information about updated coverage.

38. The second RAN node of claim 37, being further configured to perform operations corresponding to any of the methods of claims 18-22.

39. A non-transitory, computer-readable medium (1204, 1404) storing computer-executable instructions that, when executed by processing circuitry (1202, 1404) of a second radio access network, RAN, node (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, configure the second RAN node to perform operations corresponding to any of the methods of claims 17-22.

40. A computer program product (1204a, 1404a) comprising computer-executable instructions that, when executed by processing circuitry (1202, 1404) of a second radio access network, RAN, node (100, 150, 210, 220, 320, 490, 590, 690, 1010, 1200, 1402, 1504) configured for coverage and capacity optimization, CCO, configure the second RAN node to perform operations corresponding to any of the methods of claims 17-22.

67