Bearer mapping for integrated access and backhaul links

Abstract

The present invention provides a method for wireless communication, the method comprising receiving a signaling message from a second communication node by a first communication node, the signaling message comprising information associated with a first mapping and a second mapping. The method further comprises performing a first transmission by the first communication node using the first mapping. 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. The method further comprises performing a second transmission by the first communication node using the second mapping. The second mapping is established between multiple radio bearers and a third radio link control channel, or between multiple radio link control channels and a logical channel.

Description

Technical Field

[0001] The present invention generally relates to wireless communications, and more particularly, to a bearer mapping for integrated access and backhaul links. Background Art

[0002] Mobile communication technologies are moving the world towards an increasingly connected and networked society. The rapid growth of mobile communications and advances in technology have led to greater demands for capacity and connectivity. Other aspects, such as energy consumption, equipment cost, spectrum 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. Summary of the invention

[0003] The 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 can also be applied to support different mapping types between RLC channels and logical channels.

[0004] In one example aspect, a wireless communication method 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 a first mapping and a second mapping. The method includes performing, by the first communication node, a first transmission using the first mapping. 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. The method also includes performing, by the first communication node, a second transmission using the second mapping. The second mapping is established between a plurality of radio bearers and a third radio link control channel, or between a plurality of radio link control channels and a logical channel.

[0005] In another example aspect, a wireless communication method is disclosed. The method includes sending a signaling message from a first communication node to a second communication node. The signaling message includes information associated with a first mapping and a second mapping, wherein the information associated with the first mapping and the second mapping causes the second communication node to perform a first transmission using a 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 between a plurality of radio link control channels and the logical channel.

[0006] In another example aspect, a wireless communication method is disclosed. The method includes transmitting, from a first communication node to a second communication node, capabilities of the first communication node. The capabilities are used 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 requests (ARQ) supported by the first communication node, or placement of an adaptation layer.

[0007] In another example aspect, a wireless communication method is disclosed. The method includes receiving, by a first communication node, capabilities of a second communication node from a second communication node. The capabilities are used to indicate at least one of: one or more types of mapping options between radio bearers supported by the 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.

[0008] In yet another example aspect, a wireless communication apparatus is disclosed. The apparatus includes a processor configured to implement the above method.

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

[0010] These and other aspects are described in this document. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] Figure 1A An example of independent deployment of a user equipment (UE) and an integrated access and backhaul (IAB) node is shown;

[0012] Figure 1B An example deployment is shown, where the UE operates with an Evolved Packet Core (EPC) in a non-standalone case, and the IAB node operates with a Next Generation Core (NGC) in a standalone case;

[0013] Figure 1C An example deployment is shown in which a UE and an IAB node operate in a non-independent manner;

[0014] Figure 2 An example of control unit (CU) / data unit (DU) separation in the IAB architecture is shown;

[0015] Figure 3A An example scheme using a one-to-one mapping between UE data radio bearers (DRBs) and backhaul (BH) radio link control (RLC) channels is shown;

[0016] Figure 3B Another example scheme employing many-to-one mapping between UE DRBs and BH RLC channels is shown;

[0017] Figure 4A An example protocol stack that can be used to support both one-to-one and many-to-one mapping between UE DRBs and BH RLC channels is shown;

[0018] Figure 4B Another example protocol stack that can be used to support one-to-one mapping and many-to-one mapping between UE DRBs and BH RLC channels is shown;

[0019] Figure 4C Another example protocol stack that can be used to support both one-to-one and many-to-one mapping between UE DRBs and BH RLC channels is shown;

[0020] Figure 4D Another example protocol stack that can be used to support one-to-one mapping and many-to-one mapping between UE DRBs and BH RLC channels is shown;

[0021] Figure 4E Another example protocol stack that can be used to support both one-to-one and many-to-one mapping between UE DRBs and BH RLC channels is shown;

[0022] Figure 5 An example of a wireless communication system in which techniques according to one or more embodiments of the present technology may be applied is shown;

[0023] Figure 6 is a block diagram representation of a portion of a radio station to which one or more embodiments according to the present technology may be applied;

[0024] Figure 7 is a flow chart of a method for wireless communication according to one or more embodiments of the present technology;

[0025] Figure 8is a flowchart representation of another method for wireless communication in accordance with one or more embodiments of the present technology;

[0026] Fig. 9 is a flowchart representation of another method for wireless communication in accordance with one or more embodiments of the present technology;

[0027] Fig.10 is a flow chart of yet another method for wireless communication in accordance with one or more embodiments of the present technology. DETAILED DESCRIPTION

[0028] 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. Certain features are described using the example of a 5G wireless protocol. However, the applicability of the disclosed techniques is not limited to 5G wireless systems.

