WO2021019332A1 - Iab-donor cu aware remapping of bearers in iab network - Google Patents

Abstract

A method of operating an integrated access and backhaul, IAB, node in a wireless communication network is provided, wherein the IAB node includes a distributed unit, DU, for a control unit, CU, in the wireless communication network. The method includes performing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU, preparing a remapping/rerouting report describing the remapping or rerouting of the radio bearer, and transmitting the remapping/rerouting report to the CU.

Description

IAB-DONOR CU AWARE REMAPPING OF BEARERS IN IAB N ETWORK

RELATED APPLICATION

[0001] The present application claims the benefit of and priority to U.S. Provisional Patent Application No. 62/880,176, filed July 30, 2019, entitled "IAB-DONOR CU AWARE REMAPPING OF BEARERS IN IAB N ETWORK," the disclosure of which is hereby incorporated herein by reference in its entirety.

TECHN ICAL FIELD

[0002] The inventive concepts relate to wireless communication networks, and more particularly to operations of integrated access and backhaul nodes in wireless communication networks.

BACKGROU ND

[0003] 3GPP is currently standardizing integrated access and wireless access backhaul (IAB) in the New Radio (N R) standardization process. The use of short range millimeter-wave (mmWave) spectrum in N R creates a need for densified deployment with multi-hop backhauling. However, installing optical fiber to every base station will be too costly and sometimes not even possible. The main principle of IAB is to use wireless links for the backhaul (instead of fiber) to enable flexible and very dense deployment of cells without the need for densifying the transport network. Use case scenarios for IAB can include coverage extension, deployment of massive number of small cells, and fixed wireless access (FWA) (e.g. to residential/office buildings). The larger bandwidth available for N R in mmWave spectrum provides opportunity for self-backhauling, without limiting the spectrum to be used for the access links. On top of that, the inherent multi-beam and M IMO support in N R reduce cross-link interference between backhaul and access links allowing higher densification.

[0004] During the study item phase of the IAB work, it has been agreed to adopt a solution that leverages the Central Unit (CU)/Distributed Unit (DU) split architecture of N R, where the IAB node will be hosting a DU part that is controlled by a central unit. The IAB nodes also have a Mobile Termination (MT) part that they use to communicate with their parent nodes. [0005] The specifications for IAB strive to reuse existing functions and interfaces defined in NR, such as MT, gNB-DU, gNB-CU, UPF, AMF and SMF as well as the corresponding interfaces NR Uu (between MT and gNB), FI, NG, X2 and N4 are used as baseline for the IAB architectures.

[0006] The Mobile-Termination (MT) function has been defined as a component of the IAB node. MT is a function residing on an IAB-node that terminates the radio interface layers of the backhaul Uu interface toward the IAB-donor or other IAB-nodes.

[0007] Figure 1 shows a reference diagram for IAB in standalone mode, which contains one IAB-donor and multiple IAB-nodes. The IAB-donor is treated as a single logical node that comprises a set of functions such as gNB-DU, gNB-CU-CP, gNB-CU-UP and potentially other functions. In a deployment, the IAB-donor can be split according to these functions, which can all be either collocated or non- collocated as allowed by 3GPP NG-RAN architecture. IAB-related aspects may arise when such split is exercised. Also, some of the functions presently associated with the IAB-donor may eventually be moved outside of the donor in case it becomes evident that they do not perform IAB-specific tasks.

[0008] The baseline user plane and control plane protocol stacks for IAB are shown in Figures 2 and 3.

[0009] As illustrated in Figures 1 to 3, the chosen protocol stacks reuse the current CU-DU split specification in rel-15, where the full user plane Fl-U (GTP-U/UDP/IP) is terminated at the IAB node (like a normal DU) and the full control plane Fl-C (Fl-AP/SCTP/IP) is also terminated at the IAB node (like a normal DU). In the above cases, Network Domain Security (NDS) has been employed to protect both UP and CP traffic (IPsec in the case of UP, and DTLS in the case of CP). IPsec could also be used for the CP protection instead of DTLS (in this case no DTLS layer would be used).

[0010] A new protocol layer called Backhaul Adaptation Protocol (BAP) has been introduced in the IAB nodes and the IAB-donor, which is used for routing of packets to the appropriate

downstream/upstream node and also mapping the UE bearer data to the proper backhaul RLC channel (and also between ingress and egress backhaul RLC channels in intermediate IAB nodes) to satisfy the end to end QoS requirements of bearers.

[0011] The UE establishes RLC channels to the DU on the UE's access IAB-node in compliance with TS 38.300. Each of these RLC-channels is extended via Fl-U between the UE's access DU and the IAB-donor. The information embedded in Fl-U is carried over backhaul RLC-channels across the backhaul links. Transport of Fl-U over the wireless backhaul will be performed by the BAP. Since BAP is a newly defined layer for IAB networks, hence, 3GPP has made only the following agreements related to the BAP layer functionality: RAN2 confirms that routing and bearer mapping (e.g. mapping of BH RLC channels) are BAP layer functions.

RAN2 assumes that the TX part of the BAP layer performs routing and "bearer mapping", and the RX part of the BAP layer performs "bearer de-mapping".

RAN2 assumes that SDUs are forwarded from the RX part of the BAP layer to the TX part of the BAP layer (for the next hop) for packets that are relayed by the IAB node.

