WO2022039648A1

WO2022039648A1 - Methods for signalling configuration mismatch between network nodes when reporting resource status

Info

Publication number: WO2022039648A1
Application number: PCT/SE2021/050795
Authority: WO
Inventors: Luca LUNARDI; Pablo SOLDATI
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-08-17
Filing date: 2021-08-16
Publication date: 2022-02-24

Abstract

A first Radio Access Network, RAN, node can transmit information about a first RAN configuration of the first RAN node to a second RAN node; determine a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node; and receive a resource status request message from the second RAN node after determining the second RAN configuration of the first RAN node. The resource status request message can be based on the first RAN configuration of the first RAN node. The RAN node can further transmit a resource status failure message to the second RAN node responsive to receiving the resource status request message based on the first RAN configuration. The resource status failure message can includea cause value to indicate a mismatch.

Description

METHODS FOR SIGNALLING CONFIGURATION MISMATCH BETWEEN NETWORK NODES WHEN REPORTING RESOURCE STATUS

TECHNICAL FIELD

[0001] The present disclosure relates generally to communications, and more particularly to communication methods and related devices and nodes supporting wireless communications.

BACKGROUND

[0002] FIG. 1 illustrates an example of a 5th Generation (“5G”) network (also referred to as a new radio (“NR”) network) including a network node 102 (e.g., a 5G base station (“gNB”)), multiple communication devices 104 (also referred to as user equipment (“UE”)), and a neighbor network node 106. In this example, some of the communication devices 104 are within a coverage area 112 of network node 102, some of the communication devices 104 are within a coverage area 116 of neighbor network node 106, and some of the communication devices 104 are within both coverage area 112 and coverage area 116.

[0003] FIG. 2 illustrates an example of a next generation (“NG”) (also referred to as NR) system architecture. The NG-radio access network (“RAN”) node 210 includes of a set of gNBs 220, 230 connected to the 5G core (“5GC”) network through a NG interface. Each of the gNB 220, 230 can support frequency division duplexing (“FDD”) mode, time division duplexing (“TDD”) mode or dual mode operation. Each of the gNBs 220, 230 can be interconnected through a Xn interface. Each of the gNBs 220, 230 can include a gNB-CU 222, 232 and gNB-distributed units (“DUs”) 224a-b, 232a-b. Each of the gNB-CU 222, 232 can be connected with gNB-DU 224a-b, 234a-b of their respective gNB 220, 230 by a F1 logical interface. In this example, each gNB-DU 224a- b, 234a-b is connected to only one gNB-CU 222, 232. For resiliency, a gNB-DU 224a- b, 234a-b may be connected to multiple gNB-CU by appropriate implementation. The NG, Xn, and F1 interfaces can be logical interfaces. The NG-RAN node can be layered into a radio network layer (“RNL”) and a transport network layer (“TNL”). The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) can be part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality can be specified. The TNL can provide services for user plane transport and signaling transport.

[0004] A gNB may also be connected to a long term evolution (“LTE”) base station (“eNB”) via an X2 interface. Another architectural option is that where an LTE eNB connected to the Evolved Packet Core network is connected over the X2 interface with a so called nr-gNB, the latter is a gNB not connected directly to a CN and connected via X2 to an eNB for the sole purpose of performing dual connectivity.

[0005] The architecture in FIG. 2 can be expanded by spitting one or more of the gNB-CUs 222, 232 into two entities. One gNB-CU-user plane (“UP”), which serves the user plane and hosts the packet data convergence protocol (“PDCP”) and one gNB-CU- control plane (“CP”), which serves the control plane and hosts the PDCP and radio resource control (“RRC”) protocol. A gNB-DU can host the radio link control (“RLC”)/media access control (“MAC”)/physical layer (“PHY”) protocols.

SUMMARY

[0006] According to some embodiments of inventive concepts, a method of operating a first Radio Access Network RAN node of a communication network including a second RAN node is provided. Information about a first RAN configuration of the first RAN node is transmitted to the second RAN node. A second RAN configuration of the first RAN node is determined to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node, wherein the first and second RAN configurations are different. A resource status request message is received from the second RAN node after determining the second RAN configuration of the first RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node. A resource status failure message is transmitted to the second RAN node responsive to receiving the resource status request message based on the first RAN configuration, wherein the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the RAN configuration update and the first RAN configuration of the resource status request. [0007] According to some embodiments of inventive concepts, a method of operating a first Radio Access Network RAN node of a communication network including a second RAN node is provided. Information about a first RAN configuration of the first RAN node is transmitted to the second RAN node. A resource status request message is received from the second RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node. A second RAN configuration of the first RAN node is determined to provide a RAN configuration update for the first RAN node after receiving the resource status request message from the second RAN node, wherein the first and second RAN configurations are different. A RAN node configuration update message is transmitted to the second RAN node for the RAN configuration update after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node. Transmission of a scheduled resource status update message corresponding to the resource status request message is stopped after transmitting the RAN node configuration update message.

[0008] According to some embodiments of inventive concepts, a method of operating a first Radio Access Network RAN node of a communication network including a second RAN node is provided. Information about a first RAN configuration of the first RAN node is transmitted to the second RAN node, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node. A second RAN configuration of the first RAN node is determined to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node, wherein the first and second RAN configurations are different, wherein a second configuration identifier is associated with the second RAN configuration of the first RAN node, and wherein the first and second configuration identifiers are different. A resource status request message is received from the second RAN node after determining the second RAN configuration of the first RAN node, wherein the resource status request message includes the first configuration identifier. A resource status failure message is transmitted to the second RAN node responsive to receiving the resource status request message including the first configuration identifier.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0010] FIG. 1 is a schematic diagram illustrating an example of a 5th generation (“5G”) network;

[0011 ] FIG. 2 is a block diagram illustrating an example of a NR network system architecture;

[0012] FIG. 3 is a signal flow diagram illustrating an example of successful operation of resource status reporting initiation according to some embodiments of inventive concepts;

[0013] FIG. 4 is a signal flow diagram illustrating an example of unsuccessful operation of resource status reporting initiation according to some embodiments of inventive concepts;

[0014] FIG. 5 is a signal flow diagram illustrating an example of successful operation of resource status reporting according to some embodiments of inventive concepts;

[0015] FIG. 6 is a signal flow diagram illustrating an example of successful operation of an EN-DC Resource Status Reporting Initiation according to some embodiments of inventive concepts;

[0016] FIG. 7 is a signal flow diagram illustrating an example of successful operation of resource status reporting initiation according to some embodiments of inventive concepts;

[0017] FIG. 8 is a signal flow diagram illustrating an example of unsuccessful operation of resource status reporting initiation according to some embodiments of inventive concepts; [0018] FIG. 9 is a signal flow diagram illustrating an example of successful operation of resource status reporting according to some embodiments of inventive concepts;

[0019] FIG. 10 is a table illustrating an example of a Coverage Modification List IE within the ENB Configuration Update according to some embodiments of inventive concepts;

[0020] FIG. 11 is a signal flow diagram illustrating an example of successful operation of an eNB Configuration Update procedure according to some embodiments of inventive concepts;

[0021] FIG. 12 is a signal flow diagram illustrating an example of unsuccessful operation of an eNB Configuration Update according to some embodiments of inventive concepts;

[0022] FIG. 13 is a signal flow diagram illustrating an example of successful operation of an eNB Initiated EN-DC Configuration Update according to some embodiments of inventive concepts;

[0023] FIG. 14 is a signal flow diagram illustrating an example of successful operation of en-gNB Initiated EN-DC Configuration Update according to some embodiments of inventive concepts;

[0024] FIG. 15 is a signal flow diagram illustrating an example of unsuccessful operation of an eNB Initiated EN-DC Configuration Update according to some embodiments of inventive concepts;

[0025] FIG. 16 is a signal flow diagram illustrating an example of unsuccessful operation of en-gNB Initiated EN-DC Configuration Update according to some embodiments of inventive concepts;

[0026] FIG. 17 is a signal flow diagram illustrating an example of successful operation of a NG-RAN node Configuration Update according to some embodiments of inventive concepts;

[0027] FIG. 18 is a signal flow diagram illustrating an example of unsuccessful operation of a NG-RAN node Configuration Update according to some embodiments of inventive concepts; [0028] FIGS. 19-20 are tables illustrating examples of a RESOURCE STATUS FAILURE IE according to some embodiments of inventive concepts;

[0029] FIGS. 21 -25 are tables illustrating examples of a Cause IE and associated information according to some embodiments of inventive concepts;

[0030] FIGS. 26-28 are tables illustrating examples of a resource status request IE and associated information according to some embodiments of inventive concepts;

[0031 ] FIG. 29 is a signal flow diagram illustrating an example of a successful operation of an EN-DC resource status reporting initiation procedure according to some embodiments of inventive concepts;

[0032] FIG. 30 is a signal flow diagram illustrating an example of unsuccessful operation of an EN-DC resource status reporting initiation according to some embodiments of inventive concepts;

[0033] FIG. 31 is a signal flow diagram illustrating an example of successful operation of an EN-DC Resource Status Reporting according to some embodiments of inventive concepts;

[0034] FIGS. 32-34 are tables illustrating examples of a configuration update and associated information according to some embodiments of inventive concepts;

[0035] FIGS. 35-36 are tables illustrating examples of a EN-DC configuration update and associated information according to some embodiments of inventive concepts;

[0036] FIG. 37 is a table illustrating an example of a resource status failure message according to some embodiments of inventive concepts;

[0037] FIG. 38 is a table illustrating an example of a cause IE according to some embodiments of inventive concepts;

[0038] FIGS. 39-43 are tables illustrating examples of the meanings of different cause values according to some embodiments of inventive concepts;

[0039] FIGS. 44-46 are tables illustrating examples of a Resource Status Request IE and associated information according to some embodiments of inventive concepts; [0040] FIGS. 47-48 are tables illustrating examples of a NG-RAN node configuration update message and associated information according to some embodiments of inventive concepts;

[0041] FIGS. 49-53 are message diagrams illustrating messages/operations according to some embodiments of inventive concepts;

[0042] FIG. 54 is a block diagram illustrating a communication device UE according to some embodiments of inventive concepts;

[0043] FIG. 55 is a block diagram illustrating a radio access network RAN node (e.g., a base station eNB/gNB) according to some embodiments of inventive concepts;

[0044] FIG. 56 is a block diagram illustrating a core network CN node (e.g., an AMF node, an SMF node, etc.) according to some embodiments of inventive concepts;

[0045] FIGS. 57A-C and 58A-C are flow charts illustrating RAN node operations according to FIG. 49 according to some embodiments of inventive concepts;

[0046] FIGS. 59A-C and 60A-C are flow charts illustrating RAN node operations according to FIG. 50 according to some embodiments of inventive concepts;

[0047] FIGS. 61A-C and 62A-C are flow charts illustrating RAN node operations according to FIG. 53 according to some embodiments of inventive concepts;

[0048] FIG. 63 is a block diagram of a wireless network in accordance with some embodiments;

[0049] FIG. 64 is a block diagram of a user equipment in accordance with some embodiments;

[0050] FIG. 65 is a block diagram of a virtualization environment in accordance with some embodiments;

[0051] FIG. 66 is a block diagram of a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments;

[0052] FIG. 67 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments;

[0053] FIG. 68 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; [0054] FIG. 69 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments;

[0055] FIG. 70 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments; and

[0056] FIG. 71 is a block diagram of methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

DETAILED DESCRIPTION

[0057] Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0058] The following description presents various embodiments of the disclosed subject matter. These embodiments are presented as teaching examples and are not to be construed as limiting the scope of the disclosed subject matter. For example, certain details of the described embodiments may be modified, omitted, or expanded upon without departing from the scope of the described subject matter.

[0059] Mobility Load Balancing procedures in X2AP are discussed below.

[0060] The following procedures are defined to report the resource status in

X2AP (see TS 36.423 v16.2.0): Resource Status Reporting Initiation; Resource Status Reporting; EN-DC Resource Status Reporting Initiation; and EN-DC Resource Status Reporting. [0061] Resource Status reporting between eNBs is discussed below with respect to Sections 8.3.6, 8.3.6.1 , 8.3.6.2, 8.3.6.3, 8.3.6.4, 8.3.7, 8.3.7.1 , 8.3.7.2, 8.3.7.3, and 8.3.7.4 of TS 36.423 V16.2.0.

[0062] A Resource Status Reporting Initiation procedure is used by an eNB to request the reporting of load measurements to another eNB. The procedure uses non UE-associated signaling.

[0063] FIG. 3 illustrates successful operation of resource status reporting initiation. The procedure is initiated with a RESOURCE STATUS REQUEST message sent from eNBi to eNB2. Upon receipt, eNB2: shall initiate the requested measurement according to the parameters given in the request in case the Registration Request IE set to "start"; or shall stop all cells measurements and terminate the reporting in case the Registration Request IE is set to "stop"; or if supported, stop cell measurements and terminate the reporting for cells indicated in the Cell To Report IE list, in case the Registration Request IE is set to "partial stop"; or if supported, add cells indicated in the Cell To Report IE list to the measurements initiated before for the given measurement IDs, in case the Registration Request IE is set to "add".

[0064] If the eNB2 received a RESOURCE STATUS REQUEST message, which includes the Registration Request IE set to "stop", the Cell To Report IE list shall be ignored.

[0065] If the Registration Request IE is set to "start" then the Report Characteristics IE shall be included in RESOURCE STATUS REQUEST message. The eNB2 shall ignore the Report Characteristics IE, if the Registration Request IE is not set to "start".

[0066] The Report Characteristics IE indicates the type of objects eNB2 shall perform measurements on. For each cell, the eNB2 shall include in the RESOURCE STATUS UPDATE message: the Radio Resource Status IE, if the first bit, "PRB Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the S1 TNL Load Indicator IE, if the second bit, "TNL Load Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the Hardware Load Indicator IE, if the third bit, "HW Load Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the Composite Available Capacity Group IE, if the fourth bit, "Composite Available Capacity Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1. If Cell Capacity Class Value IE is included within the Composite Available Capacity Group IE, this IE is used to assign weights to the available capacity indicated in the Capacity Value IE; the ABS Status IE, if the fifth bit, "ABS Status Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 and eNBi had indicated the ABS pattern to eNB2; the RSRP Measurement Report List IE, if the sixth bit, "RSRP Measurement Report Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the CSI Report IE, if the seventh bit, "CSI Report Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 .

[0067] If the Reporting Periodicity IE is included in the RESOURCE STATUS REQUEST message, eNB2 shall use its value as the time interval between two subsequent RESOURCE STATUS UPDATE messages that include the Radio Resource Status IE, S1 TNL Load Indicator IE, Hardware Load Indicator IE, Composite Available Capacity Group IE, or ABS Status IE.

[0068] If the Reporting Periodicity of RSRP Measurement Report IE is included in the RESOURCE STATUS REQUEST message, eNB2 shall use its value as the minimum time interval between two subsequent RESOURCE STATUS UPDATE messages that include the RSRP Measurement Report List IE.

[0069] If the Reporting Periodicity of CSI Report IE is included in the RESOURCE STATUS REQUEST message, eNB2 shall use its value as the minimum time interval between two subsequent RESOURCE STATUS UPDATE messages that include the CSI Report IE.

[0070] If eNB2 is capable to provide all requested resource status information, it shall initiate the measurement as requested by eNBi, and respond with the RESOURCE STATUS RESPONSE message.

[0071 ] If eNB2 is capable to provide some but not all of the requested resource status information and the Partial Success Indicator IE is present in the RESOURCE STATUS REQUEST message, it shall initiate the measurement for the admitted measurement objects and include the Measurement Initiation Result IE in the RESOURCE STATUS RESPONSE message.

[0072] FIG. 4 illustrates unsuccessful operation of resource status reporting initiation.

[0073] If none of the requested measurements can be initiated, eNB2 shall send a RESOURCE STATUS FAILURE message. The Cause IE shall be set to an appropriate value e.g. "Measurement Temporarily not Available" or "Measurement not Supported For The Object" for each requested measurement object. The eNB may use the Complete Failure Cause Information IE to enhance the failure cause information per measurement in the RESOURCE STATUS FAILURE message.

[0074] If the initiating eNBi does not receive either RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message, the eNBi may reinitiate the Resource Status Reporting Initiation procedure towards the same eNB, provided that the content of the new RESOURCE STATUS REQUEST message is identical to the content of the previously unacknowledged RESOURCE STATUS REQUEST message.

[0075] If the initiating eNBi receives the RESOURCE STATUS RESPONSE message including the Measurement Initiation Result IE containing no admitted measurements, the eNBi shall consider the procedure as failed.

[0076] If the Report Characteristics IE bitmap is set to "0" (all bits are set to "0") in the RESOURCE STATUS REQUEST message then eNB₂ shall initiate a RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g.

"ReportCharacteristicsEmpty".

[0077] If the Reporting Periodicity IE value is not specified when at least one of the bits of the Report Characteristics IE, for which semantics is specified, other than the sixth or seventh bit, is set to 1 then eNB₂ shall initiate a RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "NoReportPeriodicity".

[0078] If the Reporting Periodicity ofRSRP Measurement Report IE value is not specified when the sixth bit of the Report Characteristics IE is set to 1 , then eNB₂ shall initiate the RESOURCE STATUS FAILURE message and the cause shall be set to appropriate value e.g. "NoReportPeriodicity". [0079] If the Reporting Periodicity of CSI Report IE value is not specified when the seventh bit of the Report Characteristics IE is set to 1 , then eNB2 shall initiate the RESOURCE STATUS FAILURE message and the cause shall be set to appropriate value e.g. "NoReportPeriodicity".

[0080] If the eNB2 received a RESOURCE STATUS REQUEST message which includes the Registration Request IE set to "start" and the eNB1 Measurement ID IE corresponding to an existing on-going load measurement reporting, then eNB2 shall initiate a RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "ExistingMeasurementlD".

[0081] If the Registration Request IE is set to "stop", "partial stop" or "add" and the RESOURCE STATUS REQUEST message does not contain eNB2 Measurement ID IE, eNB2 shall consider the procedure as failed and respond with the RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "Unknown eNB Measurement ID".

[0082] If the Registration Request IE is set to "partial stop" and the Cell To Report IE contains cells that have not been initiated for the reporting before, eNB2 shall consider the procedure as failed and respond with the RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "Cell not Available". If the Registration Request IE is set to "add" and the Cell To Report IE contains cells that have been initiated for the reporting before, eNB2 shall consider the procedure as failed and respond with the RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "Cell not Available".

[0083] A Resource Status Reporting procedure is initiated by eNB2 to report the result of measurements admitted by eNB2 following a successful Resource Status Reporting Initiation procedure. The procedure uses non UE-associated signaling.

[0084] FIG. 5 illustrates successful operation of resource status reporting. [0085] The eNB2 shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure, and thus not reported in the Measurement Failed Report Characteristics IE for the concerned cell in the RESOURCE STATUS RESPONSE message.

[0086] If the eNBi receives the RESOURCE STATUS UPDATE message which includes the UE ID IE in the RSRP Measurement Report List IE, the eNBi may use the UE ID IE to link the associated RSRP measurement report with other measurement results (e.g. CSI reports, RSRP measurement reports) of the same UE.

[0087] If the CSI Report IE including the CSI Process Configuration Index IE is received, eNBi shall interpret this IE as an index identifying one of the CSI process configurations that can be configured for all UEs within the cell where the CSI measurements were collected. For all UEs within the cell, the maximum number of CSI process configurations is given by the maximum value of the CSI Process Configuration Index IE.

[0088] If the eNBi receives the RESOURCE STATUS UPDATE message, which includes the Cell Reporting Indicator IE set to "stop request" in one or more items of the Cell Measurement Result IE, the eNBi should initialise the Resource Status Reporting Initiation procedure to remove all or some of the corresponding cells from the measurement.

[0089] If the eNBi receives a RESOURCE STATUS UPDATE message which includes the ABS Status IE, and all bits in the Usable ABS Pattern Info IE are set to 'O', the eNB1 shall ignore the DL ABS Status IE.

[0090] Resource Status Reporting for EN-DC is discussed below with respect to Sections 8.7.22, 8.7.22.2, 8.7.22.3, and 8.7.22.4 of TS 36.423 V16.2.0.