[0029] The development of a new generation of wireless communications - 5G New Radio (NR) communications - is part of the continuous mobile broadband evolution process to meet the requirements of growing network demand. NR technology imposes strict latency and reliability requirements and is expected to provide unprecedented data rates to users. The millimeter wave (mmWave) frequency band above 10 GHz therefore plays an important role. In addition, the small size of antennas at mmWaves allows very large antenna arrays with high beamforming gain, thereby overcoming the high propagation losses at such high frequencies. On the other hand, millimeter wave signals are subject to high signal attenuation and reflections, which limits the communication range of millimeter wave infrastructure.

[0030] The combination of high propagation loss and blocking issues requires high-density deployment of Next Generation Node Bases (gNBs). In such deployments, providing wired backhaul for each gNB can be expensive for network operators. Therefore, having wireless backhaul as part of the Integrated Access and Backhaul (IAB) architecture provides greater flexibility in deployment - part of the gNB is equipped with traditional fiber-like backhaul capabilities, and the rest of the gNB is wirelessly connected (optionally through multiple hops) to the fiber infrastructure.

[0031] In the IAB architecture, the communication node that supports wireless access of user equipment (UE) and wireless transmission of user plane or control plane data packets is called an IAB node. The communication access node that provides wireless backhaul function for the IAB node and has a wired connection with the core network element is called an IAB donor. The IAB donor includes an IAB donor data unit (DU) and / or an IAB control unit (CU).

[0032] The IAB architecture can support stand-alone (SA) and non-stand-alone (NSA) deployments. Figures 1A-1C An example of a deployment using the IAB architecture is shown. Figure 1A An example of SA deployment of UE and IAB node is shown. Figure 1B An example deployment is shown, in which the UE operates in NSA with the Evolved Packet Core (EPC) and the IAB node operates in SA with the Next Generation Core (NGC). Figure 1C An example deployment is shown where the UE and IAB node operate in NSA with EPC.

[0033] In addition, supporting CU / DU split deployment is an important technical feature of NR technology. Figure 2 An example of CU / DU separation in the IAB architecture is shown. In this example, the IAB node and the IAB donor include separate CU and DU logical functions. In addition, the CU may also include control plane (CP for short, the control plane in the CU is also called CU-CP) and user plane (UP for short, the user plane in the CU is also called CU-UP) logical functions.

[0034] In the case of CU / DU separation, the IAB node may provide gNB functionality or gNB-DU functionality. The IAB node may also provide a mobile termination (MT) function, which is similar to a UE function in some respects. In some embodiments, an IAB node (referred to as a child IAB node) may access another IAB node (referred to as a parent IAB node) or access an IAB donor via an air interface. User plane or control plane data packets may be transmitted 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 data packets may be sent via a multi-hop relay backhaul link between an access node and an IAB donor.

[0035] Currently, two mapping schemes between UE bearers and backhaul (BH for short) Radio Link Control (RLC for short) channels have been proposed. Figure 3A A scheme using a one-to-one mapping between UE data radio bearers (DRBs) and BH RLC channels is shown. Alternatively, Figure 3B Another mapping scheme using many-to-one mapping between UE DRB and BH RLC channel is shown. However, different services may be suitable for different mappings. For example, 1:1 mapping scheme is more suitable for VOIP service. On the other hand, N:1 mapping is more suitable for best effort service. In order to provide different services with better performance at the same time, it is necessary to support both 1:1 and N:1 mapping of UE DRB and BH RLC channel in IAB architecture.

[0036] This patent document describes techniques that can be used in various embodiments to allow for simultaneous use of 1:1 mapping and N:1 mapping between UE bearers and BH RLC channels. The techniques described herein can also be applied to support simultaneous 1:1 mapping and N:1 mapping between RLC channels and logical channels.

[0037] Figure 7 700 is a flow chart of a method 700 for wireless communication according to one or more embodiments of the present technology. The method 700 includes, at step 701, receiving a signaling message from a second communication node by a first communication node. The signaling message includes information associated with a first mapping and a second mapping. The method 700 includes, at step 702, performing a first transmission by the first communication node using the first mapping. 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. The method 700 also includes, at step 703, performing a second transmission by the first communication node using the second mapping. The second mapping is established between multiple radio bearers and a third radio link control channel, or between multiple radio link control channels and a logical channel.

[0038] Figure 8800 is a flow chart of a method 800 for wireless communication according to one or more embodiments of the present technology. The method 800 includes, at step 801, sending a signaling message from a first communication node to a second communication node. The signaling message includes information associated with a first mapping and a second mapping, wherein the information associated with the first mapping and the second mapping enables the second communication node to perform a first transmission using a 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 between a plurality of radio link control channels and the logical channel.

[0039] Fig. 9 900 is a flow chart of a method 900 for wireless communication according to one or more embodiments of the present technology. The method 900 includes, at step 901, sending capabilities of the first communication node from the first communication node to the second communication node. The capabilities are used to indicate at least one of the following: 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 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 placement of an adaptation layer.

