Coexistence of legacy cco and predicted cco in multi-neighbor gnb deployment

Abstract

Embodiments of the present disclosure relate to apparatuses, methods, computer-readable storage media, and program codes for coexistence of legacy CCO and predicted CCO in multi-neighbor GNB deployment. A device can be configured to determine that a first capacity and coverage optimization CCO state is to be applied at a first network device after a time period, the first CCO state being associated with a predicted CCO issue affecting the first network device and a second network device, and determine that a second CCO state is applied at the first network device due to a CCO state change in a third network device before the first CCO state is applied. Thereafter, the device is configured to transmit, to the second network device, information about the second CCO state applied by the first network device, and an indication that the second CCO state is applied due to the CCO state change in the third network device.

Description

Technical Field

[0001] The various example embodiments generally relate to the field of wireless technology. Some example embodiments involve updating access node capacity and coverage optimization CCO-related configurations. Background Technology

[0002] In wireless networks, distributed Coverage Control Occurrence (CCO) characteristics can be used to detect, resolve, or mitigate issues related to, for example, coverage and cell edge capacity. Based on detected CCO issues, access nodes can perform dynamic cell-level and beam-level coverage configuration changes and then notify neighboring nodes of the implemented coverage configuration changes and the corresponding CCO reasons. When neighboring access nodes receive this information, they can similarly adjust their own coverage configurations by considering the CCO reasons. However, due to various reasons, the implemented coverage configuration changes may not always be optimal. Summary of the Invention

[0003] The present invention is provided to present, in a simplified form, the selection of concepts further described below in the detailed embodiments. The present invention is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0004] The exemplary embodiments of this disclosure enable the coordination of coverage and capacity optimization involving multiple access nodes. For example, based on an indication received from a second node, an update to the capacity and coverage configuration in a cell belonging to a first access node associated with a predicted CCO problem of the second access node can be performed, wherein a detected CCO problem of a third node is triggered based on that indication. This and other benefits can be realized through the features of the independent claims. Further exemplary embodiments are provided in the dependent claims, the specification, and the drawings.

[0005] According to a first aspect, a first network device is disclosed. The first network device may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first network device to at least: determine that a first capacity and coverage optimization (CCO) state will be applied to the first network device after a period of time, the first CCO state being associated with a predicted CCO problem affecting the first network device and a second network device; determine that a second CCO state is applied to the first network device due to a change in the CCO state in a third network device before the first CCO state is applied; and transmit to the second network device information relating to the second CCO state applied by the first network device, and an indication that the second CCO state is applied due to a change in the CCO state in the third network device.

[0006] According to an embodiment of the first aspect, when executed by at least one processor, the instructions cause a first network device to: determine, based on a predicted CCO problem, that a first CCO state will be applied after the time period; and transmit to a second network device information relating to the first CCO state to be applied by the first network device after the time period.

[0007] According to an embodiment of the first aspect, when executed by at least one processor, the instructions cause a first network device to: receive from a second network device information relating to: a predicted CCO problem and a CCO state to be applied by the second network device after the time period; and determine, based on the received information, a first CCO state to be applied by the first network device after the time period.

[0008] According to an embodiment of the first aspect, the first network device includes at least one of the following: an access node, or a central unit of the access node.

[0009] According to an embodiment of the first aspect, when executed by at least one processor, the instructions cause a first network device to: receive from a third network device information relating to a CCO state change performed by the third network device; determine that the information was received before the first CCO state was applied; transmit the received information and an indication that the CCO state change in the first network device is due to a CCO state change in the third network device to a distributed unit of an access node; and receive from the distributed unit of the access node information relating to a second CCO state applied at the first network device and an indication that the second CCO state was applied due to a CCO state change in the third network device.

[0010] According to an embodiment of the first aspect, the first network device further includes a distributed unit; and the instructions, when executed by at least one processor, cause the first network device to: discard a first CCO state stored in one or more of the central unit or the distributed unit based on a second CCO state applied at the first network device prior to the application of the first CCO state.

[0011] According to a second aspect, a method is disclosed. The method may include: determining, by a first network device, that a first capacity and coverage optimization (CCO) state will be applied at the first network device after a period of time, the first CCO state being associated with a predicted CCO problem affecting both the first and second network devices; determining, by the first network device, that a second CCO state is applied at the first network device due to a change in the CCO state in a third network device prior to the application of the first CCO state; and transmitting, by the first network device, information relating to the second CCO state applied by the first network device and an indication that the second CCO state is applied due to a change in the CCO state in the third network device to the second network device.

[0012] According to a third aspect, a second network device is disclosed. The second network device may include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second network device to at least: determine that a first capacity and coverage optimization (CCO) state will be applied to the second network device after a period of time, the first CCO state being associated with a predicted CCO problem affecting both the second and first network devices; receive from the first network device information relating to a CCO state change applied by the first network device, and an indication that the CCO state change is applied due to a CCO state change in a third network device; and based on the indication, determine to apply a second CCO state based on the CCO state change executed by the first network device, and discard the first CCO state to be applied to the second network device after the period of time.

[0013] According to an embodiment of the third aspect, when executed by at least one processor, the instructions cause the second network device to: determine that a time period for a first CCO state to be applied at the second network device has not yet passed; and determine to apply a second CCO state based on the fact that the time period has not yet passed.

[0014] According to an embodiment of the third aspect, when executed by at least one processor, the instructions further cause the second network device to: receive information from the third network device relating to a CCO state change applied by the third network device; and determine a second CCO state to be applied by the second network device based on the CCO state change applied by the third network device.

[0015] According to an embodiment of the third aspect, when the instructions are executed by at least one processor, the second network device further causes the second network device to determine a second CCO state to be applied by the second network device based on a CCO state change applied by the first network device.

[0016] According to an embodiment of the third aspect, the second network device includes at least one of the following: an access node, or a distributed unit of the access node.

[0017] According to an embodiment of the third aspect, an instruction is received from a first network device via a central unit of an access node, and when executed by at least one processor, the instruction also causes a second network device to: transmit to the central unit information relating to an applied second CCO state, and an instruction that the second CCO state is applied at a second network device that adopts a CCO state matching the CCO state change applied by the first network device.

[0018] According to an embodiment of the third aspect, the second network device further includes a central unit of an access node, and wherein instructions, when executed by at least one processor, cause the second network device to: receive an indication from the central unit that a second CCO state is applied to a second network device that adopts a CCO state matching a CCO state change applied by the first network device; and discard the first CCO state in response to the received indication.