[0091] FIG. 6 illustrates successful operation of an EN-DC Resource Status Reporting procedure This procedure is initiated by the en-gNB to report the result of measurements admitted by the en-gNB following a successful EN-DC Resource Status Reporting Initiation procedure. The procedure uses non UE-associated signaling.

[0092] The en-gNB shall report the results of the admitted measurements in the EN-DC RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding EN-DC Resource Status Reporting Initiation procedure.

[0093] Mobility Load Balancing procedures in XnAP are discussed below. [0094] The 3GPP NG RAN system supports an intra-system mobility load balancing (MLB) functionality which, in many regards, enhances the MLB functionality of the 3GPP LTE system. To this end, the signalling support for a Resource Status Reporting procedure has been introduced over Xn, F1 and E1 , as well as enhanced over X2 for EN-DC. The NG-RAN MLB functionality has been enhanced with new types of load metrics that can be reported with a finer granularity compared to LTE, such as per SSB area and per network slice, including: Radio Resource Status; Composite Available Capacity (CAC); Hardware load indicator; TNL capacity indication; Number of active UEs; and Number of RRC connections

[0095] Finally, the required signaling support for a Mobility Settings Change procedure based on an LTE baseline solution has been introduced in Rel-16 for loadsharing and load balancing.

[0096] The following procedures are defined to report the resource status in XnAP (see TS 38.423 v16.2.0): Resource Status Reporting Initiation; and Resource Status Reporting.

[0097] Resource status reporting in XnAP are discussed below with respect to Sections 8.4.10, 8.4.10.1 , 8.4.10.2, 8.4.10.3, 8.4.10.4, 8.4.11 , 8.4.11.1 , 8.4.11.2, 8.4.11.3, and 8.4.11.4.

[0098] A Resource Status Reporting Initiation procedure is used by an NG-RAN node to request the reporting of load measurements to another NG-RAN node. The procedure uses non UE-associated signaling.

[0099] FIG. 7 illustrates successful operation of a Resource Status Reporting Initiation procedure.

[0100] NG-RAN nodei initiates the procedure by sending the RESOURCE STATUS REQUEST message to NG-RAN node2 to start a measurement, stop a measurement or add cells to report for a measurement. Upon receipt, NG-RAN node2: shall initiate the requested measurement according to the parameters given in the request in case the Registration Request IE set to "start"; or shall stop all cells measurements and terminate the reporting in case the Registration Request IE is set to "stop"; or shall add cells indicated in the Cell To Report List IE to the measurements initiated before for the given measurement IDs, in case the Registration Request IE is set to "add". If measurements are already initiated for a cell indicated in the Cell To Report List IE, this information shall be ignored.

[0101] If the Registration Request IE is set to "start" in the RESOURCE STATUS REQUEST message and the Report Characteristics IE indicates cell specific measurements, the Cell To Report List IE shall be included.

[0102] If Registration Request IE is set to "add" in the RESOURCE STATUS REQUEST message, the Cell To Report List IE shall be included.

[0103] If NG-RAN node2 is capable to provide all requested resource status information, it shall initiate the measurement as requested by NG-RAN nodei and respond with the RESOURCE STATUS RESPONSE message.

[0104] Interaction with other procedures is described below.

[0105] When starting a measurement, the Report Characteristics IE in the RESOURCE STATUS REQUEST indicates the type of objects NG-RAN node₂ shall perform measurements on. For each cell, NG-RAN node₂ shall include in the RESOURCE STATUS UPDATE message: the Radio Resource Status IE, if the first bit, "PRB Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 . If NG-RAN node₂ is a gNB and if the cell for which Radio Resource Status IE is requested to be reported supports more than one SSB, the Radio Resource Status IE for such cell shall include the SSB Area Radio Resource Status Item IE for all SSB areas supported by the cell. If the SSB To Report List IE is included for a cell, the Radio Resource Status IE for such cell shall include the requested SSB Area Radio Resource Status List IE; the TNL Capacity Indicator IE, if the second bit, "TNL Capacity Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the Composite Available Capacity Group IE, if the third bit, "Composite Available Capacity Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 . If the Cell Capacity Class Value IE is included within the Composite Available Capacity Group IE, this IE is used to assign weights to the available capacity indicated in the Capacity Value IE. If NG-RAN node₂ is a gNB and if the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one SSB, the Composite Available Capacity Group IE for such cell shall include the SSB Area Capacity Value List for all SSB areas supported by the cell, providing the SSB area capacity with respect to the Cell Capacity Class Value. If the SSB To Report List IE is included for a cell, the Composite Available Capacity Group IE for such cell shall include the requested SSB Area Capacity Value List IE. If the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one slice, and if the Slice To Report List IE is included for a cell, the Slice Available Capacity IE for such cell shall include the requested Slice Available Capacity Value Downlink IE and Slice Available Capacity Value Uplink IE, providing the slice capacity with respect to the Cell Capacity Class Value. the Number of Active UEs IE, if the fourth bit, "Number of Active UEs" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the RRC Connections IE, if the fifth bit, "RRC Connections" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 .

[0106] If the Reporting Periodicity IE in the RESOURCE STATUS REQUEST is present, this indicates the periodicity for the reporting of periodic measurements. If the Reporting Periodicity IE is absent, the NG-RAN node2 shall report only once.

[0107] FIG. 8 illustrates unsuccessful operation of a resource status reporting initiation procedure. If any of the requested measurements cannot be initiated, NG- RAN node₂ shall send the RESOURCE STATUS FAILURE message.

[0108] This procedure is initiated by an NG-RAN node to report the result of measurements admitted by the NG-RAN node following a successful Resource Status Reporting Initiation procedure. The procedure uses non UE-associated signaling.

[0109] FIG. 9 illustrates successful operation of a resource status reporting procedure. NG-RAN node₂ shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure.

[0110] Capacity and coverage optimization are discussed below.

[0111] Current approaches for Capacity and Coverage Optimization (CCO) in LTE are built upon the possibility to indicate a Coverage Modification List IE within the ENB CONFIGURATION UPDATE (see TS 36.423 V16.2.0) as shown in the table in FIG. 10.

[0112] As Capacity and Coverage Optimization (CCO) standardization is ongoing for NR, there are proposals to address CCO issues using at least one of the following strategies: Cell shaping, merging, splitting; SSB beam shaping, merging, splitting; and CSI-RS beam shaping, merging, splitting.

[0113] Configuration update procedures in X2AP are discussed below.

[0114] Configuration update between eNBs is discussed below with respect to Sections 8.3.5, 8.3.5.1 , 8.3.5.2, 8.3.5.3, and 8.3.5.4 of TS 36.423 V16.2.0.

[0115] The purpose of the eNB Configuration Update procedure is to update application level configuration data needed for two eNBs to interoperate correctly over the X2 interface. Update of application level configuration data also applies between two eNBs in case the SN (i.e. the en-gNB) does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [32], How to use this information when this option is used is not explicitly specified. The procedure uses non UE-associated signaling.

[0116] FIG. 11 illustrates successful operation of an eNB Configuration Update procedure. An eNBi initiates the procedure by sending an ENB CONFIGURATION UPDATE message to a peer eNB2 . Such message shall include an appropriate set of up-to-date configuration data, including, but not limited to, the complete lists of added, modified and deleted served cells, that eNBi has just taken into operational use.

[0117] Upon reception of an ENB CONFIGURATION UPDATE message, eNB₂ shall update the information for eNBi as follows: Update of Served Cell Information and Update of GU Group Id List.

[0118] In regards to updating the served cell information, if Served Cells To Add IE is contained in the ENB CONFIGURATION UPDATE message, eNB₂ shall add cell information according to the information in the Served Cell Information IE. If Number of Antenna Ports IE is contained in the Served Cell Information IE in the ENB CONFIGURATION UPDATE message, eNB₂ may use this information according to TS 36.331 [9], If the PRACH Configuration IE is contained in the Served Cell Information IE in the ENB CONFIGURATION UPDATE message, the eNB receiving the IE may use this information for RACH optimization. If Served Cells To Modify IE is contained in the ENB CONFIGURATION UPDATE message, eNB2 shall modify information of cell indicated by Old ECGI IE according to the information in the Served Cell Information IE. If MBSFN Subframe Info IE is contained in the Served Cell Information IE in the ENB CONFIGURATION UPDATE message, eNB2 may use this information according to TS 36.331 [9], If a MBSFN subframe indicated in the MBSFN Subframe Info IE coincides with an ABS, the eNB2 shall consider that the subframe is designated as ABS by the sending eNB. If BandwidthReducedSI IE is contained in the Served Cell Information IE in the ENB CONFIGURATION UPDATE message, eNB2 may use this information to determine a suitable target in case of subsequent outgoing mobility involving BL UEs or UEs requiring CE. When either served cell information or neighbour information of an existing served cell in eNBi need to be updated, the whole list of neighbouring cells, if any, shall be contained in the Neighbour Information IE. If the Deactivation Indication IE is contained in Served Cells To Modify IE, it indicates that the concerned cell was switched off to lower energy consumption. The eNB2 shall overwrite the served cell information and the whole list of neighbour cell information for the affected served cell. If Served Cells To Delete IE is contained in the ENB CONFIGURATION UPDATE message, eNB2 shall delete information of cell indicated by Old ECGI IE. If MBMS Service Area Identity List IE is contained in the Served Cell Information IE in the ENB CONFIGURATION UPDATE message, the eNB receiving the IE may use it according to TS 36.300 [15], When the MBMS Service Area Identities of a cell in eNBi need to be updated, the whole list of MBMS Service Area Identities of the affected cell shall be contained in the Served Cell Information IE. If the NPRACH Configuration IE is contained in the Served Cell Information IE in the ENB CONFIGURATION UPDATE message, the eNB receiving the IE may use this information for RACH optimization.

[0119] In regards to updating the GU Group Id List, if GU Group Id To Add List IE is contained in the ENB CONFIGURATION UPDATE message, eNB₂ shall add the GU Group Id to its GU Group Id List. If GU Group Id To Delete List IE is contained in the ENB CONFIGURATION UPDATE message, eNB2 shall remove the GU Group Id from its GU Group Id List. [0120] If Neighbour Information IE is contained in the ENB CONFIGURATION UPDATE message, eNB2 may use this information to update its neighbour cell relations, or use it for other functions, like PCI selection. The Neighbour Information IE shall only include E-UTRAN cells that are direct neighbours of cells in the reporting eNB. A direct neighbour of one cell of a given eNB may be any cell belonging to an eNB that is a neighbour of that given eNB cell e.g. even if that cell has not been reported by a UE. The Neighbour Information IE may contain the TAC IE of the included cells. The receiving eNB may use TAC IE, as described in TS 36.300 [15],

[0121] If the NR Neighbour Information IE is contained in the ENB CONFIGURATION UPDATE message, eNB2 may use this information to update its neighbour cell relations or use it for other functions. The NR Neighbour Information IE shall only include NR cells capable of performing EN-DC with the corresponding served E-UTRA cell. The eNB receiving the NR Neighbour Information IE may use it according to TS 36.300 [15],

[0122] After successful update of requested information, eNB2 shall reply with the ENB CONFIGURATION UPDATE ACKNOWLEDGE message to inform the initiating eNBi that the requested update of application data was performed successfully. In case the peer eNB2 receives an ENB CONFIGURATION UPDATE without any IE except for Message Type IE it shall reply with ENB CONFIGURATION UPDATE ACKNOWLEDGE message without performing any updates to the existing configuration.

[0123] The eNBi may initiate a further eNB Configuration Update procedure only after a previous eNB Configuration Update procedure has been completed.

[0124] For each cell served by the initiating eNBi the ENB CONFIGURATION UPDATE message may contain the MultibandlnfoList IE and may also contain the FreqBandlndicatorPriority IE. The eNB receiving the MultibandlnfoList IE shall, if supported, take this information into account when further deciding whether subsequent mobility actions between the source cell and the target cell may be performed, and use this IE and the FreqBandlndicatorPriority IE, if received, as specified in TS 36.331 [9], [0125] If the Coverage Modification List IE is present, eNB2 may use the information in the Cell Coverage State IE to identify the cell deployment configuration enabled by eNBi and for configuring the mobility towards the cell(s) indicated by the ECGI IE, as described in TS 36.300 [15], If the Cell Deployment Status Indicator IE is present in the Coverage Modification List IE, the eNB2 shall consider the cell deployment configuration of the cell to be modified as the next planned configuration and shall remove any planned configuration stored for this cell. If the Cell Deployment Status Indicator IE is present and the Cell Replacing Info IE contains non-empty cell list, the eNB2 may use this list to avoid connection or re-establishment failures during the reconfiguration, e.g. consider the cells in the list as possible alternative handover targets. If the Cell Deployment Status Indicator IE is not present, the eNB2 shall consider the cell deployment configuration of cell to be modified as activated and replace any previous configuration for the cells indicated in the Coverage Modification List IE.

[0126] Interaction with the eNB Configuration Update procedure is described below. If an eNB2 which has not stored a FreqBandlndicatorPriority IE received from eNBi, but has signaled a FreqBandlndicatorPriority IE to eNBi after the TNL association has become available, receives an ENB CONFIGURATION UPDATE message from eNBi containing the FreqBandlndicatorPriority IE, the eNB2 shall initiate the eNB Configuration Update procedure towards eNBi including the FreqBandlndicatorPriority IE.

[0127] FIG. 12 illustrates unsuccessful operation of a eNB Configuration Update. If the eNB2 can not accept the update it shall respond with an ENB CONFIGURATION UPDATE FAILURE message and appropriate cause value.

[0128] If the ENB CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE the eNBi shall wait at least for the indicated time before reinitiating the eNB Configuration Update procedure towards the same eNB2. Both nodes shall continue to operate the X2 with their existing configuration data.

[0129] If the eNBi after initiating eNB Configuration Update procedure receives neither ENB CONFIGURATION UPDATE ACKNOWLEDGE message nor ENB CONFIGURATION UPDATE FAILURE message, the eNBi may reinitiate the eNB Configuration Update procedure towards the same eNB2, provided that the content of the new ENB CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged ENB CONFIGURATION UPDATE message. [0130] Configuration update for EN-DC is discussed below with respect to Sections 8.7.2, 8.7.2.1 , 8.7.2.2, 8.7.2.3, and 8.7.2.4 of TS 36.423 V16.2.0.

[0131] The purpose of the EN-DC Configuration Update procedure is to update application level configuration data needed for eNB and en-gNB to interoperate correctly over the X2 interface. Update of application level configuration data also applies between eNB and en-gNB in case the SN (i.e. the en-gNB) does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [32], How to use this information when this option is used is not explicitly specified. The procedure uses non UE-associated signaling.

[0132] FIG. 13 illustrates successful operation of an eNB Initiated EN-DC Configuration Update.

[0133] FIG. 14 illustrates successful operation of an en-gNB Initiated EN-DC Configuration Update.

[0134] If case of network sharing with multiple cell ID broadcast with shared X2-C signaling transport, as specified in TS 36.300 [15], the EN-DC CONFIGURATION UPDATE message and the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message shall include the Interface Instance Indication IE to identify the corresponding interface instance.

[0135] An eNB initiated EN-DC Configuration Update is described below. An eNB initiates the procedure by sending an EN-DC CONFIGURATION UPDATE message to a peer en-gNB.

[0136] After successful update of requested information, en-gNB shall reply with the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message to inform the initiating eNB that the requested update of application data was performed successfully. [0137] If the Cell Assistance Information IE is present, the en-gNB shall, if supported, use it to generate the List of Served NR Cells IE and include the list in the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message.

[0138] If the EN-DC CONFIGURATION UPDATE REQUEST message contains the Protected E-UTRA Resource Indication IE, the receiving en-gNB should take this into account for cell-level resource coordination with the eNB. The en-gNB shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same eNB. The protected resource pattern indicated in the Protected E-UTRA Resource Indication IE is not valid in subframes indicated by the Reserved Subframes IE, as well as in the non-control region of the MBSFN subframes i.e. it is valid only in the control region therein. The size of the control region of MBSFN subframes is indicated in the Protected E-UTRA Resource Indication IE.

[0139] The eNB may initiate a further EN-DC Configuration Update procedure only after a previous EN-DC Configuration Update procedure has been completed. [0140] If Supplementary Uplink is configured at the en-gNB, the en-gNB shall include in the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message the SUL Information IE and the Supported SUL band List IE for each cell added in the Served NR Cells To Add IE and in the Served NR Cells To Modify IE.

[0141] If the EN-DC CONFIGURATION UPDATE message contains the TNL Transport Layer Address info IE, the receiving en-gNB shall, if supported, take this into account for IPSEC tunnel establishment.

[0142] If the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message contains the TNL Transport Layer Address info IE, the receiving eNB shall, if supported, take this into account for IPSEC tunnel establishment.

[0143] If the NR Cell PRACH Configuration IE is included in the Served NR Cell Information IE contained in the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message, the eNB may update the information.

[0144] If the CSI-RS Transmision Indication IE is contained in the EN-DC CONFIGURATION UPDATE message, en-gNB may use this information for neighbour NR cell’s CSI-RS measurement.

[0145] An en-gNB initiated EN-DC Configuration Update is described below. An en-gNB initiates the procedure by sending an EN-DC CONFIGURATION UPDATE message to an eNB.

[0146] If Supplementary Uplink is configured at the en-gNB, the en-gNB shall include in the EN-DC CONFIGURATION UPDATE message the SUL Information IE and the Supported SUL band List IE for each served cell added in the Served NR Cells To Add IE and in the Served NR Cells To Modify IE. [0147] If the Deactivation Indication IE is contained in the Served NR Cells To Modify IE, it indicates that the concerned NR cell was switched off to lower energy consumption, and is available for activation on request from the eNB, as described in TS 36.300 [15],

[0148] After successful update of requested information, eNB shall reply with the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message to inform the initiating en-gNB that the requested update of application data was performed successfully. In case the eNB receives an EN-DC CONFIGURATION UPDATE without any IE except for Message Type IE it shall reply with EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message without performing any updates to the existing configuration.

[0149] Upon reception of an EN-DC CONFIGURATION UPDATE message, eNB shall update the information for en-gNB as follows: Update of Served NR Cell Information and Update of SCTP association.

[0150] In regards to updating the Served NR Cell Information, if Served NR Cells To Add IE is contained in the EN-DC CONFIGURATION UPDATE message, eNB shall add cell information according to the information in the Served NR Cell Information IE.

If Served NR Cells To Modify IE is contained in the EN-DC CONFIGURATION UPDATE message, eNB shall modify information of cell indicated by Old NR-CGI IE according to the information in the Served NR Cell Information IE. If Served NR Cells To Delete IE is contained in the EN-DC CONFIGURATION UPDATE message, eNB shall delete information of cell indicated by Old NR-CGI IE.

[0151] The en-gNB may initiate a further EN-DC Configuration Update procedure only after a previous EN-DC Configuration Update procedure has been completed.

[0152] If the EN-DC CONFIGURATION UPDATE message contains the TNL

Transport Layer Address info IE, the receiving eNB shall, if supported, take this into account for IPSEC tunnel establishment.

[0153] If the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message contains the TNL Transport Layer Address info IE, the receiving en-gNB shall, if supported, take this into account for IPSEC tunnel establishment. [0154] If the NR Cell PRACH Configuration IE is included in the Served NR Cell Information IE contained in the EN-DC CONFIGURATION UPDATE message, the eNB may update the information.

[0155] If the CSI-RS Transmision Indication IE is contained in the EN-DC CONFIGURATION UPDATE message, eNB should take it into account when forwarding neighbour NR cell’s CSI-RS configuration.

[0156] In regards to updating SCTP associations, if the TNL Association to Add List IE is included in the EN-DC CONFIGURATION UPDATE message, the receiving eNB shall, if supported, use it to establish the TNL association(s) with the en-gNB. The eNB shall report to the en-gNB, in the EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the en-gNB as follows: A list of successfully established TNL associations shall be included in the TNL Association Setup List IE; and A list of TNL associations that failed to be established shall be included in the TNL Association Failed to Setup List IE.

[0157] If the TNL Association to Remove List IE is included in the EN-DC CONFIGURATION UPDATE message, the receiving eNB shall, if supported, initiate removal of the TNL association(s) indicated by the received Transport Layer information towards the en-gNB.