[0040] Fig.10 1 is a flowchart representation of a method 1000 for wireless communication according to one or more embodiments of the present technology. The method 1000 includes, at step 1001, receiving, by a first communication node, capabilities of a second communication node from a second communication node. The capabilities are used to indicate at least one of the following: one or more types of mapping options between radio bearers supported by the 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 supported by the second communication node, a mapping type, or a placement of an adaptation layer.

[0041] Some examples of the disclosed technology are described in the following example embodiments.

[0042] Example 1

[0043] In order to support both 1:1 and N:1 mappings between UE bearers and RLC channels, 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 approaches are described below:

[0044] Method 1: The IAB node sends its own capability information to the IAB node owner or the Mobility Management Function (AMF) through a message. In some embodiments, the message may be a Radio Resource Control (RRC) message, an F1 message, or an Xn message.

[0045] Mode 2: The IAB donor sends capability information to the AMF via a message. In some embodiments, the message may be a Next Generation (NG) message.

[0046] In some embodiments, the capability information includes at least one of: mapping options (e.g., 1:1 mapping and / or N:1 mapping), mapping type (e.g., bearer to RLC channel mapping and / or RLC channel to logical channel mapping), adaptation layer arrangement (e.g., whether the adaptation layer is above the RLC layer or above the Media Access Control (MAC) layer), or ARQ options (end-to-end (E2E) ARQ and / or hop-by-Hop (HBH) ARQ).

[0047] Mode 3: The IAB node sends configuration information or capability information to the IAB node via a message. In some embodiments, the message may be an RRC message, an F1 message, or an Xn message.

[0048] Mode 4: AMF sends the configuration information or capability information to the IAB donor or IAB node via a message. In some embodiments, the message may be an NG message.

[0049] In some embodiments, the configuration information includes at least one of the following: mapping options (e.g., 1:1 mapping and / or N:1 mapping), mapping type (e.g., UE bearer to RLC channel mapping and / or RLC channel to logical channel mapping), adaptation layer arrangement (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 the mapping between UE bearers and RLC channels, and / or information associated with the mapping between RLC channels and logical channels. In some embodiments, the information associated with any one of the mappings may include a first identifier and a second identifier. The first identifier includes at least one of the following: an identifier of the radio bearer to which the inbound data packet belongs, an identifier of the radio link control channel to which the inbound data packet belongs, or an identifier of the logical channel to which the inbound data packet belongs. The second identifier includes at least one of the following: an identifier of the radio bearer to which the outbound data packet belongs, an identifier of the radio link control channel to which the outbound data packet belongs, or an identifier of the logical channel to which the outbound data packet belongs.

[0050] In some embodiments, each QoS flow, UE, Protocol Data Unit (PDU) session, Evolved UMTS (E-UTRAN) Radio Access Bearer (E-RAB) / radio bearer may have corresponding configuration information.

[0051] In some embodiments, the IAB node may send capability information to its parent / child IAB node. 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.

[0052] In some embodiments, the IAB donor may send capability information or configuration information to a base station (e.g., E-UTRAN NodeB, eNB for short) via an X2 interface (e.g., in a dual connectivity EN-DC deployment scenario). In some embodiments, the base station (e.g., eNB) may send capability information or configuration information to the IAB donor via an X2 interface (e.g., in a dual connectivity EN-DC deployment scenario). In some embodiments, the IAB donor exchanges capability information via an Xn interface. In some embodiments, the IAB donor exchanges configuration information via an Xn interface (e.g., during a handover process).

[0053] Example 2

[0054] In some embodiments, the supported configuration information (e.g., as specified in Embodiment 1) may be indicated without an explicit signaling message. For example, a donor or IAB node of an IAB may determine the supported configuration based on the QoS information corresponding to the QoS flow. The QoS information may include at least one of the following: a QoS Class Identifier (QCI), a QoS Flow ID (QFI), a 5G QoS Indicator (5QI), a Differentiated Services Code Point (DSCP), a priority, a delay budget, a delay critical indication, an Aggregate Bit Rate (ABR) information, or a Guaranteed Bit Rate (GBR) information. For example, a UE DRB including a GBR QoS flow may use a 1:1 mapping. A UE DRB not including a GBR QoS flow may use an N:1 mapping. In a non-CU-DU split scenario, the configuration may be determined by the UE's serving IAB node (e.g., an access IAB node). The access IAB node may send configuration information to other IAB nodes or an IAB donor.

[0055] Optionally, the IAB donor or IAB node may receive judgment criterion information from the OAM or core network element such as AMF. The IAB node may also receive criterion information from the IAB donor or parent IAB node. For example, the criterion may be one of the following: a GBR-based criterion, a QoS parameter and its corresponding configuration information, a threshold of a QoS parameter (for example, if the priority value is less than the threshold, a 1:1 mapping is used). The QoS parameter may be one of the following: QCI, QFI, 5QI, DSCP, ARP, priority, delay budget, or delay critical indication. The configuration information may be one of the following: 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 above RLC or adaptation above MAC), or ARQ options (E2E ARQ and / or HBH ARQ).

