Self-organizing network reporting handling in mobile integrated access and backhaul scenarios

Abstract

A method performed by a first network node includes obtaining information associated with a self-organizing network (SON) report associated with a wireless device. The first network node determines that the information associated with the SON report is associated with a cell not served by the first network node. In response to determining that the information associated with the SON report is associated with the cell not served by the first network node, the first network node takes at least one action including deleting the information and / or transmitting the information to a second network node.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, and more particularly to systems and methods for handling self-organizing network (SON) reports in integrated access and backhaul (IAB) scenarios. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) is currently standardizing Integrated Access and Radio Access Backhaul (IAB) in New Radio (NR) in Release 16 (Rel-16).

[0003] The use of short-range millimeter-wave spectrum in NR has created a need for dense deployments utilizing multi-hop backhaul. However, fiber to every base station would be too costly and sometimes even impossible (e.g., legacy systems). The main principle of IAB (Independent Radio Access) is to use radio links for backhaul (instead of fiber) to enable flexible and very dense cell deployments without the need for densifying the transport network. Use case scenarios for IAB can include coverage extension, deployment of large numbers of small cells, and fixed radio access (FWA) (e.g., to residential / office buildings). The greater bandwidth available in NR in the millimeter-wave spectrum provides opportunities for self-backhaul without limiting the spectrum that can be used for access links. In addition, the inherent multi-beam and multiple-input multiple-output (MIMO) support in NR reduces cross-link interference between backhaul and access links, thus allowing for higher density.

[0004] During the research project phase of the IAB work discussed in 3GPP TR 38.874, a solution utilizing a Central Unit (CU) / Distributed Unit (DU) split architecture based on NR was agreed upon, in which IAB nodes would host the DU portion controlled by the CU. IAB nodes also have a Mobile Terminal (MT) portion that they use to communicate with their parent nodes.

[0005] The IAB specification strives to reuse existing functions and interfaces defined in NR. Specifically, the MT, gNodeB Distributed Unit (gNB-DU), gNodeB Central Unit (gNB-CU), User Plane Function (UPF), Access and Mobility Management Function (AMF), and Session Management Function (SMF), along with their corresponding interfaces NRUu (between MT and gNB), F1, NG, X2, and N4, are used as the baseline for the IAB architecture. Modifications or enhancements to these functions and interfaces to support IAB will be interpreted within the context of the architecture discussion. Additional functionalities such as multi-hop forwarding are included in the architecture discussion because they are necessary for understanding IAB operation and because standardization is required in certain aspects.

[0006] MT functionality has been defined as a component of the IAB node. As used herein, MT refers to a function residing on the IAB-node that terminates the radio interface layer toward the backhaul Uu interface of the IAB-donor or other IAB-nodes.

[0007] Figure 1 The diagram illustrates a high-level architecture view of the IAB network. Specifically, Figure 1 The diagram illustrates an IAB in standalone mode, comprising one IAB donor and multiple IAB nodes. The IAB donor is considered a single logical node, encompassing a set of functions such as gNB-DU, gNodeB-Central Unit-Control Plane (gNB-CU-CP), gNodeB-Central Unit-User Plane (gNB-CU-UP), and potentially other functions. In deployment, the IAB donor can be split based on these functions, which can be either co-located or non-co-located, as permitted by the 3GPP Next Generation Radio Access Network (NG-RAN) architecture. When such splitting is implemented, IAB-related aspects may arise. Furthermore, if it becomes apparent that some functions currently associated with the IAB donor do not perform IAB-specific tasks, they may eventually be removed from the donor.

[0008] Figure 2 The diagram illustrates the baseline user plane protocol stack of the IAB. Figure 3 The diagram illustrates the control plane protocol stack of the IAB.

[0009] like Figure 2 and Figure 3 As shown, the selected protocol stack reuses the current CU-DU split specification in Rel-15, where the complete User Plane F1-U (General Packet Radio Service Tunneling Protocol-User Plane (GTP-U) / User Datagram Protocol (UDP) / Internet Protocol (IP)) is terminated at the IAB node (like a regular DU), and the complete Control Plane F1-C (F1 Application Protocol (F1-AP) / Flow Control Transport Protocol (SCTP) / IP) is also terminated at the IAB node (like a regular DU). In this scenario, Network Domain Security (NDS) is employed to protect both User Plane (UP) and Control Plane (CP) traffic (IP security (IPsec) in the UP case and Datagram Transport Layer Security (DTLS) in the CP case). IPsec can also be used for CP protection instead of DTLS (in which case the DTLS layer will not be used).

[0010] A new protocol layer called Backhaul Adaptation Protocol (BAP) has been introduced in IAB nodes and IAB donors. This protocol layer is used to route packets to the appropriate downstream / upstream nodes and also to map UE bearer data to the appropriate backhaul radio link control (RLC) channels (and between the ingress and egress backhaul RLC channels in intermediate IAB nodes) to meet the end-to-end quality of service (QoS) requirements of the bearers.

[0011] At an IAB-node, the BAP sublayer contains one BAP entity at the MT function and separate, co-located BAP entities at the DU function. At an IAB-donor-DU, the BAP sublayer contains only one BAP entity. Each BAP entity has a transmit portion and a receive portion. The transmit portion of the BAP entity has a corresponding receive portion at the IAB-node or IAB-donor-DU across the backhaul link.

[0012] Figure 4 This diagram illustrates an example of a functional view of the BAP sublayer. This functional view should not limit the implementation and is based on the radio interface protocol architecture defined in 3GPP TS 38.300. Figure 4 In the example, the receiving part on the BAP entity delivers a BAP Protocol Data Unit (PDU) to the transmitting part on the co-located BAP entity. Alternatively, the receiving part may deliver a BAP Service Data Unit (SDU) to the co-located transmitting part. When transmitting a BAP SDU, the receiving part removes the BAP header, and the transmitting part adds a BAP header with the same BAP routing identifier (ID) as that carried in the original BAP PDU header. Therefore, in the implementation, transmitting a BAP SDU in this manner is functionally equivalent to transmitting a BAP PDU.

[0013] The BAP sublayer provides the following services to the upper layers: data transmission.

[0014] The BAP sublayer expects the following services from the lower layer of each RLC entity (see 3GPP TS38.322 for a detailed description): acknowledged data transmission service and unacknowledged data transmission service.

[0015] The BAP sublayer supports the following functions: data transmission; determining the BAP destination and path of packets from the upper layer; determining the egress BHRLC channel for packets routed to the next hop; routing packets to the next hop; distinguishing between traffic to be delivered to the upper layer and traffic to be delivered to the egress link; and flow control feedback and polling signaling.

[0016] The terms IAB topology adaptation, IAB migration, IAB relocation, and IAB handover are used interchangeably to refer to the process in which an IAB node changes its parent node. IAB topology adaptation can be triggered by several reasons, such as load or radio conditions at the source (overload at the parent or intermediate node between the donor CU and the IAB node, any intermediate hops towards the donor DU, and / or poor radio conditions on the backhaul link to the parent node, etc.). Topology adaptation can also be due to the mobility of IAB nodes (which may indirectly be considered / treated in the same way as topology adaptation due to radio conditions). It should be noted that currently mobile IAB nodes are not supported in 3GPP, but may be considered in future versions.

[0017] Figure 5 The illustration shows examples of some possible IAB-node migration scenarios listed in order of complexity.

[0018] In the CU-internal scenario (A), the IAB-node (e), along with the UEs it serves, is moved to a new parent node (IAB-node (b)) under the same donor-DU (1). A successful donor-internal DU migration requires establishing UE context settings for the IAB-node (e) MT in the DU of the new parent node (IAB-node (b)), updating the routing tables of the IAB nodes along the path to the IAB-node (e), and allocating resources on the new path. The IP address of the IAB-node (e) will not change, while the F1-U tunnel / connection between the donor-CU (1) and the IAB-node (e) DU will be redirected through the IAB-node (b).

[0019] The process requirements / complexity of case (B) within the CU are the same as those of case (A) within the CU. Furthermore, since the new IAB-donor DU (i.e., DU2) is connected to the same L2 network, the IAB-node (e) can use the same IP address under the new donor DU. However, the new donor DU (i.e., DU2) will need to use the IAB-node (e)'s L2 address to notify the network in order to obtain / maintain the same IP address of the IAB-node (e) through some mechanism such as Address Resolution Protocol (ARP).

[0020] The situation within the CU (C) is more complex than that within the CU (A) because it also requires the allocation of a new IP address for the IAB-node (e). If IPsec is used to secure the F1-U tunnel / connection between the donor-CU (1) and the IAB-node (e) DU, it may be possible to use the existing IP address along the path segment between the donor-CU (1) and the security gateway (SeGW), as well as the new IP address for the IPsec tunnel between the SeGW and the IAB-node (e) DU.

[0021] In terms of process requirements, the CU case (D) is the most complex and may require a new specification process that goes beyond the scope of 3GPPRel-16.

[0022] 3GPPRel-16 has standardized the process for migrations within the CU only.

[0023] During topology adaptation within a CU, both the source and target parent nodes are served by the same IAB-donor-CU. The target parent node may use a different IAB-donor-DU than the source parent node. The source path may further share common nodes with the target path. Figure 6 The illustration shows an example of a topology adaptation process where the target parent node uses a different IAB-donor-DU than the source parent node.

[0024] like Figure 6 As shown, the CU topology adaptation process within the IAB includes:

[0025] 1. Migrate IAB-MT and send a measurement report message to the source parent node gNB-DU. This report is based on the measurement configuration received from the IAB-donor-CU before migrating IAB-MT.

[0026] 2. The source parent node gNB-DU sends an "Uplink (UL) Radio Resource Control (RRC) Message Transmission" message to the IAB-donor-CU to convey the received measurement report.

[0027] 3. The IAB-donor-CU sends a "UE Context Setup Request" message to the target parent node gNB-DU to create a UE context and set up one or more bearers for the migrated IAB-MT. These bearers are then used by the migrated IAB-MT for its own data and signaling services.

[0028] 4. The target parent node gNB-DU responds to the IAB-donor-CU with a "UE context setting response" message.

[0029] 5. The IAB-donor-CU sends a "UE Context Modification Request" message to the source parent node gNB-DU. This message includes a generated RRCReconfiguration message. The transport action indicator in the "UE Context Modification Request" message indicates that data transmission to the migrating IAB-node must be stopped.

[0030] 6. The source parent node gNB-DU forwards the received RRCReconfiguration message to the migration IAB-MT.

[0031] 7. The source parent node gNB-DU responds to the IAB-donor-CU with a "UE context modification response" message.

[0032] 8. Perform the random access (RA) procedure at the target parent node gNB-DU.

[0033] 9. Migrate IAB-MT and respond to the target parent node gNB-DU with the RRCReconfigurationComplete message.

[0034] 10. The target parent node gNB-DU sends a "ULRRC Message Transmission" message to the IAB-donor-CU to convey the received RRCReconfigurationComplete message. Furthermore, uplink packets can be sent from the migrating IAB-MT, and these uplink packets are forwarded to the IAB-donor-CU via the target parent node gNB-DU. These downlink (DL) and uplink (UL) packets belong to the MT's own signaling and data services.

[0035] 11. The IAB-donor-CU configures the backhaul (BH) radio link control (RLC) channel and BAP layer routing entries on the target path between the migrating IAB-node and the target IAB-donor-DU. This step also includes assigning one or more Transport Network Layer (TNL) addresses routable via the target IAB-donor-DU. These configurations can be performed at an earlier stage, such as immediately after step 3. The one or more new TNL addresses are included in the RRCReconfiguration message in step 5.

[0036] 12. All F1-U tunnels and F1-C are switched to use one or more new TNL addresses of the migrated IAB-node.

[0037] 13. The IAB-donor-CU sends a "User Equipment (UE) Context Release Command" message to the source parent node gNB-DU.

[0038] 14. The source parent node gNB-DU releases the context of the migration IAB-MT and responds to the IAB-donor-CU with a "UE context release complete" message.

[0039] 15. The IAB-donor-CU releases BHRLC channels and BAP routing entries on the source path. Migrating an IAB-node can further release one or more TNL addresses it uses on the source path.

[0040] It can be noted that if the source and destination routes share a common node, it may not be necessary to release the BHRLC channels and BAP route entries of those nodes in step 15. For descendant nodes of the migrated IAB-node, steps 11, 12, and 15 must also be performed as follows:

[0041] Descendant nodes must also transition to the new TNL address anchored in the target IAB-donor-DU. The IAB-donor-CU can then send these addresses to the descendant nodes and release the old addresses via the corresponding RRC signaling.

[0042] - If necessary, the IAB-donor-CU configures the BHRLC channel on the target path, the BAP layer routing entries, and the BHRLC channel mapping on the descendant node in the same manner as described in step 11 for migrating the IAB-node.

[0043] Descendant nodes transform their F1-U and F1-C tunnels to the new TNL address anchored to the new IAB-donor-DU in the same manner as described in step 12 for migrating IAB-nodes.

[0044] - Depending on the implementation, these steps can be performed after or in parallel with the handover of the migrated IAB-node. In Rel-16, in-flight packets dropped during the migration process in the UL direction may not be recoverable.

[0045] Upstream, even after the target path is established, in-flight packets between the source parent node and the IAB-donor-CU can be delivered. Depending on the implementation, ongoing downlink data in the source path may be discarded. The IAB-donor-CU can determine downlink data that was not successfully delivered on the return link through its implementation.

[0046] Figure 7 The illustration depicts a radio link failure (RLF) caused by a physical layer problem. A user equipment (UE) may lose coverage of the cell to which the UE is currently connected. This can occur when the UE enters a fading dip or, as described above, when a handover was required but failed for one or more reasons. This is especially true if the "handover area" is very short, as will be further described below.

