ABSTRACT
Abstract
Methods and systems for routing data through IAB nodes 201, 202 in 5G communication networks. Embodiments herein allow routing data between a UE 206 and an IAB donor 200 though IAB nodes 201, 202 using adaptation layers of the IAB donor 200 and the IAB nodes 201, 202 . The adaptation layers of the IAB donor 200 and the IAB nodes 201, 202 are configured by defining adaptation layer header and functionality. Mapping is performed between bearers/RLC channels of the UE 206 and the IAB node 202 and between bearers/RLC channels of the IAB nodes 201, 202 and the IAB donor 200 . The means to perform the mapping is specified by the adaptation layers of either the IAB donor 200 or the IAB nodes 201, 202 . The data is routed through the bearers/RLC channels. The embodiments include managing RLC layer functionality using either hop-by-hop ARQ or end-to-end ARQ.
Description
CROSS-REFERENCE TO RELATED APPLICATION(S)
This application is a National Phase Entry of PCT International Application No. PCT/KR2019/005572, which was filed on May 9, 2019, and claims priority to Indian Provisional Patent Application No. 201841017524 filed on May 9, 2018, and Indian Complete Patent Application No. 201841017524 filed on May 7, 2019, in the Indian Intellectual Property Office, the content of each of which are incorporated herein by reference.
BACKGROUND
1. Field
Embodiments herein relate to Integrated Access and Backhaul (IAB) in 5th Generation (5G) communication networks, and more particularly to methods and systems for configuring the adaptation layer for IAB donor and IAB nodes in a 5G communication network.
2. Description of the Related Art
5G New Radio (NR) cells may be deployed in a varying range of carrier frequencies. The ranges of the frequencies can be broadly divided into a frequency range 1, for cells deployed in carrier frequencies less than 6 GHz; and a frequency range 2 for cells deployed in carrier frequencies greater than 6 GHz. At higher carrier frequencies (greater than 6 GHz), the coverage area of a cell can be relatively small. The deployment of NR cells (which operate in millimeter waves) leads to a telecommunication ecosystem, wherein cells with a small coverage area are densely deployed.
In such deployments, having independent backhaul connectivity for each of the deployed cells or Random Access Network (RAN) nodes can lead to a complex and expensive topology. As a result, it is recommended to have an ecosystem, wherein only a few of the RAN nodes are having direct backhaul connectivity. The RAN nodes not having backhaul connectivity can route their traffic to the core network directly or to the core network through the RAN nodes having backhaul connectivity. The RAN nodes without backhaul connectivity can serve as relay nodes, wherein data is relayed on to other RAN nodes which have backhaul connectivity. In NR, such relay nodes can be referred to as Integrated Access Backhaul (IAB) nodes.
The IAB nodes enable flexible and dense deployment of NR cells without a proportionate increase in the density of the transport network. A diverse range of deployment scenarios can be envisioned including support for outdoor small cell deployments, indoors, or even mobile relays (e.g. on buses or trains). IAB nodes can support access and backhaul in the above-6 GHz- and sub-6 GHz spectrums.
FIG. 1 illustrates a 5G communication network, wherein NR User Equipments (UEs) are connected to an IAB donor through IAB nodes. The UEs can be connected to the IAB donor either directly or using single/multiple hops. The NR UEs can transparently connect to an IAB node using NR. Long Term Evolution (LTE) UEs can transparently connect to an IAB-node using LTE, if the IAB node supports backhauling of LTE access. The NR supports multi-hop backhauling, which can enable range extension. The multi-hop backhauling involves relay of data generated by the UE or NR Core Network (NGC) through a plurality of IAB nodes. Multi-hop backhauling can be beneficial for cells using carrier frequencies above 6 GHz, with a limited coverage area. Multi-hop backhauling further enables backhauling around obstacles; for example, buildings in urban environment for in-clutter deployments. The maximum number of hops in a deployment can depend on multiple factors such as frequency, cell density, propagation environment, traffic load, and so on. These factors are further expected to change over time. From the architectural perspective, flexibility in hop count is, therefore, desirable.
As depicted in FIG. 1 , the 5G network supporting multi-hop backhauling between the IAB nodes includes a UE, wherein the UE is connected to an IAB donor through at least one IAB node. There is backhaul connectivity between the IAB nodes and between the IAB nodes and the IAB donor. The 5G network facilitates a multi-hop environment, wherein data from an IAB node is relayed over multiple other IAB nodes, prior to arriving at the IAB donor (Donor Next Generation Node B (gNB) (DgNB)).
The IAB nodes can support gNB functionality and terminate the radio protocols of the NR radio interface, and the Next Generation (NG) and Xn (such as X2) interfaces. In addition to the gNB functionality, the IAB nodes can also support a subset of the UE functionality, e.g. physical layer, layer-2, RRC, and Non-Access Stratum (NAS) functionality, in order to wirelessly connect to the DgNB. The IAB nodes may also support the DU functionality by terminating the radio protocols of the NR radio interface, and the F1 interfaces.
SUMMARY
The principal object of the embodiments herein is to disclose methods and systems for configuring an adaptation layer of an Integrated Access and Backhaul (IAB) donor and adaptation layers of IAB nodes in 5 th Generation (5G) communication networks.
Another object of the embodiments herein is to define contents and functionalities of the adaptation layers of the IAB donor and the IAB nodes for configuring and terminating the adaptation layers.
Another object of the embodiments herein is to manage a mapping between User Equipment (UE) bearers and IAB node bearers, between IAB node bearers, and between IAB node bearers and the IAB donor bearers.
Another object of the embodiments herein is to manage a mapping between Radio Link Control (RLC) channels of the IAB donor and the IAB nodes.
Another object of the embodiments herein is to manage RLC layer functionality using hop-by-hop Automatic Repeat Request (ARQ) and end-to-end ARQ.
Accordingly, the embodiments provide methods and systems for routing data between a User Equipment (UE) and an Integrated Access and Backhaul (IAB) donor and IAB nodes in 5th Generation (5G) communication networks using adaptation layers of the IAB donor and intermediate IAB nodes. The embodiments include configuring the adaptation layers of the IAB donor and the IAB nodes. The embodiments include defining content and functionality of the adaptation layers of the IAB donor and the IAB nodes. The embodiments include mapping between bearers/RLC channels of the UE and IAB nodes and between bearers/RLC channels of the IAB nodes and the IAB donor, wherein method adopted to perform the mapping can be specified by the adaptation layers of either the IAB donor or the IAB nodes. The embodiments include routing the data through the bearers/RLC channels. The embodiments include managing RLC layer functionality using either hop-by-hop Automatic Repeat Request (ARQ) or end-to-end ARQ.
These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.
BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments herein are illustrated in the accompanying drawings, through out which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
FIG. 1 illustrates a 5G communication network, wherein New Radio (NR) User Equipments (UEs) are connected to an Integrated Access and Backhaul (IAB) donor through IAB nodes;
FIG. 2 A illustrates a 5G network, wherein an IAB donor functions as a Next Generation Node B (gNB) having a split Central Unit (CU)-Distributed Unit (DU) architecture, according to embodiments as disclosed herein;
FIG. 2 B illustrates 5G network, wherein the IAB donor functions as gNB having a split CU-DU architecture, according to embodiments as disclosed herein;
FIG. 2 C illustrates 5G network, wherein IAB nodes are having gNB capabilities, according to embodiments as disclosed herein;
FIG. 3 is a flowchart depicting a method for configuring adaptation layers of the IAB nodes and the IAB donor, according to embodiments as disclosed herein;
FIG. 4 A depicts an example, wherein the adaptation layer of the IAB donor is terminating at the CU, according to embodiments as disclosed herein;
FIG. 4 B depicts an example, wherein the adaptation layer of the IAB donor is terminating at the DU, according to embodiments as disclosed herein;
FIG. 5 depicts configuration of adaptation layer using a Radio Resource Control (RRC) configuration message, according to embodiments as disclosed herein;
FIGS. 6 A and 6 B depict example transfer of RRC messages between an IAB node and an IAB donor, according to embodiments as disclosed herein;
FIG. 7 depicts mapping of bearers of User Equipment (UE) 1 and UE 2 with IAB nodes and an IAB donor using preconfigured bearers, according to embodiments as disclosed herein;
FIG. 8 depicts mapping of Dedicated Radio Bearers (DRBs) of UE 1 and UE 2 with DRBs of the IAB nodes and an IAB donor, wherein DRBs of the UEs are directly mapped with DRBs of the IAB nodes, according to embodiments as disclosed herein;
FIG. 9 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on the number of UEs connected to an IAB node, according to embodiments as disclosed herein;
FIG. 10 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on Quality of Service (QoS) configured for different DRBs of the UEs, according to embodiments as disclosed herein;
FIG. 11 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on number of Protocol Data Unit (PDU) sessions configured for each UE, according to embodiments as disclosed herein;
FIG. 12 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein all DRBs of all UEs are mapped to a single IAB DRB, according to embodiments as disclosed herein;
FIG. 13 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein mapping of DRBs is based on multiple QoS configured for each DRB of each UE, according to embodiments as disclosed herein;
FIG. 14 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on PDU sessions configured for all UEs, according to embodiments as disclosed herein; and
FIG. 15 depicts mapping between Radio Link Control (RLC) channels of a UE and the RLC channels of the IAB nodes, RLC channels between IAB nodes, and RLC channels between an IAB node and the IAB donor, according to embodiments as disclosed herein.
DETAILED DESCRIPTION
The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
Embodiments herein disclose methods and systems for configuring adaptation layer of an Integrated Access and Backhaul (IAB) donor and IAB nodes in Fifth Generation (5G) communication networks.
Each of the IAB nodes can include a Distributed Unit (DU). The IAB donor can include a DU and a Central Unit (CU). The IAB nodes and the IAB donor can include respective adaptation layers that can be configured to perform functions relevant to routing of data from/to User Equ
CROSS-REFERENCE TO RELATED APPLICATION(S)
This application is a National Phase Entry of PCT International Application No. PCT/KR2019/005572, which was filed on May 9, 2019, and claims priority to Indian Provisional Patent Application No. 201841017524 filed on May 9, 2018, and Indian Complete Patent Application No. 201841017524 filed on May 7, 2019, in the Indian Intellectual Property Office, the content of each of which are incorporated herein by reference.
BACKGROUND
1. Field
Embodiments herein relate to Integrated Access and Backhaul (IAB) in 5th Generation (5G) communication networks, and more particularly to methods and systems for configuring the adaptation layer for IAB donor and IAB nodes in a 5G communication network.
2. Description of the Related Art
5G New Radio (NR) cells may be deployed in a varying range of carrier frequencies. The ranges of the frequencies can be broadly divided into a frequency range 1, for cells deployed in carrier frequencies less than 6 GHz; and a frequency range 2 for cells deployed in carrier frequencies greater than 6 GHz. At higher carrier frequencies (greater than 6 GHz), the coverage area of a cell can be relatively small. The deployment of NR cells (which operate in millimeter waves) leads to a telecommunication ecosystem, wherein cells with a small coverage area are densely deployed.
In such deployments, having independent backhaul connectivity for each of the deployed cells or Random Access Network (RAN) nodes can lead to a complex and expensive topology. As a result, it is recommended to have an ecosystem, wherein only a few of the RAN nodes are having direct backhaul connectivity. The RAN nodes not having backhaul connectivity can route their traffic to the core network directly or to the core network through the RAN nodes having backhaul connectivity. The RAN nodes without backhaul connectivity can serve as relay nodes, wherein data is relayed on to other RAN nodes which have backhaul connectivity. In NR, such relay nodes can be referred to as Integrated Access Backhaul (IAB) nodes.
The IAB nodes enable flexible and dense deployment of NR cells without a proportionate increase in the density of the transport network. A diverse range of deployment scenarios can be envisioned including support for outdoor small cell deployments, indoors, or even mobile relays (e.g. on buses or trains). IAB nodes can support access and backhaul in the above-6 GHz- and sub-6 GHz spectrums.
FIG. 1 illustrates a 5G communication network, wherein NR User Equipments (UEs) are connected to an IAB donor through IAB nodes. The UEs can be connected to the IAB donor either directly or using single/multiple hops. The NR UEs can transparently connect to an IAB node using NR. Long Term Evolution (LTE) UEs can transparently connect to an IAB-node using LTE, if the IAB node supports backhauling of LTE access. The NR supports multi-hop backhauling, which can enable range extension. The multi-hop backhauling involves relay of data generated by the UE or NR Core Network (NGC) through a plurality of IAB nodes. Multi-hop backhauling can be beneficial for cells using carrier frequencies above 6 GHz, with a limited coverage area. Multi-hop backhauling further enables backhauling around obstacles; for example, buildings in urban environment for in-clutter deployments. The maximum number of hops in a deployment can depend on multiple factors such as frequency, cell density, propagation environment, traffic load, and so on. These factors are further expected to change over time. From the architectural perspective, flexibility in hop count is, therefore, desirable.
As depicted in FIG. 1 , the 5G network supporting multi-hop backhauling between the IAB nodes includes a UE, wherein the UE is connected to an IAB donor through at least one IAB node. There is backhaul connectivity between the IAB nodes and between the IAB nodes and the IAB donor. The 5G network facilitates a multi-hop environment, wherein data from an IAB node is relayed over multiple other IAB nodes, prior to arriving at the IAB donor (Donor Next Generation Node B (gNB) (DgNB)).
The IAB nodes can support gNB functionality and terminate the radio protocols of the NR radio interface, and the Next Generation (NG) and Xn (such as X2) interfaces. In addition to the gNB functionality, the IAB nodes can also support a subset of the UE functionality, e.g. physical layer, layer-2, RRC, and Non-Access Stratum (NAS) functionality, in order to wirelessly connect to the DgNB. The IAB nodes may also support the DU functionality by terminating the radio protocols of the NR radio interface, and the F1 interfaces.
SUMMARY
The principal object of the embodiments herein is to disclose methods and systems for configuring an adaptation layer of an Integrated Access and Backhaul (IAB) donor and adaptation layers of IAB nodes in 5 th Generation (5G) communication networks.
Another object of the embodiments herein is to define contents and functionalities of the adaptation layers of the IAB donor and the IAB nodes for configuring and terminating the adaptation layers.
Another object of the embodiments herein is to manage a mapping between User Equipment (UE) bearers and IAB node bearers, between IAB node bearers, and between IAB node bearers and the IAB donor bearers.
Another object of the embodiments herein is to manage a mapping between Radio Link Control (RLC) channels of the IAB donor and the IAB nodes.
Another object of the embodiments herein is to manage RLC layer functionality using hop-by-hop Automatic Repeat Request (ARQ) and end-to-end ARQ.
Accordingly, the embodiments provide methods and systems for routing data between a User Equipment (UE) and an Integrated Access and Backhaul (IAB) donor and IAB nodes in 5th Generation (5G) communication networks using adaptation layers of the IAB donor and intermediate IAB nodes. The embodiments include configuring the adaptation layers of the IAB donor and the IAB nodes. The embodiments include defining content and functionality of the adaptation layers of the IAB donor and the IAB nodes. The embodiments include mapping between bearers/RLC channels of the UE and IAB nodes and between bearers/RLC channels of the IAB nodes and the IAB donor, wherein method adopted to perform the mapping can be specified by the adaptation layers of either the IAB donor or the IAB nodes. The embodiments include routing the data through the bearers/RLC channels. The embodiments include managing RLC layer functionality using either hop-by-hop Automatic Repeat Request (ARQ) or end-to-end ARQ.
These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.
BRIEF DESCRIPTION OF THE DRAWINGS
Embodiments herein are illustrated in the accompanying drawings, through out which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
FIG. 1 illustrates a 5G communication network, wherein New Radio (NR) User Equipments (UEs) are connected to an Integrated Access and Backhaul (IAB) donor through IAB nodes;
FIG. 2 A illustrates a 5G network, wherein an IAB donor functions as a Next Generation Node B (gNB) having a split Central Unit (CU)-Distributed Unit (DU) architecture, according to embodiments as disclosed herein;
FIG. 2 B illustrates 5G network, wherein the IAB donor functions as gNB having a split CU-DU architecture, according to embodiments as disclosed herein;
FIG. 2 C illustrates 5G network, wherein IAB nodes are having gNB capabilities, according to embodiments as disclosed herein;
FIG. 3 is a flowchart depicting a method for configuring adaptation layers of the IAB nodes and the IAB donor, according to embodiments as disclosed herein;
FIG. 4 A depicts an example, wherein the adaptation layer of the IAB donor is terminating at the CU, according to embodiments as disclosed herein;
FIG. 4 B depicts an example, wherein the adaptation layer of the IAB donor is terminating at the DU, according to embodiments as disclosed herein;
FIG. 5 depicts configuration of adaptation layer using a Radio Resource Control (RRC) configuration message, according to embodiments as disclosed herein;
FIGS. 6 A and 6 B depict example transfer of RRC messages between an IAB node and an IAB donor, according to embodiments as disclosed herein;
FIG. 7 depicts mapping of bearers of User Equipment (UE) 1 and UE 2 with IAB nodes and an IAB donor using preconfigured bearers, according to embodiments as disclosed herein;
FIG. 8 depicts mapping of Dedicated Radio Bearers (DRBs) of UE 1 and UE 2 with DRBs of the IAB nodes and an IAB donor, wherein DRBs of the UEs are directly mapped with DRBs of the IAB nodes, according to embodiments as disclosed herein;
FIG. 9 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on the number of UEs connected to an IAB node, according to embodiments as disclosed herein;
FIG. 10 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on Quality of Service (QoS) configured for different DRBs of the UEs, according to embodiments as disclosed herein;
FIG. 11 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on number of Protocol Data Unit (PDU) sessions configured for each UE, according to embodiments as disclosed herein;
FIG. 12 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein all DRBs of all UEs are mapped to a single IAB DRB, according to embodiments as disclosed herein;
FIG. 13 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein mapping of DRBs is based on multiple QoS configured for each DRB of each UE, according to embodiments as disclosed herein;
FIG. 14 depicts mapping of the DRBs of UE 1 and UE 2 with the DRBs of the IAB nodes and the IAB donor, wherein the mapping is based on PDU sessions configured for all UEs, according to embodiments as disclosed herein; and
FIG. 15 depicts mapping between Radio Link Control (RLC) channels of a UE and the RLC channels of the IAB nodes, RLC channels between IAB nodes, and RLC channels between an IAB node and the IAB donor, according to embodiments as disclosed herein.
DETAILED DESCRIPTION
The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
Embodiments herein disclose methods and systems for configuring adaptation layer of an Integrated Access and Backhaul (IAB) donor and IAB nodes in Fifth Generation (5G) communication networks.
Each of the IAB nodes can include a Distributed Unit (DU). The IAB donor can include a DU and a Central Unit (CU). The IAB nodes and the IAB donor can include respective adaptation layers that can be configured to perform functions relevant to routing of data from/to User Equipments (UEs) connected to the DUs of the IAB nodes and the IAB donor; and forwarding data of the UEs through IAB nodes, if the UE is connected to the IAB donor in one or more hops. Each IAB node can be identified by a unique DU Identity (ID), wherein the IAB node can use the DU ID for interfacing the IAB nodes to the CU for performing Control Plane (CP) and User Plane (UP) functionalities. The IAB node can connect to the CU using at least one of a F1-AP or F1*-AP interface for exchanging CP messages. The IAB nodes can connect to the DU of the IAB donor using at least one of a F1-U or F1*-U interface for exchanging UP data. The F1-U or F1*-U interface can be established during the IAB node establishment procedure. The IAB nodes can be identified using their DU ID for all classifications. Each IAB node F1-U or F1*-U can be identified by using individual General Packet Radio Service (GPRS) Tunneling Protocol (GTP)-U tunnel endpoint identifiers such as an Internet Protocol (IP) address. The adaptation layer allows mapping of data from various streams (bearers) through IAB nodes.
For sending CP messages in downlink, the CU can forward the CP messages to the DU of the IAB donor over the F1*-AP interface between the CU and the DU of the IAB donor. Consider that the CP messages are to be sent to a UE through IAB nodes to a DU of an IAB node connected to the UE. Each of the IAB nodes includes a DU ID. The CU can include the DU ID of an IAB node (acting as a relay node), connected to the DU of the IAB donor, in the F1*-AP header. The DU of the IAB donor can receive the CP messages along with the F1*-AP header. The DU of the IAB donor can parse the F1*-AP header and identify that the CP message is to be forwarded over New Radio (NR) backhaul link towards the IAB node acting as a relay. The adaptation layer in the DU of the IAB donor can further encapsulate the CP message and include an adaptation layer (which can include the DU ID of the IAB node acting as a relay) on top of the F1*-AP message and forward the F1*-AP message to the IAB node (acting as a relay) using a protocol stack at the DU of the IAB donor.
The adaptation layer message can be forwarded using SRBs between IAB nodes if SRBs are configured between the IAB nodes, and between the IAB nodes and the IAB donor. Based on the reception of the adaptation layer message (packet) over a NR backhaul link by the subsequent IAB node, the IAB node can determine whether to forward the packet to the subsequent IAB node or identify the packet as meant for its DU based on information (destination or recipient DU ID) present in the adaptation header.
If SRBs between UEs and IAB nodes, between IAB nodes, and between IAB nodes and IAB donor are not supported, then the CP message can be forwarded to the subsequent IAB node over a DRB, wherein the DRB used for forwarding can have the highest priority amongst other DRBs between the IAB nodes. The F1*-AP message can be processed as a payload. Based on the information such as destination DU ID in the adaptation layer header, the CP message can be forwarded to the subsequent IAB node or terminated at the recipients IAB node.
For transfer of a CP message in uplink, a Radio Resource Control (RRC) message can be generated from a UE and sent to the DU of an IAB node connected to the UE using a NR access link. The DU of the IAB node can forward the CP message to the CU by mapping the CP message either over the SRB or a special DRB. The adaptation layer header can ensure that the IAB node is able to guarantee the required QoS for the CP (RRC) message packet in the special DRB. When the CP message is received at a UP interface of the DU of the IAB donor, the adaptation layer can map the UP message from the F1*-U to F1*-AP interface for routing the CP packet to the CU. The CU can process the CP message (as if it is) received from the UE.
For UP data in downlink, received over the F1*-U interface between the CU and the DU of the IAB donor, the UP data can be forwarded by the DU of the IAB donor based on the GTP-U ID. The UP data can be encapsulated with an adaptation layer header and then mapped to a DRB established between the DU of the IAB donor and the IAB nodes. On reception of the UP data at an IAB node, the information in the header of the adaptation layer enables the IAB node to route the received UP data packets to subsequent IAB nodes or forward the UP data packets to a particular UE connected to the IAB node.
For UP data received in uplink from a UE connected to an IAB node, the IAB node can processes the UP data and forward the UP data to subsequent IAB nodes. In an embodiment, a GTP-U packet can be prepared at the IAB Node DU and forwarded over the subsequent IAB links as simple payload. In an embodiment, the GTP-U packet can be prepared at the DU of the IAB donor. The IAB node can encapsulate the UP data using an adaptation layer header and forwards the adaptation layer packet to a subsequent IAB node. The IAB nodes that receive the adaptation layer packet from other IAB nodes in the uplink, can forward the adaptation layer packet to the subsequent IAB nodes. When the DU of the IAB donor receives the adaptation layer packet, the DU can route the packet over the F1*-U interface with the CU.
The header of the adaptation layer can be configured with information such as, but not limited to, UE ID, DRB ID, destination DU ID, source DU ID, path/route ID (if route is configurable), QFI (for QoS requirement), indication of SRB/Dedicated Radio Bearer (DRB), and so on. As all uplink data is to be routed to the DU of the IAB donor, the uplink adaptation layer header can be simplified.
As the IAB nodes may need to route a large number of data streams, the embodiments herein disclose assigning priorities amongst the data streams for managing routing decisions. The priorities can be assigned, if the amount of available resources over the backhaul links between the IAB nodes is limited.
As the number of UEs connected to an IAB node can be more than the number of DRBs available at the IAB node, the embodiments herein disclose scheduling the routing of data of different UEs by mapping DRBs of the UEs with the DRBs of the IAB nodes and DRBs of the UEs with the DRBs of the IAB donor. Independent of the method adopted to perform bearer mapping, the adaptation layer can include information about QoS requirement of different UE DRBs as QoS Flow ID (QFI) value, in order to schedule the data of the UEs on subsequent backhaul links.
For satisfying the QoS requirements of data of the UEs in UE DRBs, suitable methods such as one-to-one mapping (A UE DRB can be mapped with a IAB node DRB, i.e., when a DRB is established at a UE, a corresponding DRB is also established over all the IAB links supporting that UE), QoS mapping (An IAB node, connected to the UE, maps UE DRBs with similar QoS requirements to an IAB DRB by multiplexing data in the UE DRBs with similar QoS requirements over a single IAB DRB), and mapping UE DRBs with preconfigured IAB node DRBs can be used for supporting the QoS requirements.
The adaptation layer header can include the QoS requirement information for UP and CP data that is to be forwarded over the IAB NR access and backhaul links. In an embodiment, the QoS requirement information can be included in the routing information available at each of the IAB nodes. For transfer of UP and CP data in downlink, the adaptation layer at the IAB donor can update a field indicating the QoS requirement for each UP and CP data packet. For routing data in uplink, the adaptation layer header can be prepared at the IAB node (to which UE is connected to), and the QoS requirement can be updated by the same IAB node.
The adaptation layer of the IAB nodes can be placed above the Radio Link Control (RLC) or Medium Access Control (MAC) layers. It is necessary to provide RLC functionalities such as Automatic Repeat Request (ARQ) and segmentation as per the NR release-15 specification. In a standard RLC deployment, the RLC layer can deliver data directly to Packet Data Convergence Protocol (PDCP) layer. However, as the adaptation layer is responsible for managing the routing and scheduling functionalities, the RLC layer can deliver the data to the adaptation layer, which is further forwarded to other IAB node using subsequent hops.
The point of termination of the CP/UP data, forwarded across the IAB nodes, can be either at a UE or a Next Generation Node B (gNB). In an embodiment herein, the IAB node may support full protocol stack functionality. In an embodiment herein, the IAB node may not support full protocol stack functionality. As intermediate IAB nodes (from the perspective of a UE connected to an IAB node) are connected to each other using NR backhaul links, it may not be possible to guarantee the best possible conditions at the backhaul links. Also, based on the number of UEs connected to a particular IAB node, it may also not be possible to schedule transfer of data to a subsequent IAB node due to congestion. Therefore, RLC segmentation may/may not be supported between the IAB nodes.
ARQ between a UE and a DU can be supported using hop-by-hop ARQ (between the UE and the IAB nodes, between the IAB nodes, and between the IAB node and the IAB donor), and end-to-end ARQ (between the UE and the DU of the IAB donor).
When the connection between a UE and the Next Generation Core (NGC) is established through a plurality of IAB nodes over NR Backhaul, the expected latency may not be achieved. In case of end-to-end ARQ, the latency can be low. If there is data loss at any of the backhaul links, there can be redundant retransmissions over all backhaul links in order to recover the data. As the ARQ is performed between RLC entities of the UE and IAB donor DU, the RLC entities of the intermediate IAB nodes may use the same procedure for performing RLC Segmentation and Sequence Number (SN) assignment as the UE and the IAB donor.
If end-to-end ARQ is supported, then the adaptation layer can maintain mapping between an original RLC SN to a new RLC SN and process ARQ feedback from a UE to the IAB donor DU. The adaptation layer can request for the retransmissions of actual RLC Protocol Data Units (PDUs) or segment PDUs from the IAB donor DU. If there are multiple hops involved between the UE and the IAB donor, the embodiments herein disclose minimizing latency by preventing redundant retransmission, if the RLC PDUs are received correctly till a particular IAB node. In such a case, retransmissions from the Donor DU can be avoided. In such scenarios, the RLC PDUs for all the UEs may be buffered at each IAB node, and acknowledgements from all UEs may be relayed for each hop.
If hop-by-hop ARQ is supported, then the intermediate IAB nodes can follow RLC functionalities and RLC SN assignment independently. There RLC entities of the IAB nodes may not have information of the RLC mapping of the previous and subsequent IAB nodes or the IAB donor. The ARQ and data recovery can be performed at each hop independently. The data (RLC PDUs) forwarded by an IAB node is stored in a buffer until the RLC entity of the subsequent IAB node acknowledges the reception of the data.
Referring now to the drawings, and more particularly to FIGS. 2 a through 15 , where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
FIG. 2 A illustrates a 5G network, wherein an IAB donor 200 functioning as gNB is having a split CU-DU architecture, according to embodiments as disclosed herein. The IAB- donor 200 can be considered as a Random Access Node (RAN) node, which can act as an interface between UEs ( 204 , 205 and 206 ) and an NGC 203 . The IAB donor 200 can provide wireless backhauling functionality to the IAB nodes
201 , 202 . The IAB nodes
201 , 202 can be considered as RAN nodes sharing a wireless NR Uu access link with the UEs
205 and 206 respectively. The IAB nodes
201 , 202 can also be considered as UEs that can relay NR access traffic across wireless NR Uu backhaul links with the IAB donor 200 .
As depicted in FIG. 2 A , the IAB node 202 can act as a UE for the IAB node 201 , and the IAB node 201 can act as a UE for the IAB donor 200 . The UE part of the IAB nodes
201 , 202 can be referred to as Mobile Terminal (MT). The DUs of the IAB nodes
201 , 202 can act as the RAN node. The IAB nodes
201 , 202 act as RAN nodes to the UEs
205 and 206 respectively. As the IAB donor 200 is a gNB (as the IAB donor 200 includes both CU and DU), the UE 204 connected to the IAB donor 200 can be considered to be connected to the gNB. The IAB nodes
201 , 202 can comprise the functionality and protocol stack of both a RAN node and a UE. The MT of the IAB node 202 can terminate the radio interface layers of the backhaul Uu interface toward the IAB node 201 . The MT of the IAB node 201 can terminate the radio interface layers of the backhaul Uu interface toward the IAB donor 200 .
The IAB nodes
201 , 202 may function as a DU or have full gNB functionality. For the architecture depicted in FIG. 2 B , the IAB nodes
201 , 202 functions as DU only. The UEs in a NR network can communicate with the IAB donor 200 using either a single hop relay, a multiple hop relay, or directly. The UE 206 can communicate with the IAB donor 200 through one or more hops (through IAB nodes 202 and 201 ). The UE 205 can communicate with the IAB donor 200 through a single hop (through the IAB node 201 ). The UE 204 can communicate with the IAB donor 200 directly. The IAB nodes
201 , 202 are connected to each other and with the IAB donor 200 through NR backhaul links. The IAB nodes
201 , 202 can use the NR backhaul links to relay access traffic from multiple UEs
205 , 206 connected to the IAB nodes
201 , 202 . The link between the UEs
205 , 206 with the IAB nodes
201 , 202 respectively, and the UE 204 and the IAB donor 200 are the NR access links.
The RRC and PDCP protocol stack are included in the CU. The RLC, MAC, physical layer (PHY) and Radio Frequency (RF) are located in the DUs of the IAB nodes
201 , 202 . The IAB donor 200 and the IAB nodes
201 , 202 include an adaption layer. The adaptation layer of the IAB donor 200 can be included in either the DU or the CU. The adaptation layer can include information such as, but not limited to, UE ID, UE/IAB bearer ID, source DU ID (for uplink), destination DU ID (for downlink), path (route) ID (if the route is configurable), Quality of Service (QoS) information, indication for SRB and DRB, and so on.
The adaptation layer can manage routing and forwarding the data across the backhaul interfaces between the IAB nodes
201 , 202 , and between the IAB node 201 and the IAB donor 200 . The adaptation layer in the IAB nodes
201 , 202 and the IAB donor 200 can manage mapping between bearers/RLC channels of the individual UEs
205 , 206 and particular IAB nodes
201 , 202 connected to the UEs
205 , 206 , mapping between bearers/RLC channels of the IAB nodes
201 , 202 , mapping between bearers/RLC channels of the IAB node 201 and the IAB donor 200 , and mapping between UP PDUs and backhaul RLC channels (RLC channel of the IAB nodes
201 , 202 , and the IAB donor 200 ). The adaptation layer can identify bearers belonging to a specific UE based on UE ID and UE bearer ID (included in the adaptation layer) for a particular PDU. The adaptation layer can include relevant QoS information for different services provided to the UEs ( 204 , 205 , 206 ). The adaptation layer can manage QoS enforcement on the downlink and the uplink on the NR backhaul link.
The IAB donor 200 can manage configuration and reconfiguration of the adaptation layer using the adaptation layer included in the CU, so that the adaptation layer is enabled to perform the designated functionalities. In an embodiment, the configuration of the adaptation layer involves configuring the header of the adaptation layer using information such as, but not limited to, mapping mechanism between the UE bearers/RLC channels, route ID and IAB node ID for a UE, Internet Protocol (IP address) of a UE (in case GTP-U is replaced), QoS information of a UE, UE context, and so on. If the adaptation layer is included in the DU of the IAB donor 200 , the IAB nodes
201 , 202 can manage the configuration and reconfiguration of the respective adaptation layers. The IAB donor 200 can share relevant information to the IAB nodes
201 , 202 for configuring the respective adaptation layers.
The operation of DU of the IAB donor 200 can be controlled by the CU. The CU and DU have F1-AP and F1-U interfaces for communicating with each other. The F1-AP interface is used to share the CP information between the CU and the DU. The F1-U interface is used to share UP messages with the IAB nodes
201 , 202 . The DUs of the IAB nodes
201 , 202 can be connected to the CU of the IAB donor 200 using a logical F1* interface. The IAB donor 200 can communicate relevant information pertaining to configuration of the adaptation layer, routing, and attach or detach of the UEs to the IAB nodes
201 , 202 ; using the F1* interface.
In an embodiment, the DUs of the IAB nodes 201 , 202 (acting as RAN node) can include the, RLC, MAC and PHY layers of the NR protocol stack. When an IAB node (consider 201 ) acts as a UE for carrying data generated by the IAB node 201 or for receiving data terminating on the IAB node 201 , the MT of the IAB node 201 can utilize the UE protocol stack, i.e., RRC, RLC, MAC and PHY layers, to relay control plane and user plane information through SRBs and DRBs. The adaptation layers of the IAB nodes
201 , 202 , and the IAB donor 200 can coordinate between the respective DUs and MTs. The MTs of the IAB nodes
201 , 202 can sustain Non-Access Stratum (NAS) connectivity to the core network (NGC 103 ). The MTs of the IAB nodes
201 , 202 can further sustain a PDU session through the NGC 103 to provide connectivity for different services availed by the UEs
205 , 206 .
Each IAB node can determine an IAB node at which a UE terminates. The IAB nodes can determine the terminating point of the UEs through parameters such as UE ID, UE bearer ID, routing information, and so on, shared by the CU of the IAB donor. The parameters can be indicated on a table (including information for managing adaptation layer functionality) provided by the IAB donor or based on the parameters available at IAB nodes.
For each packet generated by the adaptation layer, information (such as the UE ID, the IAB node route ID, and so on) can be added to the packets by the adaptation layer. Alternatively, routing between the different IAB nodes can be performed based on the UE bearer ID.
FIG. 2 B illustrates a 5G network, wherein the IAB donor 200 functions as a gNB and has a split CU-DU architecture, according to embodiments as disclosed herein. In the architecture depicted in FIG. 2 B , the CU of the IAB donor 200 has User Plane Function (UPF) embedded in the IAB donor 200 . The adaptation layer can be included in the IAB nodes
201 , 202 , and the IAB donor 200 for enabling data routing and forwarding. The MT stacks in each of the IAB nodes
201 , 202 can establish a PDU session with the UPF included in the CU of the IAB donor</figure-callout
CLAIMS
Claims ( 16 )
The invention claimed is:
1. A method for routing data by an integrated access and backhaul (IAB) donor communicating with a relaying node in a wireless communication system, the method comprising:
configuring a backhaul radio link control (RLC) channel by a central unit of the IAB donor;
configuring routing information included in a header of a packet in an adaptation layer, the packet mapped to the backhaul RLC channel, and the adaptation layer enabling data routing through a first backhaul link; and
transmitting, based on the routing information, the packet including the data for a user equipment to the relaying node, the relaying node supporting a wireless access link to the user equipment and a second backhaul link to another relaying node,
wherein the packet comprises user plane (UP) data or control plane (CP) data, and the UP data and the CP data are routed through different backhaul RLC channels.
2. The method of claim 1 , wherein the relaying node and the another relaying node are IAB nodes, and
wherein each of the IAB donor and the IAB nodes include the adaptation layer.
3. The method of claim 1 , wherein the routing information includes a routing ID associated with the adaptation layer of the relaying node.
4. The method of claim 1 , wherein the header includes at least one of identification information of a destination relaying node, a path ID indicating a path which the packet is to be forwarded to the destination relaying node, and quality of service (QoS) related information.
5. An integrated access and backhaul (IAB) donor for communicating with a relaying node in a wireless communication system, the IAB donor comprising:
a memory; and
at least one processor coupled with the memory and configured to:
configure a backhaul radio link control RLC channel by a central unit of the IAB donor;
configure routing information included in a header of a packet in an adaptation layer, the packet mapped to the backhaul RLC channel, and the adaption layer enabling data routing through a first backhaul link; and
transmit, based on the routing information, the packet including the data for a user equipment to a relaying node, the relaying node supporting a wireless access link to the user equipment and a second backhaul link to another relaying node,
wherein the packet comprises user plane (UP) data or control plane (CP) data, and the UP data and the CP data are routed through different backhaul RLC channels.
6. The IAB Donor of claim 5 , wherein the relaying node and the another relaying node are IAB nodes, and
wherein each of the IAB donor and the IAB nodes include the adaptation layer.
7. The IAB donor of claim 5 , wherein the routing information includes a routing ID associated with the adaptation layer of the relaying node.
8. The IAB donor of claim 5 , wherein the header includes at least one of identification information of a destination relaying node, a path ID indicating a path which the packet is to be forwarded to the destination relaying node, and quality of service (QoS) related information.
9. A method for routing data by a relaying node communicating with an integrated access and backhaul (IAB) donor or another relaying node in a wireless communication system, the method comprising:
obtaining, from the IAB donor, routing information included in a header of a packet in an adaptation layer, the packet mapped to a backhaul radio link control (RLC) channel configured by a central unit of the IAB donor, the adaptation layer enabling data routing through a first backhaul link; and
transmitting, based on the routing information, the packet including the data for a user equipment to the other relaying node or a user equipment, the relaying node supporting a wireless access link to the user equipment and a second backhaul link to the another relaying node,
wherein the packet comprises user plane (UP) data or control plane (CP) data, and the UP data and the CP data are routed through different backhaul RLC channels.
10. The method of claim 9 , wherein the relaying node and the another relaying node are TAB nodes, and
wherein each of the IAB donor and the TAB nodes include the adaptation layer.
11. The method of claim 9 , wherein the routing information includes a routing ID associated with the adaptation layer of the relaying node.
12. The method of claim 9 , wherein the header includes at least one of identification information of a destination relaying node, a path ID indicating a path which the packet is to be forwarded to the destination relaying node, and quality of service (QoS) related information.
13. A relaying node for communicating with an integrated access and backhaul (IAB) donor or another relaying node in a wireless communication system, the relaying node comprising:
a memory; and
at least one processor coupled with the memory and configured to:
obtain, from the IAB donor, routing information included in a header of a packet in an adaptation layer, the packet mapped to a backhaul radio link control (RLC) channel configured by a central unit of the IAB donor, the adaptation layer enabling data routing through a first backhaul link;
transmit, based on the routing information, the packet including the data for a user equipment to the another relaying node or the user equipment, the relaying node supporting a wireless access link to the user equipment and a second backhaul link to the another relaying node,
wherein the packet comprises user plane (UP) data or control plane (CP) data, and the UP data and the CP data are routed through different backhaul RLC channels.
14. The relaying node of claim 13 , wherein the relaying node and the another relaying node are IAB nodes, and
wherein each of the IAB donor and the IAB nodes include the adaptation layer.
15. The relaying node of claim 13 , wherein the routing information includes a routing ID associated with the adaptation layer of the relaying node.
16. The relaying node of claim 13 , wherein the header includes at least one of identification information of a destination relaying node, a path ID indicating a path which the packet is to be forwarded to the destination relaying node, and quality of service (QoS) related information.
US17/053,910
2018-05-09
2019-05-09
Methods and systems for routing data through IAB nodes in 5G communication networks
Active
US11800429B2
( en )
Applications Claiming Priority (3)
Application Number
Priority Date
Filing Date
Title
IN201841017524
2018-05-09
IN201841017524
2019-05-07
PCT/KR2019/005572
WO2019216670A1
( en )
2018-05-09
2019-05-09
Methods and systems for routing data through iab nodes in 5g communication networks
Publications (2)
Publication Number
Publication Date
US20210243672A1
US20210243672A1 ( en )
2021-08-05
US11800429B2
true
US11800429B2 ( en )
2023-10-24
Family
ID=68466621
Family Applications (1)
Application Number
Title
Priority Date
Filing Date
US17/053,910
Active
US11800429B2
( en )
2018-05-09
2019-05-09
Methods and systems for routing data through IAB nodes in 5G communication networks
Country Status (4)
Country
Link
US
( 1 )
US11800429B2
( en )
EP
( 1 )
EP3756383A4
( en )
CN
( 1 )
CN112106404B
( en )
WO
( 1 )
WO2019216670A1
( en )
Cited By (1)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20230083708A1
( en )
*
2020-02-20
2023-03-16
Telefonaktiebolaget Lm Ericsson (Publ)
Backhaul Adaptation Protocol Path Identity for Fair Scheduling in an Integrated Access Backhaul Node
Families Citing this family (35)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
CN110475368B
( en )
*
2018-05-10
2022-12-20
ä¸å ´é讯è¡ä»½æéå ¬å¸
Information transmission method and device
CN110475267B
( en )
2018-05-11
2021-09-17
å为ææ¯æéå ¬å¸
Configuration method, data transmission method and device
US11419033B2
( en )
*
2018-06-19
2022-08-16
Sony Corporation
Methods, wireless communications networks and infrastructure equipment
GB2576204B
( en )
*
2018-07-27
2021-02-17
Samsung Electronics Co Ltd
Operation of automatic repeat request (ARQ)
WO2020022849A1
( en )
*
2018-07-27
2020-01-30
Samsung Electronics Co., Ltd.
Method and apparatus for wireless communication of wireless node in wireless communication system
KR20200013576A
( en )
*
2018-07-30
2020-02-07
주ìíì¬ ì¼ì´í°
Method for flow control for 5G wireless relay and Apparatuses thereof
WO2020029196A1
( en )
*
2018-08-09
2020-02-13
Zte Corporation
Methods, apparatus and systems for integrated access and backhaul bearer management
EP3830977B1
( en )
*
2018-08-10
2023-06-14
Ofinno Technologies, LLC
Wireless backhaul link information
GB2581121B
( en )
*
2018-10-31
2021-06-02
Tcl Communication Ltd
Bearer mapping in a wireless communications network
US12035381B2
( en )
*
2019-03-26
2024-07-09
Apple Inc.
Link establishment in relay nodes
WO2020222198A1
( en )
*
2019-05-02
2020-11-05
Telefonaktiebolaget Lm Ericsson (Publ)
Enabling uplink routing that supports multi-connectivity in integrated access backhaul networks
CN114009138B
( en )
*
2019-05-02
2024-12-10
çå ¸ç±ç«ä¿¡æéå ¬å¸
Bearer mapping in IAB node
EP3997929B1
( en )
*
2019-07-09
2023-04-26
Telefonaktiebolaget Lm Ericsson (Publ)
Mapping information for integrated access and backhaul
WO2021006783A1
( en )
*
2019-07-09
2021-01-14
Telefonaktiebolaget Lm Ericsson (Publ)
Mapping information for integrated access and backhaul
WO2021019921A1
( en )
*
2019-07-29
2021-02-04
æ¥æ¬é»æ°æ ªå¼ä¼ç¤¾
Master node, secondary node, and method thereof
WO2021019940A1
( en )
2019-07-29
2021-02-04
æ¥æ¬é»æ°æ ªå¼ä¼ç¤¾
Master node, secondary node, and method for same
CA3147811A1
( en )
*
2019-08-15
2021-02-18
Telefonaktiebolaget Lm Ericsson (Publ)
Mapping between ingress and egress backhaul rlc channels in integrated access backhaul (iab) networks
US11751100B2
( en )
*
2019-09-10
2023-09-05
Intel Corporation
Techniques for integrated access and backhaul (IAB) nodes
JP7357158B2
( en )
*
2019-11-08
2023-10-05
ãã¬ããªã³ã¢ã¯ãã¼ãã©ã²ãã ã¨ã«ã¨ã ã¨ãªã¯ã½ã³ï¼ããã«ï¼
Default path assignment in IAB network
WO2021097678A1
( en )
*
2019-11-19
2021-05-27
å为ææ¯æéå ¬å¸
Access and backhaul control method and apparatus
US12615571B2
( en )
2019-12-31
2026-04-28
Lenovo (Beijing) Ltd.
Method and apparatus for routing data in a communication system
EP4099762B1
( en )
2020-02-28
2025-10-22
Huawei Technologies Co., Ltd.
Communication method and communication apparatus
WO2022006907A1
( en )
*
2020-07-10
2022-01-13
å为ææ¯æéå ¬å¸
Communication method and apparatus
WO2022047654A1
( en )
*
2020-09-02
2022-03-10
å为ææ¯æéå ¬å¸
Communication method and apparatus
US11751218B2
( en )
*
2020-09-14
2023-09-05
Qualcomm Incorporated
Resource configuration for integrated access and backhaul radio access network sharing
EP4256843A4
( en )
2021-01-14
2024-08-07
Apple Inc.
NEW METRICS FOR FAIRNESS AND LATENCY ASSURANCE IN IAB NETWORKS
KR20230117618A
( en )
2021-01-14
2023-08-08
ì§í°ì´ ì½í¬ë ì´ì
Systems and Methods for IAB Migration
US11778515B2
( en )
*
2021-04-26
2023-10-03
T-Mobile Innovations Llc
Internet protocol (IP) communication service over wireless integrated access and backhaul (IAB) links
WO2023060546A1
( en )
*
2021-10-15
2023-04-20
Lenovo (Beijing) Limited
Method and apparatus for a data transmission over a tunnel between donor distributed units
WO2023062192A2
( en )
*
2021-10-15
2023-04-20
Fraunhofer-Gesellschaft zur Förderung der angewandten Forschung e.V.
Rfl backhaul handling with dual connectivity
JP2023069877A
( en )
*
2021-11-08
2023-05-18
ãã¤ãã³æ ªå¼ä¼ç¤¾
Control device, control method, and program
CN116456374B
( en )
*
2022-01-06
2025-12-09
大å移å¨é信设å¤æéå ¬å¸
Method and device for notifying wireless link state between nodes
GB2622783A
( en )
*
2022-09-27
2024-04-03
Nokia Solutions & Networks Oy
Configuring a wireless backhaul link for relaying wireless communication signals between nodes
US20240284295A1
( en )
*
2023-02-17
2024-08-22
Nokia Technologies Oy
Service routing for user equipment
WO2025213468A1
( en )
*
2024-04-12
2025-10-16
å京å°ç±³ç§»å¨è½¯ä»¶æéå ¬å¸
Communication method, network functions, first device, communication system and storage medium
Citations (7)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20170006499A1
( en )
2015-06-30
2017-01-05
Qualcomm Incorporated
Traffic flow migration in backhaul networks
WO2017196249A1
( en )
2016-05-13
2017-11-16
Telefonaktiebolaget Lm Ericsson (Publ)
Network architecture, methods, and devices for a wireless communications network
US20180092139A1
( en )
2016-09-29
2018-03-29
At&T Intellectual Property I, L.P.
Initial access and radio resource management for integrated access and backhaul (iab) wireless networks
KR20190034094A
( en )
2017-09-22
2019-04-01
주ìíì¬ ì¼ì´í°
Methods for processing data of relay node and Apparatuses thereof
US20190159277A1
( en )
*
2018-01-23
2019-05-23
Intel Corporation
Enhancing f1 application protocol (f1-ap) interfaces in a multi-hop relay network with centralized unit (cu) and distributed unit (du)
US20190313469A1
( en )
*
2018-04-09
2019-10-10
Lenovo (Singapore) Pte. Ltd.
V2x communication over multiple radio access types
WO2019194737A1
( en )
*
2018-04-05
2019-10-10
Telefonaktiebolaget Lm Ericsson (Publ)
Adaptation layer setup and configuration in integrated access backhauled networks
2019
2019-05-09
US
US17/053,910
patent/US11800429B2/en
active
Active
2019-05-09
CN
CN201980031189.1A
patent/CN112106404B/en
active
Active
2019-05-09
WO
PCT/KR2019/005572
patent/WO2019216670A1/en
not_active
Ceased
2019-05-09
EP
EP19800692.6A
patent/EP3756383A4/en
active
Pending
Patent Citations (9)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20170006499A1
( en )
2015-06-30
2017-01-05
Qualcomm Incorporated
Traffic flow migration in backhaul networks
CN107736004A
( en )
2015-06-30
2018-02-23
é«éè¡ä»½æéå ¬å¸
Traffic stream migration in backhaul network
WO2017196249A1
( en )
2016-05-13
2017-11-16
Telefonaktiebolaget Lm Ericsson (Publ)
Network architecture, methods, and devices for a wireless communications network
US20180092139A1
( en )
2016-09-29
2018-03-29
At&T Intellectual Property I, L.P.
Initial access and radio resource management for integrated access and backhaul (iab) wireless networks
KR20190034094A
( en )
2017-09-22
2019-04-01
주ìíì¬ ì¼ì´í°
Methods for processing data of relay node and Apparatuses thereof
US20190159277A1
( en )
*
2018-01-23
2019-05-23
Intel Corporation
Enhancing f1 application protocol (f1-ap) interfaces in a multi-hop relay network with centralized unit (cu) and distributed unit (du)
WO2019194737A1
( en )
*
2018-04-05
2019-10-10
Telefonaktiebolaget Lm Ericsson (Publ)
Adaptation layer setup and configuration in integrated access backhauled networks
US20210127430A1
( en )
*
2018-04-05
2021-04-29
Telefonaktiebolaget Lm Ericsson (Publ)
Adaptation Layer Setup and Configuration in Integrated Access Backhauled Networks
US20190313469A1
( en )
*
2018-04-09
2019-10-10
Lenovo (Singapore) Pte. Ltd.
V2x communication over multiple radio access types
Non-Patent Citations (12)
* Cited by examiner, â Cited by third party
Title
Communication dated Aug. 31, 2023, issued by State Intellectual Property Office of P. R. China in Chinese Application No. 201980031189.1.
Communication dated Jan. 14, 2022, issued by the European Patent Office in counterpart European Application No. 19800692.6.
Intel Corporation " Adaptation layer and Routing for IAB in NR " Discussion and Decision, 3GPP TSG RAN WG2 Meeting #101 bis, Sanya, China, Apr. 16-20, 2018, R2-1805685 (8 pages total).
International Search Report (PCT/ISA/210), issued by International Searching Authority in corresponding International Application No. PCT/KR2019/005572, dated Aug. 14, 2019.
KDDI Corporation et al. " Consideration on IAB node discovery and connection establishment " Discussion and decision, 3GPP TSG RAN WG2 #101 bis, Sanya, China, Apr. 16-20, 2018, R2-1804527, (5 pages total).
Nokia et al. " Architecture and Protocols: MAC adaptation layer based IAB " Discussion and Decision, 3GPP TSG-RAN WG2 Meeting #101 bis, Sanya, China, Apr. 16-20, 2018, R2-1805701 Update of R2-1800392, (8 pages total).
Qualcomm Incorporated (Rapporteur), " IAB U-plane considerations for architecture group 1, " R2-1806455, 3GPP TSG-RAN WG2 Meeting #101 bis, Apr. 28, 2018, Total 4 pages.
Qualcomm Incorporated, " IABâU-plane transport for L2-relaying, " R3-181945, 3GPP TSG-RAN WG3 Meeting #99bis, Apr. 15, 2018, Total 8 pages.
Samsung Electronics R&D Institute UK " Adaptation layer: position in the protocol stack and location within the IAB donor node " Discussion, 3GPP TSG-RAN WG2 #101-bis, Sanya, China, Apr. 16-20, 2018, R2-1804700 (6 pages total).
Samsung, " Discussions on user plane protocol for IAB ", 3GPP TSG-RAN WG3 #99bis, Apr. 16-20, 2018, Document No. R3-181874, Total 9 pages.
Written Opinion (PCT/ISA/237) issued by the International Searching Authority in corresponding International Application No. PCT/KR2019/005572, dated Aug. 14, 2019.
ZTE " Discussion on IAB architectures, " R3-181829, 3GPP TSG-RAN WG3 Meeting #99bis, Apr. 15, 2018, Total 9 pages.
Cited By (2)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20230083708A1
( en )
*
2020-02-20
2023-03-16
Telefonaktiebolaget Lm Ericsson (Publ)
Backhaul Adaptation Protocol Path Identity for Fair Scheduling in an Integrated Access Backhaul Node
US12363613B2
( en )
*
2020-02-20
2025-07-15
Telefonaktiebolaget Lm Ericsson (Publ)
Backhaul adaptation protocol path identity for fair scheduling in an integrated access backhaul node
Also Published As
Publication number
Publication date
CN112106404B
( en )
2024-08-06
US20210243672A1
( en )
2021-08-05
EP3756383A4
( en )
2022-02-16
EP3756383A1
( en )
2020-12-30
CN112106404A
( en )
2020-12-18
WO2019216670A1
( en )
2019-11-14
Similar Documents
Publication
Publication Date
Title
US20210243672A1
( en )
2021-08-05
Methods and systems for routing data through iab nodes in 5g communication networks
EP4039061B1
( en )
2023-05-10
Transfer of data packets in end-to-end multi-hop sidelink radio communication
JP7116193B2
( en )
2022-08-09
Information transmission method and device
JP7503625B2
( en )
2024-06-20
Method and device for routing and bearer mapping configuration - Patents.com
CN110351700B
( en )
2022-06-17
Relay forwarding method and node for self-access return link
US8554232B2
( en )
2013-10-08
Method and system for a wireless multi-hop relay network
US12587940B2
( en )
2026-03-24
Method and apparatus for packet rerouting
US9077430B2
( en )
2015-07-07
Method, device and system for transmitting relay data
US20220217612A1
( en )
2022-07-07
Cooperative communication for sidelink relay
Teyeb et al.
2019
Integrated access backhauled networks
CN113424499A
( en )
2021-09-21
Central Unit (CU), Distributed Unit (DU) and methods therein for forwarding data in an Integrated Access Backhaul (IAB) network
US20120243462A1
( en )
2012-09-27
Transmission in a communication system using relay nodes
JP2021521736A
( en )
2021-08-26
Configuration method, data transmission method, and equipment
JP2021510283A
( en )
2021-04-15
Nodes and communication methods
CN112567796A
( en )
2021-03-26
Method, apparatus and system for integrated access and backhaul bearer management
KR20230091856A
( en )
2023-06-23
Methods and devices for inter-donor mobility
JP2013515420A
( en )
2013-05-02
Control of service quality in relays
CN103053217A
( en )
2013-04-17
Wireless communication system and method for mapping control message on UN interface
JP7677445B2
( en )
2025-05-15
Information transmission/reception method, data transmission method and device
US20240073736A1
( en )
2024-02-29
Communication control method
US20240397376A1
( en )
2024-11-28
Systems and methods for traffic transmission in iab network
EP2490399B1
( en )
2020-08-26
Method for data transmission based on relay mobile communication system and equipment thereof
CN114424621B
( en )
2024-09-17
A buffer status report transmission method and device
JP2010206551A
( en )
2010-09-16
Multi-hop radio communication system and method
Legal Events
Date
Code
Title
Description
2020-11-09
AS
Assignment
Owner name : SAMSUNG ELECTRONICS CO., LTD., KOREA, REPUBLIC OF
Free format text : ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DESHMUKH, ANEESH;SHARMA, NEHA;ABDUL LATHEEF, FASIL;AND OTHERS;REEL/FRAME:054365/0421
Effective date : 20201007
2020-11-09
FEPP
Fee payment procedure
Free format text : ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY
2021-05-13
STPP
Information on status: patent application and granting procedure in general
Free format text : APPLICATION DISPATCHED FROM PREEXAM, NOT YET DOCKETED
2021-08-20
STPP
Information on status: patent application and granting procedure in general
Free format text : DOCKETED NEW CASE - READY FOR EXAMINATION
2022-05-11
STPP
Information on status: patent application and granting procedure in general
Free format text : NON FINAL ACTION MAILED
2022-09-01
STPP
Information on status: patent application and granting procedure in general
Free format text : FINAL REJECTION MAILED
2022-12-08
STPP
Information on status: patent application and granting procedure in general
Free format text : DOCKETED NEW CASE - READY FOR EXAMINATION
2023-04-27
STPP
Information on status: patent application and granting procedure in general
Free format text : NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS
2023-08-16
STCF
Information on status: patent grant
Free format text : PATENTED CASE
2023-09-04
STPP
Information on status: patent application and granting procedure in general
Free format text : WITHDRAW FROM ISSUE AWAITING ACTION
2023-09-15
STPP
Information on status: patent application and granting procedure in general
Free format text : PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED
2023-10-04
STCF
Information on status: patent grant
Free format text : PATENTED CASE