[0158] If the TNL Association to Update List IE is included in the EN-DC CONFIGURATION UPDATE message the receiving eNB shall, if supported, update the TNL association(s) indicated by the received Transport Layer information towards the en-gNB.

[0159] FIG. 15 illustrates unsuccessful operation of an eNB Initiated EN-DC Configuration Update.

[0160] FIG. 16 illustrates unsuccessful operation of an en-gNB Initiated EN-DC Configuration Update.

[0161] If the candidate receving node can not accept the update it shall respond with an EN-DC CONFIGURATION UPDATE FAILURE message and appropriate cause value.

[0162] If the EN-DC CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE the initiating node shall wait at least for the indicated time before reinitiating the EN-DC Configuration Update procedure towards the same peer node. Both nodes shall continue to operate the X2 with their existing configuration data.

[0163] If case of network sharing with multiple cell ID broadcast with shared X2-C signalling transport, as specified in TS 36.300 [15], the EN-DC CONFIGURATION UPDATE message and the EN-DC CONFIGURATION UPDATE FAILURE message shall include the Interface Instance Indication IE to identify the corresponding interface instance.

[0164] If the initiating node after initiating EN-DC Configuration Update procedure receives neither EN-DC CONFIGURATION UPDATE ACKNOWLEDGE message nor EN-DC CONFIGURATION UPDATE FAILURE message, the initiating node may reinitiate the EN-DC Configuration Update procedure towards the same candidate receving node, provided that the content of the EN-DC CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged EN-DC CONFIGURATION UPDATE message.

[0165] Configuration Update procedures in XnAP are discussed below with respect to Sections 8.4.2, 8.4.2.1 , 8.4.2.2, 8.4.2.3, and 8.4.2.4.

[0166] The purpose of the NG-RAN node Configuration Update procedure is to update application level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface. Update of application level configuration data also applies between two NG-RAN nodes in case the SN (i.e. the gNB) does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [8], How to use this information when this option is used is not explicitly specified. The procedure uses non UE-associated signaling.

[0167] FIG. 17 illustrates successful operation of a NG-RAN node Configuration Update. The NG-RAN nodei initiates the procedure by sending the NG-RAN NODE CONFIGURATION UPDATE message to a peer NG-RAN node₂.

[0168] If Supplementary Uplink is configured at the NG-RAN nodei, the NG-RAN nodei shall include in the NG-RAN NODE CONFIGURATION UPDATE message the SUL Information IE and the Supported SUL band List IE for each cell added in the Served NR Cells To Add IE and in the Served NR Cells To Modify IE. [0169] If Supplementary Uplink is configured at the NG-RAN node2, the NG-RAN node₂ shall include in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message the SUL Information IE and the Supported SUL band List IE for each cell added in the Served NR Cells IE if any.

[0170] If the TAI Support List IE is included in the NG-RAN NODE CONFIGURATION UPDATE message, the receiving node shall replace the previously provided TAI Support List IE by the received TAI Support List IE.

[0171] If the Cell Assistance Information NR IE is present, the NG-RAN node₂ shall, if supported, use it to generate the Served NR Cells IE and include the list in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.

[0172] If the Cell Assistance Information LTE IE is present, the NG-RAN node₂ shall, if supported, use it to generate the Served LTE Cells IE and include the list in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.

[0173] If the Partial List Indicator NR IE is included in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message and set to "partial" the NG- RAN nodei shall, if supported, assume that the Served NR Cells IE in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message includes a partial list of NR cells.

[0174] If the Partial List Indicator E-UTRA IE is included in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message and set to "partial" the NG- RAN nodei shall, if supported, assume that the Served E-UTRA Cells IE in the NG- RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message includes a partial list of NR cells.

[0175] If the Cell and Capacity Assistance Information NR IE is present in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message from the candidate NG-RAN node₂, the NG-RAN nodei shall, if supported, store the collected information to be used for future NG-RAN node interface management.

[0176] If the Cell and Capacity Assistance Information E-UTRA IE is present in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message from the candidate NG-RAN node₂, the NG-RAN nodei shall, if supported, store the collected information to be used for future NG-RAN node interface management. [0177] Upon reception of the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node2 shall update the information for NG-RAN nodei as follows. [0178] If case of network sharing with multiple cell ID broadcast with shared Xn-C signaling transport, as specified in TS 38.300 [9], the NG-RAN NODE CONFIGURATION UPDATE message and the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message shall include the Interface Instance Indication IE to identify the corresponding interface instance.

[0179] In regards to updating Served Cell Information NR, if Served Cells NR To Add IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG- RAN node2 shall add cell information according to the information in the Served Cell Information NR IE. If Served Cells NR To Modify IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node2 shall modify information of cell indicated by Old NR-CGI IE according to the information in the Served Cell Information NR IE. When either served cell information or neighbour information of an existing served cell in NG-RAN nodei need to be updated, the whole list of neighbouring cells, if any, shall be contained in the Neighbour Information NR IE. The NG-RAN node2 shall overwrite the served cell information and the whole list of neighbour cell information for the affected served cell. If the Deactivation Indication IE is contained in the Served Cells NR To Modify IE, it indicates that the concerned cell was switched off to lower energy consumption. If Served Cells NR To Delete IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node2 shall delete information of cell indicated by Old NR-CGI IE. If the Intended TDD DL-UL Configuration NR IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node2 should take this information into account for cross-link interference management and/or NR-DC power coordination with the NG-RAN nodei. The NG-RAN node2 shall consider the received Intended TDD DL-UL Configuration NR IE content valid until reception of a new update of the IE for the same NG-RAN node2. If the NR Cell PRACH Configuration IE is contained in the Served Cell Information NR IE in the NG- RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE may use this information for RACH optimization. [0180] In regards to updating Served Cell Information E-UTRA, if Served Cells E- UTRA To Add IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node2 shall add cell information according to the information in the Served Cell Information E-UTRA IE. If Served Cells E-UTRA To Modify IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node₂ shall modify information of cell indicated by Old ECGI IE according to the information in the Served Cell Information E-UTRA IE. When either served cell information or neighbour information of an existing served cell in NG-RAN nodei need to be updated, the whole list of neighbouring cells, if any, shall be contained in the Neighbour Information E- UTRA IE. The NG-RAN node₂ shall overwrite the served cell information and the whole list of neighbour cell information for the affected served cell. If the Deactivation Indication IE is contained in the Served Cells E-UTRA To Modify IE, it indicates that the concerned cell was switched off to lower energy consumption. If the Served Cells E- UTRA To Delete IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, NG-RAN node₂ shall delete information of cell indicated by Old ECGI IE. If the Protected E-UTRA Resource Indication IE is included into the NG-RAN NODE CONFIGURATION UPDATE (inside the Served Cell Information E-UTRA IE), the receiving gNB should take this into account for cell-level resource coordination with the ng-eNB. The gNB shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same ng-eNB. The protected resource pattern indicated in the Protected E-UTRA Resource Indication IE is not valid in subframes indicated by the Reserved Subframes IE (contained in E-UTRA - NR CELL RESOURCE COORDINATION REQUEST messages), as well as in the noncontrol region of the MBSFN subframes i.e. it is valid only in the control region therein. The size of the control region of MBSFN subframes is indicated in the Protected E- UTRA Resource Indication IE. If the PRACH Configuration IE is contained in the Served Cell Information E-UTRA IE in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node receiving the IE may use this information for RACH optimization.

[0181] In regards to updating TNL addresses for SCTP associations, if the TNL

Association to Add List IE is included in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node2 shall, if supported, use it to establish the TNL association(s) with the NG-RAN nodei. The NG-RAN node2 shall report to the NG-RAN nodei, in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the successful establishment of the TNL association(s) with the NG-RAN nodei as follows: A list of successfully established TNL associations shall be included in the TNL Association Setup List IE; and a list of TNL associations that failed to be established shall be included in the TNL Association Failed to Setup List IE.

[0182] If the TNL Association to Remove List IE is included in the NG-RAN NODE CONFIGURATION UPDATE message the NG-RAN node₂ shall, if supported, initiate removal of the TNL association(s) indicated by the received Transport Layer information towards the NG-RAN nodei.

[0183] If the TNL Association to Update List IE is included in the NG-RAN NODE CONFIGURATION UPDATE message the NG-RAN node2 shall, if supported, update the TNL association(s) indicated by the received Transport Layer information towards the NG-RAN nodei.

[0184] In regards to updating AMF Region Information, if AMF Region Information To Add IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node2 shall add the AMF Regions to its AMF Region List. If AMF Region Information To Delete IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node₂ shall remove the AMF Regions from its AMF Region List.

[0185] If the TNL Configuration Info IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node₂ shall take this IE into account for IPSec establishment.

[0186] If the TNL Configuration Info IE is contained in the NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, the NG-RAN nodei shall take this IE into account for IPSec establishment.

[0187] If the CSI-RS Transmission Indication IE is contained in the NG-RAN NODE CONFIGURATION UPDATE message, the NG-RAN node₂ shall take this IE into account for neighbour cell’s CSI-RS measurement. [0188] The NG-RAN NODE CONFIGURATION UPDATE message may contain for each cell served by NG-RAN nodei NPN related broadcast information. The NG- RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message may contain for each cell served by NG-RAN node2 NPN related broadcast information.

[0189] FIG. 18 illustrates unsuccessful operation of NG-RAN node Configuration Update. If the NG-RAN node2 cannot accept the update it shall respond with the NG- RAN NODE CONFIGURATION UPDATE FAILURE message and appropriate cause value.

[0190] If the NG-RAN NODE CONFIGURATION UPDATE FAILURE message includes the Time To Wait IE, the NG-RAN nodei shall wait at least for the indicated time before reinitiating the NG-RAN Node Configuration Update procedure towards the same NG-RAN node2. Both nodes shall continue to operate the Xn with their existing configuration data.

[0191] If case of network sharing with multiple cell ID broadcast with shared Xn-C signaling transport, as specified in TS 38.300 [9], the NG-RAN NODE CONFIGURATION UPDATE message and the NG-RAN NODE CONFIGURATION UPDATE FAILURE message shall include the Interface Instance Indication IE to identify the corresponding interface instance.

[0192] If the NG-RAN nodei after initiating NG-RAN node Configuration Update procedure receives neither NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message nor NG-RAN NODE CONFIGURATION UPDATE FAILURE message, the NG-RAN nodei may reinitiate the NG-RAN node Configuration Update procedure towards the same NG-RAN node2, provided that the content of the new NG- RAN NODE CONFIGURATION UPDATE message is identical to the content of the previously unacknowledged NG-RAN NODE CONFIGURATION UPDATE message.

[0193] Existing approaches may not provide sufficient coordination between procedures addressing CCO issues and reporting of resource status.

[0194] FIG. 54 is a block diagram illustrating elements of a communication device UE 5400 (also referred to as a mobile terminal, a mobile communication terminal, a wireless device, a wireless communication device, a wireless terminal, mobile device, a wireless communication terminal, user equipment, UE, a user equipment node/terminal/device, etc.) configured to provide wireless communication according to embodiments of inventive concepts. (Communication device 5400 may be provided, for example, as discussed below with respect to wireless device 4110 of FIG. 63.) As shown, communication device UE may include an antenna 5407 (e.g., corresponding to antenna 4111 of FIG. 63), and transceiver circuitry 5401 (also referred to as a transceiver, e.g., corresponding to interface 4114 of FIG. 63) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station(s) (e.g., corresponding to network node 4160 of FIG. 63, also referred to as a RAN node) of a radio access network. Communication device UE may also include processing circuitry 5403 (also referred to as a processor, e.g., corresponding to processing circuitry 4120 of FIG. 63) coupled to the transceiver circuitry, and memory circuitry 5405 (also referred to as memory, e.g., corresponding to device readable medium 4130 of FIG. 63) coupled to the processing circuitry. The memory circuitry 5405 may include computer readable program code that when executed by the processing circuitry 5403 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 5403 may be defined to include memory so that separate memory circuitry is not required. Communication device UE may also include an interface (such as a user interface) coupled with processing circuitry 5403, and/or communication device UE may be incorporated in a vehicle.

[0195] As discussed herein, operations of communication device UE may be performed by processing circuitry 5403 and/or transceiver circuitry 5401 . For example, processing circuitry 5403 may control transceiver circuitry 5401 to transmit communications through transceiver circuitry 5401 over a radio interface to a radio access network node (also referred to as a base station) and/or to receive communications through transceiver circuitry 5401 from a RAN node over a radio interface. Moreover, modules may be stored in memory circuitry 5405, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 5403, processing circuitry 5403 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to wireless communication devices). According to some embodiments, a communication device UE 5400 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.

[0196] FIG. 55 is a block diagram illustrating elements of a radio access network RAN node 5500 (also referred to as a network node, base station, eNodeB/eNB, gNodeB/gNB, etc.) of a Radio Access Network (RAN) configured to provide cellular communication according to embodiments of inventive concepts. (RAN node 5500 may be provided, for example, as discussed below with respect to network node 4160 of FIG. 63.) As shown, the RAN node may include transceiver circuitry 5501 (also referred to as a transceiver, e.g., corresponding to portions of interface 4190 of FIG. 63) including a transmitter and a receiver configured to provide uplink and downlink radio communications with mobile terminals. The RAN node may include network interface circuitry 5507 (also referred to as a network interface, e.g., corresponding to portions of interface 4190 of FIG. 63) configured to provide communications with other nodes (e.g., with other base stations) of the RAN and/or core network CN. The network node may also include processing circuitry 5503 (also referred to as a processor, e.g., corresponding to processing circuitry 4170) coupled to the transceiver circuitry, and memory circuitry 5505 (also referred to as memory, e.g., corresponding to device readable medium 4180 of FIG. 63) coupled to the processing circuitry. The memory circuitry 5505 may include computer readable program code that when executed by the processing circuitry 5503 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 5503 may be defined to include memory so that a separate memory circuitry is not required.

[0197] As discussed herein, operations of the RAN node may be performed by processing circuitry 5503, network interface 5507, and/or transceiver 5501 . For example, processing circuitry 5503 may control transceiver 5501 to transmit downlink communications through transceiver 5501 over a radio interface to one or more mobile terminals UEs and/or to receive uplink communications through transceiver 5501 from one or more mobile terminals UEs over a radio interface. Similarly, processing circuitry 5503 may control network interface 5507 to transmit communications through network interface 5507 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 5505, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 5503, processing circuitry 5503 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to RAN nodes). According to some embodiments, RAN node 5500 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.

[0198] According to some other embodiments, a network node may be implemented as a core network CN node without a transceiver. In such embodiments, transmission to a wireless communication device UE may be initiated by the network node so that transmission to the wireless communication device UE is provided through a network node including a transceiver (e.g., through a base station or RAN node). According to embodiments where the network node is a RAN node including a transceiver, initiating transmission may include transmitting through the transceiver. [0199] FIG. 56 is a block diagram illustrating elements of a core network CN node (e.g., an SMF node, an AMF node, etc.) of a communication network configured to provide cellular communication according to embodiments of inventive concepts. As shown, the CN node may include network interface circuitry 5607 (also referred to as a network interface) configured to provide communications with other nodes of the core network and/or the radio access network RAN. The CN node may also include a processing circuitry 5603 (also referred to as a processor) coupled to the network interface circuitry, and memory circuitry 5605 (also referred to as memory) coupled to the processing circuitry. The memory circuitry 5605 may include computer readable program code that when executed by the processing circuitry 5603 causes the processing circuitry to perform operations according to embodiments disclosed herein. According to other embodiments, processing circuitry 5603 may be defined to include memory so that a separate memory circuitry is not required.

[0200] As discussed herein, operations of the CN node may be performed by processing circuitry 5603 and/or network interface circuitry 5607. For example, processing circuitry 5603 may control network interface circuitry 5607 to transmit communications through network interface circuitry 5607 to one or more other network nodes and/or to receive communications through network interface circuitry from one or more other network nodes. Moreover, modules may be stored in memory 5605, and these modules may provide instructions so that when instructions of a module are executed by processing circuitry 5603, processing circuitry 5603 performs respective operations (e.g., operations discussed below with respect to Example Embodiments relating to core network nodes). According to some embodiments, CN node 5600 and/or an element(s)/function(s) thereof may be embodied as a virtual node/nodes and/or a virtual machine/machines.

[0201] Network improvement/optimization related to Mobility Load Balancing (MLB) can be biased by invalid Resource status reporting information, due to a mismatch between the configuration known at the RAN node initiating the request of resource status update (such as. XnAP Resource Status Reporting Initiation), and the actual configuration of the RAN node that is due to provide the Resource Status Update.

[0202] Due to the lack of coordination between procedures for mobility load balancing and procedures for improving/optimizing the configuration of radio cells, and their reference signal beams, such as the coverage and capacity optimization procedures, the node requesting radio resource status for MLB could base its request for load information on an outdated configuration of the neighbor RAN node. Such mismatch may either cause the procedure to fail or to successfully report load information that no longer correspond to the configuration used for the request, thereby resulting in inaccurate load information and performance loss.

[0203] According to some embodiments of inventive concepts, methods are provided to facilitate the coordination between actions triggered by Capacity and Coverage Optimization (CCO) and the reporting of resource status supporting the Mobility Load Balancing.

[0204] According to some embodiments, resource status reporting can provide more reliable information, since the RAN node requesting the resource status transfer can use the most updated configuration of the RAN node targeted for the request. Therefore, this can lead to more accurate Mobility Load Balancing actions. [0205] The terms “RAN node” or “network node” can be used interchangeably in the remainder of the present disclosure.

[0206] A RAN node can be one of: eNB, NG-RAN node, en-gNB, gNB, ng-eNB.

[0207] According to some embodiments, in a network comprising a first RAN node and a second RAN node, methods are executed to enable the first RAN node to transmit to the second RAN node Status Updates aligned to the latest valid configuration of the first RAN node.

[0208] Methods/operations executed at a first RAN node are discussed below.

[0209] In a first embodiment, transmitting to the second RAN node a Status Failure message (such as a RESOURCE STATUS FAILURE message) with a Cause indicating that the procedure initiated to request information updates (such as resource status updates) has failed because the received request concerns a configuration of the first RAN node that is different from the one currently valid. As non-limiting examples, the procedure initiated to information updates can be procedures to request resource status updates such as one of the following: X2AP “Reporting Status Reporting Initiation”, X2AP “EN-DC Resource Status Reporting Initiation”, XnAP “Reporting Status Reporting Initiation.” In one embodiment, the initiating message of the procedure initiated to request information updates such as resource status updates comprises a list of downlink RS beams (such as SSB beams or CSI-RS beam).

[0210] In another embodiment, transmitting to the second RAN node a RAN Configuration Update comprising an identifier such as a RAN Configuration Identifier. A RAN Configuration Identifier uniquely identifies a given RAN Configuration. The methods used to obtain such identifier are not discussed in the present disclosure.

Example of Configuration Update can be: NG-RAN NODE CONFIGURATION UPDATE, ENB CONFIGURATION UPDATE, EN-DC CONFIGURATION UPDATE. In another embodiment, receiving from the second RAN node the initiating message (such as a RESOURCE STATUS REQUEST) of the procedure to request information updates such as resource status updates comprising the RAN Configuration identifier which identifies a configuration of the first RAN node. In an example, the RAN Configuration Identifier identifies the most recent RAN configuration of the first RAN node known at the second RAN node. [0211] In another embodiment, transmitting to the second RAN node a Status Response message (such as a RESOURCE STATUS RESPONSE) message to indicate a successfully completed procedure to request information update such as request resource status update from the first RAN node, the message comprising the RAN Configuration Identifier.

[0212] In another embodiment, transmitting to the second RAN node a Status Update message (such as a RESOURCE STATUS UPDATE message), the message comprising the RAN Configuration Identifier.

[0213] Methods executed at a second RAN node are discussed below.

[0214] In a first embodiment, receiving from the first RAN node a Status Failure message (such as a RESOURCE STATUS FAILURE message) with a Cause indicating that the procedure initiated to request information updates (such as resource status updates) has failed because the received request concerns a configuration of the first RAN node that is different from the one currently valid.

[0215] In another embodiment, receiving from the first RAN node a Configuration Update comprising an identifier such as a RAN Configuration Identifier.

[0216] In another embodiment, transmitting to the first RAN node the initiating message of the procedure to request information updates such as resource status updates comprising the RAN Configuration identifier.