It is for future study how to model BAP layer protocol entities, e.g. whether separate for DU and MT or not, and how these are configured, i.e. via Fl-AP or RRC.

[0012] Furthermore, for the BAP routing, 3GPP made the following agreements:

The BAP routing id (carried in the BAP header) consists of BAP address and BAP path ID. Encoding of the path ID in the header is for future study.

Each BAP address defines a unique destination (unique for IAB network of one donor- IAB, either an IAB access node, or the IAB donor).

Each BAP address can have one or multiple entries in the routing table to enable local route selection. Multiple entries are for load balancing and rerouting in the event of radio link failure (RLF). For load balancing, it is for future study to determine what is decided locally and/or decided by the Donor.

Each BAP routing id has only one entry in the routing table.

The routing table can hold other information, such as priority level for entries with same BAP address, to support local selection. Configuration of this information is optional.

Load balancing by routing by donor-IAB CU shall be possible.

Local selection of path/route is done at link failure, other cases are for future study.

[0013] UE-bearer to BH-RLC-Channel mapping

[0014] An IAB-node needs to multiplex the UE DRBs to the BH RLC-Channel. The following two options can be considered with respect to bearer mapping in IAB-node.

[0015] Option 1. One-to-one (1:1) mapping between UE DRB and BH RLC-channel

[0016] In this option (illustrated in Figure 4), each UE DRB is mapped onto a separate BH RLC- channel. Further, each BH RLC-channel is mapped onto a separate BH RLC-channel on the next hop. The number of established BH RLC-channels is equal to the number of established UE DRBs.

[0017] Identifiers (e.g. for the UE and/or DRB) may be required (e.g. if multiple BH RLC- channels are multiplexed into a single BH logical channel). Which exact identifiers are needed, and which of these identifier(s) are placed within the adaptation layer header depends on the architecture/protocol option.

[0018] Option 2. Many-to-one (N:l) mapping between UE DRBs and BH RLC-channel

[0019] For the many-to-one mapping scenario (illustrated in Figure 5), several UE DRBs are multiplexed onto a single BH RLC-channel based on specific parameters such as bearer QoS profile. Other information, such as hop-count could also be configured. The IAB-node can multiplex UE DRBs into a single BH RLC-channel even if they belong to different UEs. Furthermore, a packet from one BH RLC-channel may be mapped onto a different BH RLC-channel on the next hop. All traffic mapped to a single BH RLC-channel receive the same QoS treatment on the air interface.

[0020] Since the BH RLC-channel multiplexes data from/to multiple bearers, and possibly even different UEs, each data block transmitted in the BH RLC-channel needs to contain an identifier of the UE, DRB, and/or IAB-node it is associated with. Which exact identifiers are needed, and which of these identifier(s) are placed within the adaptation layer header depends on the architecture/protocol option.

SUMMARY

[0021] Some embodiments provide a method of operating an integrated access and backhaul, IAB, node in a wireless communication network, wherein the IAB node includes a distributed unit, DU, for a control unit, CU, in the wireless communication network. The method includes performing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU, preparing a remapping/rerouting report describing the remapping or rerouting of the radio bearer, and transmitting the remapping/rerouting report to the CU.

[0022] The method may further include establishing the backhaul link to the CU, and mapping the radio bearer to a backhaul channel on the backhaul link. Performing the local remapping or rerouting of the radio bearer may include rerouting the radio bearer over a different backhaul link.

[0023] The method may further include establishing the backhaul link to the CU, and mapping the radio bearer to a backhaul channel on the backhaul link. Performing the local remapping or rerouting of the radio bearer may include remapping the radio bearer to a different backhaul channel on the backhaul link.

[0024] In some embodiments, any remapping/rerouting triggers preparation and transmission of the remapping/rerouting report. [0025] In some embodiments, only remapping/rerouting of 1:1 mapped bearers triggers preparation and transmission of the remapping/rerouting report.

[0026] The method may further include receiving information during setup of a radio bearer or backhaul channel setup indicating whether rerouting or remapping of the radio bearer or backhaul channel will trigger a remapping/rerouting report.

[0027] The IAB node may be configured to trigger generation of the remapping/rerouting report in response to rerouting or remapping of a radio bearer or backhaul channel. In some embodiments, the IAB node may be configured to trigger generation of the remapping/rerouting report in response to detecting a quality degradation of the remapped/rerouted bearer.

[0028] In some embodiments, the quality degradation is detected in response to an increase buffering for re-mapped traffic. In some embodiments, the rerouting/remapping is performed in the downlink direction, and the remapping/rerouting report is sent to the CU via Fl-AP signaling. In some embodiments, the rerouting/remapping is performed in the uplink direction, and the

remapping/rerouting report is sent to the CU via RRC signaling or via Fl-AP signaling.

[0029] In some embodiments, the remapping/rerouting report includes rerouting information including identification of a previous link and a new link involved in the rerouting. In some

embodiments, the remapping/rerouting report includes remapping information including identification of a previous backhaul channel and a new backhaul channel involved in the rerouting.

[0030] In some embodiments, the remapping/rerouting report includes a cause value for the rerouting/remapping. In some embodiments, the remapping/rerouting report includes information about remapping/rerouting on a per backhaul channel basis.

[0031] Some embodiments provide a method of operating a control unit, CU, that is connected by a backhaul link in a wireless communication network to an integrated access and backhaul, IAB, node, wherein the IAB node includes a distributed unit, DU, controlled by the CU. The method includes receiving a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU, and configuring a dedicated backhaul channel for the radio bearer.