[0047] The quality of the radio link is typically monitored in the UE, for example, at the physical layer, as described in 3GPP TS 38.300, 3GPP TS 38.331 and 3GPP TS 38.133, and is summarized here in a very brief description.

[0048] When a problem is detected at the physical layer according to the criteria defined in 3GPP TS 38.133, the physical layer sends an indication of the detected problem (asynchrony indication) to the Radio Resource Control (RRC) protocol. After a configurable number (N310) of such consecutive indications, a timer (T310) is started. If the link quality does not improve (recover) while T310 is running (i.e., there are no N311 consecutive "synchronization" indications from the physical layer), a radio link failure is declared in the UE, as... Figure 7 As depicted in the text.

[0049] Table 1 lists the relevant timers and counters mentioned above for reference. The UE reads the timer values ​​from the system information broadcast in the cell. Alternatively, it is possible to use dedicated signaling to configure UE-specific values ​​for constants and timers to the UE, i.e., to give a specific value to a specific UE using a message that is only directed to each specific UE.

[0050] Table 1

[0051]

[0052]

[0053]

[0054] In NR, T310 is used for both the primary cell group (MCG) and the secondary cell group (SCG) (i.e., for NR-DC and (NG)EN-DC). However, for cases where the secondary node (SN) is running LTE (i.e., LTE-DC and NE-DC), the timer associated with the primary and secondary cells (PSCell) is T312.

