CN113728720A

CN113728720A - Bearer mapping for integrated access and backhaul links

Info

Publication number: CN113728720A
Application number: CN201880099304.4A
Authority: CN
Inventors: 黄莹; 陈琳
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2018-11-01
Filing date: 2018-11-01
Publication date: 2021-11-30
Also published as: WO2020034427A1

Abstract

The present invention is directed to a method of wireless communication, the method comprising receiving, by a first communication node, a signaling message from a second communication node, the signaling message comprising information associated with a first mapping and a second mapping. The method also includes performing, by the first communication node, a first transmission using the first mapping. The first mapping is established between the first radio bearer and the first radio link control channel or between the second radio link control channel and the logical channel. The method also includes performing, by the first communication node, a second transmission using the second mapping. The second mapping is established between the plurality of radio bearers and a third radio link control channel, or a plurality of radio link control channels and a logical channel.

Description

Bearer mapping for integrated access and backhaul links

Technical Field

The present invention relates generally to wireless communications, and more particularly to bearer mapping for integrating access and backhaul links.

Background

Mobile communication technology is moving the world to increasingly connected and networked society. The rapid growth of mobile communications and advances in technology have resulted in greater demands for capacity and connectivity. Other aspects such as energy consumption, equipment cost, spectral efficiency and latency are also important to meet the needs of different communication scenarios. Different technologies are being discussed, including new ways to provide higher quality of service, longer battery life, and improved performance.

Disclosure of Invention

This patent document describes a technique for providing optimal performance for different service types by supporting one-to-one mapping and many-to-one mapping between Radio bearers and Radio Link Control (RLC) channels. These techniques may also be applied to support different mapping types between RLC channels and logical channels.

In one example aspect, a method of wireless communication is disclosed. The method includes receiving, by a first communication node, a signaling message from a second communication node. The signaling message includes information associated with the first mapping and the second mapping. The method includes performing, by a first communication node, a first transmission using a first mapping. The first mapping is established between the first radio bearer and the first radio link control channel or between the second radio link control channel and the logical channel. The method also includes performing, by the first communication node, a second transmission using the second mapping. The second mapping is established between the plurality of radio bearers and a third radio link control channel, or a plurality of radio link control channels and a logical channel.

In another example aspect, a method of wireless communication is disclosed. The method comprises sending a signaling message from a first communication node to a second communication node. The signaling message comprises information associated with a first mapping and a second mapping, said first mapping and second mapping associated information causing the second communication node to perform a first transmission using the first mapping established between the first radio bearer and the first radio link control channel or between the second radio link control channel and the logical channel, and to perform a second transmission using said second mapping established between the plurality of radio bearers and the third radio link control channel or between the plurality of radio link control channels and said logical channel.

In another example aspect, a method of wireless communication is disclosed. The method comprises transmitting capabilities of the first communication node from the first communication node to the second communication node. The capability is to indicate at least one of: one or more types of mapping options between radio bearers and radio link control channels supported by the first communication node, one or more types of mapping options between radio link control and logical channels, one or more types of automatic repeat request (ARQ) supported by the first communication node, or the placement of adaptation layers.

In another example aspect, a method of wireless communication is disclosed. The method comprises receiving, by the first communication node, from the second communication node, a capability of the second communication node. The capability is to indicate at least one of: one or more types of mapping options between radio bearers supported by a wireless communication node and radio link control channels supported by the second communication node, one or more types of mapping options between radio link control and logical channels supported by the second communication node, one or more types of ARQ supported by the second communication node, a mapping type or a placement of an adaptation layer.

In yet another example aspect, a wireless communications apparatus is disclosed. The apparatus includes a processor configured to implement the above-described method.

In yet another example aspect, a computer program storage medium is disclosed. The computer program storage medium includes code stored thereon. The code, when executed by a processor, causes the processor to implement the described method.

These and other aspects are described in this document.

Drawings

FIG. 1A illustrates an example of an independent deployment of User Equipment (UE) and Integrated Access and Backhaul (IAB) nodes;

fig. 1B illustrates an example deployment in which a UE operates with an Evolved Packet Core (EPC for short) in a non-standalone case, while an IAB node operates with a Next Generation Core (NGC for short) in a standalone case;

fig. 1C illustrates an example deployment in which the UE and IAB nodes operate in a non-standalone fashion;

fig. 2 shows an example of Control Unit (CU)/Data Unit (DU) separation in the IAB architecture;

fig. 3A illustrates an example scheme that employs a one-to-one mapping between UE Data Radio Bearer (DRB for short) and Backhaul (BH) Radio Link Control (RLC for short) channels;

fig. 3B illustrates another example scheme employing a many-to-one mapping between UE DRBs and BH RLC channels;

fig. 4A illustrates an example protocol stack that may be used to support both one-to-one mapping and many-to-one mapping between UE DRBs and BH RLC channels;

fig. 4B illustrates another example protocol stack that may be used to support one-to-one mapping and many-to-one mapping between UE DRBs and BH RLC channels;

fig. 4C illustrates another example protocol stack that may be used to support both one-to-one mapping and many-to-one mapping between UE DRBs and BH RLC channels;

fig. 4D illustrates another example protocol stack that may be used to support one-to-one mapping and many-to-one mapping between UE DRBs and BH RLC channels;

fig. 4E illustrates another example protocol stack that may be used to support both one-to-one mapping and many-to-one mapping between UE DRBs and BH RLC channels;

fig. 5 illustrates an example of a wireless communication system to which techniques in accordance with one or more embodiments of the present technology may be applied;

FIG. 6 is a block diagram representation of a portion of a radio station to which one or more embodiments in accordance with the present technology may be applied;

fig. 7 is a flow diagram of a method for wireless communication in accordance with one or more embodiments of the present technique;

FIG. 8 is a flowchart representation of another method for wireless communication in accordance with one or more embodiments of the present technique;

FIG. 9 is a flowchart representation of another method for wireless communication in accordance with one or more embodiments of the present technique;

fig. 10 is a flow diagram of yet another method for wireless communication in accordance with one or more embodiments of the present technology.

Detailed Description