[0032] The method may further include transmitting a notification message to the DU informing it of the dedicated backhaul channel.

[0033] Some embodiments provide a method of operating a control unit, CU, that is connected by a backhaul link in a wireless communication network to an integrated access and backhaul, IAB, node, wherein the IAB node includes a distributed unit, DU, controlled by the CU. The method includes configuring a backup backhaul channel, receiving a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU, and in response to the remapping/rerouting report, remapping the radio bearer to the backup backhaul channel.

[0034] Prior to remapping, the radio bearer may be mapped to backhaul channel via a 1:1 mapping, and the radio bearer may be remapped to the backup backhaul channel via a 1:1 mapping.

[0035] The method may further include configuring backup backhaul channels on all possible paths between the DU and the CU. The method may further include configuring backup backhaul channels on a subset of possible paths between the DU and the CU.

[0036] A network node according to some embodiments includes a processor circuit, a network interface coupled to the processor circuit, and a memory coupled to the processor circuit. The memory includes machine readable program instructions that, when executed by the processor circuit, cause the UE to perform operations including performing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between an IAB node and a CU, preparing a remapping/rerouting report describing the remapping or rerouting of the radio bearer, and transmitting the remapping/rerouting report to the CU

[0037] A wireless communication system according to some embodiments includes a control unit, CU, and an integrated access and backhaul, IAB, wherein the IAB node includes a distributed unit, DU, for the CU, in the wireless communication system. The IAB node is configured to perform operations including performing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU, preparing a remapping/rerouting report describing the remapping or rerouting of the radio bearer, and transmitting the remapping/rerouting report to the CU.

[0038] The CU may be configured to perform operations including configuring a backup backhaul channel, receiving a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU, and in response to the remapping/rerouting report, remapping the radio bearer to the backup backhaul channel.

[0039] Some embodiments described herein may help to ensure that the IAB donor CU becomes aware of local rerouting/remapping decisions at IAB nodes through rerouting/remapping notification reports. These reports may enable a donor CU to know the actual state of the network (i.e., the route/path that each bearer is going through and what kind of bearer mapping is performed, which indicates the QoS handling/treatment the packets of each bearer is getting), which allows the CU to take appropriate actions, such as establishing new backhaul channels on some of the links, to ensure that the UE bearers are receiving desired QoS handling throughout the IAB network.

BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 is a block diagram illustrating a reference diagram for IAB-architectures.

[0041] Figure 2 is a block diagram illustrating a baseline User Plane (UP) Protocol stack for IAB in rel-16.

[0042] Figure 3 is a block diagram illustrating a baseline control plane (CP) Protocol stack for IAB in rel-16.

[0043] Figure 4 is a block diagram illustrating an example of one-to-one mapping between UE DRB and BH RLC-Channel.

[0044] Figure 5 is a block diagram illustrating an example of many-to-one mapping between UE DRBs and BH RLC-channel.

[0045] Figure 6 is a block diagram illustrating an example of IAB network with both N:1 and 1:1 mapping between UE DRBs and BH RLC-channels.

[0046] Figure 7 is a block diagram illustrating an example of IAB network without extra/backup backhaul RLC channel(s).

[0047] Figure 8 is a flowchart illustrating operations according to some embodiments of the inventive concepts.

[0048] Figure 9 is a block diagram illustrating an example of IAB network with extra/backup backhaul RLC channel(s).

[0049] Figure 10 is a flowchart illustrating operations according to some embodiments of the inventive concepts.

[0050] Figure 11 is a block diagram illustrating an example of a network node according to embodiments of the inventive concepts.

[0051] Figure 12 is a block diagram of a wireless network in accordance with some embodiments.

[0052] Figure 13 is a block diagram of a user equipment in accordance with some

embodiments. [0053] Figure 14 is a block diagram of a virtualization environment in accordance with some embodiments.

DETAILED DESCRIPTION

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

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

[0056] As agreed by 3GPP, the Backhaul Adaptation Protocol (BAP) of an intermediate IAB- node can reroute the traffic locally (i.e., by itself) under certain conditions such as a backhaul radio link failure (RLF), load balancing etc. However, what is agreed upon so far is regarding the routing aspect and not the bearer mapping. It is not clear on what the IAB node will do if there is a bearer that was mapped to a backhaul (BH) radio link control (RLC) channel (e.g. LCIDx) and a similar BH RLC channel with the same LCID is not available on the new route. This is especially important in the case of bearers that are mapped 1:1, as they require a dedicated BH RLC channel on all the hops, and there will not be a dedicated BH RLC channel on the new route for that bearer.