[0055] Now, if T310 expires for the primary cell group (MCG), and as seen above, the UE initiates a connection re-establishment to resume the ongoing RRC connection. This process now includes cell selection performed by the UE. For example, the RRC_CONNECTED UE should now attempt to autonomously find a better cell to connect to, since, according to the described measurements, the connection to the previous cell failed (it's possible the UE returns to the first cell anyway, but then performs the same procedure again). Once a suitable cell is selected (as further described in 3GPP TS 38.304), the UE requests to re-establish the connection in the selected cell. It is important to note the difference in mobility behavior, as radio link failure (RLF) leads to UE-based cell selection, which contrasts with the network-controlled mobility of normal applications.

[0056] If the reconstruction is successful (which depends in particular on whether the selected cell and the gNB controlling that cell are ready to maintain the connection with the UE), the connection between the UE and the gNB can be restarted.

[0057] A failed reconstruction means the UE enters RRC_IDLE mode and the connection is released. To continue communication, a completely new RRC connection must then be requested and established.

[0058] The reason for introducing the aforementioned timer T31x and counter N31x is to add some flexibility and hysteresis to the configuration of the criteria for when a radio link should be considered a failure (and recovery). This is desirable because if the loss of link quality proves to be temporary and the UE successfully recovers the connection without any further action or process (e.g., before T310 expires, or before the count reaches value N310), prematurely abandoning the connection would harm end-user performance.

[0059] The procedures for NR radio link failure detection are disclosed in 3GPP TS 38.331.

[0060] However, some problems exist. For example, consider... Figure 8 The scenario depicted in the example scenario is shown, illustrating the network topology at two different time instances, T and T+1.

[0061] At time T, there are two donors, IAB donor 1 and IAB donor 2, each with a corresponding CU and DU. There are two IAB nodes connected to donor 1, IAB-A and IAB-B, with IAB-B being a mobile IAB node. There is a UE connected to IAB-B.

[0062] At time = T+1, IAB-A is still connected to donor 1, but IAB-B has been switched from donor 1 to donor 2.

[0063] Several RLF report-related issues led to Figure 8 The scenario described herein. For example, the first problem is that the handover might be too late. Specifically, between time = T and time = T+1, that is, when IAB-B is being served by donor 1, the UE being served by IAB-B can declare an RLF. The UE then stores the contents of the RLF report, where it stores the failedPCellId as the cell associated with the DU of IAB-B.

[0064] Then, the UE performs a rebuild or enters idle mode and re-establishes connection in the cell. This cell is associated with DU-3, which is connected to CU-3, and it is different from... Figure 8The diagram shows the DU and IAB donor. DU-3 can be a normal DU, a donor DU, or even a DU from another IAB node.

[0065] CU-3 retrieves the RLF report from the UE later than time = T+1, and based on the failedPCellId stored in the RLF report, CU-3 sends this RLF report to donor 1 (because it can identify from its neighbor relationship table that the failedPCellID belongs to donor 1).

[0066] Based on the contents of the RLF report, donor 1 realized this was a "too late switch" and wanted to forward the RLF report to the associated DU (in Figure 8 In the case of IAB-B's DU, this DU can tune associated parameters (RLM resource configuration and / or BFR configuration and / or beamforming configuration, etc.). However, donor 1 cannot send this RLF report to IAB-B's DU because IAB-B is no longer connected to it. Figure 9 The illustration shows the first problem when donor 1 cannot send an RLF report.

[0067] As another example, the second issue might relate to Random Access (RA) report forwarding. Specifically, before time = T and at time = T, the UE is connected to donor 1 via IAB-B, and the UE performs multiple (e.g., two) RA procedures toward IAB-B (e.g., for beam failure recovery purposes). Associated with these RA procedures, the UE will have already stored the RA report in the UE variable varRAReport.

[0068] However, the UE can be released into idle mode / inactive state. Then, at a later time (time > T+1), the UE returns to connection in the cell associated with DU-3, and DU-3 is then connected to CU-3. DU-3 can be a normal DU, a donor DU, or even a DU of another IAB node.

[0069] CU-3 extracts the contents of varRAReport from the UE. This varRAReport now includes information related to three RA procedures (two random access procedures to IAB-B and one access procedure to DU-3). CU-3 forwards the IAB-B-related portion of the RAReport (identified by the cell information in the report) to Donor 1. Donor 1 wants to forward the RAReport to IAB-B, but IAB-B is no longer connected to Donor 1. Figure 10 The diagram illustrates the second issue related to RA report forwarding. Summary of the Invention

[0070] Certain aspects of this disclosure and embodiments thereof may provide solutions to these or other challenges. For example, according to certain embodiments, one or more methods may be performed by a first network node acting as an IAB node in an IAB network to handle a scenario in which a report is received containing information relating to a previous failure or recovery of a UE associated with an IAB node previously served by the first network node but no longer served by it.

[0071] According to some embodiments, the method performed by a first network node includes obtaining information associated with a SON report associated with a wireless device. The first network node determines that the information associated with the SON report is associated with a cell not served by the first network node. In response to determining that the information associated with the SON report is associated with a cell not served by the first network node, the first network node takes at least one action, including deleting the information and / or transmitting the information to a second network node.

[0072] According to some embodiments, a first network node includes processing circuitry configured to obtain information associated with a SON report associated with a wireless device. The processing circuitry is configured to determine that the information associated with the SON report is associated with a cell not served by the first network node. In response to determining that the information associated with the SON report is associated with a cell not served by the first network node, the processing circuitry is configured to take at least one action, including deleting the information and / or transmitting the information to a second network node.

[0073] According to some embodiments, another method performed by the first network node includes receiving information associated with a SON report related to a wireless device. This information is received from a donor CU currently serving the wireless device, and is associated with a cell that previously served the wireless device but is not currently served by the donor CU. The first network node then transmits the information to a second network node.

[0074] According to some embodiments, a first network node includes processing circuitry configured to receive information associated with a SON report related to a wireless device. This information is received from a donor CU currently serving the wireless device, and is associated with a cell that previously served the wireless device but is not currently served by the donor CU. The processing circuitry is configured to transmit the information to a second network node.

[0075] Some embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that some embodiments make it possible to send reports to the correct IAB node, even if the IAB node is being relocated from one CU to another.

[0076] Other advantages will likely be apparent to those skilled in the art. Some embodiments may lack the advantages described or may have some or all of the advantages described. Attached Figure Description

[0077] To gain a more thorough understanding of the disclosed embodiments and their features and advantages, the following description is now taken in conjunction with the accompanying drawings, in which:

[0078] Figure 1 The diagram illustrates a high-level architecture view of the IAB network;

[0079] Figure 2 The diagram illustrates the baseline user plane protocol stack of the IAB.

[0080] Figure 3 The diagram illustrates the control plane protocol stack of the IAB.

[0081] Figure 4 This diagram illustrates an example of a functional view of the BAP sublayer;

[0082] Figure 5 The illustration shows examples of some possible IAB-node migration scenarios listed in order of complexity.

[0083] Figure 6 An example of the topology adaptation process is illustrated.

[0084] Figure 7 The diagram illustrates an RLF caused by a physical layer issue.

[0085] Figure 8 The illustration shows an example scenario of network topology in two different time instances;

[0086] Figure 9 The diagram illustrates the problem when donor 1 is unable to send an RLF report;

[0087] Figure 10 The diagram illustrates issues related to RA report forwarding;

[0088] Figure 11 The illustration depicts an example scenario in which the IAB donor CU discards the RLF report according to certain embodiments;

[0089] Figure 12 The illustration depicts an example scenario, according to certain embodiments, in which the IAB donor CU forwards an RLF report to a past handover target;

[0090] Figure 13 The illustration shows an example scenario where the IAB donor CU stores a report and sends the report to the IAB node when the IAB node returns to the same CU.

[0091] Figure 14The diagram illustrates a scenario where the source donor CU can use OAM to forward RLF reports;

[0092] Figure 15 The illustration shows an example scenario where the source donor CU can use the core network to forward RLF reports;

[0093] Figure 16 The illustration shows an example scenario for duocasting RLF reports from the CU that collects RLF reports to the old CU and DU;

[0094] Figure 17 An example wireless network according to some embodiments is illustrated;

[0095] Figure 18 The illustration shows an example network node according to some embodiments;

[0096] Figure 19 An example wireless device according to certain embodiments is illustrated;

[0097] Figure 20 An example user equipment according to certain embodiments is illustrated;

[0098] Figure 21 The illustration depicts a virtualized environment, according to certain embodiments, in which functionality implemented by some embodiments can be virtualized;

[0099] Figure 22 The illustration depicts a telecommunications network connected to a host computer via an intermediate network, according to certain embodiments;

[0100] Figure 23 The illustration shows a generalized block diagram of a host computer communicating with a user equipment via a base station through a partial wireless connection according to certain embodiments.

[0101] Figure 24 The illustration shows a method implemented in a communication system according to one embodiment;

[0102] Figure 25 The illustration shows another method implemented in a communication system according to one embodiment;

[0103] Figure 26 The illustration shows another method implemented in a communication system according to one embodiment;

[0104] Figure 27 The illustration shows another method implemented in a communication system according to one embodiment;

[0105] Figure 28 The illustration shows an example method performed by a first network node according to certain embodiments;

[0106] Figure 29The illustration shows an example virtual device according to certain embodiments;

[0107] Figure 30 The illustration shows another example method performed by a first network node according to certain embodiments;

[0108] Figure 31 The illustration shows an example virtual device according to certain embodiments;

[0109] Figure 32 The illustration shows another example method performed by a first network node according to certain embodiments;

[0110] Figure 33 The illustration shows another example virtual device according to certain embodiments;

[0111] Figure 34 The example method is illustrated;

[0112] Figure 35 Another example virtual device according to certain embodiments is illustrated. Detailed Implementation

[0113] Some embodiments of the ideas contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are contained within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as limited to 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.

[0114] Generally, all terms used herein are to be interpreted according to their common meaning in the relevant art, unless a different meaning is explicitly given and / or implied from the context of their use. Unless otherwise expressly stated, all references to an element, device, component, part, step, etc., are to be interpreted openly as referring to at least one instance of that element, device, component, part, step, etc. Unless a step is explicitly described as following or preceding another step and / or implied that a step must follow or precede another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment of the embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will be apparent from the following description.

[0115] In some embodiments, the more general term "network node" may be used, and it may correspond to any type of radio network node or any network node that communicates with the UE (directly or via another node) and / or with another network node. Examples of network nodes include NodeBs, primary eNodeBs (MeNBs), network nodes belonging to primary cell groups (MCGs) or secondary cell groups (SCGs), base stations (BSs), multi-standard radio (MSR) radio nodes (such as MSR BSs), eNodeBs (eNBs), gNodeBs (gNBs), network controllers, radio network controllers (RNCs), base station controllers (BSCs), relays, donor nodes of control relays, base transceiver stations (BTSs), access points (APs), transmission points, transmission nodes, remote radio units (RRUs), remote radio heads (RRHs), nodes in distributed antenna systems (DASs), core network nodes (such as mobile switching centers (MSCs), mobility management entities (MMEs), etc.), operations and maintenance (O&M), operations support systems (OSSs), ad hoc networks (SONs), location nodes (such as evolved Serving Mobile Location Centers (E-SMLCs)), minimized drive tests (MDTs), test equipment (physical nodes or software), etc.

[0116] In some embodiments, the non-limiting term User Equipment (UE) or Wireless Device may be used, and it may refer to any type of wireless device that communicates with a network node and / or with another UE in a cellular or mobile communication system. Examples of UEs are target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, personal digital assistants (PDAs), tablet computers, mobile terminals, smartphones, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), unified serial bus (USB) dongles, UE class M1, UE class M2, proximity service (ProSe) UEs, vehicle-to-vehicle (V2V) UEs, vehicle-to-everything (V2X) UEs, etc.

[0117] Furthermore, terms such as base station / gNodeB and UE should be considered non-restrictive and, in particular, do not imply any hierarchical relationship between the two; generally, "gNodeB" can be considered device 1, and "UE" can be considered device 2, and the two devices communicate with each other via a radio channel. And in the following text, the transmitter or receiver may be either a gNB or a UE.

[0118] This section provides an explanation of aspects related to Radio Link Failure (RLF) reporting, but similar embodiments are also applicable to Random Access (RA) reporting. The embodiments are practically applicable to any scenario / process in which reports (e.g., SON / MDT) need to be sent to the network.

[0119] In this section, explanations are provided for 5G core (5GC) related terminology in some places, but similar implementations also apply to EPC.

[0120] The terms "mobile DU" and "IAB node" can be used interchangeably.

[0121] The UE defined in any of the following solutions can be a normal UE or another MT of the IAB node.

[0122] Although the methods, techniques and solutions described in this paper are in the context of mobile IAB nodes being relocated from one donor CU to another due to mobility, the mechanisms are applicable to other scenarios, such as static IAB nodes that can be relocated from one donor CU to another due to other reasons such as load balancing, and even in non-IAB scenarios where DUs can be relocated from one CU to another.

[0123] This document discloses various methods and techniques that can be performed by a first network node acting as an IAB node in an IAB network (donor CU), for example, to handle scenarios of receiving reports containing information related to a previous failure or recovery of a UE associated with an IAB node previously served by the first network node but no longer served by it.

[0124] For example, according to some embodiments, where a first network node receives a report related to a previous failure or recovery of a UE and determines that the report is associated with a cell of an IAB node no longer served by the first node, the method may include the network node performing one or more of the following:

[0125] • Delete the received report (Example A);

[0126] • Forward the received report to the CU to which it has previously switched the relevant IAB node DU (Example B);

[0127] • Store the received report and forward it to the IAB node if / when the relevant IAB node is switched back to the first network at a later time (Example C);

[0128] • Forward the RLF / RA report associated with the IAB donor DU to the OAM, which simply stores or helps locate the current location of the IAB donor DU and forwards the RA / RLF report to it (Example D);

[0129] • The RLF / RA report associated with the IAB donor DU is sent to the core network node (e.g., AMF / MME), and the core network helps to find the current location of the IAB donor DU and forwards the RA / RLF report to it (Example E);

[0130] • Determine whether the cell information is related to a previous cell identifier used by an IAB node currently being served by a second node, which was under a first network node before being switched to the second network node, and if so, forward the report to that IAB node (Example F).

[0131] • The second network node (which includes the CU that extracts the RLF / RA report from the UE, i.e., CU-3) determines whether the cell involved in the RLF / RA report is associated with the DU corresponding to the mobile IAB node (based on the identifier stored in the RLF / RA report or the RLF / RA report itself having an indication that the corresponding report is associated with the IAB node), and then determines whether to discard the RA / RLF report or forward the RA / RLF report to other CUs / DUs (Example G, which is similar to Example A, but compared to Example A, the node that extracts the RLF / RA report from the UE itself discards the report, whereas in Example A, the RLF / RA report is forwarded to the source CU, and then the source CU discards it).

[0132] Although the embodiments are discussed individually, it should be understood that any two or more of the methods described above can be combined. Further details regarding different specific embodiments are provided below.

[0133] Completely discard RLF reports (Example A)

[0134] According to some embodiments, an IAB donor CU that receives an RLF report associated with a cell belonging to a mobile IAB node that is no longer connected to it can simply discard the RLF report. Figure 11 The illustration shows an example scenario 10 in which the IAB donor CU discards the RLF report.

[0135] Forwarded to past HO targets (Example B)

[0136] According to some embodiments, a source IAB donor CU that receives an RLF report from another CU via an RLF indication message forwards it to the CU to which the source IAB donor CU has switched the mobile IAB node. For example... Figure 12The illustration shows an example scenario 20 in which the IAB donor CU forwards the RLF report to the past HO target.

[0137] For Embodiment B to function, the first network node must store the outgoing handover history of its IAB nodes (e.g., the cell identifier of the IAB node being handed over, the identifier of the CU to which the IAB is handing over, etc.). Therefore, Figure 12 The scenario depicted may require each IAB donor node to remember the target CU to which a given mobile IAB node is switched. This method of remembering target CU information may be based on a timer duration, wherein when the timer expires, the source IAB donor discards any additional RLF / RA reports received in connection with the mobile IAB node (e.g., as in Example A above).

[0138] In a particular embodiment, if the IAB node has been relocated to yet another node, the RLF report can be propagated from one CU to another CU until the CU where the IAB node is currently located.

[0139] The report is stored and sent to the IAB node when the IAB node returns to the same CU (Example C).

[0140] According to some embodiments, the source IAB donor CU that receives an RLF report from another CU via an RLF indication message stores it in its internal memory, and when the mobile IAB node returns to the same IAB donor CU, the RLF report is forwarded to that IAB node. For example, Figure 13 The illustration shows an example scenario 30 in which the IAB donor CU stores a report and sends the report to the IAB node when the IAB node returns to the same CU.

[0141] In a particular embodiment, this may be based on a timer, wherein the source donor CU starts a timer when it receives the RLF report from another CU via an RLF indication message, and when it recognizes that the IAB node to which the RLF report should be forwarded is no longer connected to it. When this timer expires, the source donor CU may take one of the actions specified in the embodiments related to Embodiment A.

[0142] There are several ways in which an IAB donor CU can identify an IAB node. In one particular embodiment, for example, each IAB donor CU has a unique identifier (e.g., an identifier assigned by OAM), which can be passed to the donor CU (e.g., in an F1 setup request message when an IAB node establishes an F1 connection). Based on this, the IAB donor CU can identify whether the same IAB node is now connected to it compared to past connections. In another particular embodiment, each IAB donor CU has a unique identifier (e.g., an identifier assigned by OAM), which can be passed to the IAB donor CU (e.g., in an F1 setup response message when an IAB node establishes an F1 connection). Based on this, the IAB donor CU can identify whether it is connected to the same IAB donor CU compared to past connections, and if so, it can initiate an RA report / RLF report retrieval request from such an IAB donor CU.

[0143] According to various specific embodiments, the identifier associated with the IAB donor DU may include:

[0144] -gNB-DUID or gNB-DU name, which are typically configured by OAM and passed to the CU in a traditional F1 setup request message;

[0145] - Transport layer (IP address) of the IAB node (the CU can identify the transport layer from the source IP address of the IP packet carrying the F1 setup request message);

[0146] - The BAP address of the IAB node; and / or

[0147] - A new identifier introduced for this purpose.

[0148] According to various embodiments, the identifier associated with the IAB donor CU may include:

[0149] -gNB-CU name, which is typically configured by OAM and passed to the IAB node in a traditional F1 setup response message;

[0150] - The transport layer (IP address) of the IAB donor CU (the IAB node must know the transport layer in order to send an F1 setup request message, for example, passed to the IAB node in a handover command);

[0151] - The BAP address of the IAB donor DU that is connected to the IAB donor CU; and / or

[0152] - A new identifier introduced for this purpose.

[0153] Using OAM to forward RLF reports (Example D)

[0154] Figure 14 The illustration depicts scenario 40 where a source donor CU can use OAM to forward RLF reports. According to some embodiments, for example, the source donor CU can send an RLF report to OAM, and then delete the RLF report from its internal memory if it is associated with a mobile IAB node not connected to the CU. Furthermore, in a particular embodiment, in the message to OAM, the CU can indicate that the mobile IAB node to which the RLF report is addressed is no longer connected to the CU.

[0155] In a particular embodiment, the OAM may then store the RLF report or forward it to the “correct” IAB donor to which the mobile IAB node is currently connected (in a manner similar to sending a signaling-based MDT configuration). This requires updating the OAM when the IAB node is relocated. Thus, the OAM must keep track of the current donor CU to which the IAB node is connected. In another particular embodiment, the CU receiving the RLF report may be a donor CU other than the source CU, or even a CU that is not a donor CU (i.e., it does not support IAB nodes). Based on the cell identifier indicated in the failure report, the CU may identify that the cell belongs to the mobile IAB node (e.g., the network may reserve a certain number of cell identifiers for IAB node cells) and forward the RLF report directly to the OAM or any other intermediary network node or network function with the ability to communicate with the CU.

[0156] Using the core network to forward RLF reports (Example E)

[0157] According to some embodiments, the source donor CU can send an RLF report to the AMF, and then delete the RLF report from its internal memory if it is associated with a mobile IAB node not connected to the CU. For example, Figure 15 The illustration shows an example scenario 50 in which the source donor CU can use the core network to forward RLF reports.

[0158] In a particular embodiment, in a message to the AMF, the CU may indicate that the mobile IAB node to which the RLF report is addressed is no longer connected to this CU. The AMF may then store this RLF report or forward it to the “correct” IAB donor to which the mobile IAB node is currently connected (in a manner similar to sending a signaling-based MDT configuration). This particular embodiment may require updating (tracking) the AMF when the IAB node is relocated (i.e., to the current donor CU to which the IAB node is connected).

[0159] In another specific embodiment, the CU receiving the report may be a donor CU other than the source CU, or even a CU that is not a donor CU (i.e., it does not support IAB nodes). Based on the cell identifier indicated in the failure report, the CU may identify that the cell belongs to a mobile IAB node (e.g., the network may reserve a certain number of cell identifiers for IAB node cells) and forward the RLF report directly to the AMF.

[0160] In another specific embodiment, another way the AMF identifies the current location of a mobile IAB node is based on the identifier of the mobile IAB node's MT, namely the IMSI. Therefore, the AMF or another function / entity in the core network maintains a table relating the unique identifier (IMSI) of the SIM card assigned to the mobile IAB node's MT to a list of cell identifiers (such as, for example, cell group identifiers (CGI)) previously used by the mobile IAB node.

[0161] RLF reports are bicast from the CU to the old CU and DU, where RLF reports are collected from the UE (Example F).

[0162] Figure 16 The illustration depicts an example scenario 60 for a CU collecting RLF reports to duocast RLF reports to an older CU and DU. As depicted, the UE is connected to IAB donor 1 at time = T. Between time = T and time = T+1, the UE claims an RLF, but the UE cannot find coverage from either the IAB node or a non-IAB node to perform reconstruction (i.e., the UE is in a coverage hole, assuming a tunnel along a highway / traintrack where there is no coverage from non-IAB nodes, and if the IAB nodes experience a backhaul RLF for an extended period, they may also stop transmitting synchronization signals). The UE then reconnects in the same IAB node, which is now connected to IAB donor 2.

[0163] exist Figure 16 In the example scenario, IAB donor CU2 retrieves an RLF report from the UE and forwards it to the old IAB donor CU1. Now, donor CU1 may realize that the associated DU is no longer connected to it and may use any of the embodiments described above (e.g., forwarding it back to donor CU2 according to embodiment B). This will result in a delay in receiving the RLF report at the IABA and also increase network signaling overhead.

[0164] For this embodiment to work, donor CU1 must store the incoming handover history of its IAB nodes. For example, donor CU1 may store the cell identifier used by the IAB node in the previous donor, the corresponding cell identifier after the handover, the identifier of the previous donor CU, etc. For example, in certain embodiments, to address the problem, according to some embodiments, CU2 may perform the following process:

[0165] • Receive (X01) RLF report from UE;

[0166] • The identifier (X02) indicates that the RLF report needs to be forwarded to the source CU (CU1);

[0167] • Identify (X03) the source IAB node to which the RLF report needs to be forwarded and recognize that such an IAB node (IABA) is connected to itself;

[0168] • Send the RLF report directly (X04) to IABA; and / or

[0169] • Send the RLF report (X05) to the source donor CU (CU1) and indicate that the RLF report has been forwarded to IABA (because some information in the RLF report can also be used by the CU for example to fine-tune some switching parameters).

[0170] Actions taken by the CU when retrieving the RLF report from the UE (Example G)

[0171] According to certain embodiments, alternatively or additionally, the CU retrieving the RLF report from the UE may take other actions. In these embodiments, the CU retrieving the RLF / RA report from the UE (which in the above example may include IAB donor CU-3) determines whether a cell is associated with the DU corresponding to the mobile IAB node. To this end, CU-3 or other nodes may check whether such a cell is still in the list of neighboring cells of any cell controlled by CU-3, or in the list of cells controlled by a neighboring CU (for which Xn connections exist). If the cell of interest is not in such a list, CU-3 may conclude that such a cell is associated with the mobile IAB node.

[0172] In another specific embodiment, CU-3 or another node may obtain information from OAM regarding cell identifiers associated with the mobile IAB node. For example, CU-3 may request the OAM or AMF node to indicate whether the cell of interest is associated with the mobile IAB node, or the OAM / AMF node may configure a list of cell identifiers corresponding to the mobile IAB node for CU-3, allowing CU-3 to check this list upon receiving an RLF / RA report. In yet another specific embodiment, the UE itself may include an indication in the RLF / RA report that the associated report is related to the IAB donor DU. This may be an explicit or implicit indication (e.g., the CGI used may indicate cell ID space reserved for the IAB donor DU).

[0173] According to some embodiments, if the cell of interest is determined to correspond to a mobile IAB node, then CU-3 may:

[0174] • Discard associated RLF / RA reports;

[0175] • Forward the associated RA / RLF report to the OAM / AMF node;

[0176] Forward the associated RA / RLF report to the neighboring CU to which the cell of interest is currently connected (assuming the cell of interest is a neighbor of any cell controlled by CU-3, or that the cell is controlled by a CU with an Xn connection to CU-3);

[0177] • Forward the associated RA / RLF report to the neighboring CU where the cell of interest has been handed over (assuming the cell of interest was previously connected to CU-3 and that CU-3 still stores this information in memory, for example, the timer used to maintain such stored information has not expired or has not been replaced by more recent information); and / or

[0178] • If the DU is currently connected to CU-3, or if such information was still stored in CU-3 when it was connected to CU-3, the associated RA / RLF report is forwarded to the DU corresponding to the cell of interest.

[0179] Figure 17 The illustrations depict wireless networks according to some embodiments. While the subject matter described herein can be implemented using any suitable components in any appropriate type of system, the embodiments disclosed herein pertain to wireless networks (such as...). Figure 17 The example wireless network shown in the diagram is illustrated. For simplicity, Figure 17The wireless network depicted only includes network 106, network nodes 160 and 160b, and wireless devices 110, 110b, and 110c. In practice, the wireless network may further include any additional elements suitable for supporting 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. Among the illustrated components, network node 160 and wireless device 110 are described in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0180] Wireless networks may include any type of communications, telecommunications, data, cellular and / or radio network or other similar system and / or be connected to it via an interface. In some embodiments, a wireless network may be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific 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 standard; and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave and / or ZigBee standards.