[0217] In another embodiment, receiving from the first RAN node a Status Response message (such as a RESOURCE STATUS RESPONSE) message to indicate a successfully completed procedure to request information update such as requesting resource status update from the first RAN node, the message comprising the RAN Configuration Identifier.

[0218] In another embodiment, receiving from the first RAN node a Status Update message (such as a RESOURCE STATUS UPDATE message), the message comprising the RAN Configuration Identifier.

[0219] Some embodiments of inventive concepts may address issues in Mobility Load Balancing related to invalid resource status reporting between RAN nodes due to updates in RAN configuration triggered by Capacity and Coverage (CCO). [0220] Some embodiments may provide methods performed at a first RAN node and at a second RAN node to transfer measurements associated with a network function of the first and/or the second network node.

[0221] The first RAN node and the second RAN node are neighbors, i.e. connectivity between the nodes exists e.g. via an XnAP or X2AP network interface. [0222] As a result of the signaling exchanged according to existing solution (e.g. for the NR case, via NG-RAN Configuration Update), the two RAN nodes have exchanged information about serving cells.

[0223] Also, the first RAN node has requested a second RAN node to report the resource status for a list of cells and SSBs of the second RAN node.

[0224] According to some embodiments, “Resource Status Reporting Initiation” is initiated based on an “Old” configuration (also referred to as an old RAN configuration or a first RAN Configuration).

[0225] The first RAN node is about to initiate a RAN Configuration Update to inform the second RAN node that a “New” configuration (also referred to as a new RAN configuration or a second RAN configuration) has to be considered by the second RAN node, e.g. new Served Cells or beams (such as SSB beams or CSI-RS beams) have been added or some Served Cells or beams have been deleted.

[0226] The second RAN node has knowledge of the prior configuration of the first RAN node (such as “Old” configuration).

[0227] Before the RAN node configuration update procedure is completed at the second RAN node (i.e. before the second RAN node sends to the first RAN node the RAN Configuration Update Acknowledge), the first RAN node receives from the second RAN node a Resource Status Request with the indication of the cells and/or beams to be reported, based on the prior configuration of the first RAN node.

[0228] In such embodiments, a failure case is added to the Resource Status Reporting Initiation procedure so that the first RAN node is able to indicate to the second RAN node that the initiated Resource Status Reporting fails due to a mismatch between the RAN node configuration known at the second RAN node and the RAN node configuration valid at the first RAN node. (e.g. using a Cause value set to “Configuration Update”). [0229] FIG. 49 is a message diagram illustrating embodiments where the first RAN node (RAN node 1) changes its configuration to a “new” configuration (2^nd RAN configuration), while receiving a RESOURCE STATUS REQUEST message from a second RAN node (RAN node 2) based on an “old” configuration (1^st RAN configuration) of the first RAN node.

[0230] Operations of a first RAN node of FIG. 49 (implemented using the structure of FIG. 55) will now be discussed with reference to the flow charts of FIGS. 57A-C according to some embodiments of inventive concepts. For example, modules may be stored in memory 5505 of FIG. 55, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 5503, processing circuitry 5503 performs respective operations of the flow chart.

[0231 ] According to some embodiments at block 5701 , processing circuitry 5503 transmits (through network interface 5507) information about a first RAN configuration of the first RAN node to the second RAN node. The information may be transmitted as part of a set up procedure or a configuration update. Transmission of this information is shown as message/operation 4901 of FIG. 49.

[0232] According to some embodiments at block 5705, processing circuitry 5503 determines a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node, wherein the first and second RAN configurations are different. This determination is shown as operation 4902 of FIG. 49. [0233] According to some embodiments at block 5709, processing circuitry 5503 receives (through network interface 5507) a resource status request message from the second RAN node after determining the second RAN configuration of the first RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node. Reception of the resource status request message is shown as message 4904 of FIG. 49.

[0234] According to some embodiments at block 5711 , processing circuitry 5503 transmits (through network interface 5507) a resource status failure message to the second RAN node responsive to receiving the resource status request message based on the first RAN configuration. The resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the RAN configuration update and the first RAN configuration of the resource status request. Transmission of the resource status failure message is shown as message 4905 of FIG. 49. For example, the cause value may be set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

[0235] According to some embodiments, the resource status failure message including the cause value to indicate the mismatch may be transmitted responsive to receiving the resource status request message after determining the second RAN configuration and before completion of the RAN configuration update for the first RAN node.

[0236] According to some embodiments, the first RAN configuration of block 5701 defines a first plurality of cells and/or beams configured for the first RAN node, a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, the second RAN configuration of block 5705 defines a second plurality of cells and/or beams configured for the first RAN node, a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, the first and second pluralities of cells and/or beams are different, and the resource status request message includes a subset of the first plurality of identifiers. The resource status failure message including the cause value to indicate the mismatch may be transmitted responsive to determining that at least one of the subset of the first plurality of identifiers of the resource status request message does not match any of the second plurality of identifiers of the second RAN configuration.

[0237] According to some embodiments, a first configuration identifier is associated with the first RAN configuration of the first RAN node, a second configuration identifier is associated with the second RAN configuration of the first RAN node, and the first and second configuration identifiers are different. In such embodiments, the resource status request message may include the first configuration identifier, and the resource status failure message including the cause value to indicate the mismatch may be transmitted responsive to the resource status request message including the first configuration identifier. [0238] According to some embodiments at block 5715, processing circuitry 5503 transmits (through network interface 5507) a RAN node configuration update message to the second RAN node after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node. Transmission of the RAN node configuration update message is shown as message 4906 of FIG. 49. For example, the RAN node configuration update message may be transmitted after transmitting the resource status failure message.

[0239] According to some embodiments at block 5719, processing circuitry 5503 receives (through network interface 5507) a RAN node configuration update response message from the second RAN node after transmitting the RAN node configuration update message and/or after transmitting the resource status failure message, where the RAN node configuration update response message may be a RAN node configuration update acknowledge message or a RAN node configuration update failure message. Reception of the RAN node configuration update response message is shown as message 4907 of FIG. 49. As shown in block 5719-1 of FIG. 57B, the RAN node configuration update response message may be a RAN node configuration update acknowledge message which is an acknowledgement of the RAN node configuration update message completing the RAN configuration update for the second RAN configuration of the first RAN node. As shown in block 5719-2 of FIG. 57C, the RAN node configuration update response message may be a RAN node configuration update failure message which indicates failure of the RAN configuration update for the first RAN node

[0240] Various operations from the flow charts of FIGS. 57A-C may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of blocks 5715, 5719, 5719-1 , and/or 5719-2 of FIGS. 57A-C may be optional.

[0241] Operations of a second RAN node of FIG. 49 (implemented using the structure of FIG. 55) will now be discussed with reference to the flow charts of FIGS. 58A-C according to some embodiments of inventive concepts. For example, modules may be stored in memory 5505 of FIG. 55, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 5503, processing circuitry 5503 performs respective operations of the flow chart.

[0242] According to some embodiments at block 4901 , processing circuitry 5503 receives (through network interface 5507) information about a first RAN configuration of the first RAN node from the first RAN node. The information may be received as part of a set up procedure or a configuration update. Reception of this information is shown as message/operation 4901 of FIG. 49.

[0243] According to some embodiments at block 5809, processing circuitry 5503 transmits (through network interface 5507) a resource status request message to the first RAN node after receiving the information about the first RAN configuration, wherein the resource status request message is based on the first RAN configuration of the first RAN node. Transmission of this information is shown as message/operation 4904 of FIG. 49.

[0244] According to some embodiments at block 5811 , processing circuitry 5503 receives (through network interface 5507) a resource status failure message from the first RAN node, wherein the resource status failure message corresponds to the resource status request message, and wherein the resource status failure message includes a cause value to indicate a mismatch between a second RAN configuration of a RAN configuration update for the first RAN node and the first RAN configuration of the resource status request. Reception of this information is shown as message/operation 4905 of FIG. 49. For example, the cause value may be set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

[0245] According to some embodiments at block 5815, processing circuitry 5503 receives (through network interface 407) a RAN node configuration update message from the first RAN node after transmitting the resource status request message, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node. Reception of the RAN node configuration update message is shown as message/operation 4906 of FIG. 49. For example, the RAN node configuration update message may be received after receiving the resource status failure message.

[0246] According to some embodiments at block 5819, processing circuitry 5503 transmits (through network interface 5507) transmits a RAN node configuration update response message to the first RAN node after receiving the RAN node configuration update message, where the RAN node configuration update response message may be a RAN node configuration update acknowledge message or a RAN node configuration update failure message. Transmission of the RAN node configuration update response message is illustrated as message/operation 4907 of FIG. 49. As shown in block 5819- 1 of FIG. 58B, the RAN node configuration update response message may be a RAN node configuration update acknowledge message which is an acknowledgement of the RAN node configuration update message completing the RAN configuration update for the second RAN configuration of the first RAN node. As shown in block 5819-2 of FIG. 58C, the RAN node configuration update response message may be a RAN node configuration update failure message which indicates failure of the RAN configuration update for the first RAN node.

[0247] According to some embodiments, the resource status failure message including the cause value to indicate the mismatch may be received before completion of the RAN configuration update for the first RAN node.

[0248] According to some embodiments, the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, the first and second pluralities of cells and/or beams are different, and the resource status request message includes a subset of the first plurality of identifiers.

[0249] According to some embodiments, a first configuration identifier is associated with the first RAN configuration of the first RAN node, a second configuration identifier is associated with the second RAN configuration of the first RAN node, the first and second configuration identifiers are different, the resource status request message includes the first configuration identifier, and the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to the resource status request message including the first configuration identifier.

[0250] Various operations from the flow charts of FIGS. 58A-C may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 37 (set forth below), for example, operations of blocks 5815, 5819, 5819-1 , and/or 5819-2 of FIGS. 58A-C may be optional.

[0251] According to some embodiments, “Resource Status Reporting” is sent based on an “Old” configuration (also referred to as an old RAN configuration or a 1st RAN configuration).

[0252] The Resource Status Reporting Initiation procedure is successfully completed, and the first RAN node is sending Resource Status Updates to the second RAN node, according to its current configuration, which is labeled as “Old” configuration in the examples in FIGS. 50-51 .

[0253] The first RAN node initiates a RAN configuration update and informs the second RAN node about a “New” configuration (also referred to as a new RAN configuration or a 2nd RAN configuration), where, e.g. new Served Cells or beams (such as SSB beams or CSI-RS beams) have been added or Served Cells or beams have been deleted.

[0254] Note that in this scenario, the Resource Status Reporting Initiation procedure is successfully completed, hence no Resource Status Failure can be used. [0255] In this scenario, there is an issue depending on the behavior of the first RAN node.

[0256] According to the current embodiment, it is possible for the first RAN node to continue sending Resource Status Update to the second RAN node according to the “Old” configuration until the first RAN node receives a new Resource Status Request. Therefore, the second RAN node may receive inaccurate information for an excessive amount of time.

[0257] The present embodiment discloses methods to stop the first RAN node sending Resource Status Update to the second RAN node according to the “Old” configuration. [0258] To stop the first RAN node sending Resource Status Update, different triggers can be used: when the first RAN node sends to the second RAN node a RAN Configuration Update, as in FIG. 50; when the first RAN node receives from the second RAN node a RAN Configuration Update Acknowledge associated to the new configuration of the first RAN node, as in FIG. 50; when the first RAN node receives from the second RAN node a RAN Configuration Update Failure associated to the new configuration of the first RAN node, as in FIG. 50; and when the first RAN node receives from the second RAN node a new initial message of a Resource Status Reporting Initiation (such as RESOURCE STATUS REQUEST) associated to the new configuration of the first RAN node, as illustrated in FIG. 51.

[0259] FIG. 50 is a message diagram illustrating embodiments where the first RAN node changes its configuration to a “new configuration, while a resource Status Reporting procedure has been successfully initiated with a second RAN node based on an “old” configuration of the first RAN node. In this case, the first RAN node stops the transmission of RESOURCE STATUS UPDATE based on the “old” configuration if either a RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message, or a RAN NODE CONFIGURATION UPDATE FAILURE message is received.

[0260] Operations of a first RAN node of FIG. 50 (implemented using the structure of FIG. 55) will now be discussed with reference to the flow charts of FIGS. 59A-C according to some embodiments of inventive concepts. For example, modules may be stored in memory 5505 of FIG. 55, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 5503, processing circuitry 5503 performs respective operations of the flow chart.

[0261 ] According to some embodiments at block 5901 , processing circuitry 5503 transmits (through network interface 5507) information about a first RAN configuration of the first RAN node to the second RAN node. The information may be transmitted as part of a set up procedure or a configuration update. Transmission of this information is shown as message/operation 5001 of FIG. 50.

[0262] According to some embodiments at block 5905, processing circuitry 5503 receives (through network interface 5507) a resource status request message from the second RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node. Reception of the resource status request message is shown as message/operation 5003 of FIG. 50. According to some embodiments, the resource status request message may be used to schedule one or a plurality of resource status update messages.

[0263] According to some embodiments at block 5907, processing circuitry 5503 may transmit (through network interface) a scheduled resource status update message of the plurality of scheduled resource status update messages based on the resource status request message before transmitting a RAN node configuration update message (e.g., before transmitting a RAN node configuration update message at block 5911 and/or before determining a second RAN configuration at block 5909). Transmission of this scheduled resource status update message is shown as message/operation 5004 of FIG. 50.

[0264] According to some embodiments at block 5909, processing circuitry 5503 determines a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after receiving the resource status request message from the second RAN node, wherein the first and second RAN configurations are different. This determination is shown as operation 5005 of FIG. 50.

[0265] According to some embodiments at block 5910, processing circuitry 5503 may transmit (through network interface 5507) a scheduled resource status update message of the plurality of scheduled resource status update messages based on the resource status request message after determining the second RAN configuration at block 5909 and before transmitting the RAN node configuration update message at block 5911 . Transmission of this scheduled resource status update message is shown as message/operation 5006 of FIG. 50.

[0266] According to some embodiments at block 5911 , processing circuitry 5503 transmits (through network interface 5507) a RAN node configuration update message to the second RAN node for the RAN configuration update after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node. Transmission of the RAN node configuration update message is shown as message/operation 5007 of FIG. 50.

[0267] According to some embodiments at block 5915, processing circuitry 5503 receives (through network interface 5507) a RAN node configuration update response message from the second RAN node after transmitting the RAN node configuration update message. The RAN node configuration update response message may be a RAN node configuration update acknowledge message which is an acknowledgement of the RAN node configuration update message to indicate completion of the RAN configuration update, or the RAN node configuration update response message may be a RAN node configuration update failure message to indicate failure of the RAN node configuration update. Reception of the RAN node configuration update response message is illustrating in message/operation 5008 of FIG. 50.

[0268] According to some embodiments at block 5919, processing circuitry 5503 stops transmission of a scheduled resource status update message corresponding to the resource status request message after transmitting the RAN node configuration update message. Stopping transmission is shown as operation 5009 of FIG. 50. For example, transmission of the scheduled resource status update message may be stopped responsive to transmitting the RAN node configuration update message, transmission of the scheduled resource status update message may be stopped after receiving the RAN node configuration update response message, and/or transmission of the scheduled resource status update message may be stopped responsive to receiving the RAN node configuration update response message.

[0269] According to some embodiments, the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, the first and second pluralities of cells and/or beams are different, and the resource status request message includes a subset of the first plurality of identifiers. [0270] Various operations from the flow charts of FIGS. 59A-C may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 14 (set forth below), for example, operations of blocks 5907, 5910, 5915, 5919, 5915-1 , and/or 5915-2 of FIGS. 59A-C may be optional.

[0271] Operations of a second RAN node 5000 of FIG. 50 (implemented using the structure of FIG. 55) will now be discussed with reference to the flow charts of FIGS. 60A-C according to some embodiments of inventive concepts. For example, modules may be stored in memory 5505 of FIG. 55, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 5503, processing circuitry 5503 performs respective operations of the flow chart.

[0272] According to some embodiments at block 6001 , processing circuitry 5503 receives (through network interface 5507) information about a first RAN configuration of the first RAN node from the first RAN node. The information may be received as part of a set up procedure or a configuration update. Reception of this information is shown as message/operation 5001 of FIG. 50.

[0273] According to some embodiments at block 6005, processing circuitry 5503 transmits (through network interface 5507) a resource status request message to the first RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node. Transmission of the resource status request message is shown as message/operation 5003 of FIG. 50.

[0274] According to some embodiments at block 6007, processing circuitry 5503 receives (through network interface) a scheduled resource status update message of a plurality of scheduled resource status update messages based on the resource status request message (based on the first RAN configuration) before receiving the RAN node configuration update message. Reception of the resource status update message is shown as message(s)/operation(s) 5004 and/or 5006. Any number of such resource status update messages may be received based on the resource status request message before the first RAN node stops transmission of resource status updates based on the first RAN configuration. [0275] According to some embodiments at block 6011 , processing circuitry 5503 receives (through network interface 5507) a RAN node configuration update message from the first RAN node, wherein the RAN node configuration update message includes information about a second RAN configuration of the first RAN node for a RAN configuration update of the first RAN node. Reception of the RAN node configuration update message is shown as message/operation 5007 of FIG. 50.

[0276] According to some embodiments at block 6015, processing circuitry 5503 transmits (through network interface 5507) a RAN node configuration update response message to the first RAN node responsive to receiving the RAN node configuration update message, where the RAN node configuration update response message may be a RAN node configuration update acknowledge message at operation 6015-1 or a RAN node configuration update failure message at operation 6015-2. Transmission of the RAN node configuration update response message is shown as message/operation 5008 of FIG. 50. The RAN node configuration update response message may be a RAN node configuration update acknowledge message as an acknowledgement of the RAN node configuration update message to indicate completion of the RAN configuration update of the first RAN node, or the RAN node configuration update response message may be a RAN node configuration update failure message to indicate failure of the RAN configuration update of the first RAN node.

[0277] According to some embodiments, the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, the first and second pluralities of cells and/or beams are different, and the resource status request message includes a subset of the first plurality of identifiers.

[0278] Various operations from the flow charts of FIGS. 60A-C may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 49 (set forth below), for example, operations of blocks 6007, 6015, 6015-1 , and/or 6015-2 of FIG. 60A-C may be optional. [0279] FIG. 51 is a message diagram illustrating embodiments where the first RAN node changes its configuration to a “new” configuration, while a resource Status Reporting procedure has been successfully initiated with a second RAN node based on an “old” configuration of the first RAN node. In this case, the first RAN node stops the transmission of RESOURCE STATUS UPDATE based on the “old” configuration upon receiving a new RESOURCE STATUS REQUEST message based on the “new” configuration of the first RAN node.

[0280] According to some embodiments, “Resource Status Reporting Initiation” is initiated based on an “Old” configuration, “New” configuration is an extension of “Old” configuration.

[0281] This scenario is similar to the scenario of FIG. 49, where the “New” configuration is a superset of the cells and/or Beams comprised in the old configuration (e.g., the “New” configuration comprises cell identifiers and/or beam identifiers comprised in the “Old” configuration which are reused in the “New” configuration together with new cell identifiers and/or beam identifiers).

[0282] In FIG. 52, the first RAN node receiving the initial message of a Resource Status Reporting Initiation procedure is not able to detect that the request is based on an “Old” configuration. The Resource Status Initiation procedure can be successfully completed, and the subsequent Resource Status Update will provide unreliable or partial information with respect to the new configuration.

[0283] The issue may be addressed by the present embodiment by using a unique identifier, such as a RAN Configuration Identifier, which is sent by the first RAN node in a RAN Configuration Update.

[0284] Prior to the reception of a Resource Status Request, the first RAN node has sent to the second RAN node a RAN Configuration Update (or a RAN Setup, such as an X2 Setup or Xn Setup) which includes a RAN Configuration Identifier associated with the “Old” configuration.

[0285] The first RAN node receives the first message of the Resource Status Reporting procedure (such as RESOURCE STATUS REQUEST) including the same RAN Configuration Identifier associated with the ’’Old” configuration. This allows the first RAN node to determine that there is a mismatch between the RAN configuration Identifier included in the Resource Status Reporting Initiation procedure and the RAN configuration Identifier associated with the “New” configuration. The first RAN node then sends to the second RAN node a Resource Status Failure, which may include the new cause value, such as “Configuration Update”.