[0057] For example, in the IAB network shown in Figure 6, some of the UE bearers, e.g., a bearer for UE1 served by IAB9 are mapped in 1:1 manner (i.e., over a dedicated BH RLC channel) to BH RLC channel 1 on all the links of its path with IAB-donor (i.e., path IAB-donor-IABl-IAB2-IAB5-IAB8-IAB9) while UE bearers for UE2 and UE3 are mapped N:1 to BH RLC channel 2 over the same path. Similarly, the UE bearers for UE4 and UE5 connected to IAB10 are mapped N:1 to BH RLC channel 3 and 4, respectively, on all the links of its path with the IAB-donor (i.e., path IAB-donor-IABl-IAB3-IAB5-IAB8- IAB10). UE bearers for UE6 connected to IAB10 are mapped N:1 over BH RLC channel 5 on another path with the IAB-donor ((i.e., path IAB-donor-IABl-IAB4-IAB6-IAB8-IAB10). Finally, the UE bearers for UE7 and UE8 connected to IAB7 are mapped N:1 to BH RLC channel 6 on all the links of its path with the IAB- donor (i.e., path IAB-donor-IABl-IAB4-IAB6-IAB7).

[0058] For the scenario in Figure 6, suppose that at some point IAB1 detects RLF or heavy congestion on the link towards IAB2 and decides to route the traffic previously routed via IAB2 to IAB3. Assume also that traffic that was previously mapped 1:1 to BH RLC channel 1 gets mapped to BH RLC channel 3, and traffic that was previously mapped N:1 to BH RLC channel 2 gets mapped to BH RLC channel 4. However, if the two new paths for the traffic that was previously mapped to BH RLC channel 1 (i.e. BH RLC channel 3 between IAB1 and IAB3, and between IAB3 and IAB5) are multiplexing traffic from many bearers, the QoS of the rerouted/remapped bearer could be heavily impacted. Additionally, since the donor CU no longer has the correct information about all the traffic that is mapped on BH RLC channel 3 between IAB1 and IAB3 and between IAB 3 and IAB5, it could map newly established bearers to these BH RLC channels, further exacerbating the problem, not only to the traffic that was previously mapped to BH RLC channel 1, but also all bearers that are now sharing the BH RLC channel 3 between IAB1 and IAB3, and between IAB3 and IAB5.

[0059] Some embodiments described herein provide mechanisms that address these and other problems that can arise when local decisions relating to rerouting and/or remapping of the backhaul RLC channels are made by the IAB nodes.

[0060] Some embodiments described herein address the repercussion of local decisions, such as BH RLC channel remapping made by an IAB node during RLF or link congestion, etc., by providing methods at an IAB node to notify the IAB-donor CU about the local decision (remapping and/or rerouting of BH RLC channel, etc.). This will enable the donor CU to know the actual state of the network (i.e., the route/path that each bearer is going through and what kind of bearer mapping is performed, which indicates the QoS handling/treatment the packets of each bearer is getting) and hence can take appropriate actions, such as establishing new backhaul channels on some of the links, to ensure that the UE bearers are receiving the desired QoS handling throughout the IAB network.

[0061] Methods are also proposed to establish reserve/backup BH RLC channels by the IAB- donor CU on an alternative path, which are not active/used initially, but become active/used on an as- needed basis (e.g., when rerouting/remapping of traffic from one link to another link).

[0062] Some embodiments described herein may help to ensure that the IAB donor CU becomes aware of local rerouting/remapping decisions at IAB nodes through rerouting/remapping notification reports. Upon the reception of these reports, the IAB donor CU can take appropriate actions to ensure the QoS requirements of the UE bearers be maintained even after the rerouting/remapping (e.g. by establishing new backhaul channels on the new path).

[0063] The terms "backhaul RLC channel" and "backhaul bearer" are used interchangeably herein. The term "IAB-donor CU" and "donor CU" are also used interchangeably herein. While embodiments are described herein in the context of the downlink (DL) case, it will be appreciated that the methods described herein are applicable also to the uplink (UL) case.

[0064] In following description, it is assumed that rerouting followed by remapping occurs due to backhaul RLF failure, load balancing, etc. However, it will be appreciated that embodiments described herein can be applicable to scenarios in which there is no rerouting involved and/or if the IAB node performs rerouting without remapping, or remapping without rerouting.

[0065] Embodiments are described herein for the scenarios shown in Figure 7 and Figure 9.

And for the sake of brevity, it is assumed that each UE has only one bearer.

[0066] For both topology examples shown in Figure 7, the bearers are mapped in the following way:

[0067] - UEl's bearer that is served by IAB9 is mapped 1:1 to BH RLC channel 1 on all the links.

[0068] - The bearers of UE2 and UE3 that are served by IAB9 are mapped N:1 to BH RLC channel 2 on all the links.

[0069] - The bearers of UE4 and UE5 that are served by IAB10 are mapped N:1 to BH RLC channel 3 on all the links.

[0070] - The bearers of UE6 and UE7 that are served by IAB10 are mapped N:1 to BH RLC channel 4 on all the links.

[0071] - The bearers of UE8 and UE9 that are served by IAB8 are mapped N:1 to BH RLC channel 5 on all the links.

[0072] - The bearers of UE10, UE11, and UE12 that are served by IAB7 are mapped N:1 to BH RLC channel 6 on all the links.

[0073] In a first embodiment, whenever an IAB node performs a local remapping and/or rerouting decisions, the IAB node informs the donor CU about the decision. This report may be referred to as a "Rerouting/Remapping notification report". There can be several alternatives regarding this report. For example, in some embodiments, any remapping/rerouting may trigger the reporting. In other embodiments, only remapping/rerouting of 1:1 mapped bearers triggers the reporting. In some embodiments, information can be provided, during bearer or BH RLC channel setup, that indicates whether a remapping of the bearer or BH RLC channel will trigger a remapping/rerouting report. In some embodiments, an IAB node can be configured to trigger such a reporting or not. For example, an IAB node can be configured to trigger such a reporting only if it detects quality degradation of the remapped bearers (e.g. the buffering for a remapped traffic increases by a certain amount, percentage, etc. as compared to how it was before the remapping was performed).

[0074] In some embodiments, if the rerouting/remapping is performed in the DL, the remapping/rerouting notification report may be sent to the IAB-donor CU via Fl-AP signaling (i.e., from the IAB DU to IAB-donor CU). In other embodiments, the remapping/rerouting notification report can be sent via RRC signaling (e.g., from the IAB MT to the IAB-donor CU).

[0075] In some embodiments, if the rerouting/remapping is performed in the UL, the remapping/rerouting notification report may be sent to the IAB-donor CU via RRC signaling (i.e. from the IAB MT to IAB-donor CU). In other embodiments, the remapping/rerouting notification report may be sent to the IAB-donor CU via Fl-AP signaling (i.e. from the IAB DU to IAB-donor CU).

[0076] The Fl-AP message used to communicate the notification report can be an existing Fl- AP message enhanced with new lEs (e.g. gNB-CU configuration update, UE Context Modification Required, etc.), or a new message introduced for this purpose.

[0077] Similarly, the RRC message used to communicate the notification report can be an existing RRC message enhanced with new lEs (e.g. UEAssistancelnformation), or a new message introduced for this purpose.

[0078] The notification report could contain information such as information about rerouting (e.g. identification of the previous link and the new link), information about remapping (e.g.

identification of the previous BH RLC channel and the new BH RLC channel), and/or a cause value for rerouting/remapping (e.g., a valuer indicating BH RLF, load balancing, etc.).

[0079] The information about rerouting and remapping can be provided on a per BH RLC channel basis, or it can be one common information. For example, if there was only N:1 mapping in the previous link, and there was a corresponding BH RLC channel for each of them in the new link, only the change of the route can be informed, e.g., link 1 to Iink2, without the need to explicitly communicate the remapping.

[0080] The notification can be sent to IAB-donor CU by adding new lEs or modifying some lEs in existing Fl-AP messages. Upon receiving the notification report, will be up to IAB-donor CU whether or not to configure a dedicated backhaul RLC channel for the 1:1 bearer remapped to N:1 bearer. Also, the IAB-donor CU may decide to keep the remapped N:1 traffic on an exist BH RLC channel or establish a new BH bearer (for the remapped N:1 traffic) on the rerouted path. In addition, at some later point, if the issue that caused the radio link failure or congestion problem is solved, and IAB node remaps the UEs traffic back to original backhaul RLC channel(s), the IAB node may again send a notification message to IAB-donor CU informing it of the new status of the backhaul RLC channels.

[0081] Figure 8 is a flowchart illustrating operations according to some embodiments. As illustrated therein, a method of operating an integrated access and backhaul, IAB, node in a wireless communication network, wherein the IAB node comprises a distributed unit, DU, for a control unit, CU, in the wireless communication network, is provided. The method includes performing (802) a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU. In response to the remapping or rerouting, the IAB node prepares (804) a remapping/rerouting report describing the remapping or rerouting of the radio bearer, and transmits (806) the remapping/rerouting report to the CU.

[0082] In a second embodiment, one or more reserve backhaul RLC channels may be established by the CU that are not used initially, but are activated when a rerouting/remapping happens. This is illustrated in Figure 9, where the IAB-donor CU has preconfigured a backup dedicated (i.e., 1:1) backhaul RLC channel for UE1 traffic on the alternative path via IAB3. As the IAB-donor CU knows all the alternative paths from one IAB node, it can configure reserve BH RLC channels on each alternative path for some/all of the 1:1 mapped bearer (e.g. the bearers with the strictest QoS requirements). In some embodiments, reserve BH RLC channels can be established on all the possible links for that bearer to traverse. In other embodiments, reserve BH RLC channels can be only on a subset of the links (for instance, links IAB1-IAB3 and IAB3-IAB5 for UE1 traffic).

[0083] For the example shown in Figure 9, when IAB1 decides to reroute the traffic (that was previously routed towards IAB2) to IAB3, it can map the traffic of BH RLC channel 1 to the reserve BH RLC channel between IAB1 and IAB3 (shown in dotted lines). In some embodiments, if there is a reserve BH channel and remapping is done towards it, a remapping report may not be triggered. In

embodiments, a remapping/rerouting report may be triggered regardless of the availability of a reserve BH RLC channel or not.

[0084] It will be appreciated that the different embodiments described herein could be combined. For example, a rerouting/remapping notification report can be triggered even in the case where backup/reserve BH RLC channels are available.

[0085] Figure 10 is a flowchart illustrating operations according to some embodiments. As illustrated therein, a method of operating a CU that is connected by a backhaul link in a wireless communication network to an IAB node is provided, wherein the IAB node includes a DU controlled by the CU. The method includes configuring a backup backhaul channel (1002), receiving (1004) a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU, and, in response to the remapping/rerouting report, remapping (1006) the radio bearer to the backup backhaul channel.

[0086] Figure 11 is a block diagram illustrating elements of a network node 1100 of a communication system. The network node 1100 may implement a RAN node and/or a CN node in the communication system. For example, a network node 1100 may implement a CU, DU, IAB node or gNodeB or other network node in a wireless communication network.

[0087] As shown, the network node may include a network interface circuit 1107 (also referred to as a network interface) configured to provide communications with other nodes (e.g., with other base stations, RAN nodes and/or core network nodes) of the communication network. The network node 1100 may also include a wireless transceiver circuit 1102 for providing a wireless communication interface with UEs. The network node 1100 may also include a processor circuit 1103 (also referred to as a processor) coupled to the transceiver circuit 1102 and the network interface 1107, and a memory circuit 1105 (also referred to as memory) coupled to the processor circuit. The memory circuit 1105 may include computer readable program code that when executed by the processor circuit 1103 causes the processor circuit to perform operations according to embodiments disclosed herein. According to other embodiments, processor circuit 1103 may be defined to include memory so that a separate memory circuit is not required.

[0088] As discussed herein, operations of the network node may be performed by processor 1103, the wireless transceiver circuit 1102 and/or the network interface 1107. For example, the processor 1103 may control the network interface 1107 to transmit communications through network interface 1107 to one or more other network nodes and/or to receive communications through network interface from one or more other network nodes. Moreover, modules may be stored in memory 1105, and these modules may provide instructions so that when instructions of a module are executed by processor 1103, processor 1103 performs respective operations (e.g., operations discussed herein with respect to Example Embodiments).

[0089] Example Embodiments: [0090] Embodiment 1. A method of operating an integrated access and backhaul, IAB, node in a wireless communication network, wherein the IAB node comprises a distributed unit, DU, for a control unit, CU, in the wireless communication network, the method comprising: performing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; preparing a remapping/rerouting report describing the remapping or rerouting of the radio bearer; and transmitting the remapping/rerouting report to the CU.

[0091] Embodiment 2. The method of Embodiment 1, further comprising: establishing the backhaul link to the CU; and mapping the radio bearer to a backhaul channel on the backhaul link; wherein performing the local remapping or rerouting of the radio bearer comprises rerouting the radio bearer over a different backhaul link.

[0092] Embodiment 3. The method of Embodiment 1, further comprising: establishing the backhaul link to the CU; and mapping the radio bearer to a backhaul channel on the backhaul link; wherein performing the local remapping or rerouting of the radio bearer comprises remapping the radio bearer to a different backhaul channel on the backhaul link.

[0093] Embodiment 4. The method of Embodiment 1, wherein any remapping/rerouting triggers preparation and transmission of the remapping/rerouting report.

[0094] Embodiment 5. The method of Embodiment 1, wherein only remapping/rerouting of 1:1 mapped bearers triggers preparation and transmission of the remapping/rerouting report. [0095] Embodiment 6. The method of Embodiment 1, further comprising receiving information during setup of a radio bearer or backhaul channel setup indicating whether rerouting or remapping of the radio bearer or backhaul channel will trigger a remapping/rerouting report.

[0096] Embodiment 7. The method of Embodiment 1, wherein the IAB node is configured to trigger generation of the remapping/rerouting report in response to rerouting or remapping of a radio bearer or backhaul channel.

[0097] Embodiment 8. The method of Embodiment 7, wherein the IAB node is configured to trigger generation of the remapping/rerouting report in response to detecting a quality degradation of the remapped/rerouted bearer.

[0098] Embodiment 9. The method of Embodiment 8, wherein the quality degradation is detected in response to an increase buffering for re-mapped traffic.

[0099] Embodiment 10. The method of Embodiment 1, wherein the

rerouting/remapping is performed in the downlink direction, and the remapping/rerouting report is sent to the CU via Fl-AP signaling.

[0100] Embodiment 11. The method of Embodiment 1, wherein the

rerouting/remapping is performed in the uplink direction, and the remapping/rerouting report is sent to the CU via RRC signaling or via Fl-AP signaling.

[0101] Embodiment 12. The method of Embodiment 1, wherein the

remapping/rerouting report comprises rerouting information including identification of a previous link and a new link involved in the rerouting.

[0102] Embodiment 13. The method of Embodiment 1, wherein the

remapping/rerouting report comprises remapping information including identification of a previous backhaul channel and a new backhaul channel involved in the rerouting.

[0103] Embodiment 14. The method of Embodiment 1, wherein the

remapping/rerouting report comprises a cause value for the rerouting/remapping.

[0104] Embodiment 15. The method of Embodiment 1, wherein the

remapping/rerouting report comprises information about remapping/rerouting on a per backhaul channel basis.

[0105] Embodiment 16. A method of operating a control unit, CU, that is connected by a backhaul link in a wireless communication network to an integrated access and backhaul, IAB, node, wherein the IAB node comprises a distributed unit, DU, controlled by the CU, the method comprising: receiving a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; and configuring a dedicated backhaul channel for the radio bearer.

[0106] Embodiment 17. The method of Embodiment 16, further comprising transmitting a notification message to the DU informing it of the dedicated backhaul channel.

[0107] Embodiment 18. A method of operating a control unit, CU, that is connected by a backhaul link in a wireless communication network to an integrated access and backhaul, IAB, node, wherein the IAB node comprises a distributed unit, DU, controlled by the CU, the method comprising: configuring a backup backhaul channel; receiving a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; and in response to the remapping/rerouting report, remapping the radio bearer to the backup backhaul channel.

[0108] Embodiment 19. The method of Embodiment 18, wherein, prior to remapping, the radio bearer is mapped to backhaul channel via a 1:1 mapping, and wherein the radio bearer is remapped to the backup backhaul channel via a 1:1 mapping.

[0109] Embodiment 20. The method of Embodiment 18, further comprising: configuring backup backhaul channels on all possible paths between the DU and the CU.

[0110] Embodiment 21. The method of Embodiment 18, further comprising: configuring backup backhaul channels on a subset of possible paths between the DU and the CU.

[0111] Embodiment 22. A network node (1100), comprising: a processor circuit (1103);

a network interface (1107) coupled to the processor circuit; and

a memory (1105) coupled to the processor circuit, the memory comprising machine readable program instructions that, when executed by the processor circuit, cause the UE to perform operations comprising operations according to any of Embodiments 1 to 21.

[0112] Embodiment 23. A wireless communication system, comprising: a control unit, CU; and

an integrated access and backhaul, IAB, wherein the IAB node comprises a distributed unit, DU, for the CU, in the wireless communication system, wherein the IAB node is configured to perform operations comprising:

performing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU;

preparing a remapping/rerouting report describing the remapping or rerouting of the radio bearer; and

transmitting the remapping/rerouting report to the CU.

[0113] Embodiment 24. The wireless communication system of Embodiment 23, wherein the CU is configured to perform operations comprising: configuring a backup backhaul channel; receiving a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; and in response to the remapping/rerouting report, remapping the radio bearer to the backup backhaul channel.

[0092] Explanations are provided below for abbreviations that are mentioned in the present disclosure. Abbreviation Explanation 5GC 5G Core Network

5GS 5G System

AMF Access and Mobility Management Function

DC Dual Connectivity

eNB E-UTRAN NodeB

EN-DC E-UTRA-NR Dual Connectivity

E-UTRA Evolved Universal Mobile Terrestrial Radio Access

E-UTRAN Evolved Universal Mobile Terrestrial Radio Access Network

EPC Evolved Packet Core

EPS Evolved Packet System

HO Flandover

LTE Long Term Evolution

MME Mobility Management Entity

MN Master Node

MR Multi-RAT

MR-DC Multi-RAT Dual Connectivity

NG Next Generation

NR New Radio

P-GW Packet Gateway

RAN Radio Access Network

RAT Radio Access Technology

RRC Radio Resource Control

SMF Session Management Function

S-GW Serving GateWay

S-MN Source MN

SN Secondary Node

S-SN Source SN

T-MN Target MN

UE User Equipment UPF User Plane Function

CU Control Unit

DU Distributed Unit

LLS Lower-layer Split

MT Mobile Termination

RLC Radio Link Control

BAP Backhaul Adaptation Protocol

BH Backhaul

NDS Network Domain Security

DTLS Datagram Transport Layer Security

CP Control Plane

UP User Plane

UPF User Plane Function

IAB Integrated Access and Backhaul

gNB gNodeB

[0114] Citations are provided below for references that are mentioned in the present disclosure.

[1] 3GPP TS 38.300

[2] 3GPP TR 38.874

[3] 3GPP TS 38.331

[4] 3GPP TS 38.473

[0115] Further definitions and embodiments are discussed below.

[0116] In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belong. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

[0117] When an element is referred to as being "connected", "coupled", "responsive", or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being "directly connected", "directly coupled", "directly responsive", or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout.

Furthermore, "coupled", "connected", "responsive", or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term "and/or" includes any and all combinations of one or more of the associated listed items.

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

[0119] As used herein, the terms "comprise", "comprising", "comprises", "include",

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

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

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

[0122] It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0123] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts.

Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.