[0181] Network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0182] Network node 160 and wireless device 110 include various components described in more detail below. These components work together to provide the functionality of the network node and / or wireless device, such as providing wireless connectivity in a wireless network. In various embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that facilitate or participate in communication of data and / or signals, whether via wired or wireless connections.

[0183] Figure 18An example network node 160 according to certain embodiments is illustrated. As used herein, a network node refers to a device capable of, configured to, arranged to, and / or operable to communicate directly or indirectly with a wireless device and / or with other network nodes or devices in a wireless network to enable and / or provide wireless access to the wireless device and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NRNode Bs (gNBs)). Base stations may be classified based on the coverage they provide (or, in other words, their transmission power levels) and may then also be referred to as femtocells, picocells, microcells, or macrocells. 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) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio headend (RRH). Such a remote radio unit may or may not be integrated with an antenna as a radio device with an integrated antenna. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS). Further examples of network nodes include multi-standard radio (MSR) equipment (such as an MSR BS), network controllers (such as a radio network controller (RNC) or base station controller (BSC)), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node can be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured to, arranged to, and / or operable to enable wireless devices to access a wireless network and / or provide access to a wireless network to wireless devices, or provide some service to wireless devices already connected to a wireless network.

[0184] exist Figure 18 In the network node 160, processing circuitry 170, device-readable medium 180, interface 190, auxiliary equipment 184, power supply 186, power circuitry 187, and antenna 162 are included. Although in Figure 18The network node 160 illustrated in the example wireless network may represent an apparatus including the illustrated combination of hardware components, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 160 are depicted as a single box within a larger box or nested within multiple boxes, in practice, a network node may include multiple different physical components that make up a single illustrated component (e.g., apparatus-readable medium 180 may include multiple separate hard disk drives and multiple RAM modules).

[0185] Similarly, network node 160 may consist of multiple physically separate components (e.g., NodeB components and RNC components, or BTS components and BSC components, etc.), each of which may have its own respective components. In some scenarios where network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single, separate network node in some instances. In some embodiments, network node 160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs), and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include a variety of illustrated components for various wireless technologies (such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into network node 160. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 160.

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

[0187] Processing circuitry 170 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of coded logic, software, and / or hardware operable alone or in combination with other network node 160 components (such as device-readable medium 180) to provide the functionality of network node 160. For example, processing circuitry 170 may execute instructions stored in device-readable medium 180 or in memory within processing circuitry 170. Such functionality may include any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system-on-a-chip (SoC).

[0188] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, RF transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units (such as radio units and digital units). In alternative embodiments, some or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit.

[0189] In some 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 170, which executes instructions stored in memory or on device-readable medium 180 within processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 (e.g., hardwired) without executing instructions stored on separate or discrete device-readable media. In any of those embodiments, processing circuitry 170 may be configured to perform the described functionality regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functionality are not limited to processing circuitry 170 alone or other components of network node 160, but are enjoyed by network node 160 as a whole, and / or generally by end users and the wireless network.

[0190] Device-readable medium 180 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, compact discs (CDs), or digital video discs (DVDs)) 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 usable by processing circuitry 170. Device-readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, codes, tables, etc., and / or other instructions executable by processing circuitry 170 and usable by network node 160. Device-readable medium 180 may be used to store any calculations performed by processing circuitry 170 and / or any data received via interface 190. In some embodiments, processing circuitry 170 and device-readable medium 180 may be considered integrated.

[0191] Interface 190 is used in wired or wireless communication of signaling and / or data between network node 160, network 106, and / or wireless device 110. As shown, interface 190 includes one or more ports / terminals 194 for transmitting and receiving data to and from network 106, for example, via a wired connection. Interface 190 also includes radio front-end circuitry 192, which may be coupled to antenna 162 or, in some embodiments, is part of antenna 162. Radio front-end circuitry 192 includes filter 198 and amplifier 196. Radio front-end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may be configured to modulate the signal transmitted between antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may receive digital data to be transmitted via a wireless connection to other network nodes or wireless devices. Radio front-end circuitry 192 may use a combination of filter 198 and / or amplifier 196 to convert digital data into radio signals with appropriate channel and bandwidth parameters. Radio signals can then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 can collect radio signals, which are then converted into digital data by radio front-end circuitry 192. The digital data can be transmitted to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0192] In some alternative embodiments, network node 160 may not include a separate radio front-end circuitry 192; instead, processing circuitry 170 may include radio front-end circuitry and may be connected to antenna 162 without a separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of the RF transceiver circuitry 172 may be considered part of interface 190. In other embodiments, interface 190 may include one or more RF transceiver circuitry 172, radio front-end circuitry 192, and ports or terminals 194 as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0193] Antenna 162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals from devices within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals along a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separate from network node 160 and may be connected to network node 160 via an interface or port.

[0194] Antenna 162, interface 190, and / or processing circuitry 170 may be configured to perform any receive operation and / or certain acquire operation 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 device. Similarly, antenna 162, interface 190, and / or processing circuitry 170 may be configured to perform any transmit operation 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 device.

[0195] Power circuit 187 may include or be coupled to power management circuitry and is configured to supply power to the components of network node 160 for performing the functionality described herein. Power circuit 187 may receive power from power source 186. Power source 186 and / or power circuit 187 may be configured to supply power to the respective components of network node 160 in a manner suitable for each component (e.g., at the voltage and current levels required by each respective component). Power source 186 may be included in or outside of power circuit 187 and / or network node 160. For example, network node 160 may be connected to an external power source (e.g., an electrical outlet) via input circuitry or an interface (such as a cable), thereby supplying power to power circuit 187. As another example, power source 186 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power circuit 187. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0196] Alternative embodiments of network node 160 may include, in addition to Figure 18 Additional components beyond those shown may be responsible for providing certain aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, network node 160 may include a user interface device to allow information to be input into and output from network node 160. This allows users to perform diagnostic, maintenance, repair, and other management functions on network node 160.

[0197] Figure 19An example wireless device 110 according to certain embodiments is illustrated. As used herein, a wireless device refers to a means capable of, configured to, arranged to, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise indicated, the term wireless device may be used interchangeably with user equipment (UE) herein. Wireless communication may involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information over the air. In some embodiments, a wireless device may be configured to transmit and / or receive information without direct human interaction. For example, a wireless device may be designed to transmit information to a network according to a predetermined schedule when triggered by an internal or external event or in response to a request from the network. Examples of wireless devices include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, return dischargers, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded devices (LEEs), laptop mounted devices (LMEs), smart devices, wireless customer premises equipment (CPEs), and vehicle-mounted wireless terminal devices. Wireless devices may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for pass-through communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), and in this case, may be referred to as D2D communication devices. As yet another specific example, in the Internet of Things (IoT) scenario, a wireless device may represent a machine or other device that performs monitoring and / or measurement and transmits the results of such monitoring and / or measurement to another wireless device and / or network node. In this context, the wireless device can be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As a specific example, the wireless device can be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery or household or personal appliances (e.g., refrigerators, televisions, etc.), and personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the wireless device can represent a vehicle or other equipment capable of monitoring and / or reporting its operational status or other functions associated with its operation. The wireless device described above can represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, the wireless device described above can be mobile, in which case it may also be referred to as a mobile device or mobile terminal.

[0198] As shown in the figure, wireless device 110 includes an antenna 111, an interface 114, processing circuitry 120, a device-readable medium 130, a user interface device 132, auxiliary devices 134, a power supply 136, and a power circuit 137. Wireless device 110 may include multiple sets of components for one or more of the illustrated components supporting different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few examples. These wireless technologies may be integrated into a chip or chipset that is the same as or different from other components within wireless device 110.

[0199] Antenna 111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and is connected to interface 114. In some alternative embodiments, antenna 111 may be separate from wireless device 110 and may be connected to wireless device 110 via an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receive or transmit operations described herein as performed by a wireless device. Any information, data, and / or signals may be received from network nodes and / or another wireless device. In some embodiments, radio front-end circuitry and / or antenna 111 may be considered as an interface.

[0200] As shown, interface 114 includes radio front-end circuitry 112 and antenna 111. Radio front-end circuitry 112 includes one or more filters 118 and amplifiers 116. Radio front-end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to modulate the signal transmitted between antenna 111 and processing circuitry 120. Radio front-end circuitry 112 may be coupled to antenna 111 or a portion thereof. In some embodiments, wireless device 110 may not include a separate radio front-end circuitry 112; instead, processing circuitry 120 may include radio front-end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered part of interface 114. Radio front-end circuitry 112 may receive digital data to be transmitted via a wireless connection to other network nodes or wireless devices. Radio front-end circuitry 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals may then be transmitted via antenna 111. Similarly, when data is received, antenna 111 can collect radio signals, which are then converted into digital data by radio front-end circuitry 112. The digital data can then be transmitted to processing circuitry 120. In other embodiments, the interface may include different components and / or different combinations of components.

[0201] Processing circuitry 120 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of coded logic, hardware, and / or software operable alone or in combination with other wireless device 110 components (such as device-readable medium 130) to provide functionality of wireless device 110. Such functionality may include any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device-readable medium 130 or memory within processing circuitry 120 to provide the functionality disclosed herein.

[0202] As shown in the figure, the processing circuit 120 includes one or more of the following: RF transceiver circuit 122, baseband processing circuit 124, and application processing circuit 126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 120 of the wireless device 110 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 122, baseband processing circuit 124, and application processing circuit 126 may be on a separate chip or chipset. In alternative embodiments, some or all of the baseband processing circuit 124 and application processing circuit 126 may be combined into a single chip or chipset, and the RF transceiver circuit 122 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuit 122 and baseband processing circuit 124 may be on the same chip or chipset, and the application processing circuit 126 may be on a separate chip or chipset. In other alternative embodiments, some or all of the RF transceiver circuit 122, baseband processing circuit 124, and application processing circuit 126 may be combined into the same chip or chipset. In some embodiments, the RF transceiver circuit 122 may be part of the interface 114. The RF transceiver circuit 122 may regulate the RF signal of the processing circuit 120.

[0203] In some embodiments, some or all of the functionality described herein as being performed by a wireless device may be provided by processing circuitry 120 executing instructions stored on device-readable medium 130, which may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 (e.g., hardwired) without executing instructions stored on a separate or discrete device-readable storage medium. In any of those particular embodiments, processing circuitry 120 may be configured to perform the described functionality regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functionality are not limited to processing circuitry 120 alone or other components of wireless device 110, but are enjoyed by wireless device 110 as a whole, and / or generally by the end user and the wireless network.

[0204] Processing circuitry 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by a wireless device. Such operations performed by processing circuitry 120 may include, for example, processing the acquired information by converting it into other information, comparing the acquired or converted information with information stored in wireless device 110, and / or performing one or more operations based on the acquired or converted information, and determining the result of said processing.

[0205] Device-readable medium 130 may be operable to store computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 120. Device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory means that stores information, data, and / or instructions usable by processing circuitry 120. In some embodiments, processing circuitry 120 and device-readable medium 130 may be considered integrated.

[0206] User interface device 132 provides components that allow human users to interact with wireless device 110. Such interaction can take many forms, such as visual, auditory, and tactile. User interface device 132 can be operated to produce outputs to the user and allow the user to provide inputs to wireless device 110. The type of interaction may vary depending on the type of user interface device 132 installed in wireless device 110. For example, if wireless device 110 is a smartphone, interaction may be via a touchscreen; if wireless device 110 is a smart meter, interaction may be via a screen providing usage information (e.g., gallons used) or a speaker providing audible alarms (e.g., if smoke is detected). User interface device 132 may include input interfaces, means, and circuitry, as well as output interfaces, means, and circuitry. User interface device 132 is configured to allow information to be input into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface device 132 may include, for example, a microphone, proximity sensor or other sensor, buttons / buttons, touch display, one or more cameras, USB port, or other input circuitry. User interface device 132 is also configured to allow information output from wireless device 110, and to allow processing circuitry 120 to output information from wireless device 110. User interface device 132 may include, for example, a speaker, display, vibration circuitry, USB port, headphone jack, or other output circuitry. Using one or more input and output interfaces, means, and circuitry of user interface device 132, wireless device 110 can communicate with end users and / or wireless networks, allowing them to benefit from the functionality described herein.