In this document, section headings are used only to improve readability, and do not limit the scope of the embodiments and techniques disclosed in each section to only that section. Some features are described using an example of a 5G wireless protocol. However, the applicability of the disclosed technology is not limited to 5G wireless systems.

The development of New generation wireless communication, New Radio (NR) communication for 5G, is part of the continuous mobile broadband evolution process to meet the increasing demands of network demand. NR technology imposes stringent delay and reliability requirements and is expected to provide users with unprecedented data rates. The millimeter wave (mmWave) band higher than 10GHz therefore plays an important role. Furthermore, the small size of the antenna at mmWaves allows for a very large antenna array with high beamforming gain, overcoming high propagation losses at such high frequencies. On the other hand, the millimeter wave signal is subjected to high signal attenuation and reflection, thereby limiting the communication range of the millimeter wave infrastructure.

The combination of high propagation loss and blocking problems requires high density deployment of next Generation Node bs (gnbs). In such a deployment, providing a wired backhaul for each gNB may be expensive for the network operator. Thus, having wireless Backhaul as part of an Integrated Access and Backhaul (IAB) architecture provides greater flexibility in deployment — a portion of the gNB is equipped with traditional fiber-like Backhaul capabilities, and the remainder of the gNB is connected wirelessly (optionally through multi-hops) to the fiber infrastructure.

In the IAB architecture, a communication node supporting a User Equipment (User Equipment, abbreviated as UE) radio access and wirelessly transmitting a User plane or control plane packet is referred to as an IAB node. A communication access node providing wireless backhaul functionality for an IAB node and having a wired connection with a core network element is called an IAB donor. The IAB donor includes an IAB donor data unit (data unit, DU for short) and/or an IAB control unit (control unit, CU for short).

The IAB architecture can support stand-alone (SA) and non-stand-alone (NSA) deployments. 1A-1C illustrate an example of a deployment using an IAB architecture. Fig. 1A shows an example of SA deployment for a UE and an IAB node. Fig. 1B shows an example deployment in which a UE operates in NSA with an Evolved Packet Core (EPC for short) and an IAB node operates in SA with a Next Generation Core (NGC for short). Fig. 1C shows an example deployment in which a UE and an IAB node operate in NSA with EPC.

And, supporting CU/DU split deployments is an important technical feature in NR technology. Fig. 2 shows an example of CU/DU separation in the IAB architecture. In this example, the IAB node and the IAB donor include separate CU and DU logic functions. In addition, a CU may also include control plane (CP, also referred to as CU-CP) and user plane (UP, also referred to as CU-UP) logical functions.

With CU/DU separation, the IAB node may provide either the gbb function or the gbb-DU function. The IAB node may also provide Mobile Termination (MT) functionality, which is similar in some respects to UE functionality. In some embodiments, one IAB node (referred to as a child IAB node) may access another IAB node (referred to as a parent IAB node) or an IAB donor over the air interface. User-plane or control-plane packets may be communicated between IAB nodes or between an IAB node and an IAB donor via a wireless backhaul link. The access link and the backhaul link may use the same or different carrier frequencies. In addition, user-plane or control-plane packets may be sent over a multi-hop relay backhaul link between the access node and the IAB donor.

Currently, two mapping schemes between UE bearers and Backhaul (BH) Radio Link Control (RLC) channels have been proposed. Fig. 3A shows a scheme employing one-to-one mapping between UE Data Radio bearers (DRBs for short) and BH RLC channels. Alternatively, fig. 3B shows another mapping scheme that employs many-to-one mapping between UE DRBs and BH RLC channels. However, different services may be suitable for different mappings. For example, 1: the 1 mapping scheme is more suitable for VOIP services. On the other hand, N: the 1 mapping is more suitable for best effort services. To provide different services with better performance at the same time, 1: 1 and N: 1 mapping.

This patent document describes that a 1: 1 mapping and N: 1 mapping technique. The techniques described herein may also be applied to support 1: 1 mapping and N: 1 mapping.

Fig. 7 is a flow diagram of a method 700 for wireless communication in accordance with one or more embodiments of the present technology. The method 700 comprises, at step 701, receiving, by a first communication node, a signaling message from a second communication node. The signaling message includes information associated with the first mapping and the second mapping. The method 700 includes, at step 702, performing, by a first communications node, a first transmission using a first mapping. The first mapping is established between the first radio bearer and the first radio link control channel or between the second radio link control channel and the logical channel. The method 700 further comprises performing, by the first communication node, a second transmission using the second mapping, at step 703. The second mapping is established between the plurality of radio bearers and a third radio link control channel, or a plurality of radio link control channels and a logical channel.

Fig. 8 is a flow diagram of a method 800 for wireless communication in accordance with one or more embodiments of the present technology. The method 800 comprises, at step 801, sending a signaling message from a first communication node to a second communication node. The signaling message comprises information associated with a first mapping and a second mapping, said first mapping and second mapping associated information causing the second communication node to perform a first transmission using the first mapping established between the first radio bearer and the first radio link control channel or between the second radio link control channel and the logical channel, and to perform a second transmission using said second mapping established between the plurality of radio bearers and the third radio link control channel or between the plurality of radio link control channels and said logical channel.

Fig. 9 is a flow diagram of a method 900 for wireless communication in accordance with one or more embodiments of the present technology. The method 900 comprises, at step 901, transmitting capabilities of a first communication node from the first communication node to a second communication node. The capability is to indicate at least one of: one or more types of mapping options between radio bearers and radio link control channels supported by a first communication node, one or more types of mapping between radio link control and logical channels supported by the first communication node, one or more types of automatic repeat request, ARQ, supported by the first communication node, or adaptation layer placement.

Fig. 10 is a flowchart representation of a method 1000 for wireless communication in accordance with one or more embodiments of the present technology. The method 1000 comprises, at step 1001, receiving, by a first communication node, from a second communication node, capabilities of the second communication node. The capability is to indicate at least one of: one or more types of mapping options between radio bearers supported by a wireless communication node and radio link control channels supported by the second communication node, one or more types of mapping options between radio link control and logical channels supported by the second communication node, one or more types of automatic repeat request, ARQ, mapping types or adaptation layer placements supported by the second communication node.