[0286] FIG. 52 is a message diagram illustrating an issue that may be addressed by some embodiments of inventive concepts where the first RAN node changes its configuration to a “new configuration, while receiving a RESOURCE STATUS REQUEST message from a second RAN node based on an “old” configuration of the first RAN node. In this case, the “new” configuration consists of a superset of cells of RS beam areas of the “old” configuration.

[0287] FIG. 53 is a message diagram illustrating some embodiments of inventive concepts.

[0288] Operations of a first RAN node of FIG. 53 (implemented using the structure of FIG. 55) will now be discussed with reference to the flow charts of FIGS. 61 A-C according to some embodiments of inventive concepts. For example, modules may be stored in memory 5505 of FIG. 55, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 5503, processing circuitry 5503 performs respective operations of the flow chart.

[0289] According to some embodiments at block 6101 , processing circuitry 5503 transmits (through network interface 5507) information about a first RAN configuration of the first RAN node to the second RAN node, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node. The information may be transmitted as part of a set up procedure or a configuration update. Transmission of this information is shown as message/operation 5301 of FIG. 53.

[0290] According to some embodiments at block 6105, processing circuitry 5503 determines a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node. The first and second RAN configurations are different, a second configuration identifier is associated with the second RAN configuration of the first RAN node, and the first and second configuration identifiers are different. This determination is shown as operation 5302 of FIG. 53. [0291] According to some embodiments at block 6109, processing circuitry 5503 receives (through network interface 5507) a resource status request message from the second RAN node after determining the second RAN configuration of the first RAN node. The resource status request message includes the first configuration identifier. Reception of the resource status request message is shown as message/operation 5304 of FIG. 53.

[0292] According to some embodiments at block 6111 , processing circuitry 5503 transmits (through network interface 5507) a resource status failure message to the second RAN node responsive to receiving the resource status request message including the first configuration identifier. Transmission of the resource status failure message is shown as message/operation 5305 of FIG. 53. According to some embodiments, the resource status failure message may include a cause value to indicate a mismatch between the second RAN configuration of the RAN configuration update and the first RAN configuration of the resource status request message responsive to the resource status request message including the first configuration identifier. For example, the cause value may be set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update). [0293] According to some embodiments at block 6115, processing circuitry 5503 transmits (through network interface 5507) a RAN node configuration update message to the second RAN node after determining the second RAN configuration of the first RAN node. The RAN node configuration update message includes information about the second RAN configuration of the first RAN node including the second configuration identifier. Transmission of the RAN node configuration update message is shown as message/operation 5306 of FIG. 53. For example, the RAN node configuration update message may be transmitted after transmitting the resource status failure message.

[0294] According to some embodiments at block 6119, processing circuitry 5503 receives (through network interface 5507) a RAN node configuration update response message from the second RAN node after transmitting the RAN node configuration update message and/or after transmitting the resource status failure message, where the RAN node configuration update response message may be a RAN node configuration update acknowledge message of block 6119-1 or a RAN node configuration update failure message of block 6119-2. The RAN node configuration update response message may be a RAN node configuration update acknowledge message as an acknowledgement of the RAN node configuration update message to complete the RAN configuration update for the second RAN configuration of the first RAN node. The RAN node configuration update response message may be a RAN node configuration update failure message to indicate failure of the RAN configuration update for the first RAN node.

[0295] According to some embodiments, the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, the first and second pluralities of cells and/or beams are different, and the resource status request message includes a subset of the first plurality of identifiers.

[0296] Various operations from the flow charts of FIGS. 61 A-C may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 25 (set forth below), for example, operations of blocks 6115, 6119, 6119-1 , and/or 6119-2 of FIGS. 61 A-C may be optional.

[0297] Operations of a second RAN node of FIG. 53 (implemented using the structure of FIG. 55) will now be discussed with reference to the flow charts of FIGS. 62A-C according to some embodiments of inventive concepts. For example, modules may be stored in memory 5505 of FIG. 55, and these modules may provide instructions so that when the instructions of a module are executed by respective RAN node processing circuitry 5503, processing circuitry 5503 performs respective operations of the flow chart.

[0298] According to some embodiments at block 6201 , processing circuitry 5503 receives (through network interface 5507) information about a first RAN configuration of the first RAN node from the first RAN node, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node. The information may be received as part of a set up procedure or a configuration update. Reception of this information is shown as message/operation 5301 of FIG. 53.

[0299] According to some embodiments at block 6209, processing circuitry 5503 transmits (through network interface 5507) a resource status request message to the first RAN node after receiving the information about the first RAN configuration of the first RAN node, wherein the resource status request message includes the first configuration identifier. Transmission of the resource status request message is shown as message/operation 5304 of FIG. 53.

[0300] According to some embodiments at block 6211 , processing circuitry 5503 receives (through network interface 5507) a resource status failure message from the first RAN node based on the resource status request message including the first configuration identifier. Reception of the resource status failure message is shown as message/operation 5305 of FIG. 53.

[0301] According to some embodiments at block 6215, processing circuitry 5503 receives (through network interface 5507) a RAN node configuration update message from the first RAN node after transmitting the resource status request message, wherein the RAN node configuration update message includes information about a RAN configuration update for a second RAN configuration for the first RAN node including the second configuration identifier. Reception of the RAN node configuration update message is shown as message/operation 5306 of FIG. 53. For example, the RAN node configuration update message may be received after receiving the resource status failure message.

[0302] According to some embodiments at block 6219, processing circuitry 5503 transmits (through network interface 5507) a RAN Node configuration update response message to the first RAN node after receiving the RAN node configuration update message and/or after receiving the resource status failure message, where the RAN node configuration update response message may be a RAN node configuration update acknowledge message or a RAN node configuration update failure message. The RAN node configuration update response message may be a RAN node configuration update acknowledge message as an acknowledgement of the RAN node configuration update message to complete the RAN configuration update for the second RAN configuration of the first RAN node. The RAN node configuration update response message may be a RAN node configuration update failure message to indicate failure of the RAN configuration update for the first RAN node.

[0303] According to some embodiments, the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, the first and second pluralities of cells and/or beams are different, and the resource status request message includes a subset of the first plurality of identifiers.

[0304] According to some embodiments, the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the first RAN node and the first RAN configuration of the resource status request message. For example, the cause value may be set to indicate that the mismatch is due to a RAN configuration update (e.g., the cause value is set to configuration update). [0305] Various operations from the flow charts of FIGS. 62A-C may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiment 54 (set forth below), for example, operations of blocks 6215, 6219, 6219-1 , and/or 6219-2 of FIGS. 62A-C may be optional.

[0306] Embodiments relating to the first RAN node (RAN node 1) are discussed below.

[0307] In a first embodiment, transmitting to the second RAN node a Status Failure message (such as a RESOURCE STATUS FAILURE message) with a Cause indicating that the procedure initiated to request information updates (such as resource status updates) has failed because the received request concerns a configuration of the first RAN node that is different from the one currently valid. As non-limiting examples, the procedure initiated to information updates can be procedures to request resource status updates such as one of the following: X2AP “Reporting Status Reporting Initiation”, X2AP “EN-DC Resource Status Reporting Initiation”, XnAP “Reporting Status Reporting Initiation.” In one embodiment, the initiating message of the procedure initiated to request information updates such as resource status updates comprises a list of downlink RS beams (such as SSB beams or CSI-RS beam).

[0308] In another embodiment, transmitting to the second RAN node a Setup or Configuration Update request comprising an identifier such as a RAN Configuration Identifier. A RAN Configuration Identifier uniquely identify a given RAN Configuration. The methods used to obtain such identifier are not discussed in the present invention. Examples of Setup requests can be: XN SETUP REQUEST, X2 SETUP REQUEST, EN-DC X2 SETUP REQUEST. Example of Configuration Update Request can be: NG- RAN NODE CONFIGURATION UPDATE, ENB CONFIGURATION UPDATE, EN-DC CONFIGURATION UPDATE.

[0309] In another embodiment, receiving from the second RAN node the initiating message of the procedure to request information updates such as resource status updates comprising the RAN Configuration identifier.

[0310] In another embodiment, transmitting to the second RAN node a Status Response message (such as a RESOURCE STATUS RESPONSE) message to indicate a successfully completed procedure to request information update such as request resource status update from the first RAN node, the message comprising the RAN Configuration Identifier

[0311] In another embodiment, transmitting to the second RAN node a Status Update message (such as a RESOURCE STATUS UPDATE message), the message comprising the RAN Configuration Identifier.

[0312] In another embodiment, stop sending to the second RAN node resource status updates: when the first RAN node receives from the second RAN node a RAN Configuration Update Acknowledge associated to the new configuration of the first RAN node; when the first RAN node receives from the second RAN node a RAN Configuration Update Failure associated to the new configuration of the first RAN node; and when the first RAN node receives from the second RAN node a new initial message of a Resource Status Reporting Initiation (such as RESOURCE STATUS REQUEST) associated to a new configuration of the first RAN node. [0313] Embodiments relating to the second RAN node (RAN node 2) are discussed below.

[0314] In a first embodiment, receiving from the first RAN node a Status Failure message (such as a RESOURCE STATUS FAILURE message) with a Cause indicating that the procedure initiated to request information updates (such as resource status updates) has failed because the received request concerns a configuration of the first RAN node that is different from the one currently valid.

[0315] In another embodiment, receiving from the first RAN node a Setup or Configuration Update request comprising an identifier such as a RAN Configuration Identifier.

[0316] In another embodiment, transmitting to the first RAN node the initiating message of the procedure to request information updates such as resource status updates comprising the RAN Configuration identifier.

[0317] In another embodiment, receiving from the first RAN node a Status Response message (such as a RESOURCE STATUS RESPONSE) message to indicate a successfully completed procedure to request information update such as request resource status update from the first RAN node, the message comprising the RAN Configuration Identifier.

[0318] In another embodiment, receiving from the first RAN node a Status Update message (such as a RESOURCE STATUS UPDATE message), the message comprising the RAN Configuration Identifier.

[0319] In another embodiment, sending to the first RAN node a new initial message of a Resource Status Reporting Initiation (such as RESOURCE STATUS REQUEST) if a RAN Configuration Update is received from the first RAN node.

[0320] The Resource Status Request is associated to the new configuration of the first RAN node, as an example by means of a RAN Configuration Identifier.

[0321] Examples of implementations for LTE and EN-DC are provided below based on modifications to Sections 8.3.6, 8.3.6.1 , 8.3.6.2, 8.3.6.3, 8.3.7, 8.3.7.1 , 8.3.7.2, 8.3.7.3, 8.3.7.4, 9.1.2.13, 9.2.6, 9.1.2.11 , 8.7.21 , 8.7.21.1 , 8.7.21.2, 8.7.21.3, 8.7.21.4, 8.7.22, 8.7.22.1 , 8.7.22.2, 8.7.22.3, 8.7.22.4, 9.1.2.8, and 9.1.2.34 of TS 36.423 (X2AP). [0322] A Resource Status Reporting Initiation procedure is used by an eNB to request the reporting of load measurements to another eNB. The procedure uses non UE-associated signaling. FIG.3 illustrates an example of successful operation of a resource status reporting initiation. The procedure is initiated with a RESOURCE STATUS REQUEST message sent from eNB1 to eNB2. Upon receipt, eNB2: shall initiate the requested measurement according to the parameters given in the request in case the Registration Request IE set to "start"; or shall stop all cells measurements and terminate the reporting in case the Registration Request IE is set to "stop"; or if supported, stop cell measurements and terminate the reporting for cells indicated in the Cell To Report IE list, in case the Registration Request IE is set to "partial stop"; or if supported, add cells indicated in the Cell To Report IE list to the measurements initiated before for the given measurement IDs, in case the Registration Request IE is set to "add".

[0323] If the eNB2 received a RESOURCE STATUS REQUEST message, which includes the Registration Request IE set to "stop", the Cell To Report IE list shall be ignored.

[0324] If the Registration Request IE is set to "start" then the Report Characteristics IE shall be included in RESOURCE STATUS REQUEST message. The eNB2 shall ignore the Report Characteristics IE, if the Registration Request IE is not set to "start".

[0325] The Report Characteristics IE indicates the type of objects eNB2 shall perform measurements on. For each cell, the eNB2 shall include in the RESOURCE STATUS UPDATE message: the Radio Resource Status IE, if the first bit, "PRB Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the S1 TNL Load Indicator IE, if the second bit, "TNL Load Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the Hardware Load Indicator IE, if the third bit, "HW Load Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the Composite Available Capacity Group IE, if the fourth bit, "Composite Available Capacity Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 . If Cell Capacity Class Value IE is included within the Composite Available Capacity Group IE, this IE is used to assign weights to the available capacity indicated in the Capacity Value IE; the ABS Status IE, if the fifth bit, "ABS Status Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 and eNB1 had indicated the ABS pattern to eNB2; the RSRP Measurement Report List IE, if the sixth bit, "RSRP Measurement Report Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; and the CSI Report IE, if the seventh bit, "CSI Report Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 .

[0326] If the Reporting Periodicity IE is included in the RESOURCE STATUS REQUEST message, eNB2 shall use its value as the time interval between two subsequent RESOURCE STATUS UPDATE messages that include the Radio Resource Status IE, S1 TNL Load Indicator IE, Hardware Load Indicator IE, Composite Available Capacity Group IE, or ABS Status IE.

[0327] If the Reporting Periodicity of RSRP Measurement Report IE is included in the RESOURCE STATUS REQUEST message, eNB2 shall use its value as the minimum time interval between two subsequent RESOURCE STATUS UPDATE messages that include the RSRP Measurement Report List IE.

[0328] If the Reporting Periodicity of CSI Report IE is included in the RESOURCE STATUS REQUEST message, eNB2 shall use its value as the minimum time interval between two subsequent RESOURCE STATUS UPDATE messages that include the CSI Report IE.

[0329] If eNB2 is capable to provide all requested resource status information, it shall initiate the measurement as requested by eNB1 , and respond with the RESOURCE STATUS RESPONSE message.

[0330] If eNB2 is capable to provide some but not all of the requested resource status information and the Partial Success Indicator IE is present in the RESOURCE STATUS REQUEST message, it shall initiate the measurement for the admitted measurement objects and include the Measurement Initiation Result IE in the RESOURCE STATUS RESPONSE message.

[0331] Interaction with other procedures is described below. [0332] If an ENB CONFIGURATION UPDATE is received by the eNB1 from eNB2, the eNB1 shall discard the current Resource Status Reporting Initiation and may reinitialize a new Resource Status Reporting Initiation based on the new eNB2 configuration.

[0333] FIG. 4 illustrates an example of unsuccessful operation of a resource status reporting initiation

[0334] If none of the requested measurements can be initiated, eNB2 shall send a RESOURCE STATUS FAILURE message. The Cause IE shall be set to an appropriate value e.g. "Measurement Temporarily not Available" or "Measurement not Supported For The Object" for each requested measurement object. The eNB may use the Complete Failure Cause Information IE to enhance the failure cause information per measurement in the RESOURCE STATUS FAILURE message.

[0335] If the initiating eNB1 does not receive either RESOURCE STATUS RESPONSE message or RESOURCE STATUS FAILURE message, the eNB1 may reinitiate the Resource Status Reporting Initiation procedure towards the same eNB, provided that the content of the new RESOURCE STATUS REQUEST message is identical to the content of the previously unacknowledged RESOURCE STATUS REQUEST message.

[0336] If the initiating eNB1 receives the RESOURCE STATUS RESPONSE message including the Measurement Initiation Result IE containing no admitted measurements, the eNB1 shall consider the procedure as failed.

[0337] If the Report Characteristics IE bitmap is set to "0" (all bits are set to "0") in the RESOURCE STATUS REQUEST message then eNB2 shall initiate a RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "ReportCharacteristicsEmpty".

[0338] If the Reporting Periodicity IE value is not specified when at least one of the bits of the Report Characteristics IE, for which semantics is specified, other than the sixth or seventh bit, is set to 1 then eNB2 shall initiate a RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g.

"NoReportPeriodicity". [0339] If the Reporting Periodicity of RSRP Measurement Report IE value is not specified when the sixth bit of the Report Characteristics IE is set to 1 , then eNB2 shall initiate the RESOURCE STATUS FAILURE message and the cause shall be set to appropriate value e.g. "NoReportPeriodicity".

[0340] If the Reporting Periodicity of CSI Report IE value is not specified when the seventh bit of the Report Characteristics IE is set to 1 , then eNB2 shall initiate the RESOURCE STATUS FAILURE message and the cause shall be set to appropriate value e.g. "NoReportPeriodicity".

[0341] If the eNB2 received a RESOURCE STATUS REQUEST message which includes the Registration Request IE set to "start" and the eNB1 Measurement ID IE corresponding to an existing on-going load measurement reporting, then eNB2 shall initiate a RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "ExistingMeasurementlD".

[0342] If the Registration Request IE is set to "stop", "partial stop" or "add" and the RESOURCE STATUS REQUEST message does not contain eNB2 Measurement ID IE, eNB2 shall consider the procedure as failed and respond with the RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "Unknown eNB Measurement ID".

[0343] If the Registration Request IE is set to "partial stop" and the Cell To Report IE contains cells that have not been initiated for the reporting before, eNB2 shall consider the procedure as failed and respond with the RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "Cell not Available". If the Registration Request IE is set to "add" and the Cell To Report IE contains cells that have been initiated for the reporting before, eNB2 shall consider the procedure as failed and respond with the RESOURCE STATUS FAILURE message, the cause shall be set to appropriate value e.g. "Cell not Available".

[0344] A Resource Status Reporting procedure is initiated by eNB2 to report the result of measurements admitted by eNB2 following a successful Resource Status Reporting Initiation procedure.

[0345] FIG. 5 illustrates an example of successful operation of resource status reporting. [0346] The eNB2 shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure, and thus not reported in the Measurement Failed Report Characteristics IE for the concerned cell in the RESOURCE STATUS RESPONSE message.

[0347] If the eNB1 receives the RESOURCE STATUS UPDATE message which includes the UE ID IE in the RSRP Measurement Report List IE, the eNB1 may use the UE ID IE to link the associated RSRP measurement report with other measurement results (e.g. CSI reports, RSRP measurement reports) of the same UE.

[0348] If the CSI Report IE including the CSI Process Configuration Index IE is received, eNB1 shall interpret this IE as an index identifying one of the CSI process configurations that can be configured for all UEs within the cell where the CSI measurements were collected. For all UEs within the cell, the maximum number of CSI process configurations is given by the maximum value of the CSI Process Configuration Index IE.

[0349] If the eNB1 receives the RESOURCE STATUS UPDATE message, which includes the Cell Reporting Indicator IE set to "stop request" in one or more items of the Cell Measurement Result IE, the eNB1 should initialise the Resource Status Reporting Initiation procedure to remove all or some of the corresponding cells from the measurement.

[0350] If the eNB1 receives a RESOURCE STATUS UPDATE message which includes the ABS Status IE, and all bits in the Usable ABS Pattern Info IE are set to 'O', the eNB1 shall ignore the DL ABS Status IE.

[0351] If an ENB CONFIGURATION UPDATE ACKNOWLEDGE is received by the eNB2 from eNB1 , the eNB2 shall stop the procedure.

[0352] If an ENB CONFIGURATION UPDATE FAILURE is received by the eNB2 from eNB1 , the eNB2 shall stop the procedure.

[0353] A RESOURCE STATUS FAILURE message is sent by the eNB2 to indicate that for none of the requested measurement objects the measurement can be initiated. FIGS. 19-20 illustrate examples of a RESOURCE STATUS FAILURE IE and associated information.

[0354] The purpose of the cause information element is to indicate the reason for a particular event for the whole protocol.

[0355] FIGS. 21 -25 are tables illustrating examples of a Cause IE and associated information.

[0356] The meaning of the different cause values is described in the following table. In general, "not supported" cause values indicate that the concerned capability is missing. On the other hand, "not available" cause values indicate that the concerned capability is present, but insufficient resources were available to perform the requested action.

[0357] A RESOURCE STATUS REQUEST message is sent by an eNB1 to neighbouring eNB2 to initiate the requested measurement according to the parameters given in the message.

[0358] FIGS. 26-28 are tables illustrating examples of a resource status request IE and associated information.

[0359] An EN-DC Resource Status is discussed below.