[0056] In some embodiments, the IAB donor or IAB node receives indication information from the IAB donor or a core network element (such as an AMF). In some embodiments, the indication information indicates whether 1:1 mapping and / or N:1 mapping is supported. 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 will 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.

[0057] The IAB donor may configure at least one of the following items for the access or intermediate IAB node / IAB donor DU, which may be sent via an F1 message, an RRC message, or an Xn message:

[0058] 1) Indication information. The indication information indicates whether 1:1 mapping and / or N:1 mapping is to be used. 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 an adaptation layer (e.g., whether the adaptation layer is above the RLC layer or above the MAC layer).

[0059] 2) Information for mapping between RBs and RLC channels. The information includes at least one of the following: 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.

[0060] 3) Information for mapping between RLC channels and logical channels (referred to as LCH). The information includes at least one of the following: RLC channel ID and LCID, UE RB ID and LCID, one or more RLC channel IDs and LCID, or one or more UE RB IDs and LCID. In some embodiments, UERBID is an identifier for identifying the bearer of the UE. In some embodiments, UEID and RBID are used to identify the bearer of the UE. In some embodiments, UE RB is identified by one or more Tunnel End Identifiers (TEID).

[0061] In some embodiments, the RLC channel ID is used to identify the RLC channel or the 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.

[0062] Example 3

[0063] In some embodiments, QoS information (e.g., QCI, QFI, 5QI, DSCP, priority or delay requirements, GBR related information) of a QoS flow or UE bearer or RLC channel may be used by the access IAB node / intermediate IAB node / IAB donor DU to determine the configuration information to be used. The configuration information includes at least one of the following: mapping options (such as 1:1 mapping and / or N:1 mapping), mapping type (e.g., UE bearer to RLC channel mapping and / or RLC channel to logical channel mapping), adaptation layer arrangement (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 that can be used for mapping between UE bearers and RLC channels, and / or information for mapping between RLC channels and logical channels.

[0064] In some embodiments, the access IAB node / intermediate IAB node / IAB donor DU may determine the mapping or multiplexing between the RLC channel and the LCH based on the QoS parameters. The IAB donor may configure the rules for the RLC channel to LCH mapping for the IAB node / IAB donor DU, the RLC channel-related QoS parameters (e.g., priority level, GBRQoS flow information, etc.), and the LCH-related QoS parameters (e.g., priority, priority bit rate, bucketSizeDuration, etc.). The IAB donor may configure the above information to the IAB node / IAB donor DU via an RRC message, an F1 message, or an Xn message.

[0065] Example 4

[0066] This embodiment describes an example unified design for performing 1:1 and N:1 mapping on top of the RLC layer. In this embodiment, the adaptation layer is located on top of the RLC layer and supports hop-by-hop (HBH) AQR. Figures 4A-4E An example protocol stack that can be used for such a design is shown.

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

[0068] 1. Access IAB node

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

[0070] The IAB Node ID can be one of the following:

[0071] 1) Identifier of the mobile telecommunications system (MT) portion of the IAB node, including but not limited to: Cell Radio Network Temporary Identifier (C-RNTI), C-RNTI and cell identifier, C-RNTI and base station identifier, C-RNTI and DU identifier, F1AP ID, X2AP ID, XnAP ID, S1AP ID, NGAP ID or GTP TEID; or

[0072] 2) An identifier used to identify the gNB or DU part of the IAB node, including but not limited to: DU identifier, CU identifier, base station identifier, cell identifier, physical cell identifier PCI or IP address.

[0073] Here are a few example ways to configure this mapping:

[0074] 1) The IAB donor (or IAB donor CU) configures the corresponding relationship for mapping in the UE context (eg, via F1 message). That is, the DRB of each UE is configured with DRB ID and BHRB ID / RLC channel ID / LCID / next hop IAB node ID. In this way, no additional configuration of UEID is required.

[0075] 2) The IAB donor (or IAB donor CU) configures the corresponding relationship 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 the UEID and UERBID / RLC channel ID / LCID. In this example, there is no need to configure the next hop IAB node ID.

[0076] 3) The IAB donor (or IAB donor CU) configures the UE ID / UE RB ID / RLC channel ID / LCID and the BH RBID / RLC channel ID / LCID / next hop IAB node ID.

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

[0078] For downlink transmission, the configured mapping information includes RBID / RLC channel ID / LCID and UERBID / LCID / UEID in the backhaul link. Alternatively, the access IAB node can determine the target UE and UE bearer / RLC channel / LCH based on the UERBID and other information contained in the adaptation layer of the received data packet.