[0019] According to an embodiment of the third aspect, when executed by at least one processor, the instructions cause the second network device to: receive from the first network device information relating to a CCO state to be applied by the first network device after the time period; and wherein the first CCO state is determined based on the information received from the first network device.

[0020] According to an embodiment of the third aspect, when executed by at least one processor, the instructions cause the second network device to: determine a predicted CCO problem associated with the second network device and the first network device; and determine a first CCO state based on the predicted CCO problem.

[0021] According to a fourth aspect, a method is disclosed. The method may include: a second network device determining that a first capacity and coverage optimization (CCO) state will be applied at the second network device after a period of time, the first CCO state being associated with a predicted CCO problem affecting both the second and first network devices; the second network device receiving from the first network device information relating to a CCO state change applied by the first network device, and an indication that the CCO state change is applied due to a CCO state change in a third network device; and the second network device, based on the indication, determining to apply a second CCO state based on a CCO state change performed by the first network device, and discarding the first CCO state to be applied at the second network device after the period of time.

[0022] According to a fifth aspect, an apparatus is disclosed. This apparatus may include components for performing the methods provided in the specification and / or claims according to the second or fourth aspect or any of the example embodiments thereof.

[0023] According to a sixth aspect, a computer program, computer program product, or (non-transitory) computer-readable medium is disclosed. The computer program, computer program product, or (non-transitory) computer-readable medium may include instructions that, when executed by a device, cause the device to perform at least the method as provided in the specification and / or claims according to the second or fourth aspect or any of the example embodiments thereof.

[0024] Therefore, the exemplary embodiments of this disclosure are capable of providing apparatus, methods, computer programs, computer program products, or computer-readable media for improving various aspects of CCO-related processes. Any exemplary embodiment may be combined with one or more other exemplary embodiments. These and other aspects of this disclosure will become apparent from the exemplary embodiments(s) described below. The subject matter of the independent claims is provided according to some aspects. Additional aspects are defined in the dependent claims. Attached Figure Description

[0025] The accompanying drawings illustrate exemplary embodiments. The drawings are included to provide a further understanding of the exemplary embodiments and form part of this specification. The drawings, together with the description, help to explain the exemplary embodiments. In the drawings: Figure 1 An example of a communication network including one or more access nodes is shown; Figure 2 An example of a CCO configuration change performed by an access node in a communication network is shown; Figure 3 An example of a scenario is shown where an access node is affected by the predicted CCO problem and the traditional CCO problem of different neighboring access nodes; Figure 4 Examples of signaling and operations for coverage and capacity optimization performed between access nodes according to an example embodiment are shown; Figure 5 An example scenario is shown where two access nodes are affected by a predicted CCO problem between the two access nodes and a traditional CCO problem of a third access node. Figure 6 Another example of signaling and operations for coverage and capacity optimization performed between access nodes according to an example embodiment is shown; Figure 7 An example of a method for enabling updates to capacity and coverage configurations according to an example embodiment is shown; Figure 8 An example of a method for updating capacity and coverage configuration according to an example embodiment is shown; and Figure 9 An example of a device configured to practice one or more example embodiments is shown.

[0026] In the accompanying drawings, similar reference numerals are used to indicate similar parts. Detailed Implementation

[0027] Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. The detailed description provided below, in conjunction with the drawings, is intended as a description of the examples and is not intended to represent the only form in which the examples can be constructed or utilized. This specification sets forth the functionality of the examples and the sequence of steps for constructing and operating the examples. However, the same or equivalent functionality and sequence can be implemented through different examples.

[0028] Figure 1 An example of a communication network is shown. Communication network 100 may include one or more access nodes, such as access node 102 and access node 104. Access nodes 102 and 104 may be part of a radio access network (RAN) configured to enable one or more devices, represented by UE 106 throughout this specification, to access communication services provided by a core network (not shown). Access nodes may receive configuration information from a management system (OAM - Operation & Management) (not shown). Together with communication network 100, access nodes 102 and 104, and the core network, they may be collectively referred to as the “network”. UE 106 may include user equipment, terminal devices, mobile devices, etc. UE 106 may be configured to communicate with access nodes 102 and 104 via a radio interface (which may also be referred to as an air interface). Access nodes 102 and 104 may also be referred to as network devices or network nodes. Access nodes 102 and 104 may be configured to communicate via a network interface (Xn).

[0029] The radio interface can be configured, for example, based on the 5G NR (New Radio) standard defined by the 3rd Generation Partnership Project (3GPP) or any future standard or technology (e.g., 6G). Access node 102 and access node 104 may include, for example, a 5th generation access node (gNB). The communication network 100 may include a wireless communication network or a mobile communication network, such as, for example, a cellular communication network.

[0030] In a split access node architecture, a portion of the protocol layer can be implemented at the central unit (CU) of the access node, such as the gNB-CU, which can be configured to handle upper layers of the protocol stack, such as SDAP and PDCP layers. Furthermore, the central unit can be configured to handle Radio Resource Control (RRC) operations. The central unit of the access node can be associated with one or more distributed units (DUs) of the access node (e.g., gNB-DU), for example, configured to control one or more distributed units (DUs) of the access node, which can be configured to handle lower layers of the protocol stack, such as RLC, MAC, and L1. The radio units of the distributed units (multiple units) can be configured to transmit data to / receive data from the UEs (multiple UEs) via radio interfaces. The central unit can be referred to as the central node, and the distributed units can be referred to as distributed nodes.

[0031] Apart from Figure 1 Those other than those shown or as Figure 1 As shown in the alternatives, communication network 100 may include other network functions(s), network devices(s), or protocols(s). Network devices may be configured to implement one or more network functions. Although some embodiments have been described in the context of 5G, it should be understood that embodiments of this disclosure are not limited to this example network. Therefore, the example embodiments can be applied to any current or future communication network. Apparatus (such as, for example, access node 102, access node 104) may include one or more protocol layers described herein, or be configured to implement (e.g., by means of software) one or more protocol layers described herein.

[0032] Access node 102 and access node 104 can be configured to communicate with one or more UEs 106 via one or more cells. For example, access node 102 can be configured to serve a UE in a first cell (cell 1). Access node 104 can be configured to serve a UE in a second cell (cell 2). A cell can be configured to serve a UE in a specific geographic area using a specific radio frequency or a radio frequency range around the center frequency of the cell.