[0360] An EN-DC Resource Status Reporting Initiation procedure is used by the eNB to request the reporting of load measurements to the en-gNB. The procedure uses non UE-associated signaling.

[0361 ] FIG. 29 illustrates an example of successful operation of an EN-DC Resource Status Reporting Initiation procedure. The procedure is initiated with an EN- DC RESOURCE STATUS REQUEST message sent from the eNB to the en-gNB to start a measurement, stop a measurement, add cells to report for a measurement.

[0362] If the Report Characteristics IE is included in the EN-DC RESOURCE STATUS REQUEST message and indicates cell specific measurements, the Cell To Report EN-DC List IE shall be included.

[0363] Upon receipt of the EN-DC RESOURCE STATUS REQUEST message, the en-gNB: shall initiate the requested measurement according to the parameters given in the request in case the Registration Request IE set to "start"; or shall stop all cells measurements and terminate the reporting in case the Registration Request IE is set to "stop"; or shall add cells indicated in the Cell To Report EN-DC List IE list to the measurements initiated before for the given measurement IDs, in case the Registration Request IE is set to "add". If measurements are already initiated for a cell indicated in the Cell To Report EN-DC List IE, this information shall be ignored.

[0364] The en-gNB shall send an EN-DC RESOURCE STATUS RESPONSE message to the eNB to indicate that all of the requested measurement objects the measurement can be initiated.

[0365] Interaction with other procedures is described below.

[0366] When starting a measurement, the Report Characteristics IE in the EN-DC RESOURCE STATUS REQUEST indicates the type of objects en-gNB shall perform measurements on. For each cell, the en-gNB shall include in the EN-DC RESOURCE STATUS UPDATE message: the Radio Resource Status IE, if the first bit, "PRB Periodic" of the Report Characteristics IE included in the EN-DC RESOURCE STATUS REQUEST message is set to 1. If the cell for which Radio Resource Status IE is requested to be reported supports more than one SSB, the Radio Resource Status IE for such cell shall include the SSB Area Radio Resource Status Item IE for all SSB areas supported by the cell. If the SSB To Report List IE is included for a cell, the Radio Resource Status IE for such cell shall include the requested SSB Area Radio Resource Status List IE; the TNL Capacity Indicator IE, if the second bit, "TNL Capacity Ind Periodic" of the Report Characteristics IE included in the EN-DC RESOURCE STATUS REQUEST message is set to 1 ; the Composite Available Capacity Group IE, if the third bit, "Composite Available Capacity Periodic" of the Report Characteristics IE included in the EN-DC RESOURCE STATUS REQUEST message is set to 1 . If Cell Capacity Class Value IE is included within the Composite Available Capacity Group IE, this IE is used to assign weights to the available capacity indicated in the Capacity Value IE. If the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one SSB, and if the SSB To Report List IE is included for a cell, the Composite Available Capacity Group IE for such cell shall include the requested SSB Area Capacity Value List IE, providing the SSB area capacity with respect to the Cell Capacity Class Value. [0367] If the Reporting Periodicity IE in the EN-DC RESOURCE STATUS REQUEST is present, this indicates the periodicity for the reporting of periodic measurements. The en-gNB shall only report more than once if the Reporting Periodicity IE is included.

[0368] If a ENB CONFIGURATION UPDATE is received by the eNB from en- gNB, the eNB shall discard the current Resource Status Reporting Initiation and may reinitialize a new Resource Status Reporting Initiation based on the new en-gNB configuration.

[0369] FIG. 30 illustrates an example of an unsuccessful operation of an EN-DC Resource Status Reporting Initiation procedure.

[0370] If any of the requested measurements cannot be initiated, the en-gNB shall send a RESOURCE STATUS FAILURE message.

[0371] An EN-DC Resource Status Reporting procedure is initiated by the en- gNB to report the result of measurements admitted by the en-gNB following a successful EN-DC Resource Status Reporting Initiation procedure. The procedure uses non UE-associated signaling.

[0372] FIG. 31 illustrates an example of a successful operation of an EN-DC Resource Status Reporting procedure.

[0373] The en-gNB shall report the results of the admitted measurements in the EN-DC RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding EN-DC Resource Status Reporting Initiation procedure.

[0374] For eNB Initiated EN-DC Configuration Update, if an EN-DC CONFIGURATION UPDATE ACKNOWLEDGE is received by the eNB from en-gNB, the eNB shall stop the procedure.

[0375] For eNB Initiated EN-DC Configuration Update, if an EN-DC CONFIGURATION UPDATE FAILURE is received by the eNB from en-gNB, the eNB shall stop the procedure.

[0376] Configuration Update message is sent by an eNB to a peer eNB to transfer updated information for a TNL association. FIGS. 32-34 illustrate examples of a Configuration Update IE and associated information. [0377] An EN-DC CONFIGURATION UPDATE message is sent by an initiating node to a peer neighbouring node, both nodes able to interact for EN-DC, to transfer updated information for a TNL association. FIGS. 35-36 illustrate examples of a EN-DC Configuration Update IE and associated information.

[0378] An example of an implementation for NR (New Radio) is discussed below with respect to modifications of Sections 8.4.10, 8.4.10.1 , 8.4.10.2, 8.4.10.3, 8.4.10.4, 8.4.11 , 8.4.11.1 , 8.4.11.2, 8.4.11.3, 8.4.11.4, 9.1.3.20, 9.2.3.2, 9.1.3.18, and 9.1.3.4 of TS 38.423 (XnAP).

[0379] A Resource Status Reporting Initiation procedure is used by an NG-RAN node to request the reporting of load measurements to another NG-RAN node. The procedure uses non UE-associated signaling.

[0380] FIG. 7 illustrates an example of a successful operation of a resource status reporting initiation.

[0381] NG-RAN nodel initiates the procedure by sending the RESOURCE STATUS REQUEST message to NG-RAN node2 to start a measurement, stop a measurement or add cells to report for a measurement. Upon receipt, NG-RAN node2: shall initiate the requested measurement according to the parameters given in the request in case the Registration Request IE set to "start"; or shall stop all cells measurements and terminate the reporting in case the Registration Request IE is set to "stop"; or shall add cells indicated in the Cell To Report List IE to the measurements initiated before for the given measurement IDs, in case the Registration Request IE is set to "add". If measurements are already initiated for a cell indicated in the Cell To Report List IE, this information shall be ignored.

[0382] If the Registration Request IE is set to "start" in the RESOURCE STATUS REQUEST message and the Report Characteristics IE indicates cell specific measurements, the Cell To Report List IE shall be included.

[0383] If Registration Request IE is set to "add" in the RESOURCE STATUS REQUEST message, the Cell To Report List IE shall be included.

[0384] If NG-RAN node2 is capable to provide all requested resource status information, it shall initiate the measurement as requested by NG-RAN nodel and respond with the RESOURCE STATUS RESPONSE message. [0385] Interaction with other procedures is described below.

[0386] When starting a measurement, the Report Characteristics IE in the RESOURCE STATUS REQUEST indicates the type of objects NG-RAN node2 shall perform measurements on. For each cell, NG-RAN node2 shall include in the RESOURCE STATUS UPDATE message: the Radio Resource Status IE, if the first bit, "PRB Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 . If NG-RAN node2 is a gNB and if the cell for which Radio Resource Status IE is requested to be reported supports more than one SSB, the Radio Resource Status IE for such cell shall include the SSB Area Radio Resource Status Item IE for all SSB areas supported by the cell. If the SSB To Report List IE is included for a cell, the Radio Resource Status IE for such cell shall include the requested SSB Area Radio Resource Status List IE; the TNL Capacity Indicator IE, if the second bit, "TNL Capacity Ind Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the Composite Available Capacity Group IE, if the third bit, "Composite Available Capacity Periodic" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 . If the Cell Capacity Class Value IE is included within the Composite Available Capacity Group IE, this IE is used to assign weights to the available capacity indicated in the Capacity Value IE. If NG-RAN node2 is a gNB and if the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one SSB, the Composite Available Capacity Group IE for such cell shall include the SSB Area Capacity Value List for all SSB areas supported by the cell, providing the SSB area capacity with respect to the Cell Capacity Class Value. If the SSB To Report List IE is included for a cell, the Composite Available Capacity Group IE for such cell shall include the requested SSB Area Capacity Value List IE. If the cell for which Composite Available Capacity Group IE is requested to be reported supports more than one slice, and if the Slice To Report List IE is included for a cell, the Slice Available Capacity IE for such cell shall include the requested Slice Available Capacity Value Downlink IE and Slice Available Capacity Value Uplink IE, providing the slice capacity with respect to the Cell Capacity Class Value The Number of Active UEs IE, if the fourth bit, "Number of Active UEs" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 ; the RRC Connections IE, if the fifth bit, "RRC Connections" of the Report Characteristics IE included in the RESOURCE STATUS REQUEST message is set to 1 .

[0387] If the Reporting Periodicity IE in the RESOURCE STATUS REQUEST is present, this indicates the periodicity for the reporting of periodic measurements. If the Reporting Periodicity IE is absent, the NG-RAN node2 shall report only once.

[0388] If a NG-RAN CONFIGURATION UPDATE is received by the NG-RAN nodel from NG-RAN node2, the NG-RAN nodel shall discard the current Resource Status Reporting Initiation and may reinitialize a new Resource Status Reporting Initiation based on the new NG-RAN node2 configuration.

[0389] FIG. 8 illustrates an unsuccessful operation of resource status reporting initiation. If any of the requested measurements cannot be initiated, NG-RAN node2 shall send the RESOURCE STATUS FAILURE message. This procedure is initiated by an NG-RAN node to report the result of measurements admitted by the NG-RAN node following a successful Resource Status Reporting Initiation procedure. The procedure uses non UE-associated signaling.

[0390] FIG. 9 illustrates a successful operation of resource status reporting. NG- RAN node2 shall report the results of the admitted measurements in RESOURCE STATUS UPDATE message. The admitted measurements are the measurements that were successfully initiated during the preceding Resource Status Reporting Initiation procedure.

[0391] If a NG-RAN CONFIGURATION UPDATE ACKNOWLEDGE is received by the NG-RAN node2 from NG-RAN nodel , the NG-RAN node2 shall stop the procedure.

[0392] If a NG-RAN CONFIGURATION UPDATE FAILURE is received by the NG-RAN node2 from NG-RAN nodel , the NG-RAN node2 shall stop the procedure. [0393] A RESOURCE STATUS FAILURE message is sent by the NG-RAN node2 to NG-RAN nodel to indicate that for any of the requested measurement objects the measurement cannot be initiated. FIG. 37 is a table illustrating an example of a resource status failure message. [0394] The purpose of the Cause IE is to indicate the reason for a particular event for the XnAP protocol. FIG. 38 illustrates an example of a Cause IE. The meaning of the different cause values is specified in the tables of FIGS. 39-43. In general, “not supported” cause values indicate that the related capability is missing. On the other hand, “not available” cause values indicate that the related capability is present, but insufficient resources were available to perform the requested action. [0395] A RESOURCE STATUS REQUEST message is sent by NG-RAN nodel to NG-RAN node2 to initiate the requested measurement according to the parameters given in the message. FIGS. 44-46 illustrate examples of a resource status request IE and associated information.

[0396] A NG-RAN NODE CONFIGURATION UPDATE message is sent by a NG- RAN node to a neighbouring NG-RAN node to transfer updated information for an Xn-C interface instance. FIGS. 47-48 illustrate examples of a NG-RAN node configuration update message and associated information.

[0397] Example embodiments are discussed below.

[0398] Embodiment 1. A method of operating a first Radio Access Network, RAN, node of a communication network including a second RAN node, the method comprising: transmitting (5701 , 4901) information about a first RAN configuration of the first RAN node to the second RAN node; determining (5705, 4902) a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node, wherein the first and second RAN configurations are different; receiving (5709, 4904) a resource status request message from the second RAN node after determining the second RAN configuration of the first RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node; and transmitting (5711 , 4905) a resource status failure message to the second RAN node responsive to receiving the resource status request message based on the first RAN configuration, wherein the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the RAN configuration update and the first RAN configuration of the resource status request.

[0399] Embodiment 2. The method of Embodiment 1 , wherein the cause value is set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

[0400] Embodiment 3. The method of any of Embodiments 1-2, further comprising: transmitting (5715, 4906) a RAN node configuration update message to the second RAN node after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node.

[0401] Embodiment 4. The method of Embodiment 3, wherein the RAN node configuration update message is transmitted after transmitting the resource status failure message.

[0402] Embodiment 5. The method of any of Embodiments 3-4, further comprising: receiving (5719-1 , 4907) a RAN node configuration update acknowledge message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message.

[0403] Embodiment 6. The method of Embodiment 5, wherein the RAN node configuration update acknowledge message is received after transmitting the resource status failure message.

[0404] Embodiment 7. The method of any of Embodiments 5-6, wherein reception of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node.

[0405] Embodiment 8. The method of any of Embodiments 3-4, further comprising: receiving (5719-2, 4907) a RAN node configuration update failure message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

[0406] Embodiment 9. The method of Embodiment 8, wherein the RAN node configuration update failure message is received after transmitting the resource status failure message.

[0407] Embodiment 10. The method of any of Embodiments 1-9, wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to receiving the resource status request message after determining the second RAN configuration and before completion of the RAN configuration update for the first RAN node.

[0408] Embodiment 11 . The method of any of Embodiments 1-10, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers.

[0409] Embodiment 12. The method of Embodiment 11 , wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to determining that at least one of the subset of the first plurality of identifiers of the resource status request message does not match any of the second plurality of identifiers of the second RAN configuration.

[0410] Embodiment 13. The method of any of Embodiments 1-12, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node, wherein a second configuration identifier is associated with the second RAN configuration of the first RAN node, wherein the first and second configuration identifiers are different, wherein the resource status request message includes the first configuration identifier, and wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to the resource status request message including the first configuration identifier.

[0411] Embodiment 14. A method of operating a first Radio Access Network, RAN, node of a communication network including a second RAN node, the method comprising: transmitting (5901 , 5001) information about a first RAN configuration of the first RAN node to the second RAN node; receiving (5905, 2003) a resource status request message from the second RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node; determining (5909, 5005) a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after receiving the resource status request message from the second RAN node, wherein the first and second RAN configurations are different; transmitting (5911 , 5007) a RAN node configuration update message to the second RAN node for the RAN configuration update after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node; and stopping (5919, 5009) transmission of a scheduled resource status update message corresponding to the resource status request message after transmitting the RAN node configuration update message.

[0412] Embodiment 15. The method of Embodiment 14, wherein transmission of the scheduled resource status update message is stopped responsive to transmitting the RAN node configuration update message.

[0413] Embodiment 16. The method of any of Embodiments 14-15, further comprising: receiving (5915-1 , 5008) a RAN node configuration update acknowledge message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message to indicate completion of the RAN configuration update, and wherein transmission of the scheduled resource status update message is stopped after receiving the RAN node configuration update acknowledge message.

[0414] Embodiment 17. The method of Embodiment 16, wherein transmission of the scheduled resource status update message is stopped responsive to receiving the RAN node configuration update acknowledge message.

[0415] Embodiment 18. The method of any of Embodiments 14-15, further comprising: receiving (5915-2, 5008) a RAN node configuration update failure message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN node configuration update, and wherein transmission of the scheduled resource status update message is stopped after receiving the RAN node configuration update failure message.

[0416] Embodiment 19. The method of Embodiment 18, wherein transmission of the scheduled resource status update message is stopped responsive to receiving the RAN node configuration update failure message.

[0417] Embodiment 20. The method of any of Embodiments 14-19, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers.

[0418] Embodiment 21 . The method of any of Embodiments 14-20, wherein the scheduled resource status update message is a second scheduled resource status update message of a plurality of scheduled resource status update messages based on the resource status request message, the method further comprising: transmitting (5907, 5004) a first scheduled resource status update message of the plurality of scheduled resource status update messages based on the resource status request message before transmitting the RAN node configuration update message.

[0419] Embodiment 22. The method of Embodiment 21 , wherein the first scheduled resource status update message is transmitted before determining the second RAN configuration.

[0420] Embodiment 23. The method of Embodiment 22 further comprising: transmitting (5910, 5006) a third scheduled resource status update message of the plurality of scheduled resource status update messages based on the resource status request message after determining the second RAN configuration and before transmitting the RAN node configuration update message.

[0421] Embodiment 24. The method of Embodiment 21 , wherein the first scheduled resource status update message is transmitted after determining the second RAN configuration.

[0422] Embodiment 25. A method of operating a first Radio Access Network, RAN, node of a communication network including a second RAN node, the method comprising: transmitting (6101 , 5301) information about a first RAN configuration of the first RAN node to the second RAN node, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node; determining (6105, 5302) a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node, wherein the first and second RAN configurations are different, wherein a second configuration identifier is associated with the second RAN configuration of the first RAN node, and wherein the first and second configuration identifiers are different; receiving (6109, 5304) a resource status request message from the second RAN node after determining the second RAN configuration of the first RAN node, wherein the resource status request message includes the first configuration identifier; and transmitting (6111 , 5305) a resource status failure message to the second RAN node responsive to receiving the resource status request message including the first configuration identifier.

[0423] Embodiment 26. The method of Embodiment 25, wherein the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the RAN configuration update and the first RAN configuration of the resource status request message responsive to the resource status request message including the first configuration identifier.

[0424] Embodiment 27. The method of Embodiment 26, wherein the cause value is set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

[0425] Embodiment 28. The method of any of Embodiments 25-27, further comprising: transmitting (6115, 5306) a RAN node configuration update message to the second RAN node after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node including the second configuration identifier.

[0426] Embodiment 29. The method of Embodiment 28, wherein the RAN node configuration update message is transmitted after transmitting the resource status failure message.

[0427] Embodiment 30. The method of any of Embodiments 28-29, further comprising: receiving (6119-1 , 5307) a RAN node configuration update acknowledge message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message.

[0428] Embodiment 31 . The method of Embodiment 30, wherein the RAN node configuration update acknowledge message is received after transmitting the resource status failure message. [0429] Embodiment 32. The method of any of Embodiments 30-31 , wherein reception of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node.

[0430] Embodiment 33. The method of any of Embodiments 28-29 further comprising: receiving (6119-2, 5307) a RAN node configuration update failure message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

[0431] Embodiment 34. The method of Embodiment 33, wherein the RAN node configuration update failure message is received after transmitting the resource status failure message.

[0432] Embodiment 35. The method of any of Embodiments 33-34, wherein reception of the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

[0433] Embodiment 36. The method of any of Embodiments 25-35, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers.

[0434] Embodiment 37. A method of operating a second Radio Access Network, RAN, node of a communication network including a first RAN node, the method comprising: receiving (5801 , 4901) information about a first RAN configuration of the first RAN node from the first RAN node; transmitting (5809, 4904) a resource status request message to the first RAN node after receiving the information about the first RAN configuration, wherein the resource status request message is based on the first RAN configuration of the first RAN node; and receiving (5811 , 4905) a resource status failure message from the first RAN node, wherein the resource status failure message corresponds to the resource status request message, and wherein the resource status failure message includes a cause value to indicate a mismatch between a second RAN configuration of a RAN configuration update for the first RAN node and the first RAN configuration of the resource status request.

[0435] Embodiment 38. The method of Embodiment 37, wherein the cause value is set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

[0436] Embodiment 39. The method of any of Embodiments 37-38, further comprising: receiving (5815, 4906) a RAN node configuration update message from the first RAN node after transmitting the resource status request message, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node.

[0437] Embodiment 40. The method of Embodiment 39, wherein the RAN node configuration update message is received after receiving the resource status failure message.

[0438] Embodiment 41 . The method of any of Embodiments 39-40, further comprising: transmitting (5819-1 , 4907) a RAN node configuration update acknowledge message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message.

[0439] Embodiment 42. The method of Embodiment 41 , wherein the RAN node configuration update acknowledge message is transmitted after receiving the resource status failure message. [0440] Embodiment 43. The method of any of Embodiments 41 -42, wherein transmission of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node. [0441] Embodiment 44. The method of any of Embodiments 39-40, further comprising: transmitting (5819-2, 4907) a RAN node configuration update failure message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

[0442] Embodiment 45. The method of Embodiment 44, wherein the RAN node configuration update failure message is transmitted after receiving the resource status failure message.