[0079] 2. Intermediate IAB Node

[0080] The intermediate IAB node can determine the exit RB / RLC channel / LCH based on the entry RB / RLC channel / LCH. In this way, for uplink transmission, the IAB donor (or IAB donor CU) configures the entry RBID / RLC channel ID / LCID / optional child IAB node ID and the exit RBID / RLC channel ID / LCID / optional parent IAB node or donor DUID. For downlink transmission, the IAB donor (or IAB donor CU) configures the entry RBID / RLC channel ID / LCID / optional parent IAB node ID and the exit RBID / RLC channel ID / LCID / optional child IAB node or donor DUID.

[0081] Alternatively, the intermediate IAB node can be mapped based on the UE RB ID of the adaptation layer in the received data packet. In this way, for uplink transmission, the IAB donor (or IAB donor CU) configures the UERBID and the 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.

[0082] 3. Donor DU

[0083] The GPRS Tunneling Protocol (GTP) is a set of Internet Protocol (IP)-based communication protocols for carrying general packet radio service (GPRS) within 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) can configure the UERBID and the GTP-U tunnel identified by the GTP Tunnel Endpoint Identifier (TEID) and / or the Transport Network Layer (TNL) address. The donor DU can determine the GTP-U tunnel based on the UE RB ID in the adaptation layer.

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

[0085] For downlink transmission, the IAB donor (or IAB donor DU) maps the UE GTP-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 data packet belongs. The donor DU then adds the above information to the adaptation layer. In some embodiments, the IAB donor (or IAB donor CU) can configure at least one of the following for the donor DU: GTP-U tunnel and egress RB / RLC channel / LCH, GTP-U tunnel and UE RBID, UE RBID and egress RB / RLC channel / LCH.

[0086] The method described in the above embodiment can also be applied here.

[0087] Example 5

[0088] This embodiment describes an example unified design for performing 1:1 and N:1 mapping on top of the RLC layer. The adaptation layer is located on top of the MAC layer. End-to-end E2E or HBH ARQ is supported. Figures 4A-4B An example protocol stack that can be used for such a design is shown.

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

[0090] Example 6

[0091] This embodiment describes an example unified design for performing 1:1 and N:1 mapping above the MAC layer. The adaptation layer is located above the MAC layer. End-to-end E2E and / or HBHARQ are supported. Figures 4A-4B An example protocol stack that can be used for such a design is shown.

[0092] In this design, multiple RLC channels can be multiplexed into one logical channel. The adaptation layer performs multiplexing or demultiplexing operations and is located above the MAC layer.

[0093] If both E2EARQ and HBHARQ are supported (e.g., some UE / RB use E2EARQ and some UE / RB 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 in the two ARQ modes are different. Here are some example methods for determining the ARQ mode:

[0094] 1) Method 1: 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 can determine the ARQ mode by itself or receive a signaling message from the IAB donor CU. For uplink transmission, the access IAB node indicates the ARQ mode in the adaptation layer header. The access IAB node can determine the ARQ mode by itself based on QoS parameters such as the number of hops, latency, and reliability. The access IAB node can also determine the ARQ mode by receiving a signaling message (e.g., F1 signaling or Xn signaling) from the IAB donor or IAB donor CU.

[0095] 2) Method 2: The IAB donor may configure the RB / RLC channel / LCH and the associated ARQ mode (HBH or E2E) for the access IAB node, intermediate IAB node or IAB donor DU.

[0096] The methods described in the above Examples and Example 7 can also be applied here.

[0097] Example 7

[0098] This embodiment describes an example unified design in which 1:1 mapping and N:1 mapping are supported. N:1 mapping is performed above the RLC layer that only supports HBH ARQ mode. In this design, multiple UE bearers can be mapped to the same RLC channel mapping using N:1 mapping. N:1 mapping is performed on the adaptation layer above the RLC, and HBHARQ is used. For 1:1 mapping, E2EARQ or HBHARQ is used, and the adaptation layer is above the MAC layer. 1:1 and N:1 mapping use different protocol stacks (i.e., the location of the adaptation layer is different) and the ARQ modes can be different (HBH and / or E2E). The access / intermediate IAB nodes and IAB donors 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 is supported (e.g., E2E or HBH).

[0099] In some embodiments, for uplink transmission, 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 whether to pass the data packet to the RLC layer or the adaptation layer after MAC layer demultiplexing. The IAB donor (or IAB donor CU) can configure the RB / RLC channel / LCH and associated mapping options / mapping types / ARQ modes / adaptation layer positions to the access / intermediate IAB node and IAB donor DU. The configuration information can be configured for each QoS flow / radio bearer / RLC channel / LCH of the IAB node / IAB donor DU.