[0033] Access nodes 102 and 104 can be configured to determine CCO issues based on UE radio measurements from UE 106, radio link failure (RLF) reports, and performance metrics (e.g., throughput or packet loss). In a split access node architecture, the CCO function can reside in the gNB-CU. After determining or detecting a CCO issue, access nodes 102 and 104 can autonomously switch between pre-configured coverage states. CCO detection can refer to any algorithmic estimation, prediction, or application that enables network devices (e.g., access nodes 102 and 104) to determine the existence of future CCO issues and the possible duration of CCO issues. Coverage states can be, for example, pre-configured by the operator. Coverage states can also be referred to as CCO states or coverage configurations. Coverage states can implement at least one of, for example, cell splitting, cell merging, or cell shaping. Using cell shaping, the shape of a cell or SSB beam is modified to optimize capacity at cell boundaries. Cell shaping can be performed, particularly when cells are controlled by different access nodes. For example, access node 102 may determine that access node 104 should control the reshaping of cell 1 beam 108 to reduce overlap with cell 2 beam 110.

[0034] Figure 2 An example of capacity optimization performed by an access node of communication network 100 based on an adjusted coverage configuration is illustrated. For example, access node 102 may adjust cell or SSB beam parameters in cell 1, such as beam direction or transmission power, based on a detected CCO (Cellular Cost of Operations) issue, to improve the signal quality of one or more UEs. For example, an active antenna system (AAS) may be used to perform the adjustment. Access node 102 may then notify neighboring access node 104 of the modified configuration (e.g., a reduced beam 108 for capacity optimization) and the CCO reason (e.g., “cell edge capacity”). This notification may be transmitted, for example, via XnAP signaling from the CU (Cumulative Unit) of access node 102. Access node 104 may then determine to adjust cell 2 parameters accordingly (e.g., beam 110), for example, to reduce interference, balance load, and / or ensure seamless connectivity for UE 106 at the cell edge. Adjustments can be coordinated between the two access nodes to maintain optimal performance in overlapping coverage areas.

[0035] However, access nodes may not always be able to select the optimal configuration state to mitigate coverage or capacity issues between them, especially when a coverage state change performed by one access node potentially affects the coverage or capacity of one or more other access nodes. Furthermore, in AI / ML-based CCO (Content Optimization) approaches, access nodes can be configured to identify or predict potential CCO problems in neighboring access nodes and initiate a process to coordinate with neighboring access nodes to resolve predicted CCO problems. In some scenarios, access nodes may need to be able to determine the optimal coverage state to apply when both predicted and immediate CCO problems occur within a relatively short time frame.

[0036] The CCO (Coverage Control Operator) function is designed to detect, resolve, or mitigate CCO issues. RAN nodes (e.g., gNBs) can autonomously adjust within and switch between coverage configurations. When a coverage configuration change is performed, the RAN node can notify its neighboring RAN nodes, for example, by including a list of cells and SSBs with the modified coverage.

[0037] In traditional CCO solutions, a reactive approach is used: when the gNB (gNB-CU in the case of a CU-DU split architecture) detects a CCO issue that negatively impacts network and UE performance after the CCO issue has already occurred, the gNB (gNB-DU in the case of a CU-DU split architecture) attempts to resolve or mitigate the CCO issue.

[0038] By leveraging AI / ML-based CCO, a more proactive approach can be used to prevent (or limit) CCO issues at an early stage, thereby avoiding network (and UE) performance degradation.

[0039] In this paper, the traditional CCO problem is referred to as the immediate / detected / traditional CCO problem, and the AI / ML-based CCO problem is referred to as the predicted CCO problem.

[0040] Figure 3 An example of a scenario is shown where an access node is affected by the predicted CCO problem and the conventional CCO problem of different neighboring access nodes.

[0041] At point 300, the first access node 306 can predict a CCO problem 312 between itself and the second access node 308. This prediction can be performed, for example, by the central unit of the first access node 306. The predicted problem 312 can be associated with one or more cells of the distributed units of the first access node 306 and the distributed units of the second access node 308. Based on the predicted CCO problem 312, the first access node 306 can determine that its CCO state needs to be changed after a period of time, and determine that this change will affect the second access node 308 and notify the second access node 308 of the future CCO state change. The second access node 308 can then determine that a matching coverage state needs to be applied, for example, close to the time point of the future CCO state change in the first access node 306.

[0042] However, in addition to the CCO problem predicted by the first access node 306, the third access node 310 also detects an immediate (conventional) CCO problem 314 between the first access node 306 and the third access node 310. The immediate CCO problem 314 may be related, for example, to one or more cells of the distributed units of the first access node 306 and the third access node 310.

[0043] At point 302, the first access node 306 and the third access node 310 determine to change the coverage configuration of the corresponding(s) cells(s) to resolve the immediate CCO problem 314. The predicted CCO problem 312 may also be resolved using the applied future coverage state. Alternatively, due to changes in the coverage configuration of the first access node 306 before the future coverage configuration is applied, the predicted CCO problem and the associated future coverage configuration may need to be reassessed. In other words, the predicted CCO problem 312 may no longer be relevant because the prediction was performed based on the previous coverage configuration of the first access node 306.

[0044] At point 304, the new coverage configuration is applied by the second access node 308 based on the agreed future coverage configuration. However, due to an immediate CCO issue at the third access node 310, the new coverage configuration may be incompatible with the latest coverage configuration applied by the first access node 306. This may result in a new CCO issue 316 between the first access node 306 and the second access node 308 that needs to be resolved.

[0045] The aim is to improve signaling between access nodes to avoid incompatibility of CCO states between them. In particular, incompatibility of applied CCO states can be avoided in situations where new CCO problems may occur due to immediate CCO problems detected by neighboring access nodes that are different from those previously predicted to be resolved.

[0046] According to an example embodiment, a method is provided for the coexistence of traditional CCO procedures and predicted CCO procedures in a deployment where a cell is adjacent to more than one access node (e.g., a gNB). In the example embodiment, as a result of a solution to predicted CCO issues between access nodes, an access node that sends / receives information about future CCO coverage configurations to neighboring access nodes notifies the receiving / sending access node of an update to its own coverage status. Information about the update performed can be transmitted along with an indication that the update is not due to any capacity or coverage issues in the sending node, but rather due to a problem in a third access node requiring an adaptation to the coverage status. The receiver of the indication can then determine and apply the matching coverage status and cancel the initially planned future coverage status update.

[0047] Figure 4 Examples of signaling and operations performed between access nodes for coverage and capacity optimization, according to an example embodiment, are shown. Figure 4 The signaling and operations shown can be used, for example, to resolve... Figure 3 The potential incompatibility issues are illustrated. Signaling can be performed between the first access node, the second access node, and the third access node. The first access node may include a first central unit (CU-A) 400 and a first distributed unit (DU-A) 402. The second access node may include a second central unit (CU-B) 404 and a second distributed unit (DU-B) 406. The third access node may include a third central unit (CU-C) 408 and a second distributed unit (DU-C) 410.