Some examples of the disclosed techniques are described in the following example embodiments.

Example 1

To support 1: 1 and N: 1 mapping, it is desirable to allow IAB nodes and/or IAB donors to obtain each other's capabilities so that each node can determine which type of mapping can be used. Several methods are described below:

in the first mode, the IAB node sends its own capability information to an IAB node owner or a Mobility Management Function (AMF) through a message. In some embodiments, the message may be a Radio Resource Control (RRC) message or an F1 message or an Xn message.

In the second mode, the IAB donor sends the capability information to the AMF through a message. In some embodiments, the message may be a Next Generation (NG) message.

In some embodiments, the capability information comprises at least one of: mapping options (e.g., 1: 1 mapping and/or N: 1 mapping), mapping types (e.g., bearer-to-RLC channel mapping and/or RLC channel-to-logical channel mapping), adaptation layer placements (e.g., whether the adaptation layer is above the RLC layer or above a Media Access Control (MAC) MAC layer), or ARQ options (end-to-end, abbreviated E2E) ARQ and/or Hop-by-Hop (HBH) ARQ).

And thirdly, the IAB node sends the configuration information or the capability information to the IAB node through the message. In some embodiments, the message may be an RRC message, an F1 message, or an Xn message.

And fourthly, the AMF sends the configuration information or the capability information to the IAB node or the IAB node through the message. In some embodiments, the message may be an NG message.

In some embodiments, the configuration information comprises at least one of: mapping options (e.g., 1: 1 mapping and/or N: 1 mapping), mapping types (e.g., UE bearer to RLC channel mapping and/or RLC channel to logical channel mapping), adaptation layer arrangements (e.g., whether the adaptation layer is above the RLC layer or above the MAC layer), ARQ options (E2EARQ and/or HBHARQ), information associated with mapping between UE bearers to RLC channels, and/or information associated with mapping between RLC channels and logical channels. In some embodiments, the information associated with any of the mappings may include a first identifier and a second identifier. The first identification comprises at least one of: the identifier of the radio bearer to which the incoming data packet belongs, the identifier of the radio link control channel to which the incoming data packet belongs, or the identifier of the logical channel to which the incoming data packet belongs. The second identifier comprises at least one of: an identifier of a radio bearer to which an outgoing packet belongs, an identifier of a radio link control channel to which the outgoing packet belongs, or an identifier of a logical channel to which the outgoing packet belongs.

In some embodiments, each QoS flow, UE, Protocol Data Unit (PDU) session, terrestrial Radio Access network (Evolved UMTS, abbreviated E-UTRAN) Radio Access Bearer (E-UTRAN Radio Access Bearer), Radio Bearer may have corresponding configuration information.

In some embodiments, an IAB node may send capability information to its parent/child IAB nodes. In some embodiments, the IAB node may send configuration information to the child/parent IAB node. In some embodiments, the IAB node may send configuration information to the IAB donor.

In some embodiments, the IAB donor may send capability information or configuration information to a base station (e.g., E-UTRAN NodeB, abbreviated eNB) over an X2 interface (e.g., in a dual connectivity EN-DC deployment scenario). In some embodiments, a base station (e.g., eNB) may send capability information or configuration information to an IAB donor over an X2 interface (e.g., in a dual connectivity EN-DC deployment scenario). In some embodiments, the IAB donors exchange capability information over the Xn interface. In some embodiments, the IAB donors exchange configuration information over the Xn interface (e.g., during handover).

Example 2

In some embodiments, the supported configuration information may be indicated without an explicit signaling message (e.g., as specified in embodiment 1). For example, the denor of the IAB or the IAB node may determine the supported configuration according to the QoS information corresponding to the QoS flow. The QoS information may include at least one of: QoS Class Identifier (QoS Class Identifier, abbreviated as QCI), QoS Flow ID (QoS Flow ID, abbreviated as QFI), 5G QoS Indicator (5G QoS Indicator, abbreviated as 5QI), Differentiated Service Code Point (DSCP), priority, delay budget, delay critical indication, Aggregate Bit Rate (ABR) information, or Guaranteed Bit Rate (GBR) information. For example, a UE DRB comprising a GBR QoS flow may use 1: 1 mapping. UE DRBs that do not include GBR QoS flows may use N: 1 mapping. In the non-CU-DU splitting case, the configuration may be determined by the serving IAB node of the UE (e.g., the access IAB node). An access IAB node may send configuration information to other IAB nodes or IAB donors.

Alternatively, the IAB donor or IAB node may receive the decision criterion information from an OAM or core network element, such as the AMF. The IAB node may also receive criteria information from the IAB donor or parent IAB node. For example, the criterion may be one of: based on the criteria of the GBR, the QoS parameters and their corresponding configuration information, the threshold of the QoS parameters (e.g., if the priority value is less than the threshold, a 1: 1 mapping is used). The QoS parameter may be one of: QCI, QFI, 5QI, DSCP, ARP, priority, delay budget, or delay critical indication. The configuration information may be one of: mapping options (1: 1 mapping and/or N: 1 mapping), mapping type (UE bearer to RLC channel mapping and/or RLC channel to logical channel mapping), adaptation layer arrangement (adaptation over RLC or over MAC), or ARQ options (E2E ARQ and/or HBH ARQ).

In some embodiments, an IAB donor or IAB node receives indication information from an IAB donor or core network element (such as an AMF). In some embodiments, the indication information indicates whether 1: 1 mapping and/or N: 1 mapping. In some embodiments, the indication information may include a mapping type (e.g., UE bearer to RLC channel mapping and/or RLC channel to logical channel mapping). In some embodiments, the indication information may also indicate whether end-to-end ARQ and/or hop-by-hop ARQ is to be used. In some embodiments, the indication information may indicate the placement of the adaptation layer (e.g., whether the adaptation layer is above the RLC layer or above the MAC layer). For example, each QoS flow, UE, Protocol Data Unit (PDU) session, E-UTRAN radio access bearer (E-RAB)/radio bearer has corresponding indication information.