[0100] In some embodiments, for downlink transmission, 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 to pass the data packet to RLC or adaptation layer after MAC layer demultiplexing. The IAB donor can configure the RB / RLC channel / LCH and the associated mapping options / mapping types / ARQ modes / adaptation layer locations to the access / intermediate IAB nodes and IAB donor DUs. The configuration information can be configured according to QoS flow / radio bearer / RLC channel / LCH.

[0101] The method described in the above embodiment can also be applied here.

[0102] Example 8

[0103] This embodiment describes an example unified design in which 1:1 and N:1 mapping of UE bearers to RLC channels is supported. In this embodiment, 1:1 and N:1 mapping of RLC channels to logical channels are supported. 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 can be implemented at the GTP-U layer above the RLC. The mapping of 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 (above the MAC layer or above the RLC layer) or which ARQ mode is supported (for example, E2E or HBH). The methods described in the above embodiments can also be applied here.

[0104] Figure 5 An example of a wireless communication system 500 to which techniques according to one or more embodiments of the present technology may be applied is shown. 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. The base stations 505a, 505b may provide wireless services to the 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.

[0105] The core network 525 can communicate with one or more base stations 505a, 505b. The core network 525 provides connections with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 510a, 510b, 510c and 510d. The first base station 505a can provide wireless services based on a first radio access technology, and the second base station 505b can provide wireless services based on a second radio access technology. The base stations 505a and 505b can be co-located or can be installed separately in the field according to the deployment scenario. The wireless devices 510a, 510b, 510c and 510d can support a variety of different radio access technologies.

[0106] Figure 6 605 is a block diagram representation of a portion of a radio station. The radio station 605 (such as a base station or a wireless device (or UE)) may include a processor electronic device 610 (such as a microprocessor) that implements one or more wireless technologies presented in this document. The radio station 605 may include a transceiver electronic device 615 to send and / or receive wireless signals through one or more communication interfaces such as an antenna 620. The radio station 605 may include other communication interfaces for sending 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 electronic component 610 may include at least a portion of the transceiver electronic component 615. In some embodiments, the radio station 605 is used to implement at least some of the disclosed techniques, modules, or functions.

[0107] It will be appreciated that the present document discloses techniques that can be implemented into a wireless communication system to support both 1:1 and N:1 mappings between radio bearers and RLC channels and between RLC channels and logical channels, thereby providing optimal performance for different types of services.

[0108] In one example aspect, a method of wireless communication includes: receiving a signaling message by a first communication node from a second communication node. The signaling message includes information associated with a first mapping and a second mapping. The method includes performing a first transmission by the first communication node using the first mapping. 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. The method also includes performing a second transmission by the first communication node using a second mapping. The second mapping is established between multiple radio bearers and a third radio link control channel, or between multiple radio link control channels and a logical channel.

[0109] In some embodiments, an adaptation header of a data packet associated with the first transmission or the second transmission indicates at least one of: an automatic repeat request (ARQ) option, a placement of an adaptation layer, a mapping option, or a mapping type.

[0110] In some embodiments, the information associated with the first mapping or the second mapping includes a first identifier and a second identifier. The first identifier includes at least one of the following: 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, or an identifier for a logical channel to which the incoming data packet belongs. The second identifier includes at least one of the following: an identifier for a radio bearer to which an outgoing data packet belongs, an identifier for a radio link control channel to which the outgoing data packet belongs, or an identifier for a logical channel to which the outgoing data packet belongs.

[0111] 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 Services (GPRS) Tunneling Protocol User Plane (GTP-U) tunnel.

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

[0113] In some embodiments, the first protocol stack and the second protocol stack are the same. The adaptation layer is placed above the media access control 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 or hop-by-hop ARQ.

[0114] 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 protocol stack and the second protocol stack, and both the first protocol stack and the second protocol stack support hop-by-hop ARQ.

[0115] In some embodiments, the first protocol stack and the second protocol stack are different. The adaptation layer is placed above the media access control MAC layer in the first protocol stack, and the first protocol stack supports at least one of the following: 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.

[0116] In another example aspect, a method for wireless communication includes: sending a signaling message from a first communication node to a second communication node. The signaling message includes information associated with a first mapping and a second mapping, wherein the information associated with the first mapping and the second mapping causes the second communication node to perform a first transmission using a 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 multiple radio bearers and a third radio link control channel or between multiple radio link control channels and the logical channel.

[0117] In some embodiments, an adaptation header of a data packet associated with the first transmission or the second transmission indicates at least one of: an automatic repeat request (ARQ) option, a placement of an adaptation layer, a mapping option, or a mapping type.

[0118] In some embodiments, the information associated with the first mapping or the second mapping includes a first identifier and a second identifier. The first identifier includes at least one of the following: an identifier of a radio bearer to which an incoming data packet belongs, an identifier of a radio link control channel to which the incoming data packet belongs, or an identifier of 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 data packet belongs, an identifier of a radio link control channel to which the outgoing data packet belongs, or an identifier of a logical channel to which the outgoing data packet belongs.