[0124] Additional explanation is provided below.

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

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

[0127] Figure 12: A wireless network in accordance with some embodiments.

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

[0129] The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile

Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[0130] Network QQ106 may comprise one or more backhaul networks, core networks,

IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable

communication between devices.

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

[0132] As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network.

Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

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

[0134] Similarly, network node QQ160 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node QQ160.

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

determination.

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

[0137] In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on the same chip or set of chips, boards, or units.

[0138] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

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

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

[0141] In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

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

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

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

The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

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

[0146] As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using

electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (loT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-loT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

[0147] As illustrated, wireless device QQ110 includes antenna QQ111, interface

QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD QQ110.

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

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

[0150] Processing circuitry QQ120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application- specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD QQ110 components, such as device readable medium QQ130, WD QQ110 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry QQ120 may execute instructions stored in device readable medium QQ130 or in memory within processing circuitry QQ120 to provide the functionality disclosed herein. [0151] As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

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

[0153] Processing circuitry QQ120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. [0154] Device readable medium QQ130 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry QQ120. Device readable medium QQ130 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated. User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

[0155] Auxiliary equipment QQ134 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment QQ134 may vary depending on the embodiment and/or scenario. [0156] Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

[0157] Figure 13: User Equipment in accordance with some embodiments

[0158] Figure 13 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE QQ2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in Figure 13, is one example of a WD configured for communication in accordance with one or more

communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 13 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0159] In Figure 13, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, read-only memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231, power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 13, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