[0048] At point 412, the predicted CCO procedure is initiated. For example, at operation 414, CU-A 400 can predict a CCO problem between the first and second access nodes. Based on the predicted CCO problem, CU-A 400 can transmit information about the CCO problem (coverage or capacity problem), the time of the predicted CCO problem, and the affected cells and beams to DU-A 402. Based on the predicted CCO problem, DU-A 402 determines a future CCO state A1 that will be applied by the first access node during a specific time period, represented as the time for the future CCO state. This time may differ from the time for the predicted CCO problem. For example, CU-A 400 can predict that a capacity or coverage problem related to the second access node will occur after 90 seconds, and therefore DU-A 402 can determine that state A1 should be applied to increase capacity or coverage at or before 90 seconds (the time for the predicted CCO problem).

[0049] At operation 416, DU-A 402 can transmit information to CU-A 400 about when the future CCO state A1 will be applied. For example, DU-A 402 can indicate that state A1 will be applied at a predicted time or before a certain time period (e.g., 90 seconds). At operation 418, CU-A 400 can transmit information to the second access node about the predicted CCO problem, the future CCO state A1, and the specific future time when the first access node will apply CCO state A1.

[0050] The information transmitted at operation 418 can be received, for example, by CU-B 404. At operation 420, CU-B 404 can forward the received information to DU-B 406. Based on the received information, DU-B 406 can determine a future CCO state B1 that matches CCO state A1. At operation 422, DU-B 406 can transmit information related to the determined future CCO state B1 to CU-B 404. When it is determined that the CCO state of an access node matches the CCO state of another access node, this can refer to using the coverage configuration of one or more cells of the access node to match the coverage configuration of neighboring cells. These matching coverage configurations can have already been configured in the access node by the management system (OAM).

[0051] Therefore, the first and second access nodes may have already agreed to apply future CCO states A1 and B1 at a specific future time to resolve the predicted CCO problem. Subsequently, the immediate CCO problem between the first and third access nodes can occur before the future CCO states are applied.

[0052] At operation 424, an immediate CCO problem procedure is initiated. For example, at operation 426, CU-C 408 can detect an immediate CCO problem and notify DU-C 410 of the detection. At operation 428, DU-C 410 can determine and apply CCO state C1 in response to CU-C 408 to resolve the detected CCO problem. At operation 430, CU-C 408 can transmit information related to CCO state C1 applied by the third access node to CU-A 400 to resolve the detected immediate CCO problem between the first and third access nodes. At operation 432, CU-A 400 notifies DU-A 402 of the CCO state C1 applied by the third access node due to the immediate CCO problem. DU-A 402 then determines to apply a CCO state (such as state A2) that matches CCO state C1. At operation 434, DU-A 402 transmits information to CU-A 400 relating to CCO state A2, which is used to resolve the immediate CCO problem of the third access node.

[0053] At 436, potential problems arising from the simultaneous execution of processes related to predicted and immediate CCO problems between different access nodes are described. For example, problems may arise due to changes in the CCO state applied by the first access node while the future CCO state A1 is still pending application.

[0054] For example, at operation 438, the first access node may determine not to apply future CCO state A1. This may occur, for example, because the specific time for applying future CCO state A1 has not yet passed and the reassessment of the predicted CCO problem is still in progress. The reassessment of the predicted CCO problem between the first and second access nodes may be triggered by the new CCO state A1 applied by the first access node, and thus the situation between the first and second access nodes has changed relative to the current CCO state. Furthermore, the predicted CCO problem may not be reassessed due to at least one of the following: the absence of a UE in the relevant predicted CCO problem area, the lack of data available for the relevant predicted CCO problem, or the short time interval between the moment when the new CCO state A2 is applied (e.g., 60 seconds after prediction) and the specific time when future CCO state A1 should be applied (e.g., 90 seconds after prediction).

[0055] For example, when a specific time has elapsed for applying the future CCO state A1, the first access node may still be in the phase of applying the new CCO state A2, and therefore, the future CCO state A1 is not applied by the first access node as the second access node expected. However, the second access node may be unaware of the CCO state change performed by the first access node due to a CCO problem with the third access node, and that the first access node has not yet applied the previously agreed future CCO state A1.

[0056] Therefore, at operation 440, the second access node applies the future CCO state B1. This may lead to incompatible overlay configurations at both the first and second access nodes, as CCO state B1 is determined to match a CCO state A1 that the first access node has not applied. This incompatibility results in new CCO issues. Furthermore, due to the CCO state change performed by the third access node at operation 428, the CCO state B1 applied by the second access node may be incompatible with the CCO state C1 applied by the third access node.

[0057] To address this issue, at 442, a process is described for notifying the second access node of the CCO state update performed by the first access node when a detected CCO problem occurs with the third access node while the predicted CCO state is still unresolved.

[0058] In an example embodiment, at operation 444, CU-A 400 can be configured to notify DU-A 402 that a CCO state change will be performed due to an immediate CCO problem at the third access node, while a future CCO state change agreed upon with the second access node remains undecided. For example, CU-A 400 can be configured to transmit an indication to DU-A 402 at operation 446 that a CCO state change will be performed due to a CCO state change performed by the third access node, at which point the future CCO state A1 associated with the first access node remains undecided.

[0059] This indication can be configured to be triggered when the CU-A 400 notices a CCO issue for one or more cells of the DU-A and the future CCO state is pending for the corresponding cell(s). For example, the indication can be included by the CU-A 400 in a message transmitted at operation 432. In one example, the indication may include information elements regarding the reason for the performed CCO state change, referred herein as a matching coverage state indication or a matching CCO state indication. The purpose of this indication is to notify the receiver that the corresponding CCO state change is associated with a different access node for which a CCO issue has been predicted.

[0060] At operation 448, after applying a CCO state that matches the CCO state applied by the third access node, DU-A402 may respond to CU-A 400. The response may include an indication that a CCO state change has been applied due to a future CCO state change performed by the third access node if the CCO state is pending. This indication may be included in a message transmitted, for example, at operation 434. This indication may be the same as or a different indication received from CU-A 400.