[0207] The auxiliary device 134 is operable to provide more specific functionality that is generally not possible by a wireless device. This may include dedicated sensors for measuring for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and type of components of the auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0208] In some embodiments, power source 136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a power battery. Wireless device 110 may further include power circuitry 137 for delivering power from power source 136 to various portions of wireless device 110 that require power from power source 136 to perform any functionality described or indicated herein. In some embodiments, power circuitry 137 may include power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in this case, wireless device 110 may be connectable to an external power source (e.g., an electrical outlet) via input circuitry or an interface (e.g., a power cable). In some embodiments, power circuitry 137 may also be operable to deliver power from an external power source to power source 136. For example, this can be used for charging power source 136. Power circuitry 137 may perform any formatting, conversion, or other modifications on the power from power source 136 to adapt the power to the corresponding components of wireless device 110 to which it is supplied power.

[0209] Figure 20 An embodiment of UE 200 according to the various aspects described herein is illustrated. 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 associated device. Instead, a UE may represent a device intended to be sold to or operated by a human user, but which may not or may not initially be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device not intended to be sold to or operated 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 200 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine-Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 18 The UE200 illustrated is an example of a radio device configured to communicate according to one or more communication standards published by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the terms radio device and UE can be used interchangeably. Therefore, although... Figure 20 This is for UEs, but the components discussed in this article also apply to wireless devices, and vice versa.

[0210] exist Figure 20In this embodiment, UE 200 includes processing circuitry 201 operatively coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network connectivity interface 211, a memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and a storage medium 221, a communication subsystem 231, a power supply 233, and / or any other components or any combination thereof. Storage medium 221 includes an operating system 223, application programs 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Some UEs may utilize... Figure 20 All components shown, or only a subset of components, can be used. The integration level between components can vary from one UE to another. Additionally, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0211] exist Figure 20 In this system, processing circuitry 201 can be configured to process computer instructions and data. Processing circuitry 201 can be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, 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 programs, a general-purpose processor (such as a microprocessor or digital signal processor (DSP)) together with appropriate software; or any combination of the foregoing. For example, processing circuitry 201 may include two central processing units (CPUs). Data may be information in a computer-appropriate form.

[0212] In the depicted embodiments, the input / output interface 205 may be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 200 may be configured to use an output device via the input / output interface 205. The output device may use an interface port of the same type as the input device. For example, a USB port may be used to provide input to and output from the UE 200. The output device may be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 200 may be configured to use an input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. A presence-sensitive display may include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, another similar sensor, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and light sensors.

[0213] exist Figure 20 In this configuration, RF interface 209 can be configured to provide a communication interface to RF components (such as transmitters, receivers, and antennas). Network connectivity interface 211 can be configured to provide a communication interface to network 243a. Network 243a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 243a may include a Wi-Fi network. Network connectivity interface 211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (such as Ethernet, TCP / IP, SONET, ATM, etc.). Network connectivity interface 211 can implement receiver and transmitter functionality suitable for communication network links (e.g., optical, electrical, etc.). Transmitter and receiver functionality may share circuit components, software, or firmware, or alternatively may be implemented separately.

[0214] RAM 217 may be configured to interface with processing circuitry 201 via bus 202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 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) stored in non-volatile memory. Storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash memory drive. In one example, storage medium 221 may be configured to include operating system 223, application 225 (such as a web browser application, widget or gadget engine, or another application), and data file 227. Storage medium 221 may store any of a variety of operating systems or combinations of operating systems for use by UE 200.

[0215] Storage medium 221 may be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital multifunction disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) optical disc drive, an external micro dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), an external micro DIMM SDRAM, smart card memory (such as a subscriber identification module or a removable subscriber identity (SIM / RUIM) module), other memory, or any combination thereof. Storage medium 221 may allow UE 200 to access computer-executable instructions, applications, etc., stored on a transient or non-transient storage medium to unload or upload data. Articles of manufacture (such as an article utilizing a communication system) may be tangibly embodied in storage medium 221, which may include a device-readable medium.

[0216] exist Figure 20In this embodiment, processing circuitry 201 can be configured to communicate with network 243b using communication subsystem 231. Networks 243a and 243b can be the same one or more networks or different one or more networks. Communication subsystem 231 can be configured to include one or more transceivers for communicating with network 243b. For example, communication subsystem 231 can be configured to include one or more transceivers for communicating with one or more remote transceivers of another device (such as another wireless device, UE, or a base station of a radio access network (RAN)) capable of wireless communication according to one or more communication protocols (such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include transmitter 233 and / or receiver 235 to respectively implement transmitter or receiver functionality suitable for the RAN link (e.g., frequency allocation, etc.). Additionally, the transmitter 233 and receiver 235 of each transceiver can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0217] In the illustrated embodiment, the communication functions of the communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. For example, the communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 243b may include 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 similar network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0218] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 200, or divided across multiple components of UE 200. Additionally, the features, benefits, and / or functions described herein may be implemented using any combination of hardware, software, or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Additionally, processing circuitry 201 may be configured to communicate with any of these components via bus 202. In another example, any of these components may be represented by program instructions stored in memory that, when executed by processing circuitry 201, perform the corresponding functions described herein. In another example, the functionality of any such component may be divided between processing circuitry 201 and communication subsystem 231. In yet another example, the non-computationally intensive functions of any such component may be implemented using software or firmware, and the computationally intensive functions may be implemented using hardware.

[0219] Figure 21 This is a schematic block diagram illustrating a virtualization environment 300, in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating virtual versions of devices or apparatuses, which may include virtualized hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or apparatuses (e.g., UEs, wireless devices, or any other type of communication apparatus) or components thereof, and involves at least a portion of their functionality being implemented as an implementation of one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executed on one or more physical processing nodes in one or more networks).

[0220] In some embodiments, some or all of the functionalities described herein may be implemented as virtual components executed by one or more virtual machines, which are implemented in one or more virtual environments 300 hosted by one or more hardware nodes in hardware node 330. Additionally, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may then be fully virtualized.

[0221] These functionalities can be implemented by one or more applications 320 (alternatively, they may be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to provide some of the features, functions, and / or benefits disclosed in the embodiments herein. The applications 320 operate in a virtualization environment 300, which provides hardware 330 including processing circuitry 360 and memory 390. The memory 390 contains instructions 395 executable by the processing circuitry 360, thereby enabling the applications 320 to provide one or more of the features, benefits, and / or functions disclosed herein.

[0222] The virtualization environment 300 includes general-purpose or special-purpose network hardware devices 330. Device 330 includes one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, specialized application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or a special-purpose processor. Each hardware device may include memory 390-1, which may be non-persistent memory for temporarily storing software or instructions 395 executed by the processing circuitry 360. Each hardware device may include one or more network interface controllers (NICs) 370 (also referred to as network interface cards), which include physical network interfaces 380. Each hardware device may also include a non-transitory, permanent, machine-readable storage medium 390-2 in which instructions and / or software 395 executable by the processing circuitry 360 are stored. Software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software for executing virtual machines 340, and software that allows them to perform the functions, features, and / or benefits described in conjunction with some embodiments described herein.

[0223] Virtual machine 340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage devices, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of virtual appliance 320 may be implemented on one or more of virtual machines 340, and this implementation may be carried out in different ways.

[0224] During operation, the processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 350 can present a virtual operating platform to the virtual machine 340 that appears to be networked hardware.

[0225] like Figure 21As shown, hardware 330 can be a standalone network node with general or specific components. Hardware 330 may include antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger hardware cluster (e.g., such as in a data center or customer premises equipment (CPE)) in which many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among other things, oversees the lifecycle management of application 320.

[0226] Hardware virtualization is sometimes referred to as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard high-capacity server hardware, physical switches, and physical storage devices, which can reside in data centers and customer premises.

[0227] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine, and its programs run as if they were executing on a physical, non-virtualized machine. Each virtual machine in 340, as well as the portion of hardware 330 that executes that virtual machine (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines in 340), forms a separate virtual network element (VNE).

[0228] Within the context of NFV, a Virtual Network Function (VNF) is responsible for handling specific network functions running in one or more virtual machines 340 on top of the hardware networking infrastructure 330, and corresponds to Figure 21 Application 320.

[0229] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio unit 3200 may communicate directly with the hardware node 330 via one or more suitable network interfaces and may be used in combination with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0230] In some embodiments, some signaling can be affected by the use of a control system 3230, which can alternatively be used for communication between hardware node 330 and radio unit 3200.

[0231] Figure 22 The illustration depicts a telecommunications network connected to a host computer via an intermediate network, according to some embodiments. (Reference) Figure 22According to an embodiment, the communication system includes a telecommunications network 410, such as a 3GPP-type cellular network, which includes an access network 411, such as a radio access network, and a core network 414. The access network 411 includes multiple base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs, or other types of wireless access points, each base station defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c can be connected to the core network 414 via a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to or be paged by the corresponding base station 412c. A second UE 492 in coverage area 413a can wirelessly connect to the corresponding base station 412a. Although multiple UEs 491, 492 are illustrated in this example, the disclosed embodiments are equally applicable to situations where only one UE is in the coverage area or where only one UE is connected to the corresponding base station 412.

[0232] Telecommunications network 410 is itself connected to host computer 430, 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 430 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 421 and 422 between telecommunications network 410 and host computer 430 may extend directly from core network 414 to host computer 430, or may be via optional intermediate network 420. Intermediate network 420 may be one or more of public, private, or hosted networks; intermediate network 420 (if any) may be a backbone network or the Internet; in particular, intermediate network 420 may include two or more subnetworks (not shown).

[0233] Figure 22The communication system as a whole enables connectivity between connected UEs 491 and 492 and host computer 430. This connectivity can be described as an over-the-top (OTT) connection 450. Host computer 430 and connected UEs 491 and 492 are configured to use access network 411, core network 414, any intermediate network 420, and possibly other infrastructure (not shown) as intermediaries to transmit data and / or signaling via OTT connection 450. OTT connection 450 can be transparent in the sense that the participating communication devices traversed by OTT connection 450 are unaware of the routes of uplink and downlink communications. For example, it may not be necessary or required to inform base station 412 about the past routes of incoming downlink communications having data originating from host computer 430 to be forwarded (e.g., handover) to connected UE 491. Similarly, base station 412 does not need to know the future routes of outgoing uplink communications originating from UE 491 to host computer 430.

[0234] Figure 23 The illustration shows a host computer communicating with a user equipment via a base station through a partial wireless connection, according to some embodiments.

[0235] Now refer to Figure 23 Example implementations of the UE, base station, and host computer discussed in the preceding paragraphs according to embodiments are described. In communication system 500, host computer 510 includes hardware 515 including a communication interface 516 configured to establish and maintain a wired or wireless connection to an interface with different communication devices of communication system 500. Host computer 510 further includes processing circuitry 518, which may have storage and / or processing capabilities. In particular, processing circuitry 518 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Host computer 510 further includes software 511 stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 may be operable to provide services to remote users, such as UE 530 connected via an OTT connection 550 terminated between UE 530 and host computer 510. In providing services to remote users, host application 512 may provide user data transmitted using OTT connection 550.

[0236] The communication system 500 further includes a base station 520, which is disposed in the telecommunications system and includes hardware 525 enabling it to communicate with a host computer 510 and a UE 530. Hardware 525 may include a communication interface 526 for setting up and maintaining wired or wireless connections to different communication devices of the communication system 500, and for setting up and maintaining connections with at least the coverage area served by the base station 520. Figure 23 The radio interface 527 of the UE530 (not shown) is the wireless connection 570. The communication interface 526 can be configured to facilitate a connection 560 to the host computer 510. The connection 560 can be direct, or it can be via the core network of a telecommunications system (…). Figure 23 (not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 525 of base station 520 further includes processing circuitry 528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

[0237] The communication system 500 further includes the previously mentioned UE 530. The hardware 535 of the UE 530 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area where the UE 530 is currently located. The hardware 535 of the UE 530 further includes processing circuitry 538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 530 further includes software 531 stored in or accessible by the UE 530 and executable by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 may be operable to provide services to human or non-human users via the UE 530 with the support of a host computer 510. In the host computer 510, a executing host application 512 may communicate with the executing client application 532 via an OTT connection 550 terminated between the UE 530 and the host computer 510. In providing services to users, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transmit both the request data and the user data. Client application 532 can interact with the user to generate the user data it provides.

[0238] Notice, Figure 23 The host computer 510, base station 520, and UE530 shown in the diagram can respectively connect with... Figure 22The host computer 430, base stations 412a, 412b, and 412c, and UEs 491 and 492 are similar to or identical to each other. That is to say, the internal workings of these entities can be as follows: Figure 23 As shown, and independently, the surrounding network topology can be Figure 22 The network topology.

[0239] exist Figure 23 In this diagram, OTT connection 550 is abstractly depicted to illustrate communication between host computer 510 and UE 530 via base station 520, without explicitly mentioning any intermediary devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to conceal it from either the UE 530 or the service provider operating the host computer 510, or both. When OTT connection 550 is active, the network infrastructure can further make decisions, through which it dynamically changes the routing (e.g., based on network reconfiguration or load balancing considerations).

[0240] The wireless connection 570 between UE530 and base station 520 is consistent with the teachings of the embodiments described throughout this disclosure. One or more embodiments in the various embodiments improve the performance of OTT services provided to UE530 using OTT connection 550, wherein wireless connection 570 forms the final segment. More precisely, the teachings of these embodiments can improve data rates, latency, and / or power consumption, and thereby provide benefits such as reduced user wait times, relaxed restrictions on file size, better responsiveness, and / or extended battery life.

[0241] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors improved by one or more embodiments. Optional network functionality may further exist for reconfiguring the OTT connection 550 between host computer 510 and UE 530 in response to changes in measurement results. The network functionality and / or measurement procedures for reconfiguring the OTT connection 550 may be implemented using software 511 and hardware 515 of host computer 510, or software 531 and hardware 535 of UE 530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices traversed by the OTT connection 550; sensors may participate in the measurement process by supplying values ​​of the monitored quantities illustrated above, or by supplying values ​​of other physical quantities that software 511, 531 may calculate or estimate based on the monitored quantities. Reconfiguration of the OTT connection 550 may include message formatting, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect base station 520, and it may be unknown or imperceptible to base station 520. Such processes and functionality can be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 510 in measuring throughput, propagation time, latency, etc. Measurements can be performed in such a way that software 511 and 531, while monitoring propagation time, errors, etc., use OTT connection 550 to enable the transmission of messages (especially empty or 'virtual' messages).

[0242] Figure 24 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 22 and 23 The host computers, base stations, and UEs described herein. For the sake of simplicity in this disclosure, this section will only include descriptions of... Figure 24 Referring to the accompanying drawings. In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides user data by executing a host application. In step 620, the host computer initiates a transmission carrying user data to the UE. In step 630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0243] Figure 25 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 22 and 23 The host computers, base stations, and UEs described herein. For the sake of simplicity in this disclosure, this section will only include descriptions of... Figure 25 Refer to the accompanying drawings. In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 720, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may be carried out via a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0244] Figure 26 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 22 and 23 The host computers, base stations, and UEs described herein. For the sake of simplicity in this disclosure, this section will only include descriptions of... Figure 26 Referring to the accompanying drawings. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 of step 820 (which may be optional), the UE provides user data by executing a client application. In sub-step 811 of step 810 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. In providing user data, the executed client application may further consider user input received from the user. Regardless of the specific method used to provide user data, in sub-step 830 (which may be optional), the UE initiates the transmission of user data to the host computer. In step 840 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.