[0161] In the depicted embodiment, input/output interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE QQ200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. The input device may include a touch- sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor. [0162] In Figure 13, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a

telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface QQ211 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

[0163] RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium QQ221 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 disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0164] Storage medium QQ221 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221, which may comprise a device readable medium.

[0165] In Figure 13, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks. Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802. QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

[0166] In the illustrated embodiment, the communication functions of communication subsystem QQ231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based

communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a

telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200. [0167] The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200.

Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

[0168] Figure 14: Virtualization environment in accordance with some embodiments

[0169] Figure 14 is a schematic block diagram illustrating a virtualization environment

QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

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

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

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

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

[0174] During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

[0175] As shown in Figure 14, hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) QQ3100, which, among others, oversees lifecycle management of applications QQ320. [0176] Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0177] In the context of NFV, virtual machine QQ340 may be a software

implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines QQ340, forms a separate virtual network elements (VNE).

[0178] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Figure 14.

[0179] In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0180] In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

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

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

Claims

What is claimed is:

1. A method of operating an integrated access and backhaul, IAB, node in a wireless communication network, wherein the IAB node comprises a distributed unit, DU, for a control unit, CU, in the wireless communication network, the method comprising: performing (802) a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; preparing (804) a remapping/rerouting report describing the remapping or rerouting of the radio bearer; and transmitting (806) the remapping/rerouting report to the CU.