[0061] At operation 450, CU-A 400 may transmit information to CU-B 404 relating to a CCO state change for A2 performed by the first access node. This information may be transmitted after operation 434 (or operation 448). This transmission may include an indication that the CCO state change was applied in response to resolve an immediate CCO problem in a neighboring cell. In this case, an indication is transmitted in response to a CCO state change for C1 performed by the third access node due to a CCO problem between the cells(s) of DU-C and the cells(s) of DU-A. This indication may include information elements such as a matching coverage state indication. Based on this indication, CU-B 404 may determine to discard the future CCO state B1. In other words, the second access node may determine that both the predicted CCO problem and the corresponding future CCO state are invalid.

[0062] In operation 452, CU-B 404 may forward the information received in operation 450 to DU-B 406. Based on the received information, at operation 454, DU-B 406 may determine and apply CCO state B2 to match CCO state A2 applied by the first access node. Furthermore, DU-B 406 determines to discard the previously stored future CCO state B1 based on an indication included in the received information. Before applying the new (B2) CCO state, DU-B 406 may determine that the time period for applying the future CCO state B1 has not yet expired. When an indication forwarded by CU-B 404 is received and the time period has not yet expired, DU-B 406 may determine to apply CCO state B2. At operation 456, DU-B 406 may transmit the determined CCO state B2, along with an indication that CCO state B2 is applied to match CCO state A2 (i.e., due to a CCO problem detected between the first and third access nodes), to CU-B 404.

[0063] Figure 5 An example scenario is shown where two access nodes are affected by a predicted CCO problem between the two access nodes and a conventional CCO problem of a third access node.

[0064] One of the access nodes (such as the first access node 306) may have predicted the CCO problem between the first access node 306 and the second access node 308. In the case of a split access node architecture, prediction can be performed by the central unit of the first access node 306 based on the coverage configuration applied by the distributed units of the first access node 306 and the second access node 308.

[0065] In addition to the predicted CCO problem 312, the third access node 310 may have detected an immediate CCO problem between the cells of the first access node 306, the second access node 308, and the third access node 310. Therefore, when at least one of the first access node 306 or the second access node 308 applies a new coverage configuration to resolve the immediate CCO problem 502 of the third access node 310, the previously performed prediction may no longer be valid. However, due to the CCO problem 502 of the third access node 310, the first access node 306 and the second access node 308 may be unaware of the coverage configuration update performed by the other access node.

[0066] Figure 6 Another example of signaling and operations performed between access nodes for coverage and capacity optimization, according to an example embodiment, is shown. Figure 6 The signaling and operations shown can be used, for example, to resolve... Figure 5The potential incompatibility issues are illustrated. Signaling can be performed between a first access node, a second access node, and a third access node, wherein the first access node includes a first central unit 400 and a first distributed unit 402, the second access node includes a second central unit 404 and a second centralized unit 406, and the third access node includes a third central unit 408 and a third centralized unit 410.

[0067] At point 412, the predicted CCO procedure is initiated. For example, CU-A 400 can predict the CCO issue between the first and second access nodes. Based on the predicted CCO issue, the first and second access nodes can agree that future CCO states (such as CCO state A1 and CCO state B1) will be applied by the respective access nodes at a specific time in the future (such as after a specific time period). The signaling and operations performed by the first and second access nodes during the process at 412 can correspond to... Figure 4 Operations 414, 416, 418, 420, and 422 are described in the text.

[0068] At operation 602, the immediate CCO procedure is executed. For example, at operation 426, CU-C 408 can detect an immediate CCO problem and notify DU-C 410 of the detection. At operation 428, DU-C 410 can determine and apply CCO state C1 in response to CU-C 408 to resolve the detected CCO problem. Here, the immediate CCO problem can exist between the third access node and both the first and second access nodes. Therefore, the third access node can determine and notify both the first and second access nodes of the detected CCO problem via CU-C 408.

[0069] At operation 430, CU-C 408 can transmit information to CU-A 400 regarding the CCO state C1 applied by the third access node to resolve a detected immediate CCO problem between the first and third access nodes. At operation 432, CU-A 400 notifies DU-A 402 of the CCO state C1 applied by the third access node due to the immediate CCO problem. DU-A 402 then determines to apply a CCO state A2 that matches CCO state C1. At operation 434, DU-A 402 transmits an indication to CU-A 400 that CCO state A2 is applied to resolve the immediate CCO problem of the third access node.

[0070] At operation 604, CU-C 408 can transmit information to CU-B 404 regarding the CCO state C1 applied by the third access node to resolve an immediate CCO problem detected between the second and third access nodes. At operation 606, CU-B 404 notifies DU-B 406 of the CCO state C1 applied by the third access node due to the immediate CCO problem. DU-B 406 can then determine and apply a new coverage configuration matching the CCO state C1, such as CCO state B2. At operation 608, DU-B 406 transmits an indication to CU-B 404 that CCO state B2 is applied to resolve the immediate CCO problem of the third access node.

[0071] One or more problems may occur, as depicted at 610, due to a change in the CCO state applied by at least one of the first or second access nodes while the future CCO state is pending. For example, at operation 438, the first access node may determine not to apply CCO state A1. This may occur, for example, because the specific time for applying future CCO state A1 has not yet passed and a reassessment of the predicted CCO problem is still in progress. The reassessment of the predicted CCO problem between the first and second access nodes may be triggered by the new CCO state A1 applied by the first access node, and thus the situation between the first and second access nodes has changed relative to the current CCO state. Furthermore, the predicted CCO problem may not be reassessed due to at least one of the following: the absence of a UE in the relevant predicted CCO problem area, the lack of data available for the relevant predicted CCO problem, or the short time interval between the moment when the new CCO state A2 is applied and the specific time when future CCO state A1 should be applied. For example, when a specific time has passed for applying future CCO state A1, the first access node may still be in the stage of applying the new CCO state A2, and therefore, future CCO state A1 is not applied by the first access node as the second access node expected.

[0072] However, the second access node may be unaware of the CCO state change performed by the first access node due to a CCO issue with the third access node, and that the first access node has not yet applied the previously agreed future CCO state A1. Therefore, at operation 440, the second access node applies the future CCO state B1. This may result in incompatible overlay configurations at both the first and second access nodes, as CCO state B1 is determined to match a CCO state A1 that the first access node has not applied. This incompatibility may lead to new CCO issues. Furthermore, due to the CCO state change performed by the third access node at operation 428, the CCO state B1 applied by the second access node may be incompatible with the CCO state C1 applied by the third access node.

[0073] The first and second access nodes can complete the matching coverage configuration in response to a CCO state change C1 performed by the third access node at different times. Depending on which access node performs the CCO state change first, the access node can be configured to perform either procedure 612 or procedure 620.