[0443] Embodiment 46. The method of any of Embodiments 37-45, wherein the resource status failure message including the cause value to indicate the mismatch is received before completion of the RAN configuration update for the first RAN node. [0444] Embodiment 47. The method of any of Embodiments 37-46, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers.

[0445] Embodiment 48. The method of any of Embodiments 37-47, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node, wherein a second configuration identifier is associated with the second RAN configuration of the first RAN node, wherein the first and second configuration identifiers are different, wherein the resource status request message includes the first configuration identifier, and wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to the resource status request message including the first configuration identifier.

[0446] Embodiment 49. A method of operating a second Radio Access Network, RAN, node of a communication network including a first RAN node, the method comprising: receiving (6001 , 5001) information about a first RAN configuration of the first RAN node from the first RAN node; transmitting (6005, 5003) a resource status request message to the first RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node; receiving (6011 , 5007) a RAN node configuration update message from the first RAN node, wherein the RAN node configuration update message includes information about a second RAN configuration of the first RAN node for a RAN configuration update of the first RAN node.

[0447] Embodiment 50. The method of Embodiment 49, further comprising: transmitting (6015-1 , 5008) a RAN node configuration update acknowledge message to the first RAN node responsive to receiving the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message to indicate completion of the RAN configuration update of the first RAN node.

[0448] Embodiment 51 . The method of Embodiment 49, further comprising: transmitting (6015-2, 5008) a RAN node configuration update failure message to the first RAN node responsive to receiving the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update of the first RAN node.

[0449] Embodiment 52. The method of any of Embodiments 49-51 , wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers.

[0450] Embodiment 53. The method of any of Embodiments 49-52 further comprising: receiving (6007, 5004, 5006) a scheduled resource status update message of a plurality of scheduled resource status update messages based on the resource status request message before receiving the RAN node configuration update message. [0451] Embodiment 54. A method of operating a second Radio Access Network, RAN, node of a communication network including a first RAN node, the method comprising: receiving (6201 , 5301) information about a first RAN configuration of the first RAN node from the first RAN node, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node; transmitting (6209, 5304) a resource status request message to the first RAN node after receiving the information about the first RAN configuration of the first RAN node, wherein the resource status request message includes the first configuration identifier; and receiving (6211 , 5305) a resource status failure message from the first RAN node based on the resource status request message including the first configuration identifier. [0452] Embodiment 55. The method of Embodiment 54, further comprising: receiving (6215, 5306) a RAN node configuration update message from the first RAN node after transmitting the resource status request message, wherein the RAN node configuration update message includes information about a RAN configuration update for a second RAN configuration for the first RAN node including the second configuration identifier.

[0453] Embodiment 56. The method of Embodiment 55, wherein the RAN node configuration update message is received after receiving the resource status failure message.

[0454] Embodiment 57. The method of any of Embodiments 55-56, further comprising: transmitting (6219-1 , 5307) a RAN node configuration update acknowledge message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message.

[0455] Embodiment 58. The method of Embodiment 57, wherein the RAN node configuration update acknowledge message is transmitted after receiving the resource status failure message.

[0456] Embodiment 59. The method of any of Embodiments 57-58, wherein transmission of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node. [0457] Embodiment 60. The method of any of Embodiments 55-56 further comprising: transmitting (6219-2, 5307) a RAN node configuration update failure message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

[0458] Embodiment 61 . The method of Embodiment 60, wherein the RAN node configuration update failure message is transmitted after receiving the resource status failure message.

[0459] Embodiment 62. The method of any of Embodiments 60-61 , wherein transmission of the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

[0460] Embodiment 63. The method of any of Embodiments 54-62, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers. [0461] Embodiment 64. The method of any of Embodiments 55-63, wherein the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the first RAN node and the first RAN configuration of the resource status request message.

[0462] Embodiment 65. The method of Embodiment 64, wherein the cause value is set to indicate that the mismatch is due to a RAN configuration update (e.g., the cause value is set to configuration update).

[0463] Embodiment 66. A first radio access network, RAN, node (5500) comprising: processing circuitry (5503); and memory (5505) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first RAN node to perform operations according to any of Embodiments 1 -36.

[0464] Embodiment 67. A first radio access network, RAN, node (5500) adapted to perform according to any of Embodiments 1-36.

[0465] Embodiment 68. A computer program comprising program code to be executed by processing circuitry (5503) of a first radio access network, RAN, node (5500), whereby execution of the program code causes the first RAN node (5500) to perform operations according to any of embodiments 1 -36.

[0466] Embodiment 69. A computer program product comprising a non- transitory storage medium including program code to be executed by processing circuitry (5503) of a first radio access network, RAN, node (5500), whereby execution of the program code causes the first RAN node (5500) to perform operations according to any of embodiments 1-36.

[0467] Embodiment 70. A second radio access network, RAN, node (5500) comprising: processing circuitry (5503); and memory (5505) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the second RAN node to perform operations according to any of Embodiments 37-65. [0468] Embodiment 71 . A second radio access network, RAN, node (5500) adapted to perform according to any of Embodiments 37-65.

[0469] Embodiment 72. A computer program comprising program code to be executed by processing circuitry (5503) of a second radio access network, RAN, node (5500), whereby execution of the program code causes the second RAN node (5500) to perform operations according to any of embodiments 37-65.

[0470] Embodiment 73. A computer program product comprising a non- transitory storage medium including program code to be executed by processing circuitry (5503) of a second radio access network, RAN, node (5500), whereby execution of the program code causes the second RAN node (5500) to perform operations according to any of embodiments 37-65.

[0471] Additional explanation is provided below.

[0472] 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 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 may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

[0473] 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 by way of example to convey the scope of the subject matter to those skilled in the art.

[0474] FIG. 63 illustrates a wireless network in accordance with some embodiments.

[0475] Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIG. 63. For simplicity, the wireless network of FIG. 63 only depicts network 4106, network nodes 4160 and 4160b, and WDs 4110, 4110b, and 4110c (also referred to as mobile terminals). In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 4160 and wireless device (WD) 4110 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

[0476] The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[0477] Network 4106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0478] Network node 4160 and WD 4110 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.

[0479] As used herein, network node refers to 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 wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless 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 NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also 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). Yet further examples of network nodes include 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), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E- SMLCs), and/or minimization of drive tests (MDTs). As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

[0480] In FIG. 63, network node 4160 includes processing circuitry 4170, device readable medium 4180, interface 4190, auxiliary equipment 4184, power source 4186, power circuitry 4187, and antenna 4162. Although network node 4160 illustrated in the example wireless network of FIG. 63 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 4160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 4180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0481] Similarly, network node 4160 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 4160 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 NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 4160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 4180 for the different RATs) and some components may be reused (e.g., the same antenna 4162 may be shared by the RATs). Network node 4160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 4160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 4160.

[0482] Processing circuitry 4170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 4170 may include processing information obtained by processing circuitry 4170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

[0483] Processing circuitry 4170 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 4160 components, such as device readable medium 4180, network node 4160 functionality. For example, processing circuitry 4170 may execute instructions stored in device readable medium 4180 or in memory within processing circuitry 4170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 4170 may include a system on a chip (SOC).

[0484] In some embodiments, processing circuitry 4170 may include one or more of radio frequency (RF) transceiver circuitry 4172 and baseband processing circuitry 4174. In some embodiments, radio frequency (RF) transceiver circuitry 4172 and baseband processing circuitry 4174 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 4172 and baseband processing circuitry 4174 may be on the same chip or set of chips, boards, or units [0485] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 4170 executing instructions stored on device readable medium 4180 or memory within processing circuitry 4170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 4170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 4170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 4170 alone or to other components of network node 4160, but are enjoyed by network node 4160 as a whole, and/or by end users and the wireless network generally.

[0486] Device readable medium 4180 may comprise any form of volatile or nonvolatile 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 4170. Device readable medium 4180 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 4170 and, utilized by network node 4160. Device readable medium 4180 may be used to store any calculations made by processing circuitry 4170 and/or any data received via interface 4190. In some embodiments, processing circuitry 4170 and device readable medium 4180 may be considered to be integrated.

[0487] Interface 4190 is used in the wired or wireless communication of signalling and/or data between network node 4160, network 4106, and/or WDs 4110. As illustrated, interface 4190 comprises port(s)/terminal(s) 4194 to send and receive data, for example to and from network 4106 over a wired connection. Interface 4190 also includes radio front end circuitry 4192 that may be coupled to, or in certain embodiments a part of, antenna 4162. Radio front end circuitry 4192 comprises filters 4198 and amplifiers 4196. Radio front end circuitry 4192 may be connected to antenna 4162 and processing circuitry 4170. Radio front end circuitry may be configured to condition signals communicated between antenna 4162 and processing circuitry 4170. Radio front end circuitry 4192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 4192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 4198 and/or amplifiers 4196. The radio signal may then be transmitted via antenna 4162. Similarly, when receiving data, antenna 4162 may collect radio signals which are then converted into digital data by radio front end circuitry 4192. The digital data may be passed to processing circuitry 4170. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0488] In certain alternative embodiments, network node 4160 may not include separate radio front end circuitry 4192, instead, processing circuitry 4170 may comprise radio front end circuitry and may be connected to antenna 4162 without separate radio front end circuitry 4192. Similarly, in some embodiments, all or some of RF transceiver circuitry 4172 may be considered a part of interface 4190. In still other embodiments, interface 4190 may include one or more ports or terminals 4194, radio front end circuitry 4192, and RF transceiver circuitry 4172, as part of a radio unit (not shown), and interface 4190 may communicate with baseband processing circuitry 4174, which is part of a digital unit (not shown).

[0489] Antenna 4162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 4162 may be coupled to radio front end circuitry 4192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 4162 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 4162 may be separate from network node 4160 and may be connectable to network node 4160 through an interface or port.

[0490] Antenna 4162, interface 4190, and/or processing circuitry 4170 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 4162, interface 4190, and/or processing circuitry 4170 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[0491] Power circuitry 4187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 4160 with power for performing the functionality described herein. Power circuitry 4187 may receive power from power source 4186. Power source 4186 and/or power circuitry 4187 may be configured to provide power to the various components of network node 4160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 4186 may either be included in, or external to, power circuitry 4187 and/or network node 4160. For example, network node 4160 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 4187. As a further example, power source 4186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 4187. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

[0492] Alternative embodiments of network node 4160 may include additional components beyond those shown in FIG. 63 that may be responsible 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 4160 may include user interface equipment to allow input of information into network node 4160 and to allow output of information from network node 4160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 4160.

[0493] As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may 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. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD 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 WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal. [0494] As illustrated, wireless device 4110 includes antenna 4111 , interface 4114, processing circuitry 4120, device readable medium 4130, user interface equipment 4132, auxiliary equipment 4134, power source 4136 and power circuitry 4137. WD 4110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 4110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 4110.

[0495] Antenna 4111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 4114. In certain alternative embodiments, antenna 4111 may be separate from WD 4110 and be connectable to WD 4110 through an interface or port. Antenna 4111 , interface 4114, and/or processing circuitry 4120 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 4111 may be considered an interface.

[0496] As illustrated, interface 4114 comprises radio front end circuitry 4112 and antenna 4111. Radio front end circuitry 4112 comprise one or more filters 4118 and amplifiers 4116. Radio front end circuitry 4112 is connected to antenna 4111 and processing circuitry 4120, and is configured to condition signals communicated between antenna 4111 and processing circuitry 4120. Radio front end circuitry 4112 may be coupled to or a part of antenna 4111. In some embodiments, WD 4110 may not include separate radio front end circuitry 4112; rather, processing circuitry 4120 may comprise radio front end circuitry and may be connected to antenna 4111. Similarly, in some embodiments, some or all of RF transceiver circuitry 4122 may be considered a part of interface 4114. Radio front end circuitry 4112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 4112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 4118 and/or amplifiers 4116. The radio signal may then be transmitted via antenna 4111. Similarly, when receiving data, antenna 4111 may collect radio signals which are then converted into digital data by radio front end circuitry 4112. The digital data may be passed to processing circuitry 4120. In other embodiments, the interface may comprise different components and/or different combinations of components.

[0497] Processing circuitry 4120 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 WD 4110 components, such as device readable medium 4130, WD 4110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 4120 may execute instructions stored in device readable medium 4130 or in memory within processing circuitry 4120 to provide the functionality disclosed herein.

[0498] As illustrated, processing circuitry 4120 includes one or more of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 4120 of WD 4110 may comprise a SOC. In some embodiments, RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 4124 and application processing circuitry 4126 may be combined into one chip or set of chips, and RF transceiver circuitry 4122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 4122 and baseband processing circuitry 4124 may be on the same chip or set of chips, and application processing circuitry 4126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 4122, baseband processing circuitry 4124, and application processing circuitry 4126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 4122 may be a part of interface 4114. RF transceiver circuitry 4122 may condition RF signals for processing circuitry 4120.

[0499] In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 4120 executing instructions stored on device readable medium 4130, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 4120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 4120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 4120 alone or to other components of WD 4110, but are enjoyed by WD 4110 as a whole, and/or by end users and the wireless network generally.

[0500] Processing circuitry 4120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 4120, may include processing information obtained by processing circuitry 4120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 4110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. [0501] Device readable medium 4130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 4120. Device readable medium 4130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., 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 4120. In some embodiments, processing circuitry 4120 and device readable medium 4130 may be considered to be integrated.

[0502] User interface equipment 4132 may provide components that allow for a human user to interact with WD 4110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 4132 may be operable to produce output to the user and to allow the user to provide input to WD 4110. The type of interaction may vary depending on the type of user interface equipment 4132 installed in WD 4110. For example, if WD 4110 is a smart phone, the interaction may be via a touch screen; if WD 4110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 4132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 4132 is configured to allow input of information into WD 4110, and is connected to processing circuitry 4120 to allow processing circuitry 4120 to process the input information. User interface equipment 4132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 4132 is also configured to allow output of information from WD 4110, and to allow processing circuitry 4120 to output information from WD 4110. User interface equipment 4132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 4132, WD 4110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[0503] Auxiliary equipment 4134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 4134 may vary depending on the embodiment and/or scenario.

[0504] Power source 4136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 4110 may further comprise power circuitry 4137 for delivering power from power source 4136 to the various parts of WD 4110 which need power from power source 4136 to carry out any functionality described or indicated herein. Power circuitry 4137 may in certain embodiments comprise power management circuitry. Power circuitry 4137 may additionally or alternatively be operable to receive power from an external power source; in which case WD 4110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 4137 may also in certain embodiments be operable to deliver power from an external power source to power source 4136. This may be, for example, for the charging of power source 4136. Power circuitry 4137 may perform any formatting, converting, or other modification to the power from power source 4136 to make the power suitable for the respective components of WD 4110 to which power is supplied.

[0505] FIG. 64 illustrates a user Equipment in accordance with some embodiments.

[0506] FIG. 64 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or 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 42200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 4200, as illustrated in FIG. 64, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIG. 64 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0507] In FIG. 64, UE 4200 includes processing circuitry 4201 that is operatively coupled to input/output interface 4205, radio frequency (RF) interface 4209, network connection interface 4211 , memory 4215 including random access memory (RAM) 4217, read-only memory (ROM) 4219, and storage medium 4221 or the like, communication subsystem 4231 , power source 4213, and/or any other component, or any combination thereof. Storage medium 4221 includes operating system 4223, application program 4225, and data 4227. In other embodiments, storage medium 4221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIG. 64, or only a subset of the components. 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.

[0508] In FIG. 64, processing circuitry 4201 may be configured to process computer instructions and data. Processing circuitry 4201 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 4201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0509] In the depicted embodiment, input/output interface 4205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 4200 may be configured to use an output device via input/output interface 4205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 4200. The output device may be 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. UE 4200 may be configured to use an input device via input/output interface 4205 to allow a user to capture information into UE 4200. The input device may 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, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[0510] In FIG. 64, RF interface 4209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 4211 may be configured to provide a communication interface to network 4243a. Network 4243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 4243a may comprise a Wi-Fi network. Network connection interface 4211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 4211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

[0511] RAM 4217 may be configured to interface via bus 4202 to processing circuitry 4201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 4219 may be configured to provide computer instructions or data to processing circuitry 4201 . For example, ROM 4219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 4221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 4221 may be configured to include operating system 4223, application program 4225 such as a web browser application, a widget or gadget engine or another application, and data file 4227. Storage medium 4221 may store, for use by UE 4200, any of a variety of various operating systems or combinations of operating systems.

[0512] Storage medium 4221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 4221 may allow UE 4200 to access computer-executable instructions, application programs or 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 in storage medium 4221 , which may comprise a device readable medium. [0513] In FIG. 64, processing circuitry 4201 may be configured to communicate with network 4243b using communication subsystem 4231 . Network 4243a and network 4243b may be the same network or networks or different network or networks. Communication subsystem 4231 may be configured to include one or more transceivers used to communicate with network 4243b. For example, communication subsystem 4231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11 , CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 4233 and/or receiver 4235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 4233 and receiver 4235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0514] In the illustrated embodiment, the communication functions of communication subsystem 4231 may include 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. For example, communication subsystem 4231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 4243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 4243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 4213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 4200. [0515] The features, benefits and/or functions described herein may be implemented in one of the components of UE 4200 or partitioned across multiple components of UE 4200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 4231 may be configured to include any of the components described herein. Further, processing circuitry 4201 may be configured to communicate with any of such components over bus 4202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 4201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 4201 and communication subsystem 4231 . In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[0516] FIG. 65 illustrates a virtualization environment in accordance with some embodiments.

[0517] FIG. 65 is a schematic block diagram illustrating a virtualization environment 4300 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 a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

[0518] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 4300 hosted by one or more of hardware nodes 4330. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

[0519] The functions may be implemented by one or more applications 4320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 4320 are run in virtualization environment 4300 which provides hardware 4330 comprising processing circuitry 4360 and memory 4390. Memory 4390 contains instructions 4395 executable by processing circuitry 4360 whereby application 4320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

[0520] Virtualization environment 4300, comprises general-purpose or specialpurpose network hardware devices 4330 comprising a set of one or more processors or processing circuitry 4360, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 4390-1 which may be non- persistent memory for temporarily storing instructions 4395 or software executed by processing circuitry 4360. Each hardware device may comprise one or more network interface controllers (NICs) 4370, also known as network interface cards, which include physical network interface 4380. Each hardware device may also include non- transitory, persistent, machine-readable storage media 4390-2 having stored therein software 4395 and/or instructions executable by processing circuitry 4360. Software 4395 may include any type of software including software for instantiating one or more virtualization layers 4350 (also referred to as hypervisors), software to execute virtual machines 4340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

[0521] Virtual machines 4340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 4350 or hypervisor. Different embodiments of the instance of virtual appliance 4320 may be implemented on one or more of virtual machines 4340, and the implementations may be made in different ways.

[0522] During operation, processing circuitry 4360 executes software 4395 to instantiate the hypervisor or virtualization layer 4350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 4350 may present a virtual operating platform that appears like networking hardware to virtual machine 4340.

[0523] As shown in FIG. 65, hardware 4330 may be a standalone network node with generic or specific components. Hardware 4330 may comprise antenna 43225 and may implement some functions via virtualization. Alternatively, hardware 4330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 43100, which, among others, oversees lifecycle management of applications 4320.

[0524] 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.

[0525] In the context of NFV, virtual machine 4340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 4340, and that part of hardware 4330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 4340, forms a separate virtual network elements (VNE).

[0526] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 4340 on top of hardware networking infrastructure 4330 and corresponds to application 4320 in FIG. 65.

[0527] In some embodiments, one or more radio units 43200 that each include one or more transmitters 43220 and one or more receivers 43210 may be coupled to one or more antennas 43225. Radio units 43200 may communicate directly with hardware nodes 4330 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.

[0528] In some embodiments, some signalling can be effected with the use of control system 43230 which may alternatively be used for communication between the hardware nodes 4330 and radio units 43200.

[0529] FIG. 66 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. [0530] With reference to FIG. 66, in accordance with an embodiment, a communication system includes telecommunication network 4410, such as a 3GPP- type cellular network, which comprises access network 4411 , such as a radio access network, and core network 4414. Access network 4411 comprises a plurality of base stations 4412a, 4412b, 4412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 4413a, 4413b, 4413c. Each base station 4412a, 4412b, 4412c is connectable to core network 4414 over a wired or wireless connection 4415. A first UE 4491 located in coverage area 4413c is configured to wirelessly connect to, or be paged by, the corresponding base station 4412c. A second UE 4492 in coverage area 4413a is wirelessly connectable to the corresponding base station 4412a. While a plurality of UEs 4491 , 4492 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 4412.