[0119] In some embodiments, the first identifier comprises an identifier of a user equipment or a previous 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.

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

[0121] In some embodiments, the first protocol stack and the second protocol stack are the same. The adaptation layer is placed above the media access control 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 or hop-by-hop ARQ.

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

[0123] In some embodiments, the first protocol stack and the second protocol stack are different. An adaptation layer is placed 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 the adaptation layer is placed above a radio link control RLC layer in the second protocol stack, and the second protocol stack supports the hop-by-hop ARQ.

[0124] In another example aspect, a method for wireless communication includes transmitting, from a first communication node to a second communication node, capabilities of the first communication node. The capabilities are used 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.

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

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

[0127] In some embodiments, the first communication node is used to provide 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, 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 the core network, and the second communication node is used to provide 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.

[0128] In another example aspect, a method for wireless communication includes: receiving, by a first communication node, capabilities of a second communication node from a second communication node. The capabilities are used 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 an adaptation layer.

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

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

[0131] In some embodiments, 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 the second communication node comprises a network node in the core network.

[0132] In some embodiments, the first communication node comprises a network node in a core network, and the second communication node is used to provide 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.

[0133] In another example aspect, a wireless communication device comprises: a processor, wherein the processor is configured to implement any of the above methods.

[0134] In yet another example aspect, a computer storage medium is characterized by comprising: a code stored on the computer storage medium, wherein when the code is executed by a processor, the processor is caused to implement the method described above.

[0135] The disclosed and other embodiments, modules and functional operations described in this document may be implemented in digital electronic circuits, or in computer software, firmware or hardware, including the structures disclosed in this document and their structural equivalents, or in a combination 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 a data processing device or for controlling the operation of the data processing device. The computer-readable medium may be a machine-readable storage device, a machine-readable storage substrate, a memory device, a material component that affects a machine-readable propagation signal, or a combination of one or more of them. The term "data processing device" includes all devices, devices and machines for processing data, including, for example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code that constitutes a processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagation signal is an artificially generated signal, for example, a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device.

[0136] A computer program (also referred to as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and 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 may be stored in a portion of a file that stores 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 storing portions of one or more modules, subroutines, or codes). A computer program may be deployed to execute on a computer or multiple computers located at one site or distributed across multiple sites and interconnected by a communication network.

[0137] 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. These processes and logic flows can also be performed by special-purpose logic circuits (e.g., field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs)), and the apparatus can also be implemented as special-purpose logic circuits.

[0138] For example, processors suitable for executing computer programs include general and special purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data or be operably coupled to receive data from one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) or transfer data to one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) or both. 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, for example, semiconductor memory devices, such as Erasable Programmable Read Only Memory (EPROM), 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 Disk Read Only Memory (DVD-ROM). The processor and memory may be supplemented by or incorporated into a dedicated logic circuit.

[0139] Although this patent document contains many details, these details should not be interpreted as limitations on the scope of any invention or what may be claimed, but rather should be interpreted as descriptions of features that may be specific to a particular embodiment of a particular invention. Certain features described in the context of separate embodiments in this patent document may also be implemented in combination in a single embodiment. Conversely, different features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable subcombination. In addition, although features may be described above as working in certain combinations and even initially claimed, in some cases, one or more features from the claimed combination may be cut out from the combination, and the claimed combination may be directed to a subcombination or a variant of the subcombination.

[0140] Similarly, while operations are depicted in a particular order in the drawings, 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 the desired results. Furthermore, 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.

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

Claims

1. A wireless communication method, characterized in that: include: The first communication node receives a signaling message from the second communication node, wherein the signaling message includes information associated with the first mapping and the second mapping; The first communication node performs 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 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 between a plurality of radio link control channels and the logical channel; The adaptation header of the data packet associated with the first transmission or the second transmission indicates at least one of the following: an automatic repeat request ARQ option, a placement of an adaptation layer, a mapping option or a mapping type.

2. The method according to claim 1, characterized in that The information associated with the first mapping or the second mapping includes a first identifier and a second identifier, The first identifier includes at least one of the following: an identifier for a radio bearer to which the 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 The second identifier includes at least one of the following: an identifier of a radio bearer to which the output data packet belongs, an identifier of a radio link control channel to which the output data packet belongs, and an identifier of a logical channel to which the output data packet belongs.

3. The method according to claim 2, characterized in that 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.

4. The method according to claim 2, characterized in that: The first identifier or the second identifier comprises: an identifier of a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) tunnel.

5. The method according to claim 1, characterized in that 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.