[0074] In cases where the CCO state change is first executed by the first access node to resolve the immediate CCO problem of the third access node, the process is similar to... Figure 4 The process 442 is described herein, and therefore the descriptions of corresponding operations 444, 446, 448, 450, and 452 will not be repeated here. However, in this case, the second access node may also consider the information received from the third access node at operation 604 regarding the CCO state change C1.

[0075] For example, at operation 614, DU-B 406 can determine a CCO state that matches the current CCO state of the first access node. Based on the received indication that the first access node changed the CCO state due to a CCO problem of the third access node, DU-B 406 determines to further consider previously received information related to the CCO state change performed by the third access node.

[0076] For example, DU-B 406 can determine whether CCO state B3 is compatible with both CCO state A2 and CCO state C1. If so, DU-B 406 can apply CCO state B3 at operation 616. DU-B 406 can also determine that the time period for applying future CCO state B1 has not yet passed, or that future CCO state B1 has not yet been applied. If the time period has not passed and / or future CCO state B1 has not yet been applied, DU-B 406 can determine to apply CCO state B3. Furthermore, DU-B 406 determines to discard previously stored future CCO state B1. At operation 618, DU-B 406 can transmit information related to the applied CCO state B3 to CU-B 404. The transmitted information may also include an indication that the CCO state has been changed to match the CCO state changed by the first access node due to a CCO problem at the third access node (e.g., overwrite modification reason = matching overwrite state).

[0077] In cases where a CCO state change is first performed by a second access node to resolve an immediate CCO problem at a third access node, the second access node can be configured to notify the first access node of the performed CCO state. For example, at operation 626, CU-B 404 can transmit information to CU-A 400 related to the CCO state change B2 performed by the second access node. This information may also include an indication that the CCO state change was performed due to a CCO problem at the third access node. For example, CU-B 404 may include an information element with a coverage state indication of coverage modification reason = match. At operation 628, CU-A 400 may forward the received information to DU-A 402.

[0078] At operation 630, DU-A 402 can determine a CCO state that matches the current CCO state of the second and third access nodes. For example, DU-A 402 can determine whether CCO state A3 is compatible with both CCO state B2 and CCO state C1. If so, DU-A 402 can apply CCO state A3 at operation 632. DU-A 402 can also determine whether the time period for applying future CCO state A1 has not yet expired, or whether future CCO state A1 has not yet been applied. If the time period has not expired and / or future CCO state A1 has not yet been applied, DU-A 402 can determine to apply CCO state A3. Furthermore, DU-A 402 can determine to discard previously stored future CCO state A1. At operation 634, DU-A 402 can transmit information related to the applied CCO state A3 to CU-A 400. The transmitted information may also include an indication that the CCO state has been changed to match the CCO state changed by the second access node due to a CCO problem at the third access node (e.g., Coverage Modification Reason = Matching Coverage State).

[0079] Optionally, CU-B 404 can be configured, according to procedure 620, to indicate to DU-B 406 when a detected CCO problem is associated with an access node different from a predicted CCO problem. For example, at operation 622, CU-B 404 may include an indication of information transmitted at operation 606, wherein CU-B 404 informs DU-B 406 of a detected immediate CCO problem with a third access node and a CCO state C1 applied by the third access node. Based on the received indication, DU-B 406 may determine to discard a future CCO state B1. At operation 624, DU-B 406 may also be configured to indicate to CU-B 404 that a CCO state change applied to a second access node should be performed due to a CCO state change performed by the third access node. This indication may be included in signaling, for example, performed at operation 608.

[0080] Figure 7 An example of a method 700 for enabling updates to capacity and coverage configurations according to an example embodiment is shown. Method 700 may be performed by a device (e.g., access node 102 or access node 104) or by a control device configured to control its functions when installed therein. In one example, the device may include at least a central unit of the access node.

[0081] At operation 702, the method may include determining that a first CCO state will be applied at a first network device after a period of time, the first CCO state being associated with a predicted CCO problem affecting both the first and second network devices.

[0082] At operation 704, the method may include determining that a second CCO state was applied at the first network device because the CCO state in the third network device changed before the first CCO state was applied.

[0083] At operation 706, the method may include transmitting to a second network device information relating to a second CCO state applied by the first network device, and an indication that the second CCO state is applied due to a change in the CCO state in a third network device.

[0084] In one embodiment, the method may further include determining, based on the predicted CCO problem, that a first CCO state will be applied after the time period; and transmitting to a second network device information relating to the first CCO state to be applied by the first network device after the time period.

[0085] In one embodiment, the method may include: receiving from a third network device information relating to a CCO state change performed by the third network device; determining that the information was received before a first CCO state was applied; transmitting the received information and an indication that the CCO state change in the first network device is due to a CCO state change in the third network device to a distributed unit of the access node; and receiving from the distributed unit of the access node information relating to a second CCO state applied at the first network device and an indication that the second CCO state is applied due to a CCO state change in the third network device.

[0086] In one embodiment, the first network device may further include a distributed unit of the access node, and the method may further include discarding the first CCO state stored in one or more of the central unit or the distributed unit based on a second CCO state applied at the first network device before the first CCO state is applied.

[0087] Figure 8An example of a method 800 for updating capacity and coverage configuration according to an example embodiment is shown. Method 800 may be performed by a device (e.g., access node 102 or access node 104) or by a control device configured to control its functions when installed therein. In one example, the device may include at least distributed units of the access nodes.

[0088] At operation 802, the method may include determining that a first CCO state will be applied at a second network device after a period of time, the first CCO state being associated with a predicted CCO problem affecting both the second and first network devices.

[0089] At operation 804, the method may include receiving from a first network device information relating to a CCO state change applied by the first network device, and an indication that the CCO state change is applied due to a CCO state change in a third network device.

[0090] At operation 806, the method may include, based on the instruction, determining to apply a second CCO state based on a CCO state change performed by the first network device, and discarding the first CCO state to be applied at the second network device after the time period.

[0091] In one embodiment, the method may further include determining that a time period for a first CCO state to be applied at a second network device has not yet passed; and determining to apply a second CCO state based on the fact that the time period has not yet passed.

[0092] In one embodiment, the method may include receiving information from a third network device relating to a CCO state change applied by the third network device; and determining a second CCO state to be applied by a second network device based on the CCO state change applied by the third network device.

[0093] In one embodiment, the method may include determining a second CCO state to be applied by a second network device based on a CCO state change applied by a first network device.