[0245] Figure 27 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 22 and 23 The host computers, base stations, and UEs described herein. For the sake of simplicity in this disclosure, this section will only include descriptions of... Figure 27Refer to the accompanying drawings. In step 910 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0246] Figure 28 A method 1000 performed by a first network node 160 according to certain embodiments is described. In step 1002, the first network node 160 obtains information related to a radio link failure or radio link recovery associated with the wireless device 110. In step 1004, the first network node 160 determines that the information is related to a radio link failure or radio link recovery associated with a cell associated with a second network node not served by the first network node. In step 1006, the first network node 160 takes at least one action in response to determining that the information is related to a radio link failure or radio link recovery associated with a cell not served by the first network node 160 but associated with the second network node 160.

[0247] In a particular embodiment, the first network node is acting as a donor CU for at least one IABDU node in the IAB network.

[0248] In a particular embodiment, when information is obtained, the second network node includes an IABDU node that is not served by the first network node.

[0249] In a particular embodiment, obtaining information includes receiving information from the wireless device.

[0250] In a particular embodiment, the information is received in messages that include radio link failure (RLF) reports and / or random access (RA) reports.

[0251] In a particular embodiment, taking at least one action includes deleting information.

[0252] In a particular embodiment, taking at least one action includes transmitting (i.e., forwarding) information to a third network node currently serving the second network node. In another particular embodiment, the second network node includes an IABDU node, and the third network node includes a central unit, and the second network node has already been switched from the first network node to the third network node during a handover process. In yet another particular embodiment, the first network node stores the handover history of the second network node; and based on the handover history, it is determined that the second network node has been switched to the third network node, and information is transmitted to the third network node based on the handover history indicating that the second network node has been switched to the third network node.

[0253] In a particular embodiment, taking at least one action includes: storing information; determining that a second network node has been switched to a first network node; and transmitting the information to the second network node. In another particular embodiment, the second network node is associated with a unique identifier, and the first network node stores information as associated with the unique identifier associated with the second network node, receives a setup message (including the unique identifier associated with the second network node) associated with the second network node that has been switched to the first network node, determines that the information is associated with the second network node based on the setup message including the unique identifier associated with the second network node, and transmits the information to the second network node in response to determining that the information is associated with the second network node. In yet another particular embodiment, the first network node is associated with a unique identifier, and the first network node receives a setup message (including the unique identifier associated with the first network node) associated with the second network node that has been switched to the first network node, determines that the information is associated with the second network node based on the setup message including the unique identifier associated with the first network node, and transmits the information to the second network node in response to determining that the information is associated with the second network node.

[0254] In a particular embodiment, taking at least one action includes transmitting information to a fourth network node operating as an Operation and Maintenance (OAM) node, so as to forward it to a fifth network node currently serving the second network node.

[0255] In a particular embodiment, taking at least one action includes sending a request for handover information to a fourth network node operating as an OAM node, receiving handover information from the fourth network node, and sending information to a fifth network node. The handover information indicates that the second network node is being served by the fifth network node.

[0256] In a particular embodiment, taking at least one action includes transmitting information to a core network node so as to forward it to a fifth network node that is currently serving the second network node.

[0257] In a particular embodiment, taking at least one action includes sending a request for handover information to a core network node, receiving handover information from the core network node, and sending information to a fifth network node. The handover information indicates that the second network node is being served by the fifth network node.

[0258] In another specific embodiment, the core network node includes an Access and Mobility Management Function (AMF) and / or a Mobility Management Entity (MME).

[0259] In a particular embodiment, obtaining information related to a radio link failure or radio link recovery associated with a wireless device includes receiving information from a message received from the wireless device.

[0260] In a particular embodiment, obtaining information related to a radio link failure or radio link recovery associated with a wireless device includes receiving information from a message from a sixth network node that acts as a donor CU, which is a second network node when a radio link failure or radio link recovery occurs associated with the wireless device.

[0261] In a particular embodiment, the first network node determines that the second network node is a mobile IAB node, and in response to determining that the second network node is a mobile IAB node, takes at least one action in at least part.

[0262] In a particular embodiment, determining that the second network node is a mobile IAB node includes determining that the cell is not on a list that includes at least one cell that is a neighbor of any cell controlled by the first network node. In another particular embodiment, determining that the second network node is a mobile IAB node includes determining that the cell is not on a list that includes at least one cell controlled by a neighboring network node operating as a CU. In yet another particular embodiment, determining that the second network node is a mobile IAB node includes receiving information from the OAM indicating that the cell is associated with the mobile IAB node. In yet another particular embodiment, the information received from the OAM includes a list identifying at least one cell as associated with the mobile IAB node.

[0263] In another specific embodiment, the first network node transmits a request to the OAM for information indicating the association of the cell with the mobile IAB node.