The IAB donor can configure an access or intermediate IAB node/IAB donor DU, which can be sent via F1 message, RRC message, or Xn message, with at least one of the following:

1) indicating the information. The indication information indicates whether to use 1: 1 mapping and/or N: 1 mapping. The indication information may include a mapping type (e.g., UE bearer to RLC channel mapping and/or RLC channel to logical channel mapping). The indication information may also indicate whether end-to-end ARQ and/or hop-by-hop ARQ is to be used. The indication information may also indicate the placement of the adaptation layer (e.g., whether the adaptation layer is above the RLC layer or above the MAC layer).

2) Information for mapping between RB and RLC channels. The information includes at least one of: RB ID/RLC channel ID/LCID in the access link, RB ID/RLC channel ID/LCID in the backhaul link, ingress RB ID/RLC channel ID/LCID and egress RB ID/RLC channel ID/LCID, or UE RB ID and egress RB ID/RLC channel ID/LCID.

3) Information for mapping between an RLC channel and a Logical Channel (LCH). The information includes at least one of: an RLC channel ID and LCID, a UE RB ID and LCID, one or more RLC channel IDs and LCIDs, or one or more UE RB IDs and LCIDs. In some embodiments, the UE rbid is an identifier for identifying a bearer of the UE. In some embodiments, the UE id and the RBID are used to identify the bearer of the UE. In some embodiments, the UE RBs are identified by one or more Tunnel End Identifiers (TEIDs).

In some embodiments, the RLC channel ID is used to identify the RLC channel or RLC bearer. The RLC channel ID may be a newly defined identifier, a UE bearer identifier, or a combination of a UE identifier and a bearer identifier.

Example 3

In some embodiments, QoS information (e.g., QCI, QFI, 5QI, DSCP, priority or delay requirements, GBR related information) for a QoS flow or UE bearer or RLC channel may be used by an access IAB node/intermediate IAB node/IAB donor DU to determine configuration information to use. The configuration information includes at least one of: mapping options (e.g., 1: 1 mapping and/or N: 1 mapping), mapping types (e.g., UE bearer to RLC channel mapping and/or RLC channel to logical channel mapping), adaptation layer arrangements (e.g., whether the adaptation layer is above the RLC layer or above the MAC layer), ARQ options (E2E ARQ and/or HBH ARQ), information available for mapping between UE bearers to RLC channels, and/or information available for mapping between RLC channels and logical channels.

In some embodiments, the access/intermediate IAB node/IAB donor DU may determine the mapping or multiplexing between RLC channels and LCHs according to QoS parameters. The IAB donor may configure rules for RLC channel to LCH mapping of IAB nodes/IAB donor DUs, RLC channel related QoS parameters (e.g., priority level, GBRQoS flow information, etc.), and LCH related QoS parameters (e.g., priority bit rate, bucketSizeDuration, etc.). The IAB donor may configure the above information to the IAB node/IAB donor DU through an RRC message or F1 message or Xn message.

Example 4

The present embodiment describes performing 1: 1 and N: an example unified design of 1 mapping. In this embodiment, the adaptation layer is located above the RLC layer and supports hop-by-hop (HBH) AQR. Fig. 4A-4E illustrate example protocol stacks that may be used for such a design.

In some embodiments, for N: 1 bearer mapping, which the IAB donor (or IAB donor CU) can determine based on the QoS parameters of the UE bearer or ingress RB/RLC channel/LCH. In some embodiments, the IAB donor may access the IAB node/intermediate IAB node/donor DU as follows:

1. access IAB node

For uplink transmissions, the IAB donor may configure the UE RB ID/LCID (optional UE ID) in the access link and the associated RB ID/RLC channel ID/LCID (optional: next hop IAB node ID) in the backhaul link.

The IAB node ID may be one of:

1) identification of the Mobile Telecommunications system (MT) part of the IAB node includes, but is not limited to: a Cell Radio Network Temporary Identifier (C-RNTI for short), a C-RNTI and a Cell Identifier, a C-RNTI and a base station Identifier, a C-RNTI and a DU Identifier, an F1AP ID, an X2AP ID, an XnAP ID, an S1AP ID, an NGAP ID or a GTP TEID; or

2) Identification of the gNB or DU part for identifying the IAB node, including but not limited to: DU identity, CU identity, base station identity, cell identity, physical cell identity PCI or IP address.

Here are several example ways of configuring such correspondence:

1) the IAB donor (or IAB donor CU) configures the correspondence for mapping in the UE context (e.g., via F1 message). That is, the DRB of each UE is configured with a DRB ID and BHRB ID/RLC channel ID/LCID/next hop IAB node ID. Thus, no additional UEID configuration is required.

2) The IAB donor (or IAB donor CU) configures the correspondence for the mapping in the MT context (e.g., via RRC messages). That is, the DRB of each MT (or the logical channel/RLC channel of each MT) is configured with a ue ID and a ue rbid/RLC channel ID/LCID. In this example approach, the next-hop IAB node ID need not be configured.

3) IAB donor (or IAB donor CU) configures UE ID/UE RB ID/RLC channel ID/LCID and BH RB ID/RLC channel ID/LCID/next hop IAB node ID.

In some embodiments, the access IAB node determines the next hop IAB node/IAB donor or BHRB/RLC channel/LCH from the received MAC subheader and/or LCID in the source UE. In some embodiments, the access IAB may determine the RBID from the LCID.

For downlink transmission, the configured mapping information includes RBID/RLC channel ID/LCID and UE RBID/LCID/UE ID in the backhaul link. Alternatively, the access IAB node may determine the target UE and the UE bearer/RLC channel/LCH according to the information such as the UE rbid included in the adaptation layer of the received data packet.

2. Intermediate IAB node

The intermediate IAB node may determine the egress RB/RLC channel/LCH from the ingress RB/RLC channel/LCH. In this way, the IAB donor (or IAB donor CU) configures an ingress RBID/RLC channel ID/LCID/optional child IAB node ID and an egress RBID/RLC channel ID/LCID/optional parent IAB node or donor DUID for uplink transmission. For downlink transmission, the IAB donor (or IAB donor CU) configures an ingress RBID/RLC channel ID/LCID/optional parent IAB node ID and an egress RBID/RLC channel ID/LCID/optional child IAB node or donor DUID.