[0094] In one embodiment, an indication is received from a first network device via a central unit of an access node, and the method may further include transmitting to the central unit information relating to an applied second CCO state, and an indication that the second CCO state is applied at a second network device that adopts a CCO state matching the CCO state change applied by the first network device.

[0095] In one embodiment, the second network device may include a central unit of an access node, and the method may further include: receiving by the central unit an indication that a second CCO state is applied to a second network device that adopts a CCO state matching a CCO state change applied by the first network device; and discarding the first CCO state by the central unit in response to the received indication.

[0096] In one embodiment, the method may include receiving information from a first network device by a second network device relating to a CCO state to be applied by the first network device after the time period; and wherein the first CCO state is determined based on the information received from the first network device.

[0097] In an embodiment, the method may include: determining, by a second network device, a predicted CCO problem associated with the second network device and the first network device; and determining, by the second network device, a first CCO state based on the predicted CCO problem.

[0098] Other features of the method, such as those directly derived from the functionality of access node 102 and access node 104, as described throughout the description, claims, and drawings, will not be repeated here. An apparatus (e.g., a device such as an access node or a subset thereof) may be configured to perform or cause to perform any aspect of the methods(s) described herein. Furthermore, a computer program, computer program product, or (non-transitory) computer-readable medium may include instructions for causing the apparatus to perform any aspect of the methods(s) described herein when executed by the apparatus. Additionally, an apparatus may include components for performing any aspect of the methods(s) described herein. According to an example embodiment, such components include: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to perform at least any aspect of the methods(s).

[0099] Figure 9Examples of apparatuses configured to practice one or more exemplary embodiments are shown. Apparatus 900 may include devices such as access nodes (e.g., access node 102 or access node 104), base stations, access points, radio network nodes, or their subdivisions (e.g., central or distributed units of access nodes), or generally any apparatus configured to implement the functions described herein. Apparatus 900 may include at least one processor 902. At least one processor 902 may include one or more of various processing devices such as, for example, coprocessors, microprocessors, controllers, digital signal processors (DSPs), processing circuitry systems with or without an accompanying DSP, or various other processing devices including integrated circuits such as, for example, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), microcontroller units (MCUs), hardware accelerators, dedicated computer chips, etc.

[0100] The device 900 may also include at least one memory 904. Memory 904 may be configured to store, for example, computer program code, such as operating system software and application software. Memory 904 may include one or more volatile memory devices, one or more non-volatile memory devices, and / or combinations thereof. For example, memory may be embodied as a magnetic storage device (such as a hard disk drive, magnetic tape, etc.), an optical magnetic storage device, or a semiconductor memory (such as a mask ROM, PROM (programmable ROM), EPROM (erasable PROM), flash ROM, RAM (random access memory), etc.). Examples of memory 904 provided as a (non-transitory) computer-readable medium are provided. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), not a limitation on the persistence of data storage (e.g., RAM and ROM).

[0101] The device 900 may further include a communication interface 908 configured to enable the device 900 to transmit information to and / or receive information from other devices. The communication interface 908 may include an external communication interface, such as a radio interface between the UE 106 and access nodes 102 and 104, or a communication interface (e.g., an Fs-U and / or Fs-C interface) between the central unit of an access node and distributed units (e.g., an Fs-U and / or Fs-C interface). The communication interface 908 may include one or more radio transmitters or receivers that may be coupled to one or more antennas of the device 900, or configured to be coupled to one or more antennas external to the device 900.

[0102] The device 900 may also include other components and / or functions, such as a user interface (not shown) including at least one input device and / or at least one output device. The input device may take various forms, such as a keyboard, a touchscreen, or one or more embedded control buttons. The output device may include, for example, a display, a speaker, etc.

[0103] When the device 900 is configured to perform a certain function, one or more components of the device 900 (e.g., at least one processor 902 and / or at least one memory 904) may be configured to perform that function. Furthermore, when at least one processor 902 is configured to perform a certain function, that function may be implemented using, for example, program code 906 included in at least one memory 904.

[0104] The functions described herein can be performed, at least in part, by one or more computer program product components, such as software components. According to an example embodiment, device 900 includes a processor or processor circuitry, such as a microcontroller, configured by program code 906 to, when executed, perform embodiments of the operations and functions described herein. Program code 906 is provided as an example of instructions that, when executed by at least one processor 902, cause execution of device 900.

[0105] Alternatively or additionally, the functions described herein may be performed at least in part by one or more hardware logic components. For example, but not limited to, illustrative types of hardware logic components that may be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), complex programmable logic devices (CPLDs), graphics processing units (GPUs), and the like.

[0106] Apparatus 900 may be configured to perform or cause the execution of the methods(s) described herein, or may include components for performing the methods(s) described herein. In one example, the components include at least one processor 902, and at least one memory 904 includes instructions (e.g., program code 906) configured to cause apparatus 900 to perform the methods(s) when executed by at least one processor 902. Typically, computer program instructions may be executed on components that provide general processing functionality. Such components may be embedded in, for example, personal computers, smartphones, network devices, etc. Thus, the methods(s) may be implemented by a computer, for example, based on algorithms(s) executable by general processing functionality, an example of which is at least one processor 902. The components may include transmitting or receiving components, such as one or more radio transmitters or receivers, which may be coupled or configured to be coupled to one or more antennas. Although apparatus 900 is shown as a single device, it should be understood that, where applicable, the functionality of apparatus 900 may be distributed across multiple devices.

[0107] Any range or device values ​​given herein may be extended or modified without losing the desired effect. Furthermore, any embodiment may be combined with another embodiment unless expressly permitted.

[0108] Although the subject matter has been described in language specific to structural features and / or actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims, and other equivalent features and actions are intended to fall within the scope of the claims.

[0109] It should be understood that the above benefits and advantages may relate to one embodiment or several embodiments. Embodiments are not limited to embodiments that solve any or all of the described problems or that have any or all of the described benefits and advantages. It will also be understood that references to "a" may refer to one or more of those items.

[0110] The steps or operations of the methods described herein can be performed in any suitable order, or simultaneously where appropriate. Additionally, individual boxes may be removed from any method without departing from the scope of the subject matter described herein. Aspects of any of the example embodiments described above may be combined with aspects of any other example embodiments described to form further example embodiments without losing the desired effect.

[0111] The term “comprising” is used herein to mean including the identified method or box element, but such box element is not an exclusive list, and the method or apparatus may include additional boxes or elements.

[0112] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.

[0113] Although a topic may be referred to as "first" or "second" topic, this does not necessarily indicate any order or importance of the topics. Rather, such a property may be used solely for the purpose of distinguishing topics.