2. The method of Claim 1, further comprising: establishing the backhaul link to the CU; and mapping the radio bearer to a backhaul channel on the backhaul link; wherein performing the local remapping or rerouting of the radio bearer comprises rerouting the radio bearer over a different backhaul link.

3. The method of Claim 1, further comprising: establishing the backhaul link to the CU; and mapping the radio bearer to a backhaul channel on the backhaul link; wherein performing the local remapping or rerouting of the radio bearer comprises remapping the radio bearer to a different backhaul channel on the backhaul link.

4. The method of Claim 1, wherein any remapping/rerouting triggers preparation and transmission of the remapping/rerouting report.

5. The method of Claim 1, wherein only remapping/rerouting of 1:1 mapped bearers triggers preparation and transmission of the remapping/rerouting report.

6. The method of Claim 1, further comprising receiving information during setup of a radio bearer or backhaul channel setup indicating whether rerouting or remapping of the radio bearer or backhaul channel will trigger a remapping/rerouting report.

7. The method of Claim 1, wherein the IAB node is configured to trigger generation of the remapping/rerouting report in response to rerouting or remapping of a radio bearer or backhaul channel.

8. The method of Claim 7, wherein the IAB node is configured to trigger generation of the remapping/rerouting report in response to detecting a quality degradation of the remapped/rerouted bearer.