Alternatively, the intermediate IAB node may map according to the UE RB ID of the adaptation layer in the received packet. In this manner, for uplink transmissions, the IAB donor (or IAB donor CU) configures the UERBID and associated egress RBID/RLC channel ID/LCID/optional parent IAB node or donor DUID. For downlink transmission, the IAB donor (or IAB donor CU) configures the UERBID and egress RBID/RLC channel ID/LCID/optional child IAB node or donor DUID.

3. Donor DU

The GPRS Tunneling Protocol (GTP) is a set of communication protocols based on Internet Protocol (IP) for carrying General Packet Radio Service (GPRS) in a wireless network. For uplink transmission, the IAB donor (or IAB donor DU) maps the ingress RB/RLC channel/LCH to the corresponding GTP-U tunnel. In some embodiments, the IAB donor (or IAB donor CU) may configure the UERBID and GTP-U tunnels identified by a GTP Tunnel Endpoint Identifier (TEID) and/or Transport Network Layer (TNL) address. The donor DU may determine the GTP-U tunnel from the UE RB ID in the adaptation layer.

Alternatively, the IAB donor (or IAB donor CU) may configure the RB/RLC channel/LCH identified by the RBID/RLC channel ID/LCID and the associated GTP-U tunnel identified by the GTPTEID and/or TNL address. The donor DU may determine the GTP-U tunnel from the ingress RB/RLC channel/LCH.

For downlink transmission, the IAB donor (or IAB donor DU) maps the UEGTP-U tunnel to the corresponding egress RB/RLC channel/LCH. The donor DU also determines the ue rbid and/or destination information (e.g., destination IAB node or access IAB node identifier) corresponding to the GTP-U tunnel to which the received packet belongs. The donor DU then adds the above information to the adaptation layer. In some embodiments, the IAB donor (or IAB donor CU) may configure the donor DU with at least one of the following: GTP-U tunnel and egress RB/RLC channel/LCH, GTP-U tunnel and UERBID, UERBID and egress RB/RLC channel/LCH.

The methods described in the above embodiments may also be applied thereto.

Example 5

The present embodiment describes performing 1: 1 and N: an example unified design of 1 mapping. The adaptation layer is located above the MAC layer. End-to-end E2E or HBH ARQ is supported. Fig. 4A-4B illustrate example protocol stacks that may be used for such a design.

In this embodiment, N: mapping 1 means that multiple UE bearers can be mapped to the same RLC channel, and N is performed above RLC: 1 mapping. The methods described in the above-described embodiments and embodiments 6 and 7 can also be applied thereto.

Example 6

This embodiment describes performing 1: 1 and N: an example unified design of 1 mapping. The adaptation layer is located above the MAC layer. End-to-end E2E and/or HBHARQ is supported. Fig. 4A-4B illustrate example protocol stacks that may be used for such a design.

In this design, multiple RLC channels may be multiplexed into one logical channel. The adaptation layer performs multiplexing or demultiplexing operation and is located above the MAC layer.

If both E2EARQ and HBHARQ are supported (e.g., some UEs/RBs use E2EARQ and some UEs/RBs use HBHARQ), the access IAB node and the intermediate IAB node determine whether to perform E2EARQ or HBHARQ. This is because the RLC functions of the access IAB node and the intermediate IAB node are different in the two ARQ modes. Here are some example methods for determining an ARQ mode:

1) the method comprises the following steps: for downlink transmission, the IAB donor DU or IAB donor indicates the ARQ mode in the adaptation layer header. In some embodiments, the IAB donor DU may determine the ARQ mode itself or receive a signaling message from the IAB donor CU. For uplink transmissions, the access IAB node indicates the ARQ mode in the adaptation layer header. The access IAB node can determine the ARQ mode according to the QoS parameters such as hop count, time delay, reliability and the like. The access IAB node may also determine the ARQ mode by receiving a signaling message (e.g., F1 signaling or Xn signaling) from the IAB donor or the IAB donor CU.

2) The method 2 comprises the following steps: the IAB donor may configure RB/RLC channels/LCHs and associated ARQ modes (HBH or E2E) for the access IAB node, the intermediate IAB node, or the IAB donor DU.

The methods described in the above embodiments and embodiment 7 can also be applied here.

Example 7

This embodiment describes an example unified design, where 1: 1 mapping and N: 1 mapping. Performing N on the RLC layer supporting only the HBH ARQ mode: 1 mapping. In this design, N: the 1 mapping maps multiple UE bearers to the same RLC channel mapping. Performing N: 1 mapping and uses HBHARQ. For 1: 1 mapping, using E2EARQ or HBHARQ, and an adaptation layer above the MAC layer. 1: 1 and N: the 1 mapping uses different protocol stacks (i.e., the location of the adaptation layer is different) and the ARQ modes may be different (HBH and/or E2E). The access/intermediate IAB node and the IAB donor therefore need to be able to determine the location of the adaptation layer (whether above the MAC layer or above the RLC layer) or which ARQ mode (e.g., E2E or HBH) is supported.

In some embodiments, for uplink transmissions, the access/intermediate IAB node determines whether to perform adaptation layer or RLC layer encapsulation first after RLC processing. Alternatively, the intermediate IAB node/IAB donor DU decides to pass the packet to the RLC or adaptation layer after demultiplexing at the MAC layer. The IAB donor (or IAB donor CU) can configure the RB/RLC channel/LCH and associated mapping options/mapping type/ARQ mode/adaptation layer location to the access/intermediate IAB node and IAB donor DU. The configuration information may be configured for each QoS flow/radio bearer/RLC channel/LCH of the IAB node/IAB donor DU.

In some embodiments, for downlink transmissions, the donor DU and the intermediate IAB node first determine whether to perform adaptation layer or RLC layer encapsulation when transmitting packets. The intermediate IAB node/access IAB node also determines whether the MAC layer delivers the data packets to the RLC or adaptation layer after demultiplexing. The IAB donor can configure RB/RLC channel/LCH and associated mapping options/mapping type/ARQ mode/adaptation layer location to the access/intermediate IAB node and the IAB donor DU. The configuration information may be configured according to QoS flow/radio bearer/RLC channel/LCH.