[0531] Telecommunication network 4410 is itself connected to host computer 4430, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 4430 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 4421 and 4422 between telecommunication network 4410 and host computer 4430 may extend directly from core network 4414 to host computer 4430 or may go via an optional intermediate network 4420. Intermediate network 4420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 4420, if any, may be a backbone network or the Internet; in particular, intermediate network 4420 may comprise two or more sub-networks (not shown).

[0532] The communication system of FIG. 66 as a whole enables connectivity between the connected UEs 4491 , 4492 and host computer 4430. The connectivity may be described as an over-the-top (OTT) connection 4450. Host computer 4430 and the connected UEs 4491 , 4492 are configured to communicate data and/or signaling via OTT connection 4450, using access network 4411 , core network 4414, any intermediate network 4420 and possible further infrastructure (not shown) as intermediaries. OTT connection 4450 may be transparent in the sense that the participating communication devices through which OTT connection 4450 passes are unaware of routing of uplink and downlink communications. For example, base station 4412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer 4430 to be forwarded (e.g., handed over) to a connected UE 4491 . Similarly, base station 4412 need not be aware of the future routing of an outgoing uplink communication originating from the UE 4491 towards the host computer 4430.

[0533] FIG. 67 illustrates a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments.

[0534] Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to FIG. 67. In communication system 4500, host computer 4510 comprises hardware 4515 including communication interface 4516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system 4500. Host computer 4510 further comprises processing circuitry 4518, which may have storage and/or processing capabilities. In particular, processing circuitry 4518 may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 4510 further comprises software 4511 , which is stored in or accessible by host computer 4510 and executable by processing circuitry 4518. Software 4511 includes host application 4512. Host application 4512 may be operable to provide a service to a remote user, such as UE 4530 connecting via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the remote user, host application 4512 may provide user data which is transmitted using OTT connection 4550.

[0535] Communication system 4500 further includes base station 4520 provided in a telecommunication system and comprising hardware 4525 enabling it to communicate with host computer 4510 and with UE 4530. Hardware 4525 may include communication interface 4526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 4500, as well as radio interface 4527 for setting up and maintaining at least wireless connection 4570 with UE 4530 located in a coverage area (not shown in FIG. 67) served by base station 4520. Communication interface 4526 may be configured to facilitate connection 4560 to host computer 4510. Connection 4560 may be direct or it may pass through a core network (not shown in FIG. 67) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware 4525 of base station 4520 further includes processing circuitry 4528, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station 4520 further has software 4521 stored internally or accessible via an external connection.

[0536] Communication system 4500 further includes UE 4530 already referred to. Its hardware 4535 may include radio interface 4537 configured to set up and maintain wireless connection 4570 with a base station serving a coverage area in which UE 4530 is currently located. Hardware 4535 of UE 4530 further includes processing circuitry 4538, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 4530 further comprises software 4531 , which is stored in or accessible by UE 4530 and executable by processing circuitry 4538. Software 4531 includes client application 4532. Client application 4532 may be operable to provide a service to a human or non-human user via UE 4530, with the support of host computer 4510. In host computer 4510, an executing host application 4512 may communicate with the executing client application 4532 via OTT connection 4550 terminating at UE 4530 and host computer 4510. In providing the service to the user, client application 4532 may receive request data from host application 4512 and provide user data in response to the request data. OTT connection 4550 may transfer both the request data and the user data. Client application 4532 may interact with the user to generate the user data that it provides.

[0537] It is noted that host computer 4510, base station 4520 and UE 4530 illustrated in FIG. 67 may be similar or identical to host computer 4430, one of base stations 4412a, 4412b, 4412c and one of UEs 4491 , 4492 of FIG. 66, respectively. This is to say, the inner workings of these entities may be as shown in FIG. 67 and independently, the surrounding network topology may be that of FIG. 66.

[0538] In FIG. 67, OTT connection 4550 has been drawn abstractly to illustrate the communication between host computer 4510 and UE 4530 via base station 4520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE 4530 or from the service provider operating host computer 4510, or both. While OTT connection 4550 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network). [0539] Wireless connection 4570 between UE 4530 and base station 4520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments may improve the performance of OTT services provided to UE 4530 using OTT connection 4550, in which wireless connection 4570 forms the last segment. More precisely, the teachings of these embodiments may improve the random access speed and/or reduce random access failure rates and thereby provide benefits such as faster and/or more reliable random access. [0540] 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 4550 between host computer 4510 and UE 4530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 4550 may be implemented in software 4511 and hardware 4515 of host computer 4510 or in software 4531 and hardware 4535 of UE 4530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 4550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 4511 , 4531 may compute or estimate the monitored quantities.

The reconfiguring of OTT connection 4550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 4520, and it may be unknown or imperceptible to base station 4520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 4510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 4511 and 4531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 4550 while it monitors propagation times, errors etc.

[0541] FIG. 68 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

[0542] FIG. 68 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 66-67. For simplicity of the present disclosure, only drawing references to FIG. 68 will be included in this section. In step 4610, the host computer provides user data. In substep 4611 (which may be optional) of step 4610, the host computer provides the user data by executing a host application. In step 4620, the host computer initiates a transmission carrying the user data to the UE. In step 4630 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 4640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0543] FIG. 69 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments.

[0544] FIG. 69 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 66-67. For simplicity of the present disclosure, only drawing references to FIG. 69 will be included in this section. In step 4710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 4720, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 4730 (which may be optional), the UE receives the user data carried in the transmission.

[0545] FIG. 70 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0546] FIG. 70 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 66-67. For simplicity of the present disclosure, only drawing references to FIG. 70 will be included in this section. In step 4810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 4820, the UE provides user data. In substep 4821 (which may be optional) of step 4820, the UE provides the user data by executing a client application. In substep 4811 (which may be optional) of step 4810, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 4830 (which may be optional), transmission of the user data to the host computer. In step 4840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0547] FIG. 71 illustrates methods implemented in a communication system including a host computer, a base station and a user equipment in accordance with some embodiments

[0548] FIG. 71 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference to FIGS. 66-67. For simplicity of the present disclosure, only drawing references to FIG. 71 will be included in this section. In step 4910 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 4920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 4930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station. [0549] 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 processors (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.

[0550] The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may 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.

[0551] ABBREVIATIONS

[0552] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

1x RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMACode Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response CP Cyclic Prefix

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-1 D (positioning method)

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel

E-SMLC evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

FFS For Further Study

GERAN GSM EDGE Radio Access Network gNB Base station in NR

GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover HSPA High Speed Packet Access

HRPD High Rate Packet Data

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MBMS Multimedia Broadcast Multicast Services

MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network PM I Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio SON Self Optimized Network

SS Synchronization Signal

SSS Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal TTI Transmission Time Interval

UE User Equipment

UL Uplink

UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival

UTRA Universal Terrestrial Radio Access

UTRAN Universal Terrestrial Radio Access Network

WCDMA Wide CDMA

WLAN Wide Local Area Network

[0553] Further definitions and embodiments are discussed below.

[0554] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. 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 present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, 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.

[0555] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" (abbreviated “/”) includes any and all combinations of one or more of the associated listed items.

[0556] It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.

[0557] As used herein, the terms "comprise", "comprising", "comprises", "include", "including", "includes", "have", "has", "having", or variants thereof are open- ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation "e.g.", which derives from the Latin phrase "exempli gratia," may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation "i.e.", which derives from the Latin phrase "id est," may be used to specify a particular item from a more general recitation.

[0558] Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).

[0559] These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as "circuitry," "a module" or variants thereof.

[0560] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0561] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

Claims

1 . A method of operating a first Radio Access Network, RAN, node of a communication network including a second RAN node, the method comprising: transmitting (5701 , 4901) information about a first RAN configuration of the first RAN node to the second RAN node; determining (5705, 4902) a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node, wherein the first and second RAN configurations are different; receiving (5709, 4904) a resource status request message from the second RAN node after determining the second RAN configuration of the first RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node; and transmitting (5711 , 4905) a resource status failure message to the second RAN node responsive to receiving the resource status request message based on the first RAN configuration, wherein the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the RAN configuration update and the first RAN configuration of the resource status request.

2. The method of Claim 1 , wherein the cause value is set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

3. The method of any of Claims 1-2, further comprising: transmitting (5715, 4906) a RAN node configuration update message to the second RAN node after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node, wherein the RAN node configuration update message is transmitted after transmitting the resource status failure message.

4. The method of Claim 3, further comprising: receiving (5719-1 , 4907) a RAN node configuration update acknowledge message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is received after transmitting the resource status failure message, and wherein reception of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node.

5. The method of Claim 3, further comprising: receiving (5719-2, 4907) a RAN node configuration update failure message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node, and wherein the RAN node configuration update failure message is received after transmitting the resource status failure message.

6. The method of any of Claims 1-5, wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to receiving the resource status request message after determining the second RAN configuration and before completion of the RAN configuration update for the first RAN node, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, wherein the resource status request message includes a subset of the first plurality of identifiers, wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to determining that at least one of the subset of the first plurality of identifiers of the resource status request message does not match any of the second plurality of identifiers of the second RAN configuration, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node, wherein a second configuration identifier is associated with the second RAN configuration of the first RAN node, wherein the first and second configuration identifiers are different, wherein the resource status request message includes the first configuration identifier, and wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to the resource status request message including the first configuration identifier.

7. A method of operating a first Radio Access Network, RAN, node of a communication network including a second RAN node, the method comprising: transmitting (5901 , 5001) information about a first RAN configuration of the first RAN node to the second RAN node; receiving (5905, 2003) a resource status request message from the second RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node; determining (5909, 5005) a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after receiving the resource status request message from the second RAN node, wherein the first and second RAN configurations are different; transmitting (5911 , 5007) a RAN node configuration update message to the second RAN node for the RAN configuration update after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node; and stopping (5919, 5009) transmission of a scheduled resource status update message corresponding to the resource status request message after transmitting the RAN node configuration update message.

8. The method of Claim 7, wherein transmission of the scheduled resource status update message is stopped responsive to transmitting the RAN node configuration update message.

9. The method of any of Claims 7-8, further comprising: receiving (5915-1 , 5008) a RAN node configuration update acknowledge message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message to indicate completion of the RAN configuration update, wherein transmission of the scheduled resource status update message is stopped after receiving the RAN node configuration update acknowledge message, and wherein transmission of the scheduled resource status update message is stopped responsive to receiving the RAN node configuration update acknowledge message.

10. The method of Claim 9, further comprising: receiving (5915-2, 5008) a RAN node configuration update failure message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN node configuration update,

121 wherein transmission of the scheduled resource status update message is stopped after receiving the RAN node configuration update failure message, and wherein transmission of the scheduled resource status update message is stopped responsive to receiving the RAN node configuration update failure message.

11 . The method of any of Claims 9-10, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, wherein the resource status request message includes a subset of the first plurality of identifiers, and wherein the scheduled resource status update message is a second scheduled resource status update message of a plurality of scheduled resource status update messages based on the resource status request message, the method further comprising: transmitting (5907, 5004) a first scheduled resource status update message of the plurality of scheduled resource status update messages based on the resource status request message before transmitting the RAN node configuration update message.

12. The method of Claim 11 , wherein the first scheduled resource status update message is transmitted before determining the second RAN configuration, the method further comprising: transmitting (5910, 5006) a third scheduled resource status update message of the plurality of scheduled resource status update messages based on the

122 resource status request message after determining the second RAN configuration and before transmitting the RAN node configuration update message.

13. The method of Claim 11 , wherein the first scheduled resource status update message is transmitted after determining the second RAN configuration.

14. A method of operating a first Radio Access Network, RAN, node of a communication network including a second RAN node, the method comprising: transmitting (6101 , 5301) information about a first RAN configuration of the first RAN node to the second RAN node, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node; determining (6105, 5302) a second RAN configuration of the first RAN node to provide a RAN configuration update for the first RAN node after transmitting the information about the first RAN configuration to the second RAN node, wherein the first and second RAN configurations are different, wherein a second configuration identifier is associated with the second RAN configuration of the first RAN node, and wherein the first and second configuration identifiers are different; receiving (6109, 5304) a resource status request message from the second RAN node after determining the second RAN configuration of the first RAN node, wherein the resource status request message includes the first configuration identifier; and transmitting (6111 , 5305) a resource status failure message to the second RAN node responsive to receiving the resource status request message including the first configuration identifier.

15. The method of Claim 14, wherein the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the RAN configuration update and the first RAN configuration of the resource status request message responsive to the resource status request message including the first configuration identifier, wherein the cause value is set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

123

16. The method of any of Claims 14-15, further comprising: transmitting (6115, 5306) a RAN node configuration update message to the second RAN node after determining the second RAN configuration of the first RAN node, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node including the second configuration identifier.

17. The method of Claim 16, wherein the RAN node configuration update message is transmitted after transmitting the resource status failure message, the method further comprising: receiving (6119-1 , 5307) a RAN node configuration update acknowledge message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is received after transmitting the resource status failure message, and wherein reception of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node.

18. The method of Claim 17 further comprising: receiving (6119-2, 5307) a RAN node configuration update failure message from the second RAN node after transmitting the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node, wherein the RAN node configuration update failure message is received after transmitting the resource status failure message, and wherein reception of the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

124

19. The method of any of Claims 14-18, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers.

20. A method of operating a second Radio Access Network, RAN, node of a communication network including a first RAN node, the method comprising: receiving (5801 , 4901) information about a first RAN configuration of the first RAN node from the first RAN node; transmitting (5809, 4904) a resource status request message to the first RAN node after receiving the information about the first RAN configuration, the resource status request message being based on the first RAN configuration of the first RAN node; and receiving (5811 , 4905) a resource status failure message from the first RAN node, wherein the resource status failure message corresponds to the resource status request message, wherein the resource status failure message includes a cause value to indicate a mismatch between a second RAN configuration of a RAN configuration update for the first RAN node and the first RAN configuration of the resource status request, and wherein the cause value is set to indicate that the mismatch is due to the RAN configuration update (e.g., the cause value is set to configuration update).

21 . The method of Claim 20, further comprising:

125 receiving (5815, 4906) a RAN node configuration update message from the first RAN node after transmitting the resource status request message, wherein the RAN node configuration update message includes information about the second RAN configuration of the first RAN node, wherein the RAN node configuration update message is received after receiving the resource status failure message.

22. The method of any of Claims 20-21 , further comprising: transmitting (5819-1 , 4907) a RAN node configuration update acknowledge message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is transmitted after receiving the resource status failure message, and wherein transmission of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node.

23. The method of any of Claims 20-21 , further comprising: transmitting (5819-2, 4907) a RAN node configuration update failure message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node, wherein the RAN node configuration update failure message is transmitted after receiving the resource status failure message.

24. The method of any of Claims 18-23, wherein the resource status failure message including the cause value to indicate the mismatch is received before completion of the RAN configuration update for the first RAN node, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node,

126 wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, wherein the resource status request message includes a subset of the first plurality of identifiers, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node, wherein a second configuration identifier is associated with the second RAN configuration of the first RAN node, wherein the first and second configuration identifiers are different, wherein the resource status request message includes the first configuration identifier, and wherein the resource status failure message including the cause value to indicate the mismatch is transmitted responsive to the resource status request message including the first configuration identifier.

25. A method of operating a second Radio Access Network, RAN, node of a communication network including a first RAN node, the method comprising: receiving (6001 , 5001) information about a first RAN configuration of the first RAN node from the first RAN node; transmitting (6005, 5003) a resource status request message to the first RAN node, wherein the resource status request message is based on the first RAN configuration of the first RAN node; receiving (6011 , 5007) a RAN node configuration update message from the first RAN node, wherein the RAN node configuration update message includes information about a second RAN configuration of the first RAN node for a RAN configuration update of the first RAN node.

127

26. The method of Claim 25, further comprising: transmitting (6015-1 , 5008) a RAN node configuration update acknowledge message to the first RAN node responsive to receiving the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message to indicate completion of the RAN configuration update of the first RAN node; and transmitting (6015-2, 5008) a RAN node configuration update failure message to the first RAN node responsive to receiving the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update of the first RAN node.

27. The method of any of Claims 25-26, wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, and wherein the resource status request message includes a subset of the first plurality of identifiers, the method further comprising: receiving (6007, 5004, 5006) a scheduled resource status update message of a plurality of scheduled resource status update messages based on the resource status request message before receiving the RAN node configuration update message.

28. A method of operating a second Radio Access Network, RAN, node of a communication network including a first RAN node, the method comprising:

128 receiving (6201 , 5301) information about a first RAN configuration of the first RAN node from the first RAN node, wherein a first configuration identifier is associated with the first RAN configuration of the first RAN node; transmitting (6209, 5304) a resource status request message to the first RAN node after receiving the information about the first RAN configuration of the first RAN node, wherein the resource status request message includes the first configuration identifier; and receiving (6211 , 5305) a resource status failure message from the first RAN node based on the resource status request message including the first configuration identifier.

29. The method of Claim 28, further comprising: receiving (6215, 5306) a RAN node configuration update message from the first RAN node after transmitting the resource status request message, wherein the RAN node configuration update message includes information about a RAN configuration update for a second RAN configuration for the first RAN node including the second configuration identifier, wherein the RAN node configuration update message is received after receiving the resource status failure message.

30. The method of any of Claims 28-29, further comprising: transmitting (6219-1 , 5307) a RAN node configuration update acknowledge message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is an acknowledgement of the RAN node configuration update message, wherein the RAN node configuration update acknowledge message is transmitted after receiving the resource status failure message, and wherein transmission of the RAN node configuration update acknowledge message completes the RAN configuration update for the second RAN configuration of the first RAN node.

31 . The method of any of Claims 28-30 further comprising: transmitting (6219-2, 5307) a RAN node configuration update failure message to the first RAN node after receiving the RAN node configuration update message, wherein the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node, wherein the RAN node configuration update failure message is transmitted after receiving the resource status failure message, and wherein transmission of the RAN node configuration update failure message indicates failure of the RAN configuration update for the first RAN node.

32. The method of any of Claims 28-31 , wherein the first RAN configuration defines a first plurality of cells and/or beams configured for the first RAN node, wherein a first plurality of identifiers are associated with respective ones of the first plurality of cells and/or beams, wherein the second RAN configuration defines a second plurality of cells and/or beams configured for the first RAN node, wherein a second plurality of identifiers are associated with respective ones of the second plurality of cells and/or beams, wherein the first and second pluralities of cells and/or beams are different, wherein the resource status request message includes a subset of the first plurality of identifiers, wherein the resource status failure message includes a cause value to indicate a mismatch between the second RAN configuration of the first RAN node and the first RAN configuration of the resource status request message, and wherein the cause value is set to indicate that the mismatch is due to a RAN configuration update (e.g., the cause value is set to configuration update).

33. A first radio access network, RAN, node (5500) comprising: processing circuitry (5503); and memory (5505) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first RAN node to perform operations according to any of Claims 1-19.

34. A first radio access network, RAN, node (5500) adapted to perform according to any of Claims 1-19.

35. A computer program comprising program code to be executed by processing circuitry (5503) of a first radio access network, RAN, node (5500), whereby execution of the program code causes the first RAN node (5500) to perform operations according to any of Claims 1-19.

36. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (5503) of a first radio access network, RAN, node (5500), whereby execution of the program code causes the first RAN node (5500) to perform operations according to any of Claims 1-19.

37. A second radio access network, RAN, node (5500) comprising: processing circuitry (5503); and memory (5505) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the second RAN node to perform operations according to any of Claims 20-32.

38. A second radio access network, RAN, node (5500) adapted to perform according to any of Claims 20-32.

39. A computer program comprising program code to be executed by processing circuitry (5503) of a second radio access network, RAN, node (5500), whereby execution of the program code causes the second RAN node (5500) to perform operations according to any of Claims 20-32.

40. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (5503) of a second radio access network, RAN, node (5500), whereby execution of the program code causes the second RAN node (5500) to perform operations according to any of Claims 20-32.

132