[0114] As used herein, the term “circuit system” may refer to one or more or all of the following: (a) a hardware circuit implementation only (such as an implementation only in analog and / or digital circuit systems), and (b) a combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog and / or digital hardware circuitry with software / firmware, and (ii) any portion of (multiple) hardware processors (including (multiple) digital signal processors), software, and (multiple) memories having software, which work together to enable a device such as a mobile phone or server to perform various functions, and (c) software (e.g., firmware) required for operation, (multiple) hardware circuitry, and / or (multiple) processors, such as (multiple) microprocessors or portions thereof, but the software may be absent when it is not required for operation. This definition of circuit system applies to all uses of the term herein (including in any claim).

[0115] As another example, as used in this application, the term "circuit system" also encompasses implementations of only hardware circuitry or processors (or processors), or a portion thereof, and its (or their) accompanying software and / or firmware. For example, and if applicable to a particular claim element, the term "circuit system" also encompasses baseband integrated circuits or processor integrated circuits for mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or network devices.

[0116] It should be understood that the above description is given by way of example only, and various modifications can be made by those skilled in the art. The above specification, examples, and data provide a complete description of the structure and use of exemplary embodiments. Although various embodiments have been described above with a degree of specificity or by reference to one or more individual embodiments, many changes can be made to the disclosed embodiments by those skilled in the art without departing from the scope of this specification.

Claims

1. A first network device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the first network device to: The first capacity and coverage optimization CCO state will be applied at the first network device after a period of time, and the first CCO state is associated with the predicted CCO problem affecting the first network device and the second network device. The second CCO state is determined to be applied at the first network device because the CCO state in the third network device changes before the first CCO state is applied. as well as Transmit to the second network device information relating to the second CCO state applied by the first network device, and an indication that the second CCO state is applied due to a change in the CCO state in the third network device.

2. The first network device according to claim 1, wherein the instructions, when executed by the at least one processor, cause the first network device to: Based on the predicted CCO problem, it is determined that the first CCO state will be applied after the said time period; and Information relating to the first CCO state to be applied by the first network device after the said time period is transmitted to the second network device.

3. The first network device according to claim 1 or 2, wherein the first network device comprises at least one of the following: an access node, or a central unit of the access node.

4. The first network device according to claim 3, wherein the instructions, when executed by the at least one processor, cause the first network device to: Receive information related to the CCO state change performed by the third network device; It is determined that the information was received before the first CCO state was applied; The received information and an indication that the change in the CCO state in the first network device is due to the change in the CCO state in the third network device are transmitted to the distributed unit of the access node. The distributed unit of the access node receives information relating to the second CCO state applied at the first network device, and an indication that the second CCO state is applied due to a change in the CCO state in the third network device.

5. The first network device of claim 3, wherein the first network device further comprises the distributed unit, and the instructions, when executed by the at least one processor, cause the first network device to: Based on the second CCO state applied at the first network device before the first CCO state is applied, the first CCO state stored at one or more of the central unit or the distributed unit is discarded.

6. A second network device for communication, comprising: At least one processor; as well as At least one memory storing instructions that, when executed by the at least one processor, cause the second network device to: A first capacity and coverage optimization (CCO) state will be applied to the second network device after a period of time, and the first CCO state is associated with a predicted CCO problem affecting the second network device and the first network device. Receive information from the first network device relating to a CCO state change applied by the first network device, and an indication that the CCO state change is applied due to a CCO state change in the third network device. as well as Based on the instruction, a second CCO state is determined to be applied based on the CCO state change performed by the first network device, and the first CCO state to be applied at the second network device is discarded after the time period.

7. The second network device of claim 6, wherein the instructions, when executed by the at least one processor, cause the second network device to: The time period for determining that the first CCO state to be applied at the second network device has not yet elapsed; and Based on the fact that the time period has not yet passed, the second CCO state is determined to be applied.

8. The second network device according to claim 6 or 7, wherein the instructions, when executed by the at least one processor, further cause the second network device to: Receive information from the third network device relating to a change in CCO state applied by the third network device; and Based on the CCO state change applied by the third network device, the second CCO state to be applied by the second network device is determined.

9. The second network device of claim 8, wherein the instructions, when executed by the at least one processor, further cause the second network device to: Based on the CCO state change applied by the first network device, the second CCO state to be applied by the second network device is determined.

10. The second network device according to claim 6 or 7, wherein the second network device comprises at least one of the following: an access node, or a distributed unit of the access node.

11. The second network device of claim 10, wherein the instruction is received from the first network device via the central unit of the access node, and the instruction, when executed by the at least one processor, further causes the second network device to: The central unit transmits information related to the applied second CCO state, as well as an indication that the second CCO state is applied at a second network device that matches the CCO state change applied by the first network device.

12. The second network device of claim 11, wherein the second network device further comprises a central unit of an access node, and wherein the instructions, when executed by at least one processor, cause the second network device to: The central unit receives the indication that the second CCO state is applied to a second network device that matches the CCO state change applied by the first network device; and The central unit discards the first CCO state in response to the received instruction.

13. The second network device according to claim 6 or 7, wherein the instructions, when executed by the at least one processor, cause the second network device to: Receive information from the first network device relating to the CCO status to be applied by the first network device after the said time period; and The first CCO state is determined based on information received from the first network device.

14. The second network device according to claim 6 or 7, wherein the instructions, when executed by the at least one processor, cause the second network device to: Determine the predicted CCO problem associated with the second network device and the first network device; and The first CCO state is determined based on the predicted CCO problem.

15. A method for communication, comprising: The first capacity and coverage optimization CCO state determined by the first network device will be applied at the first network device after a period of time. The first CCO state is associated with the predicted CCO problem affecting the first network device and the second network device. The second CCO state is determined by the first network device and applied at the first network device because the CCO state in the third network device changes before the first CCO state is applied. as well as The first network device transmits information related to the second CCO state applied by the first network device to the second network device, as well as an indication that the second CCO state is applied due to a change in the CCO state in the third network device.

16. A method for communication, comprising: The second network device determines that a first CCO state will be applied at the second network device after a period of time, and the first CCO state is associated with a predicted CCO problem affecting the second network device and the first network device; The second network device receives from the first network device information related to a CCO state change applied by the first network device, and an indication that the CCO state change is applied due to a CCO state change in the third network device; as well as Based on the indication, the second network device determines to apply a second CCO state based on the CCO state change performed by the first network device, and discards the first CCO state to be applied at the second network device after the time period.

Images