The methods described in the above embodiments may also be applied thereto.

Example 8

This embodiment describes an example unified design in which 1: 1 and N: 1 mapping. In this embodiment, 1: 1 and N: 1 mapping. The mapping of UE bearers to RLC channels is implemented at the adaptation layer above the RLC. Alternatively, the mapping of UE bearers to RLC channels may be implemented at the GTP-U layer above RLC. The mapping of the RLC channels to logical channels is implemented at the adaptation layer above the MAC layer. In this design, the access/intermediate IAB node and the IAB donor determine the location of the adaptation layer (either above the MAC layer or above the RLC layer) or which ARQ mode (e.g., E2E or HBH) is supported. The methods described in the above embodiments may also be applied thereto.

Fig. 5 illustrates an example of a wireless communication system 500 to which techniques in accordance with one or more embodiments of the present technology may be applied. The wireless communication system 500 may include one or more Base Stations (BSs) 505a, 505b, one or

more wireless devices

510a, 510b, 510c, 510d, and a core network 525. Base stations 505a, 505b may provide wireless service to

wireless devices

510a, 510b, 510c, and 510d in one or more wireless sectors. In some implementations, the base stations 505a, 505b include directional antennas to generate two or more directional beams to provide wireless coverage in different sectors.

The core network 525 may communicate with one or more base stations 505a, 505 b. The core network 525 provides connectivity to other wireless and wireline communication systems. The core network may include one or more service subscription databases to store information related to the subscribed

wireless devices

510a, 510b, 510c, and 510 d. The first base station 505a may provide wireless service based on a first radio access technology, while the second base station 505b may provide wireless service based on a second radio access technology. The base stations 505a and 505b may be co-located or may be installed separately in the field depending on the deployment scenario. The

wireless devices

510a, 510b, 510c, and 510d may support a number of different radio access technologies.

Fig. 6 is a block diagram representation of a portion of a radio station. A radio station 605, such as a base station or wireless device (or UE), may include processor electronics 610, such as a microprocessor, that implement one or more of the radio technologies presented in this document. The radio station 605 may include transceiver electronics 615 to transmit and/or receive wireless signals over one or more communication interfaces, such as an antenna 620. The radio station 605 may include other communication interfaces for transmitting and receiving data. The radio station 605 may include one or more memories (not explicitly shown) configured to store information such as data and/or instructions. In some implementations, the processor electronics 610 may include at least a portion of the transceiver electronics 615. In some embodiments, at least some of the disclosed techniques, modules, or functions are implemented using a radio station 605.

It will be appreciated that this document discloses a method that can be implemented into a wireless communication system to support 1: 1 mapping and N: 1 mapping both techniques to provide optimal performance for different types of services.

In one example aspect, a method of wireless communication includes: a signaling message is received by a first communication node from a second communication node. The signaling message includes information associated with the first mapping and the second mapping. The method includes performing, by a first communication node, a first transmission using a first mapping. The first mapping is established between the first radio bearer and the first radio link control channel, or between the second radio link control channel and the logical channel. The method also includes performing, by the first communication node, a second transmission using the second mapping. The second mapping is established between the plurality of radio bearers and a third radio link control channel, or a plurality of radio link control channels and a logical channel.

In some embodiments, the adaptation header of the data packet associated with the first transmission or the second transmission indicates at least one of: an automatic repeat request, ARQ, option, placement of adaptation layers, mapping option, or mapping type.

In some embodiments, the information associated with the first mapping or the second mapping includes a first identifier and a second identifier. The first identification comprises at least one of: an identifier for a radio bearer to which an incoming data packet belongs, an identification of a radio link control channel to which the incoming data packet belongs, or an identification of a logical channel to which the incoming data packet belongs. The second identifier comprises at least one of: an identifier of a radio bearer to which an outgoing packet belongs, an identifier of a radio link control channel to which the outgoing packet belongs, or an identifier of a logical channel to which the outgoing packet belongs.

In some embodiments, the first identifier comprises an identifier of a user equipment or a previous-hop communication node associated with an incoming radio bearer to which the incoming data packet belongs, or the second identifier comprises an identifier of a next-hop communication node. In some embodiments, the first identifier or the second identifier comprises an identifier of a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) tunnel.

In some embodiments, the first transmission using the first mapping is performed using a first protocol stack and the second transmission using the second mapping is performed using a second protocol stack.

In some embodiments, the first protocol stack and the second protocol stack are the same. The adaptation layer is disposed above a medium access control, MAC, layer in the first and second protocol stacks, and both the first and second protocol stacks support at least one of: end-to-end automatic repeat request ARQ or hop-by-hop ARQ.

In some embodiments, the first protocol stack and the second protocol stack are the same. The adaptation layer is located above the radio link control, RLC, layer in the first and second protocol stacks, both of which support hop-by-hop ARQ.

In some embodiments, the first protocol stack and the second protocol stack are different. The adaptation layer is placed above a medium access control, MAC, layer in the first protocol stack, and the first protocol stack supports at least one of: end-to-end ARQ or hop-by-hop ARQ. The adaptation layer is placed above the radio link control, RLC, layer in the second protocol stack, and the second protocol stack supports hop-by-hop ARQ.

In another example aspect, a method for wireless communication includes: a signaling message is sent from a first communication node to a second communication node. The signaling message comprises information associated with a first mapping and a second mapping, said first mapping and second mapping associated information causing the second communication node to perform a first transmission using the first mapping established between the first radio bearer and the first radio link control channel or between the second radio link control channel and the logical channel, and to perform a second transmission using said second mapping established between the plurality of radio bearers and the third radio link control channel or between the plurality of radio link control channels and said logical channel.

In some embodiments, the information associated with the first mapping or the second mapping includes a first identifier and a second identifier. The first identification comprises at least one of: an identification for a radio bearer to which an incoming data packet belongs, an identification for a radio link control channel to which the incoming data packet belongs, or an identification for a logical channel to which the incoming data packet belongs. The second identifier includes at least: an identifier of a radio bearer to which an outgoing packet belongs, an identifier of a radio link control channel to which the outgoing packet belongs, or an identifier of a logical channel to which the outgoing packet belongs.