6. The method according to claim 5, characterized in that The first protocol stack is the same as the second protocol stack, and An adaptation layer is arranged above the media access control MAC layer in the first protocol stack and the second protocol stack, and both the first protocol stack and the second protocol stack support at least one of the following: end-to-end automatic repeat request ARQ and hop-by-hop ARQ.

7. The method according to claim 5, characterized in that The first protocol stack is the same as the second protocol stack, and An adaptation layer is arranged above the radio link control RLC layer in the first protocol stack and the second protocol stack, and both the first protocol stack and the second protocol stack support hop-by-hop ARQ.

8. The method according to claim 5, characterized in that The first protocol stack is different from the second protocol stack, The adaptation layer is placed above the media access control MAC layer in the first protocol stack, and the first protocol stack supports at least one of the following: end-to-end ARQ, hop-by-hop ARQ, and 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.

9. A wireless communication method, comprising: sending a signaling message from the first communication node to the second communication node, wherein the signaling message includes information associated with a first mapping and a second mapping, wherein the information associated with the first mapping and the second mapping enables 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 between a plurality of radio link control channels and the logical channel; The adaptation header of the data packet associated with the first transmission or the second transmission indicates at least one of the following: an automatic repeat request ARQ option, a placement of an adaptation layer, a mapping option or a mapping type.

10. The method according to claim 9, characterized in that The information associated with the first mapping or the second mapping includes a first identifier and a second identifier, The first identifier includes at least one of the following: an identifier for a radio bearer to which the 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 The second identifier includes: an identifier of a radio bearer to which the output data packet belongs, an identifier of a radio link control channel to which the output data packet belongs, or an identifier of a logical channel to which the output data packet belongs.

11. The method according to claim 10, characterized in that The first identifier comprises an identifier of a user equipment or a previous hop communication node associated with the incoming radio bearer, and the second identifier comprises an identifier of a next hop communication node.

12. The method according to claim 10, characterized in that The first identifier or the second identifier comprises: an identifier of a General Packet Radio Service (GPRS) Tunneling Protocol User Plane (GTP-U) tunnel.

13. The method according to claim 9, characterized in that 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.

14. The method according to claim 13, characterized in that The first protocol stack is the same as the second protocol stack, and An adaptation layer is arranged above the media access control MAC layer in the first protocol stack and the second protocol stack, and both the first protocol stack and the second protocol stack support at least one of the following: end-to-end automatic repeat request ARQ and hop-by-hop ARQ.

15. The method according to claim 13, characterized in that The first protocol stack is the same as the second protocol stack, and An adaptation layer is arranged above the radio link control RLC layer in the first protocol stack and the second protocol stack, and both the first protocol stack and the second protocol stack support hop-by-hop ARQ.

16. The method according to claim 13, characterized in that The first protocol stack is different from the second protocol stack, wherein the adaptation layer is placed above the 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 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.

17. A method for wireless communication, comprising: sending, from a first communication node to a second communication node, a capability of the first communication node, The capability is used to indicate at least one of the following: one or more mapping options between a radio bearer and a radio link control channel supported by the first communication node, one or more mapping options between a radio link control and a logical channel, 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; receiving a signaling message fed back by the second communication node to the first communication node based on the capability; wherein the signaling message includes information associated with the first mapping and the second mapping; The first communication node performs 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 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.

18. The method according to claim 17, characterized in that 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.

19. The method according to claim 17, characterized in that The first communication node is configured to provide an interface to a core network and backhaul functionality to the second communication node, and the second communication node is configured to provide wireless backhaul functionality to one or more mobile devices.

20. The method according to claim 17, characterized in that 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 the second communication node comprises a network node in the core network.

21. The method according to claim 17, characterized in that The first communication node comprises a network node in a core network, and the second communication node is used to provide 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.

22. A method for wireless communication, comprising: receiving, by the first communication node, from the second communication node, a capability of the second communication node, The capability is used to indicate at least one of the following: one or more mapping options between a radio bearer and a radio link control channel supported by the second communication node, one or more mapping options between a radio link control and a logical channel 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 an adaptation layer; A first communication node sends a signaling message to a second communication node; the signaling message includes information associated with a first mapping and a second mapping, and the information associated with the first mapping and the second mapping enables 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 multiple radio bearers and a third radio link control channel or between multiple radio link control channels and the logical channel.

23. The method according to claim 22, characterized in that 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.

24. The method according to claim 22, characterized in that The first communication node is configured to provide an interface to a core network and backhaul functionality to the second communication node, and the second communication node is configured to provide wireless backhaul functionality to one or more mobile devices.

25. The method according to claim 22, characterized in that 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 the second communication node comprises a network node in the core network.

26. The method according to claim 22, characterized in that The first communication node comprises a network node in a core network, and the second communication node is used to provide 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.

27. A wireless communication device, characterized in that: include: A processor, wherein the processor is configured to implement the method according to any one of claims 1 to 26.

28. A computer storage medium, characterized in that include: 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 26.

Images