[0264] Figure 29 The diagram illustrates a wireless network (e.g., Figure 17 A schematic block diagram of a virtual device 1100 in a wireless network (as shown in the diagram). This device can be located in a wireless device or network node (e.g., Figure 17 This is implemented in the wireless device 110 or network node 160 shown. Device 1100 is operable to implement the reference. Figure 28 The example methods described herein, and possibly any other procedures or methods disclosed herein. It should also be understood that... Figure 28 The method is not necessarily performed solely by device 1100. At least some operations of the method may be performed by one or more other entities.

[0265] The virtual device 1100 may include processing circuitry and other digital hardware. The processing circuitry may include one or more microprocessors or microcontrollers, and the other digital hardware may include digital signal processors (DSPs), application-specific digital logic (ASICs), etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the acquisition module 1110, the determination module 1120, the action taking module 1130, and any other suitable units of the device 1100 to perform corresponding functions according to one or more embodiments of this disclosure.

[0266] According to some embodiments, the acquisition module 1110 may perform certain acquisition functions of the acquisition functions of the device 1100. For example, the acquisition module 1110 may acquire information related to radio link failure or radio link recovery associated with the wireless device.

[0267] According to some embodiments, the determining module 1120 may perform certain determining functions of the determining function of the device 1100. For example, the determining module 1120 may determine that the information is related to a radio link failure or radio link recovery, which is associated with a cell of a second network node not served by the first network node.

[0268] According to some embodiments, the action module 1130 may perform certain action functions of the action functions of the device 1100. For example, the action module 1130 may take at least one action in response to determining that the information is related to a radio link failure or radio link recovery, which is associated with a cell not served by a first network node.

[0269] As used herein, the term "unit" may have the conventional meaning in the fields of electronics, electrical devices and / or electronic devices, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing corresponding tasks, processes, calculations, outputs and / or displays, as described herein.

[0270] Figure 30 Another method 1200 performed by a first network node 160 according to certain embodiments is described. In step 1202, the first network node 160 receives information related to a radio link failure or radio link recovery associated with the wireless device 110. The information is received from a second network node currently serving the wireless device 110. The information is associated with a cell of a third network node that previously served the wireless device 110. The third network node is not currently being served by the second network node. In step 1204, the first network node takes at least one action regarding the information.

[0271] In a particular embodiment, the second network node is acting as a donor central unit (CU) for at least one IAB distributed unit (DU) node in an integrated access and radio access backhaul (IAB) network, and the third network node includes an IAB node not served by the second network node.

[0272] In a particular embodiment, the information is received in messages that include radio link failure (RLF) reports and / or random access (RA) reports.

[0273] In a particular embodiment, taking at least one action includes transmitting information to a fourth network node that is currently serving a third network node.

[0274] In a particular embodiment, the first network node is operating as an Operation and Maintenance (OAM) node.

[0275] In a particular embodiment, the first network node is a core network node. In another particular embodiment, the core network node includes an Access and Mobility Management Function (AMF) and / or a Mobility Management Entity (MME).

[0276] In another specific embodiment, the first network node receives a request for handover information and transmits the handover information to another network node. The handover information indicates that the third network node is being served by the fourth network node.

[0277] In a particular embodiment, the third network node is a mobile IAB node, and at least one of the actions is taken in response to determining that the third network node is a mobile IAB node.

[0278] In another specific embodiment, the first network node determines that the third network node is a mobile IAB node. In yet another specific embodiment, determining that the third network node is a mobile IAB node includes determining that the cell is not on a list that includes at least one cell that is a neighbor of any cell controlled by the second network node. Alternatively, in yet another specific embodiment, determining that the third network node is a mobile IAB node includes determining that the cell is not on a list that includes at least one cell controlled by a neighboring network node operating as a CU.

[0279] In a particular embodiment, taking at least one action further includes transmitting information indicating that a cell is associated with a mobile IAB node to at least one other network node, wherein such information includes a list identifying at least one cell as associated with a mobile IAB node.

[0280] In a particular embodiment, taking at least one action further includes transmitting information to at least one other network node. In a particular embodiment, at least one other network node includes any one or more of the following:

[0281] Second network node,

[0282] The third network node that previously served the wireless device;

[0283] Core network nodes:

[0284] Currently serving wireless devices (DU);

[0285] Previously served wireless devices DU;

[0286] IAB nodes that previously served wireless devices;

[0287] The IAB node currently serving the wireless device;

[0288] The CU that previously served the wireless device; and

[0289] The CU of the currently serving wireless device.

[0290] Figure 31 The diagram illustrates a wireless network (e.g., Figure 17 Another schematic block diagram of a virtual device 1300 in a wireless network (as shown in the diagram). This device can be located in a wireless device or network node (e.g., Figure 17 This is implemented in the wireless device 110 or network node 160 shown. Device 1300 is operable to implement the reference... Figure 30 The example methods described herein, and possibly any other procedures or methods disclosed herein. It should also be understood that... Figure 30 The method is not necessarily to be performed solely by device 1300. At least some operations of the method may be performed by one or more other entities.

[0291] The virtual device 1300 may include processing circuitry and other digital hardware. The processing circuitry may include one or more microprocessors or microcontrollers, and the other digital hardware may include digital signal processors (DSPs), application-specific digital logic (ASICs), etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the receiving module 1310, the action module 1320, and any other suitable units of the device 1300 to perform corresponding functions according to one or more embodiments of this disclosure.

[0292] According to some embodiments, the receiving module 1310 may perform certain receiving functions of the receiving function of the device 1300. For example, the receiving module 1310 may receive information related to a radio link failure or radio link recovery associated with a wireless device. The information is received from a second network node currently serving the wireless device. The information is associated with a cell associated with a third network node that previously served the wireless device. The third network node is not currently being served by the second network node.

[0293] According to some embodiments, the action module 1320 may perform certain action functions of the action function of the device 1300. For example, the action module 1320 may take at least one action regarding information.

[0294] Figure 32 An example method 1400 performed by a first network node 160 according to certain embodiments is illustrated. In step 1402, the first network node 160 obtains information associated with a SON report associated with a wireless device. In step 1404, the first network node 160 determines that the information associated with the SON report is associated with a cell not served by the first network node 160. In step 1406, in response to determining that the information associated with the SON report is associated with a cell not served by the first network node 160, the first network node 160 takes at least one action, including deleting the information or transmitting the information to a second network node.

[0295] In certain embodiments, at least one of the following is true: the SON report includes a link failure report; the link failure report includes a handover failure report or an RLF report; and the SON report is associated with a random access procedure. In some examples, the SON report contains information related to a previous radio failure or recovery of the wireless device. In some examples, obtaining information associated with the SON report (1402) includes obtaining the SON report, or obtaining information, such as information related to a radio failure or recovery of the wireless device. In some examples, the information relates to a link failure, such as a handover failure or a radio link failure. The SON report can be considered a report that includes any such information.

[0296] In some examples, deleting or transmitting information in step 1406 corresponds to deleting or transmitting information in the SON report (e.g., information related to radio failure or recovery of the wireless device), or deleting or transmitting the SON report.

[0297] In a particular embodiment, the first network node 160 is acting as a donor CU for at least one IAB DU node in the IAB network.

[0298] In a particular embodiment, when the information is obtained, the second network node includes an IABDU node that is not served by the first network node 160, and the second network node is currently serving a cell.

[0299] In a particular embodiment, the first network node 160 stores the handover history of at least one additional node in the IAB network and determines, based on the handover history, that at least one additional network node has been switched to the second network node. Information indicating that the at least one additional network node has been switched to the second network node is transmitted to the second network node.

[0300] In another specific embodiment, the second network node is serving the cell when the information is generated.

[0301] In a particular embodiment, when information is obtained, the first network node 160 receives information from the wireless device 110.

[0302] In a particular embodiment, when transmitting information to the second network node, the first network node 160 stores information associated with the SON report, determines that the second network node has been switched to the first network node 160, and in response to determining that the second network node has been switched to the first network node 160, transmits information associated with the SON report to the second network node.

[0303] In a particular embodiment, the second network node is associated with a unique identifier, and the first network node 160 stores information associated with the unique identifier associated with the second network node. The first network node 160 receives a setup message associated with the second network node that has been switched to the first network node, and the setup message includes the unique identifier associated with the second network node. Based on the setup message including the unique identifier associated with the second network node, the first network node 160 determines that information is associated with the second network node, and in response to determining that information associated with the SON report is associated with the second network node, transmits the information associated with the SON report to the second network node.

[0304] In another specific embodiment, a first network node 160 is associated with a unique identifier. The first network node 160 receives a setup message associated with a second network node that has been switched to the first network node 160, and the setup message includes a unique identifier associated with the first network node 160. Based on the setup message including the unique identifier associated with the first network node, the first network node 160 determines that information is associated with the second network node, and in response to determining that information is associated with the second network node, transmits information associated with the SON report to the second network node.

[0305] In a particular embodiment, transmitting information to the second network node includes transmitting information to the OAM node for forwarding to the third network node currently serving the cell.

[0306] In a particular embodiment, transmitting information to the second network node includes sending a request for handover information to the OAM node or core network node, and receiving handover information from the OAM node or core network node. The handover information indicates that the cell is being served by the second network node. The first network node transmits information associated with the SON report to the second network node.

[0307] In a particular embodiment, transmitting information associated with the SON report to a second network node includes transmitting information associated with the SON report to a core network node for forwarding to at least one additional network.

[0308] In a particular embodiment, the first network node 160 determines that the cell is associated with a mobile IAB node, and in response to determining that the cell is associated with a mobile IAB node, takes at least one action in at least part.

[0309] In another specific embodiment, determining that a cell is associated with a mobile IAB node includes determining that the cell is not on a list that includes at least one cell controlled by a neighboring network node operating as a CU.

[0310] In another specific embodiment, determining the association between a cell and a mobile IAB node includes receiving information from the OAM node indicating that the cell is associated with the mobile IAB node.

[0311] Figure 33 The diagram illustrates a wireless network (e.g., Figure 17 Another schematic block diagram of a virtual device 1500 in a wireless network (as shown in the diagram). This device can be located in a wireless device or network node (e.g., Figure 17 This is implemented in the wireless device 110 or network node 160 shown. Device 1500 is operable to implement the reference... Figure 32 The example methods described herein, and possibly any other procedures or methods disclosed herein. It should also be understood that... Figure 32 The method is not necessarily to be performed solely by device 1500. At least some operations of the method may be performed by one or more other entities.

[0312] The virtual device 1500 may include processing circuitry and other digital hardware. The processing circuitry may include one or more microprocessors or microcontrollers, and the other digital hardware may include digital signal processors (DSPs), application-specific digital logic (ASICs), etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the acquisition module 1510, the determination module 1520, the action taking module 1530, and any other suitable modules of the device 1500 to perform corresponding functions according to one or more embodiments of this disclosure.

[0313] According to some embodiments, the acquisition module 1510 may perform certain acquisition functions of the acquisition functions of the device 1500. For example, the acquisition module 1510 may acquire information associated with SON reports associated with wireless devices.

[0314] According to some embodiments, the determining module 1520 may perform certain determining functions of the determining function of the device 1500. For example, the determining module 1520 may determine that information associated with the SON report is associated with a cell not served by the first network node 160.

[0315] According to some embodiments, the action module 1530 may perform certain action functions of the action functions of the device 1500. For example, in response to information associated with a SON report being associated with a cell not served by the first network node 160, the action module 1520 may take at least one action, including deleting the information or transmitting the information to a second network node.

[0316] Figure 34An example method 1600 performed by a first network node 160 according to certain embodiments is illustrated. In step 1602, the first network node receives information associated with a SON report associated with the radio device 110. The information is received from the donor CU currently serving the radio device 110, and the information is associated with a cell that previously served the radio device 110 and is not currently served by the donor CU. In step 1606, the first network node 160 transmits the information to a second network node.

[0317] In a particular embodiment, at least one of the following is true: the SON report includes a link failure report; the SON report includes a handover failure report or a radio link failure (RLF) report; and the SON report is associated with a random access procedure.

[0318] In a particular embodiment, the information is associated with an IAB node that is not served by the donor CU.

[0319] In a particular embodiment, the second network node includes the IABDU node of the currently serving cell.

[0320] In a particular embodiment, the first network node 160 is operating as a core network node or OAM node, including AMF and / or MME.

[0321] In a particular embodiment, the first network node 160 receives a request for handover information from the second network node. In response to the request, information is transmitted to the second network node, and the information indicates that the cell is being served by a third network node.

[0322] In another specific embodiment, the cell is associated with a mobile IAB node, and in response to determining that the cell is associated with a mobile IAB node, information is transmitted to a second network node.

[0323] In another specific embodiment, determining that a cell is associated with a mobile IAB node includes determining that the cell is not on a list that includes at least one cell controlled by a neighboring network node operating as a CU.

[0324] In a particular embodiment, the information associated with the SON report indicates that the cell is associated with a mobile IAB node.

[0325] In another specific embodiment, the information associated with the SON report includes a list identifying at least one cell as associated with a mobile IAB node.

[0326] In a particular embodiment, the second network node includes any one or more of the following: a network node of a previously serving wireless device, a core network node, a DU of a currently serving wireless device, a DU of a previously serving wireless device, an IAB node of a previously serving wireless device, an IAB node of a currently serving wireless device, a donor CU of a previously serving wireless device, and a CU of a currently serving wireless device.

[0327] Figure 35 The diagram illustrates a wireless network (e.g., Figure 17 Another schematic block diagram of a virtual device 1700 in a wireless network (as shown in the diagram). This device can be located in a wireless device or network node (e.g., Figure 17 This is implemented in the wireless device 110 or network node 160 shown. Device 1700 is operable to implement the reference. Figure 34 The example methods described herein, and possibly any other procedures or methods disclosed herein. It should also be understood that... Figure 34 The method is not necessarily to be performed solely by device 1700. At least some operations of the method may be performed by one or more other entities.

[0328] The virtual device 1700 may include processing circuitry and other digital hardware. The processing circuitry may include one or more microprocessors or microcontrollers, and the other digital hardware may include digital signal processors (DSPs), application-specific digital logic (ASICs), etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In some embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols, and instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the receiving module 1710, the transmitting module 1720, and any other suitable modules of the device 1700 to perform corresponding functions according to one or more embodiments of this disclosure.

[0329] According to some embodiments, the receiving module 1710 may perform certain receiving functions of the receiving function of the device 1700. For example, the receiving module 1710 may receive information related to a SON report associated with a wireless device. The information is received from a donor CU currently serving the wireless device, and the information is associated with a cell that previously served the wireless device but is not currently being served by the donor CU.

[0330] According to some embodiments, the transmission module 1720 may perform certain transmission functions of the device 1700. For example, the transmission module 1720 may transmit information to a second network node.

[0331] Example Implementation

[0332] Group A1 Examples

[0333] Example 1. A method performed by a first network node, the method comprising: obtaining information related to a radio link failure or radio link recovery associated with a wireless device; determining that the information is related to a radio link failure or radio link recovery, the radio link failure or radio link recovery being associated with a cell associated with a second network node not served by the first network node; and taking at least one action in response to determining that the information is related to a radio link failure or radio link recovery, the radio link failure or radio link recovery being associated with a cell associated with a second network node not served by the first network node.

[0334] Example 2. The method of Example 1, wherein a first network node is acting as a donor central unit (CU) of at least one IAB distributed unit (DU) node in an integrated access and radio access backhaul (IAB) network.

[0335] Example 3. The method of any of the embodiments of Examples 1 to 2, wherein when information is obtained, the second network node includes an IABDU node not served by the first network node.

[0336] Example 4A. A method of any of the embodiments 1 to 3, wherein obtaining information includes receiving information from a wireless device.

[0337] Example 4B. The method of any of the embodiments 1 to 4A, wherein information is received in a message including a radio link failure (RLF) report and / or a random access (RA) report.

[0338] Example 5. A method of any of the embodiments 1 to 4B, wherein taking at least one action includes deleting information.

[0339] Example 6. A method of any of the embodiments 1 to 5, wherein taking at least one action includes transmitting (i.e., forwarding) information to a third network node that is currently serving a second network node.

[0340] Example 7. The method of Example 6, wherein the second network node includes an IABDU node and the third network node includes a central unit, and the second network node has been switched from the first network node to the third network node during the handover process.

[0341] Example 8. The method of any of the embodiments of Examples 6 and 7 further includes: storing the handover history of the second network node; and determining, based on the handover history, that the second network node has been switched to a third network node, wherein information is transmitted to the third network node based on the handover history indicating that the second network node has been switched to the third network node.

[0342] Example 9. A method of any of the embodiments 1 to 8, wherein taking at least one action includes: storing information; determining that a second network node has been switched to a first network node; and transmitting the information to the second network node.

[0343] Example 10. The method of Example 9, wherein a second network node is associated with a unique identifier, and wherein the method further includes: storing information as associated with a unique identifier associated with the second network node; receiving a setting message associated with a second network node switched to a first network node, the setting message including a unique identifier associated with the second network node; and determining that information is associated with the second network node based on the setting message including the unique identifier associated with the second network node; and transmitting information to the second network node in response to determining that information is associated with the second network node.

[0344] Example 11. The method of Example 9, wherein a first network node is associated with a unique identifier, and wherein the method further includes: receiving a setup message associated with a second network node switched to the first network node, the setup message including a unique identifier associated with the first network node; and determining, based on the setup message including the unique identifier associated with the first network node, that information is associated with the second network node; and transmitting information to the second network node in response to determining that information is associated with the second network node.

[0345] Example 12. A method of any of the embodiments 1 to 11, wherein taking at least one action includes transmitting information to a fourth network node operating as an Operation and Maintenance (OAM) node for forwarding to a fifth network node currently serving a second network node.

[0346] Example 13. A method of any of the embodiments 1 to 12, wherein taking at least one action includes: transmitting a request for handover information to a fourth network node operating as an OAM node; receiving handover information from the fourth network node, the handover information indicating that a second network node is being served by a fifth network node; and transmitting the information to the fifth network node.

[0347] Example 14. A method of any of the embodiments 1 to 13, wherein taking at least one action includes transmitting information to a core network node for forwarding to a fifth network node currently serving a second network node.

[0348] Example 15. A method of any of the embodiments 1 to 14, wherein taking at least one action includes: transmitting a request for handover information to a core network node; receiving handover information from the core network node, the handover information indicating that a second network node is being served by a fifth network node; and transmitting the information to the fifth network node.

[0349] Example 16. A method of any of the embodiments of Examples 14 to 15, wherein the core network node includes an Access and Mobility Management Function (AMF) and / or a Mobility Management Entity (MME).

[0350] Example 17. A method of any of the embodiments 1 to 16, wherein obtaining information related to a radio link failure or radio link recovery associated with a wireless device includes receiving information from a message from the wireless device.

[0351] Example 18. A method of any of the embodiments 1 to 16, wherein obtaining information related to a radio link failure or radio link recovery associated with a wireless device includes: receiving information from a message from a sixth network node that acts as a donor CU, which is a second network node when a radio link failure or radio link recovery associated with a wireless device occurs.

[0352] Example 19. The method of any of the embodiments 1 to 17 further includes: determining that the second network node is a mobile IAB node, and wherein at least one action is taken in response to determining that the second network node is a mobile IAB node.

[0353] Example 20. The method of Example 19, wherein determining that the second network node is a mobile IAB node includes determining that the cell is not on a list that includes at least one cell that is a neighbor of any cell controlled by the first network node.

[0354] Example 21. The method of Example 19, wherein determining that the second network node is a mobile IAB node includes determining that the cell is not on the list including at least one cell controlled by a neighboring network node operating as a CU.

[0355] Example 22. The method of Example 19, wherein determining that the second network node is a mobile IAB node includes receiving information from OAM indicating that the cell is associated with the mobile IAB node.

[0356] Example 23. The method of Example 22, wherein the information received from OAM includes a list identifying at least one cell as associated with a mobile IAB node.

[0357] Example 24. The method of any of the embodiments 22 to 23 further includes: transmitting to the OAM a request for information indicating the association of a cell with a mobile IAB node.

[0358] Example 25. A first network node, including processing circuitry configured to perform any of the steps or operations of Examples 1 to 24.

[0359] Example 26. A computer program including instructions that, when executed on a computer, perform any of the methods of Examples 1 to 24.

[0360] Example 27. A computer program product including a computer program, the computer program including instructions that, when executed on a computer, perform any of the methods of Examples 1 to 24.

[0361] Example 28. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods of Examples 1 to 24.

[0362] Group A2 Examples

[0363] Example 29. A method performed by a first network node (OAM, AMF, core network node), the method comprising: receiving information related to a radio link failure or radio link recovery associated with a radio device, the information being received from a second network node (CU3) currently serving the radio device, the information being associated with a cell of a third network node (IABB) previously serving the radio device, the third network node not being served by the second network node; and taking at least one action regarding the information.

[0364] Example 30. The method of Example 29, wherein a second network node is acting as a donor central unit (CU) of at least one IAB distributed unit (DU) node in an integrated access and radio access backhaul (IAB) network, and wherein a third network node includes an IAB node not served by the second network node.

[0365] Example 31. The method of any of the embodiments of Examples 29 to 30, wherein information is received in a message including a radio link failure (RLF) report and / or a random access (RA) report.

[0366] Example 32. A method of any of the embodiments 29 to 31, wherein taking at least one action includes transmitting information to a fourth network node that is currently serving a third network node.

[0367] Example 33. The method of any of the embodiments 29 to 32, wherein the first network node is operating as an operation and maintenance (OAM) node.

[0368] Example 34. The method of any of the embodiments 29 to 32, wherein the first network node is a core network node.

[0369] Example 35. The method of Example 34, wherein the core network node includes an Access and Mobility Management Function (AMF) and / or a Mobility Management Entity (MME).

[0370] Example 36. The method of any of the embodiments 33 to 35 further includes: receiving a request for handover information; transmitting handover information to another network node, the handover information indicating that the third network node is being served by the fourth network node.

[0371] Example 37. A method of any of the embodiments 1 to 17, wherein the third network node is a mobile IAB node, and wherein at least one action is taken in response to determining that the third network node is a mobile IAB node.

[0372] Example 38. The method of Example 37 further includes: determining that the third network node is a mobile IAB node.

[0373] Example 39. The method of Example 38, wherein determining that the third network node is a mobile IAB node includes determining that the cell is not on a list of at least one cell that is a neighbor of any cell controlled by the second network node.

[0374] Example 40. The method of Example 38, wherein determining that the third network node is a mobile IAB node includes determining that the cell is not on the list including at least one cell controlled by a neighboring network node operating as a CU.

[0375] Example 41. The method of any of the embodiments of Examples 29 to 40, wherein taking at least one action further includes transmitting information indicating that the cell is associated with the mobile IAB node to at least one other network node.

[0376] Example 42. The method of Example 41, wherein the information includes a list identifying at least one cell as associated with a mobile IAB node.

[0377] Example 43. The method of any of the embodiments 29 to 42, wherein taking at least one action further includes transmitting information to at least one other network node.

[0378] Example 44. The method of any of the embodiments of Examples 41 to 43, wherein at least one other network node includes any one or more of the following: a second network node, a third network node of a previously serving wireless device, a core network node, a DU of the currently serving wireless device, a DU of the previously serving wireless device, an IAB node of the previously serving wireless device, an IAB node of the currently serving wireless device, a CU of the previously serving wireless device, and a CU of the currently serving wireless device.

[0379] Example 45. A first network node, including processing circuitry configured to perform any step or operation of embodiments 29 to 44.

[0380] Example 46. A computer program including instructions that, when executed on a computer, perform any of the methods of Examples 29 to 44.

[0381] Example 47. A computer program product including a computer program, the computer program including instructions that, when executed on a computer, perform any of the methods of Examples 29 to 44.

[0382] Example 48. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform any of the methods of Examples 29 to 44.

[0383] Group B Implementation Examples

[0384] Example 49. A network node includes: processing circuitry configured to perform any step of any embodiment in the A1 and A2 group embodiments; and power supply circuitry configured to supply power to a wireless device.

[0385] Example 50. A communication system including a host computer, the host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a wireless device, wherein the cellular network includes network nodes having a radio interface and processing circuitry, the processing circuitry of the network nodes being configured to perform any step of any embodiment in the A1 and A2 group embodiments.

[0386] Example 51. The communication system of the previous embodiment further includes network nodes.

[0387] Example 52. The communication system of the preceding two embodiments further includes a wireless device, wherein the wireless device is configured to communicate with a network node.

[0388] Example 53. The communication system of the preceding three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, thereby providing user data; and the wireless device includes processing circuitry configured to execute a client application associated with the host application.

[0389] Example 54. A method implemented in a communication system including a host computer, a network node, and a wireless device, the method comprising: providing user data at the host computer; and initiating a transmission carrying the user data from the host computer to the wireless device via a cellular network including the network node, wherein the network node performs any step of any embodiment in the A1 and A2 group embodiments.

[0390] Example 55. The method of the previous embodiment further includes: transmitting user data at a network node.

[0391] Example 56. The method of the preceding two embodiments, wherein user data is provided at a host computer by executing a host application, the method further includes: executing a client application associated with the host application at a wireless device.

[0392] Example 57. A wireless device configured to communicate with a network node, the wireless device including processing circuitry and a radio interface configured to perform the methods of the preceding three embodiments.

[0393] Example 58. A communication system of the previous embodiment, wherein the cellular network further includes network nodes configured to communicate with wireless devices.

[0394] Example 59. The communication system of the preceding two embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing user data; and the processing circuitry of the wireless device is configured to execute a client application associated with the host application.

[0395] Example 60. A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from a wireless device to a network node, wherein the network node includes a radio interface and processing circuitry configured to perform any step of any embodiment in the A1 and A2 group embodiments.

[0396] Example 61. The communication system of the previous embodiment further includes network nodes.

[0397] Example 62. The communication system of the preceding two embodiments further includes a wireless device, wherein the wireless device is configured to communicate with a network node.

[0398] Example 63. The communication system of the preceding three embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; the wireless device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0399] Example 64. A method of any of the preceding embodiments, wherein the network node includes a base station.

[0400] Example 65. A method of any of the preceding embodiments, wherein the wireless device includes a user equipment (UE).

[0401] Modifications, additions, or omissions may be made to the systems and devices described herein without departing from the scope of this disclosure. Components of the systems and devices may be integrated or separated. Furthermore, the operation of the systems and devices may be performed by more, fewer, or other components. Additionally, the operation of the systems and devices may be performed using any suitable logic, including software, hardware, and / or other logic. As used in this document, "each" means each member of a set or each member of a subset of a set.

[0402] Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of this disclosure. The methods may include more, fewer, or other steps. Additionally, these steps may be performed in any suitable order.

[0403] Although this disclosure has been described with reference to certain embodiments, variations and substitutions of these embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments is not intended to limit this disclosure. Other changes, substitutions, and modifications are possible without departing from the spirit and scope of this disclosure.

Claims

1. A method (1400) performed by a first network node (160), the method comprising: Obtain (1402) information associated with the self-organizing network SON report associated with the wireless device (110); Determine (1404) that the information associated with the SON report is associated with a cell not served by the first network node; The cell is associated with the mobile integrated access and backhaul IAB nodes; as well as In response to determining that the information associated with the SON report is associated with a cell not served by the first network node, and determining that the cell is associated with the mobile IAB node, at least one action (1406) is taken, including: Delete the information; or The information is transmitted to the second network node. The first network node is acting as the donor central unit (CU) of at least one IAB distributed unit (DU) node in the IAB network.

2. The method of claim 1, wherein, At least one of the following: The SON report includes link failure reports; The link failure report includes a handover failure report or a radio link failure (RLF) report; and The SON report is associated with the random access procedure.

3. The method of claim 1, wherein, When the information is obtained, the second network node includes an IAB DU node that is not served by the first network node, and wherein the second network node is currently serving the cell.

4. The method of claim 3, further comprising: Store the switching history of at least one additional node in the IAB network; as well as Based on the handover history, it is determined that at least one additional network node has been switched to the second network node, and The information is transmitted to the second network node based on the switching history indicating that at least one additional network node has been switched to the second network node.

5. The method of claim 1, wherein, When the information is generated, the second network node is serving the cell.

6. The method of any one of claims 1 to 2, wherein, Obtaining the information includes receiving the information from the wireless device.

7. The method of any one of claims 1 to 2, wherein, Transmitting the information to the second network node includes: Store the information associated with the SON report; It is determined that the second network node has been switched to the first network node; and In response to determining that the second network node has been switched to the first network node, the information associated with the SON report is transmitted to the second network node.

8. The method of claim 7, wherein, The second network node is associated with a unique identifier, and the method further includes: The information is stored as an association with the unique identifier associated with the second network node; Receive a configuration message associated with the second network node that has been switched to the first network node, the configuration message including the unique identifier associated with the second network node; and Based on the setting message including the unique identifier associated with the second network node, it is determined that the information is associated with the second network node; and In response to determining that the information associated with the SON report is associated with the second network node, the information associated with the SON report is transmitted to the second network node.

9. The method of claim 7, wherein, The first network node is associated with a unique identifier, and the method further includes: Receive a configuration message associated with the second network node that has been switched to the first network node, the configuration message including the unique identifier associated with the first network node; and Based on the setting message including the unique identifier associated with the first network node, it is determined that the information is associated with the second network node; and In response to determining that the information is associated with the second network node, the information associated with the SON report is transmitted to the second network node.

10. The method of any one of claims 1 to 2, wherein, Transmitting the information to the second network node includes transmitting the information to the operation and maintenance OAM node for forwarding to the third network node currently serving the cell.

11. The method of any one of claims 1 to 2, wherein, Transmitting the information to the second network node includes: Send a request for handover information to the OAM node or core network node; Receive the handover information from the OAM node or the core network node, the handover information indicating that the cell is being served by a second network node; and The information associated with the SON report is transmitted to the second network node.

12. The method of any one of claims 1 to 2, wherein, Transmitting the information associated with the SON report to the second network node includes transmitting the information associated with the SON report to the core network node for forwarding to at least one additional network.

13. The method of claim 1, wherein, Determining that the cell is associated with the mobile IAB node includes determining that the cell is not on a list that includes at least one cell controlled by a neighboring network node operating as a CU.

14. The method of claim 1, wherein, Determining the association between the cell and the mobile IAB node includes receiving information from the OAM node indicating that the cell is associated with the mobile IAB node.

15. A first network node (160), comprising: Processing circuit (170), the processing circuit (170) being configured to: Obtain information associated with the self-organizing network SON report associated with the wireless device (110); The information associated with the SON report is determined to be associated with a cell not served by the first network node; The cell is associated with the mobile integrated access and backhaul IAB nodes; as well as In response to determining that the information associated with the SON report is associated with a cell not served by the first network node, and determining that the cell is associated with the mobile IAB node, at least one action is taken, including: Delete the information; or The information is transmitted to the second network node. The first network node is acting as the donor central unit (CU) of at least one IAB distributed unit (DU) node in the IAB network.

16. The first network node as described in claim 15, wherein, At least one of the following: The SON report includes link failure reports; The link failure report includes a handover failure report or a radio link failure (RLF) report; and The SON report is associated with the random access procedure.

17. The first network node as described in claim 15, wherein, When the information is obtained, the second network node includes an IAB DU node that is not served by the first network node, and wherein the second network node is currently serving the cell.

18. The first network node as claimed in claim 17, wherein, The processing circuit is configured to: Store the handover history of at least one additional node in the IAB network; and Based on the handover history, it is determined that at least one additional network node has been switched to the second network node, and The information is transmitted to the second network node based on the switching history indicating that at least one additional network node has been switched to the second network node.

19. The first network node as described in claim 15, wherein, When the information is generated, the second network node is serving the cell.

20. The first network node as described in any one of claims 15 to 16, wherein, Obtaining the information includes receiving the information from the wireless device.

21. The first network node as described in any one of claims 15 to 16, wherein, When the information is transmitted to the second network node, the processing circuit is configured to: Store the information associated with the SON report; It has been determined that the second network node has been switched to the first network node; as well as In response to determining that the second network node has been switched to the first network node, the information associated with the SON report is transmitted to the second network node.

22. The first network node as described in claim 21, wherein, The second network node is associated with a unique identifier, and the processing circuit is configured to: The information is stored as an association with the unique identifier associated with the second network node; Receive a configuration message associated with the second network node that has been switched to the first network node, the configuration message including the unique identifier associated with the second network node; and Based on the setting message including the unique identifier associated with the second network node, it is determined that the information is associated with the second network node; and In response to determining that the information associated with the SON report is associated with the second network node, the information associated with the SON report is transmitted to the second network node.

23. The first network node as described in claim 21, wherein, The first network node is associated with a unique identifier, and the processing circuit is configured to: Receive a configuration message associated with the second network node that has been switched to the first network node, the configuration message including the unique identifier associated with the first network node; and Based on the setting message including the unique identifier associated with the first network node, it is determined that the information is associated with the second network node; and In response to determining that the information is associated with the second network node, the information associated with the SON report is transmitted to the second network node.

24. The first network node as described in any one of claims 15 to 16, wherein, When the information is transmitted to the second network node, the processing circuitry is configured to transmit the information to the Operation and Maintenance (OAM) node for forwarding to the third network node currently serving the cell.

25. The first network node as described in any one of claims 15 to 16, wherein, When the information is transmitted to the second network node, the processing circuit is configured to: Send a request for handover information to the OAM node or core network node; The handover information is received from the OAM node or the core network node, the handover information indicating that the cell is being served by a second network node; as well as The information associated with the SON report is transmitted to the second network node.

26. The first network node as described in any one of claims 15 to 16, wherein, When the information associated with the SON report is transmitted to the second network node, the processing circuitry is configured to transmit the information associated with the SON report to the core network node for forwarding to at least one additional network.

27. The first network node as described in claim 15, wherein, When it is determined that the cell is associated with the mobile IAB node, the processing circuitry is configured to determine that the cell is not on a list that includes at least one cell controlled by a neighboring network node operating as a CU.

28. The first network node as described in claim 15, wherein, When it is determined that the cell is associated with the mobile IAB node, the processing circuit is configured to receive information from the OAM node indicating that the cell is associated with the mobile IAB node.

Images