In some embodiments, the first identifier comprises an identifier of a user equipment or a last hop communication node associated with the incoming radio bearer, and the second identifier comprises an identifier of a next hop communication node. In some embodiments, the first identifier or the second identifier comprises an identifier of a general packet radio service GPRS tunneling protocol user plane GTP-U tunnel.

In some embodiments, the first transmission using the first mapping is performed using a first protocol stack, and wherein the second transmission using the second mapping is performed using a second protocol stack. And the second transmission using the second mapping is performed using a second protocol stack.

In some embodiments, the adaptation layer is placed above the radio link control, RLC, layer in the first and second protocol stacks, and both the first and second protocol stacks support hop-by-hop ARQ.

In some embodiments, the first protocol stack and the second protocol stack are different. The adaptation layer is disposed above a medium access control, MAC, layer in a first protocol stack and the first protocol stack supports at least one of end-to-end ARQ or hop-by-hop ARQ, and the adaptation layer is disposed above a radio link control, RLC, layer in the second protocol stack and the second protocol stack supports the hop-by-hop ARQ.

In another example aspect, a method for wireless communication includes transmitting, from a first communication node to a second communication node, a capability of the first communication node. The capability is to indicate at least one of: one or more mapping options between radio bearers supported by a first communication node and radio link control channels, one or more mapping options between radio link control and logical channels, one or more types of automatic repeat request, ARQ, supported by the first communication node, a mapping type or a placement of an adaptation layer.

In some embodiments, the first communication node is configured to provide wireless backhaul functionality to one or more mobile devices, and wherein the second communication node is configured to provide an interface to a core network and backhaul functionality to the first communication node. And wherein the second communication node is for providing an interface to a core network and a backhaul function to the first communication node.

In some embodiments, the first communication node is for providing an interface to a core network and backhaul functionality to the second communication node, and the second communication node is for providing wireless backhaul functionality to one or more mobile devices.

In some embodiments, the first communication node is for providing an interface to a core network and backhaul functionality to a third communication node for providing wireless backhaul functionality to one or more mobile devices, and the second communication node comprises a network node in the core network. In some embodiments, the first communication node comprises a network node in a core network, and the second communication node is for providing an interface to the core network and backhaul functionality to a third communication node for providing wireless backhaul functionality to one or more mobile devices.

In another example aspect, a method for wireless communication includes: the capabilities of the second communication node are received by the first communication node from the second communication node. The capability is to indicate at least one of: one or more mapping options between radio bearers supported by the wireless communication node and radio link control channels, one or more mapping options between radio link control and logical channels supported by the second communication node, one or more types of automatic repeat request, ARQ, supported by the second communication node, a mapping type or a placement of adaptation layers.

In some embodiments, the first communication node is configured to provide wireless backhaul functionality to one or more mobile devices, and wherein the second communication node is configured to provide an interface to a core network and backhaul functionality to the first communication node.

In some embodiments, the first communication node is for providing an interface to a core network and backhaul functionality to a third communication node for providing wireless backhaul functionality to one or more mobile devices, and the second communication node comprises a network node in the core network.

In some embodiments, the first communication node comprises a network node in a core network, and the second communication node is for providing an interface to the core network and backhaul functionality to a third communication node for providing wireless backhaul functionality to one or more mobile devices.

In another example aspect, a wireless communications apparatus comprises: a processor, wherein the processor is configured to implement the method of any of the above.

In yet another example aspect, a computer storage medium, comprising: code stored on the computer storage medium, which when executed by a processor, causes the processor to implement the method described above.

The disclosed and other embodiments, modules, and functional operations described in this document can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this document and their structural equivalents, or in combinations of one or more of them. The disclosed and other embodiments may be implemented as one or more computer program products, i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter effecting a machine-readable propagated signal, or a combination of one or more of them. The term "data processing apparatus" includes all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagated signal is an artificially generated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus.

A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this document can be performed by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such a device. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile Memory, media and Memory devices, including by way of example semiconductor Memory devices, such as Erasable Programmable Read Only Memory (EPROM), and flash Memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and Compact Disc Read Only Memory (CDROM) and Digital Video Disc Read Only Memory (DVD-ROM). The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

While this patent document contains many specifics, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this patent document in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Moreover, the separation of various system components in the embodiments described in this patent document should not be understood as requiring such separation in all embodiments.

Only a few implementations and examples are described and other implementation changes and variations may be made based on what is described and illustrated in this patent document.

Claims

1. A method of wireless communication, comprising:

a first communication node receiving a signaling message from a second communication node, wherein the signaling message includes information associated with a first mapping and a second mapping;

the first communication node performing a first transmission using the first mapping, wherein the first mapping is established between a first radio bearer and a first radio link control channel or between a second radio link control channel and a logical channel; and is

The first communication node performs a second transmission using the second mapping, wherein the second mapping is established between a plurality of radio bearers and a third radio link control channel, or a plurality of radio link control channels and the logical channel.

2. The method of claim 1, wherein an adaptation header of a packet associated with the first transmission or the second transmission indicates at least one of: an automatic repeat request, ARQ, option, placement of adaptation layers, mapping option, or mapping type.

3. The method according to claim 1 or 2, wherein the information associated with the first mapping or the second mapping comprises a first identifier and a second identifier,

wherein the first identifier comprises at least one of: an identifier for a radio bearer to which an incoming data packet belongs, an identifier for a radio link control channel to which the incoming data packet belongs, an identifier for a logical channel to which the incoming data packet belongs, and

wherein the second identifier comprises at least one of: an identifier of a radio bearer to which an outgoing data packet belongs, an identifier of a radio link control channel to which the outgoing data packet belongs, and an identifier of a logical channel to which the outgoing data packet belongs.

4. The method of claim 3, wherein the first identifier comprises: an identifier of a user equipment or a previous-hop communication node associated with an incoming radio bearer to which the incoming data packet belongs, or the second identifier comprises an identifier of a next-hop communication node.