9. The method of Claim 8, wherein the quality degradation is detected in response to an increase buffering for re-mapped traffic.

10. The method of Claim 1, wherein the rerouting/remapping is performed in the downlink direction, and the remapping/rerouting report is sent to the CU via Fl-AP signaling.

11. The method of Claim 1, wherein the rerouting/remapping is performed in the uplink direction, and the remapping/rerouting report is sent to the CU via RRC signaling or via Fl-AP signaling.

12. The method of Claim 1, wherein the remapping/rerouting report comprises rerouting information including identification of a previous link and a new link involved in the rerouting.

13. The method of Claim 1, wherein the remapping/rerouting report comprises remapping information including identification of a previous backhaul channel and a new backhaul channel involved in the rerouting.

14. The method of Claim 1, wherein the remapping/rerouting report comprises a cause value for the rerouting/remapping.

15. The method of Claim 1, wherein the remapping/rerouting report comprises information about remapping/rerouting on a per backhaul channel basis.

16. A method of operating a control unit, CU, that is connected by a backhaul link in a wireless communication network to an integrated access and backhaul, IAB, node, wherein the IAB node comprises a distributed unit, DU, controlled by the CU, the method comprising: receiving a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; and configuring a dedicated backhaul channel for the radio bearer.

17. The method of Claim 16, further comprising transmitting a notification message to the DU informing it of the dedicated backhaul channel.

18. A method of operating a control unit, CU, that is connected by a backhaul link in a wireless communication network to an integrated access and backhaul, IAB, node, wherein the IAB node comprises a distributed unit, DU, controlled by the CU, the method comprising: configuring (1002) a backup backhaul channel; receiving (1004) a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; and in response to the remapping/rerouting report, remapping (1006) the radio bearer to the backup backhaul channel.

19. The method of Claim 18, wherein, prior to remapping, the radio bearer is mapped to backhaul channel via a 1:1 mapping, and wherein the radio bearer is remapped to the backup backhaul channel via a 1:1 mapping.

20. The method of Claim 18, further comprising: configuring backup backhaul channels on all possible paths between the DU and the CU.

21. The method of Claim 18, further comprising: configuring backup backhaul channels on a subset of possible paths between the DU and the CU.

22. A network node (1100), comprising: a processor circuit (1103); a network interface (1107) coupled to the processor circuit; and a memory (1105) coupled to the processor circuit, the memory comprising machine readable program instructions that, when executed by the processor circuit, cause the UE to perform operations comprising operations according to any of Claims 1 to 21.

23. A wireless communication system, comprising: a control unit, CU; and an integrated access and backhaul, IAB, wherein the IAB node comprises a distributed unit, DU, for the CU, in the wireless communication system, wherein the IAB node is configured to perform operations comprising: performing (802) a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; preparing (804) a remapping/rerouting report describing the remapping or rerouting of the radio bearer; and transmitting (806) the remapping/rerouting report to the CU.

24. The wireless communication system of Claim 23, wherein the CU is configured to perform operations comprising: configuring (1002) a backup backhaul channel; receiving (1004) a remapping/rerouting report from the DU describing a local remapping or rerouting of a radio bearer over one or more backhaul channels on one or more backhaul links between the IAB node and the CU; and in response to the remapping/rerouting report, remapping (1006) the radio bearer to the backup backhaul channel.