5. The method of claim 3, wherein the first identifier or the second identifier comprises: an identifier of a general packet radio service, GPRS, tunneling protocol user plane, GTP-U, tunnel.

6. The method of any of claims 1-5, wherein the first transmission using the first mapping is performed using a first protocol stack, and wherein the second transmission using the second mapping is performed using a second protocol stack.

7. The method of claim 6, wherein the first protocol stack is the same as the second protocol stack, and wherein

Wherein, an adaptation layer is arranged above the MAC layer in the first protocol stack and the second protocol stack, and the first protocol stack and the second protocol stack both support at least one of the following: end-to-end automatic repeat request ARQ, hop-by-hop ARQ.

8. The method of claim 6, wherein the first protocol stack is the same as the second protocol stack, and wherein

The first protocol stack and the second protocol stack both support hop-by-hop ARQ.

9. The method of claim 6, wherein the first protocol stack is different from the second protocol stack,

wherein an adaptation layer is disposed above a medium access control, MAC, layer in the first protocol stack, and the first protocol stack supports at least one of: end-to-end ARQ, hop-by-hop ARQ, and

wherein the adaptation layer is placed above a radio link control, RLC, layer in the second protocol stack and the second protocol stack supports hop-by-hop ARQ.

10. A method of wireless communication, comprising:

sending a signaling message from a first communication node to a second communication node,

wherein the signalling message comprises information associated with a first mapping and a second mapping, the first mapping and second mapping associated information causing the second communication node to perform a first transmission using the first mapping established between a first radio bearer and a first radio link control channel or between a second radio link control channel and a logical channel, and to perform a second transmission using the second mapping established between a plurality of radio bearers and a third radio link control channel or a plurality of radio link control channels and the logical channel.

11. The method of claim 10, wherein an adaptation header of a packet associated with the first transmission or the second transmission indicates at least one of: an automatic repeat request, ARQ, option, placement of adaptation layers, mapping option, or mapping type.

12. The method according to claim 10 or 11, wherein the information associated with the first mapping or the second mapping comprises a first identifier and a second identifier,

wherein the second identifier comprises: an identifier of a radio bearer to which an outgoing packet belongs, an identifier of a radio link control channel to which the outgoing packet belongs, or an identifier of a logical channel to which the outgoing packet belongs.

13. The method of claim 12, wherein the first identifier comprises an identifier of a user equipment or a previous-hop communication node associated with the incoming radio bearer, and wherein the second identifier comprises an identifier of a next-hop communication node.

14. The method of claim 12, wherein the first identifier or the second identifier comprises: an identifier of a general packet radio service, GPRS, tunneling protocol user plane, GTP-U, tunnel.

15. The method of any of claims 10-14, wherein the first transmission using the first mapping is performed using a first protocol stack, and wherein the second transmission using the second mapping is performed using a second protocol stack.

16. The method of claim 15, wherein the first protocol stack is the same as the second protocol stack, and wherein

17. The method of claim 15, wherein the first protocol stack is the same as the second protocol stack, and wherein

18. The method of claim 15, wherein the first protocol stack is different from the second protocol stack,

wherein an adaptation layer is disposed above a media access control, MAC, layer in the first protocol stack and the first protocol stack supports at least one of end-to-end ARQ or hop-by-hop ARQ, and

19. A method for wireless communication, comprising:

transmitting capabilities of a first communication node from the first communication node to a second communication node,

wherein the capability is to indicate at least one of: one or more mapping options between radio bearers and radio link control channels supported by the first communication node, one or more mapping options between radio link control and logical channels, one or more types of automatic repeat request, ARQ, supported by the first communication node, a mapping type or a placement of an adaptation layer.

20. The method of claim 19, wherein the first communication node is configured to provide wireless backhaul functionality to one or more mobile devices, and wherein the second communication node is configured to provide an interface to a core network and backhaul functionality to the first communication node.

21. The method of claim 19, wherein the first communication node is configured to provide an interface to a core network and backhaul functionality to the second communication node, and wherein the second communication node is configured to provide wireless backhaul functionality to one or more mobile devices.

22. The method of claim 19, wherein the first communication node is configured to provide an interface to a core network and backhaul functionality to a third communication node configured to provide wireless backhaul functionality to one or more mobile devices, and wherein the second communication node comprises a network node in the core network.

23. The method of claim 19, wherein the first communication node comprises a network node in the core network, and wherein the second communication node is configured to provide an interface to a core network and backhaul functionality to a third communication node configured to provide wireless backhaul functionality to one or more mobile devices.

24. A method for wireless communication, comprising:

receiving, by the first communication node, the capabilities of the second communication node from the second communication node,

wherein the capability is to indicate at least one of: one or more mapping options between radio bearers and radio link control channels supported by the second communication node, one or more mapping options between radio link control and logical channels supported by the second communication node, one or more types of automatic repeat request, ARQ, mapping types or adaptation layer placements supported by the second communication node.

25. The method of claim 24, wherein the first communication node is configured to provide wireless backhaul functionality to one or more mobile devices, and wherein the second communication node is configured to provide an interface to a core network and backhaul functionality to the first communication node.

26. The method of claim 24, wherein the first communication node is configured to provide an interface to a core network and backhaul functionality to the second communication node, and wherein the second communication node is configured to provide wireless backhaul functionality to one or more mobile devices.

27. The method of claim 24, wherein the first communication node is configured to provide an interface to a core network and backhaul functionality to a third communication node configured to provide wireless backhaul functionality to one or more mobile devices, and wherein the second communication node comprises a network node in the core network.

28. The method of claim 24, wherein the first communication node comprises a network node in the core network, and wherein the second communication node is configured to provide an interface to a core network and backhaul functionality to a third communication node configured to provide wireless backhaul functionality to one or more mobile devices.

29. A wireless communications apparatus, comprising: a processor, wherein the processor is configured to implement the method of any one of claims 1 to 28.

30. A computer storage medium, comprising: code stored on the computer storage medium, which when executed by a processor causes the processor to implement the method of any one of claims 1 to 28.