Patent Application
20240015098
This disclosure relates to the field of communication technologies.
Integrated access and backhaul (IAB) enables a function of radio relay in a next generation radio access network (NG-RAN). An integrated access and backhaul node (IAB-node) supports access and backhaul via New Radio (NR). A termination point of NR backhaul at a network side is referred to as an IAB-donor, which denotes a network device (e.g. a gNB) supporting an IAB function.
An IAB-node is connected to an IAB-donor via one or more hops. These multi-hop connections form a directed acyclic graph (DAG) topology with the IAB-donor as a root node. The IAB-donor is responsible for executing centralized resource management, topology management and routing management in an IAB network topology.
The IAB-node supports a function of a gNB-DU (distributed unit), and an IAB-node DU is also referred to as an IAB-DU, which is an end point of a New Radio access (NR access) interface to a terminal equipment (UE) and a next hop IAB-node and is also an end point of an F1 protocol to a gNB-CU (central unit) on the IAB-node. The IAB-DU may serve for a common UE and an IAB child node. The IAB-DU enables functions of a network side device, is connected to a downstream child IAB-node, provides NR air-interface access for UEs and downstream IAB child nodes, and establishes F1 connection to an IAB donor-CU.
In addition to the function of the gNB-DU, the IAB-node also supports some functions of the UE, referred to as an IAB-MT (mobile termination). The IAB-MT includes, for example, a physical layer, layer 2, RRC and NAS functions to be connected to a gNB-DU on another IAB-node or IAB-donor, a gNB-CU on the IAB-donor and a core network. The IAB-MT may support such functions as a UE physical layer, an access stratum (AS), a radio resource control (RRC) layer and a non-access stratum (NAS), and may be connected to an IAB parent node.
As shown in
It should be noted that the above description of the background is merely provided for clear and complete explanation of this disclosure and for easy understanding by those skilled in the art. And it should not be understood that the above technical solution is known to those skilled in the art as it is described in the background of this disclosure.
It was found by the inventors that:
For example,
In order to solve the above problems, embodiments of this disclosure provide a method and apparatus for transmitting and receiving a signal and a communication system, in which when a destination BAP address of a first path of an IAB-node is unreachable, a route is changed for data of the first path that are not successfully transmitted or data of the first path that are received. Hence, data may be transmitted based on the changed route, thereby avoiding loss of data.
According to an aspect of the embodiments of this disclosure, there is provided an apparatus for transmitting and receiving a signal, applicable to an integrated access and backhaul node (IAB-node), the apparatus including:
According to another aspect of the embodiments of this disclosure, there is provided an apparatus for transmitting and receiving a signal, applicable to a child node of an integrated access and backhaul node (IAB-node), the apparatus including:
According to a further aspect of the embodiments of this disclosure, there is provided an apparatus for transmitting and receiving a signal, applicable to a donor centralized unit (donor-CU), the apparatus including:
According to still another aspect of the embodiments of this disclosure, there is provided a method for transmitting and receiving a signal, applicable to an integrated access and backhaul node (IAB-node), the method including:
According to yet another aspect of the embodiments of this disclosure, there is provided a method for transmitting and receiving a signal, applicable to a child node of an integrated access and backhaul node (IAB-node), the method including:
According to yet still another aspect of the embodiments of this disclosure, there is provided a method for transmitting and receiving a signal, applicable to a donor centralized unit (donor-CU), the method including:
An advantage of the embodiments of this disclosure exists in that when a destination BAP address of a first path of the IAB-node is unreachable, a route of unsuccessfully transmitted first path data or received first path data is changed. Hence, data may be transmitted based on the changed route, thereby avoiding loss of data.
With reference to the following description and drawings, the particular embodiments of this disclosure are disclosed in detail, and the principle of this disclosure and the manners of use are indicated. It should be understood that the scope of the embodiments of this disclosure is not limited thereto. The embodiments of this disclosure contain many alternations, modifications and equivalents within the spirits and scope of the terms of the appended claims.
Features that are described and/or illustrated with respect to one embodiment may be used in the same way or in a similar way in one or more other embodiments and/or in combination with or instead of the features of the other embodiments.
It should be emphasized that the term “comprise/include” when used in this specification is taken to specify the presence of stated features, integers, steps or components but does not preclude the presence or addition of one or more other features, integers, steps, components or groups thereof.
Elements and features depicted in one drawing or embodiment of the disclosure may be combined with elements and features depicted in one or more additional drawings or embodiments. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views and may be used to designate like or similar parts in more than one embodiments.
These and further aspects and features of this disclosure will be apparent with reference to the following description and attached drawings. In the description and drawings, particular embodiments of the disclosure have been disclosed in detail as being indicative of some of the ways in which the principles of the disclosure may be employed, but it is understood that the disclosure is not limited correspondingly in scope. Rather, the disclosure includes all changes, modifications and equivalents coming within the spirit and terms of the appended claims.
In the embodiments of this disclosure, terms “first”, and “second”, etc., are used to differentiate different elements with respect to names, and do not indicate spatial arrangement or temporal orders of these elements, and these elements should not be limited by these terms. Terms “and/or” include any one and all combinations of one or more relevantly listed terms. Terms “contain”, “include” and “have” refer to existence of stated features, elements, components, or assemblies, but do not exclude existence or addition of one or more other features, elements, components, or assemblies.
In the embodiments of this disclosure, single forms “a”, and “the”, etc., include plural forms, and should be understood as “a kind of” or “a type of” in a broad sense, but should not defined as a meaning of “one”; and the term “the” should be understood as including both a single form and a plural form, except specified otherwise. Furthermore, the term “according to” should be understood as “at least partially according to”, the term “based on” should be understood as “at least partially based on”, except specified otherwise.
In the embodiments of this disclosure, the term “communication network” or “wireless communication network” may refer to a network satisfying any one of the following communication standards: long term evolution (LTE), long term evolution-advanced (LTE-A), wideband code division multiple access (WCDMA), and high-speed packet access (HSPA), etc.
And communication between devices in a communication system may be performed according to communication protocols at any stage, which may, for example, include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, and 5G and New Radio (NR) in the future, etc., and/or other communication protocols that are currently known or will be developed in the future.
In the embodiments of this disclosure, the term “network device”, for example, refers to a device in a communication system that accesses a user equipment to the communication network and provides services for the user equipment. The network device may include but not limited to the following devices: Integrated access and backhaul nodes (IAB-node), a base station (BS), an access point (AP), a transmission reception point (TRP), a broadcast transmitter, a mobile management entity (MME), a gateway, a server, a radio network controller (RNC), a base station controller (BSC), etc.
The base station may include but not limited to a node B (NodeB or NB), an evolved node B (eNodeB or eNB), and a 5G base station (gNB), etc. Furthermore, it may include a remote radio head (RRH), a remote radio unit (RRU), a relay, or a low-power node (such as a femto, and a pico, etc.). The term “base station” may include some or all of its functions, and each base station may provide communication coverage for a specific geographical area. And a term “cell” may refer to a base station and/or its coverage area, depending on a context of the term.
In the embodiments of this disclosure, the term “user equipment (UE)” or “terminal equipment (TE) or terminal device” refers to, for example, an equipment accessing to a communication network and receiving network services via a network device. The terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), and a station, etc.
The terminal equipment may include but not limited to the following devices: a cellular phone, a personal digital assistant (PDA), a wireless modem, a wireless communication device, a hand-held device, a machine-type communication device, a lap-top, a cordless telephone, a smart cell phone, a smart watch, and a digital camera, etc.
For another example, in a scenario of the Internet of Things (IoT), etc., the user equipment may also be a machine or a device performing monitoring or measurement. For example, it may include but not limited to a machine-type communication (MTC) terminal, a vehicle mounted communication terminal, a device to device (D2D) terminal, and a machine to machine (M2M) terminal, etc.
Moreover, the term “network side” or “network device side” refers to a side of a network, which may be a base station or one or more network devices including those described above. The term “user side” or “terminal side” or “terminal equipment side” refers to a side of a user or a terminal, which may be a UE, and may include one or more terminal equipments described above.
In the embodiments of this disclosure, higher-layer signaling may be, for example, radio resource control (RRC) signaling; for example, it is referred to an RRC message, which includes MIB, system information, and a dedicated RRC message; or, it is referred to an as RRC IE (RRC information element). Higher-layer signaling may also be, for example, F1-C signaling, or an F1AP protocol; however, this disclosure is not limited thereto.
During movement of an IAB-node, if it is disconnected from an original parent IAB-node and is connected to a new parent IAB-node, a change of routing from the IAB-node and its child nodes to a donor-CU, i.e. a change of network topology, is resulted.
For a process of update of the network topology when the IAB-node moves in a DU under the same donor-CU, when the IAB-node is handed over, the donor-CU configures the IAB-node with a default backhaul RLC channel (default BH RLC channel) used for a target path of uplink F1-C and non-F1 data and a default BAP routing identifier (default BAP routing ID) via an RRC reconfiguration message. If the donor-DU is changed after handover, the donor-DU may possibly configure the IAB-node with an IP address that can be routed to the target donor-DU, wherein the default routing ID contains the BAP address and path ID of the target donor-DU. After the IAB-node handed over to a new parent node, the IAB-node starts to apply the above configuration, that is, transferring a transmission path to the target side.
The embodiment of the first aspect of this disclosure provides a method for transmitting and receiving a signal, applicable to an integrated access and backhaul node (IAB-node).
According to this disclosure, the route of the first path data is changed, thereby transmitting the data based on the changed route, and avoiding loss of data.
In operation 401 of this disclosure, the changing route of the first path data includes: changing a destination BAP address of the first path data into a destination BAP address of a second path, or changing a destination BAP address of the first path data into a destination BAP address of a second path, and changing a path ID of the first path data into a path ID of the second path. The unsuccessfully transmitted first path data are first path data that have been generated or received, but have not been transmitted in buffer or have been transmitted but a correct response from an RLC layer has not been received. If the destination BAP address routed by the first path is unreachable, the IAB-node may change the route of the first path data so that they are transmitted based on the changed route of the second path and reach the donor-CU.
In this disclosure, the first path may be an uplink data transmission path before the IAB-node moves, and the path formed after the route change is the second path.
In operation 402 of this disclosure, the transmitting the first path data includes: transmitting the first path data to a backhaul RLC channel between the IAB-node and a next hop of node of the second path.
When the IAB-node changes the routes of the first path data, it transmits the first path data to the next hop of node under the second path. If the donor-CU has already configured the IAB-node with a relationship of mapping from a backhaul RLC channel or an access RLC channel between a last hop of node and the IAB-node to a backhaul RLC channel between the IAB-node and the next hop of node of the second path, that is, a suitable next hop of RLC channel already exists, the IAB-node may select a backhaul RLC channel for transmitting the first path data according to the relationship of mapping. For example, in a case where the IAB-node has maintained a connection with the next hop of node of the second path, if the above relationship of mapping does not exist, the IAB-node may select any backhaul RLC channel to the next hop of node of the second path to transmit the first path data. And if the IAB-node is not connected to the next hop of node of the second path, the IAB-node needs to transmit the first path data after establishing a connection therewith.
As shown in
In at least one embodiment, as shown in
When the IAB-node deems that the first path data have been transmitted, it stops changing the routes of the first path data. In operation 403, changing the routes of the first path data may be stopped under any one of the following conditions:
In condition 3, when the IAB-node receives an end indication transmitted by the downlink child node of the IAB-node, the IAB-node determines that the downlink child node transmits the unsuccessfully transmitted first path data. The end indication may be placed in a header of a BAP data PDU or in a control PDU of the BAP.
In at least one embodiment, the situation where the destination BAP address of the first path of the IAB-node is unreachable includes the following situation 1 or 2:
In at least one embodiment, as shown in
The IAB-node is often not configured with routing change related parameters when it is away from its original parent node. For example, if a second path route has not been established or even connection with a next hop of node of the second path has not been established, relevant configuration may be obtained in operation 404, so that the IAB-node performs routing change in operation 401.
In implementation 1 of operation 404, the path reconfiguration parameter may include a destination BAP address and a path identifier of the first path. In this way, if some of the original path data do not require routing changes, or if the IAB-node does not know which original paths need routing changes, the donor-CU may configure paths that the IAB-node needs to perform routing changes.
In implementation 2 of operation 404, the path reconfiguration parameter may include mapping of the destination BAP address of the first path to the destination BAP address of the second path, or may include mapping of the destination BAP address and path identifier of the first path to the destination BAP address and path identifier of the second path, so that different first paths are routed to different donor-DUs by using different second paths, thereby satisfying different QoS requirements of the uplink data.
In implementation 3 of operation 404, the path reconfiguration parameter may include the destination BAP address of the second path, the path identifier of the second path and an identifier of an RLC channel from the IAB-node to a next hop of node of the second path. The destination BAP address of the second path and the path identifier of the second path are used to replace the destination BAP address and path identifier in the BAP header of the first path data. The backhaul RLC channel from the IAB-node to the next hop of node of the second path is an uplink backhaul RLC channel used for transmitting the first path data to the next hop of node of the second path.
In implementation 3 of operation 404, the destination BAP address of the second path is a destination BAP address used for uplink F1-C and non-F1 data, and the path ID of the second path is a path ID used for the uplink F1-C and non-F1 data, or the destination BAP address of the second path is a destination BAP address used for uplink F1-U data, and the path ID of the second path is a path ID used for the uplink F1-U data. Hence, if the IAB-node has been configured with the second path route used for the uplink F1-U data and the non-F1 data, the IAB-node may use the second path route of the uplink F1-U data and the non-F1 data as the route of the first path data; and when the IAB-node is further configured with the second path route used for the uplink F1-U data, the IAB-node may use the second path route of the F1-U data as the route of the first path data.
In implementation 3 of operation 404, the ID of the backhaul RLC channel from the IAB-node to the next hop of node of the second path is: an ID of a backhaul RLC channel used for uplink F1-C and non-F1 data, or an ID of a backhaul RLC channel used for uplink F1-U data. In this way, if the IAB-node is configured with a backhaul RLC channel for the uplink F1-C and non-F1 data, the IAB-node may use the backhaul RLC channel of the F1-C and non-F1 data as a channel for transmitting the first path data. If the IAB-node is further configured with a backhaul RLC channel for the uplink F1-U data, the IAB-node may use the channel of the F1-U data as a channel for transmitting the first path data.
In a first example of implementations 1-3 of operation 404, if the situation where the destination BAP address of the first path is unreachable is situation 1, i.e. the destination BAP address of the first path is unreachable due to the switching of the IAB-node to a new parent node, the path reconfiguration parameter may be transmitted by an RRC reconfiguration message for handover transmitted by the donor-CU, and the IAB-node triggers routing change of the first path data in completing random access to the new parent node.
In a second example of implementations 1-3 of operation 404, if the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 1, the path reconfiguration parameter may be transmitted from an F1AP message received from the donor-CU after the IAB-node completes handover to the new parent node, and the transmission of the first path data is stopped when the IAB-node is handed over to the new parent node, for example, the IAB-node may stop transmitting a scheduling request (SR) or a buffer size requests (BSR) to the parent node, or stop scheduling an uplink resource grant of the child node. The IAB-node may trigger routing change of the first path data in receiving the F1AP message. As the first path data are unable to reach the destination donor-DU after the IAB-node is handed over, stopping transmitting the first path data immediately after the handover may avoid loss of data.
In a third example of implementations 1-3 of operation 404, if the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 2, i.e. the destination BAP address of the first path is unreachable due to radio link failure occurring in the link between the IAB-node and the parent node, the path reconfiguration parameter may be transmitted via an RRC reconfiguration message or the F1AP message received from the donor-CU after the IAB-node completes establishment with a new parent node, and transmission of the first path data is stopped when a radio link failure occurs in the link between the IAB-node and the first parent node. For example, the IAB-node may stop transmitting the SR and BSR to the parent node or stop scheduling an uplink resource grant of the child node. The IAB-node triggers routing change of the first path data after receiving the path reconfiguration parameter. As the first path data are unable to reach the destination donor-DU after the link between the IAB-node and the parent node fails, immediately stopping transmitting the first path data may avoid loss of data.
In a fourth example of implementations 1-3 of operation 404, if the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 2, the path reconfiguration parameter may be transmitted via the F1AP message received from the donor-CU after the IAB-node reports the radio link failure information to the donor-CU, and transmission of the first path data is stopped when a radio link failure occurs in the link between the IAB-node and the first parent node. For example, the IAB-node may stop transmitting the SR and BSR to the parent node or stop scheduling an uplink resource grant of the child node. The IAB-node triggers routing change of the first path data after receiving the F1AP message.
In this disclosure, if a second path route already exists in the IAB-node, routing change may be performed on the first path data without executing operation 404. For example, the IAB-node forms a dual connection with the first parent node and second parent node, wherein a radio link failure occurs in a link between the IAB-node and the first parent node, and no radio link failure occurs in a link between the IAB-node and the second parent node. In this case, the IAB-node triggers routing change of the first path data immediately after an RLF occurs in the link between IAB-node and the first parent node, and a destination BAP address in a BAP packet header of a path passing the first parent node is replaced with a destination BAP address of a path passing the link between the IAB-node and the second parent node, or, a destination BAP address and path identifier are respectively replaced with a destination BAP address and path identifier of the path passing the link between the IAB-node and the second parent node. Hence, the first path is the path passing the link between the IAB-node and the first parent node, and the second path is the path passing the link between the IAB-node and the second parent node.
The method for transmitting and receiving a signal in
In Embodiment 1, the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 1 (i.e. the destination BAP address of the first path is unreachable due to the switching of the IAB-node to a new parent node).
In this embodiment, after the IAB-node is handed over, the original donor-DU is different from the target donor-DU. The IAB-node or its child node changes routes of buffered uplink F1 data and uplink F1 data received from the downstream node on the original path (i.e. the first path), and replaces the BAP address of the original donor-DU in the BAP packet header with the BAP address of the target donor-DU (i.e. the destination BAP address of the second path), or replaces the BAP address and original path identifier of the original donor-DU with a target donor-DU address and a target side path (i.e. the second path) identifier, respectively. Furthermore, the IAB-node may transmit the uplink F1 data on the original path to an RLC channel between the IAB-node and a next hop of node of the target side path, thereby transmitting the first path data based on the changed route.
A process of changing routes of buffered uplink F1 data and uplink F1 data received from the downstream node on the original path by the IAB-node shall be described below.
When the IAB-node is handed over to a new parent node, target transmission path parameters for uplink F1-C and non-F1 data are configured by an RRC message transmitted by the donor-CU via the original path, and include a target donor-DU address, a path identifier and an uplink UL BH RLC channel. The donor-CU may configure target side routing for uplink F1-U data via the same RRC message, including a target donor-DU address, a path identifier and a UL BH RLC channel.
The IAB-node may transmit the buffered uplink F1-U data on the original path by using the destination donor-DU address, target side path identifier and uplink UL BH RLC channel of the uplink F1-C and non-F1 data, and may also transmit the uplink data on the original path via the target path parameters for the uplink F1-U data. Or, the donor-CU may specifically change configuration parameters for routes of the uplink data on the original path. In order to identify the uplink data on the original path, the IAB-node may reserve the original destination address and path identifier for a period of time after handover, or the donor-CU may configure a routing identifier of uplink data needing to be rerouted (the original donor-DU address and original path identifier) to the IAB-node.
In order to meet different QoS requirements of the uplink data, uplink data on different original donor-DUs or original paths may need to be routed to different target donor-DUs or transmitted by using different target paths. The donor-CU may configure mapping from the original donor-DU address to the target donor-DU address, or configure mapping from the BAP address of the original donor-DU and original path identifier to the target donor-DU address and target path identifier.
Relevant configuration of the routing change of original path data may be transmitted to the IAB-node via an RRC reconfiguration message during the handover or an F1AP message after the handover is completed.
In this embodiment, an activation method for performing routing change on the original path data by the IAB-node (i.e. a method for triggering the routing change in operation 401) may include:
when the IAB-node has saved the path update configuration, completing random access to the target cell by the IAB-node; or, after handover of the IAB-node is completed, receiving configuration related to changes of the routes of the original path data transmitted via the F1AP message.
In this embodiment, an activation method for performing routing change on the original path data (i.e. executing operation 403) may include:
In addition, in this embodiment, the uplink data generated after the handover is generated according to the target side path, hence, there is no need to update routes the uplink data generated after the handover.
Furthermore, in Embodiment 1, a method for activating routing change of the original path data by the child node includes: in a case where the child node has saved the path update configuration, when a handover success indication message transmitted by the IAB-node after completing random access to the target cell, activating routing change of the original path data; or, when the IAB-node receives configuration related to routing change of the original path data transmitted by donor-CU via an F1AP message after completing handover, activating routing change of the original path data.
In Embodiment 1, a method for deactivating routing change of the original path data by the child node includes: starting a timer after the child node activates the routing change, and deactivating the routing change of the original path data after the timer expires; or, deactivating by the child node after transmitting currently buffered unsuccessfully transmitted original path data; or, deactivating by the child node after determining that all original path data in the downstream node have been transmitted and transmitting all unsuccessfully transmitted original path data.
In Embodiment 2, the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 2 (i.e. the destination BAP address of the first path is unreachable due to a radio link failure occurring in the link between the IAB-node and the first parent node).
In Embodiment 2, after the IAB-node completes rebuilding, the original donor-DU is different from the target donor-DU.
After the IAB is rebuilt to a new cell, there may be some uplink data on the original path that have not been transmitted to the original parent node, and if these data are directly transmitted via the new path, they may be dropped by the new donor-DU.
The IAB-node or its child node change the routes of buffered uplink F1 data and the uplink F1 data on the original path received from the downstream node, and replaces the BAP address of the original donor-DU in the BAP packet header with a BAP address of a new donor-DU, or replaces the BAP address of the original donor-DU and the original path identifier with a new donor-DU address and a new path identifier, respectively.
When the IAB-node completes rebuilding to the new cell, it changes the routes of the buffered uplink F1 data and the uplink F1 data of the original path received from the downstream node.
In rebuilding, parameters of the new transmission path for the uplink F1-C and non-F1 data include the destination donor-DU address, target side path identifier and uplink UL BH RLC channel configured by the donor-CU. The donor-CU may configure the parameters of the new transmission path for the uplink F1-U data via the same RRC message. IAB-node may transmit the buffered uplink F1-U data on the original path by using the transmission path parameters of the uplink F1-C and non-F1 data, including the donor-DU address, path identifier and uplink UL BH RLC channel, and may also transmit the uplink on the original path by using the transmission path parameters for F1-U. Or, the donor-CU may specifically change configuration parameters for the routes of the uplink data on the original path. In order to identify the uplink data on the original path, after the rebuilding is successful, the IAB-node may keep the original destination address and path identifier for a period of time, or the donor-CU may configure the IAB-node with an original donor-DU address and original path identifier needing to be rerouted.
In order to meet different QoS requirements of the uplink data, different uplink data may need to be routed to different target donor-DUs or transmitted by using different target paths. The donor-CU may configure mapping from the original donor-DU address to the target donor-DU BAP address, or configure mapping from the BAP address of the original donor-DU and original path identifier to the target donor-DU address and target path identifier.
Relevant configuration of the routing change of original path data may be transmitted to the IAB-node via an RRC reconfiguration message after the rebuilding or an F1AP message after the rebuilding.
After the IAB-node completes access to the new cell, it may stop transmitting uplink data on the original path via the new transmission path, so as to prevent the uplink data from being dropped by the new donor-DU.
In this embodiment, an activation method for performing routing change of data by the IAB-node (i.e. a method for triggering the routing change in operation 401) may include: after rebuilding of the IAB-node is completed, receiving configuration related to changes of the routes of the original path data transmitted via the RRC message or the F1AP message.
In this embodiment, reference may be made to Embodiment 1 for a method for activating routing change of the original path data, which shall not be described herein any further.
Furthermore, in Embodiment 2, a method for activating routing change of the original path data in the process of performing routing change of uplink data on the original path by the child node includes: in a case where the child node has saved path update configuration, such as in a case where the IAB-node is rebuilt to the target cell during handover of the IAB-node, the child node activates the routing change when it receives a successful rebuilding indication message transmitted by the IAB-node after completing random access to the new cell; or, the child node activates the routing change when it receives the configuration related to the routing change of the original path data transmitted by donor-CU.
In Embodiment 2, reference may be made to Embodiment 1 for a method for activating routing change of the original path data by the child node, which shall not be described herein any further.
In Embodiment 3, when the IAB-node rebuilds dual connection, the F1 transmission path is transferred from one cell group (CG) to another CG, such as when an RLF occurs in a BH link between the IAB-node and a parent node of a CG. After an RLF occurs in a path of the IAB-node, there may be some uplink data transmitted via the RLF path that have not yet reached the parent node. If these data are directly transmitted via another path where no RLF occurs, they are dropped by a donor-DU of the other path.
The IAB-node changes the routes of the buffered uplink F1 data and uplink F1 data received from the downstream node and passing the path of the RLF link, and replaces a BAP address of a donor-DU corresponding to the path passing the RLF link in the BAP packet header with a BAP address of a donor-DU corresponding to a path not passing the RLF link, or further replace an identifier of the path passing the RLF link with a BAP address of a path not passing the RLF link.
When an RLF occurs in a connection, the IAB-node may transmit an RLF report to the donor-CU via an RRC message. For example, when an RLF occurs in a master cell group (MCG), master cell group failure information (MCGfailureInformation) is transmitted, and when an RLF occurs in a secondary cell group (SCG), secondary cell group failure information (SCGFailureInformation) is transmitted.
After receiving the RLF report, the donor-CU may configure parameters for the uplink data, i.e. the destination donor-DU address, path identifier and the UL BH RLC channel, and the IAB-node may reroute uplink data of the path passing the RLF link according to the routing change parameters configured by the donor-CU. And the donor-CU may further configure routing identifiers of uplink data needing to be rerouted to the IAB-node.
In order to meet different QoS requirements of the uplink data, different uplink data may need to be routed to different target donor-DUs or transmitted by using different target paths. The donor-CU may configure different routes used by different paths passing the RLF link.
In this embodiment, an activation method for performing route change of the data by the IAB-node (i.e. the method for triggering routing change in operation 401) may include: detecting that an RLF occurs in a link by the IAB-node, or, receiving, by the IAB-node, configuration related to routing changes of the uplink data transmitted by the donor-CU.
In this embodiment, reference may be made to Embodiment 1 for a method for activating routing change of the original path data, which shall not be described herein any further. In addition, uplink data generated after the F1 transmission path is transferred from one CG to another does not need their routes to be updated, as they are generated according to the new path.
Furthermore, in Embodiment 3, when the IAB-node detects the RLF, it transmits an RLF indication to the child node, the RLF indication including a routing identifier (including a path identifier and a destination BAP address) of the path passing the RLF link. The child node changes routes of the successfully transmitted uplink F1 data and uplink F1 data of the path passing the RLF link received from the downstream node.
The donor-CU be configure relevant parameters for rerouting the RLF path, i.e. the destination BAP address, path identifier and UL BH RLC channel, and the child node reroutes the uplink data of the path where the RLF occurs according to the parameters. The donor-CU may further configure the child node with the routing identifier (including the destination BAP address and path identifier) of uplink F1 data needing to be rerouted.
Moreover, in Embodiment 3, a method for activating route change of the data at the child node includes: activating path data routing change when the child node receives the RLF indication transmitted by the IAB-node, or, activating path data routing change when the child node receives configuration related to rerouting uplink data transmitted by the donor-CU.
In Embodiment 3, reference may be made to Embodiment 1 for a deactivation method of the child node, which shall not be repeated herein any further.
According to the embodiment of the first aspect of this disclosure, routes of the data of the first path are changed, thereby transmitting data based on the changed routes, so as to avoid loss of data.
At least addressed to the same problem as the embodiment of the first aspect, the embodiment of the second aspect of this disclosure provides a method for transmitting and receiving a signal, which corresponds to the method of the embodiment of the first aspect. The method for transmitting and receiving a signal of the embodiment of the second aspect of this disclosure is applicable to a child node of an integrated access and backhaul node (IAB-node).
According to the embodiment of the first aspect of this disclosure, the route of the data of the first path is changed, thereby transmitting data based on the changed routes, so as to avoid loss of data.
In operation 801, the changing routes of the first path data includes:
In operation 802, the transmitting the first path data includes: transmitting the first path data to a backhaul RLC channel between the child node and a next hop of node of the second path.
Change the destination BAP address of the first path data to the destination BAP address of the second path; or, change the destination BAP address of the first path data to the destination BAP address of the second path, and change the path identifier of the first path data to the path identifier of the second path.
In operation 802, the first path data is transmitted, including: transmitting the first path data to a backhaul RLC channel between the child node and the next hop of node of the second path.
When the child node changes the routes of the first path data, it transmits the first path data to the next hop of node under the second path. If the donor-CU has already configured the child node with a relationship of mapping from a backhaul RLC channel or access RLC channel between a last hop of node and the child node to a backhaul RLC channel of a next hop of node of the second path, that is, a suitable next hop of RLC channel already exists, the child node may select to transmit the RLC channel of the first path data according to the relationship of mapping. For example, in a case where the child node keeps a connection with the next hop of node of the second path, if the above relationship of mapping does not exist, the child node may select any backhaul RLC channel to the next hop of node of the second path to transmit the first path data, and if the child node is not connected to the next hop of node of the second path, the IAB-node needs to establish a connection with it before transmitting the first path data.
In this embodiment, that a destination BAP address of a first path of the IAB-node is unreachable includes situation 1 or situation 2 below:
As shown in
When the child node deems that the first path data have been transmitted, it stops changing the routes of the first path data. In at least one embodiment, operation 803 may be executed when any one of the following conditions is satisfied:
As shown in
The child node is often not configured with parameters related to routing change when it is away from the original parent node, for example, second path routing is not established in the child node, hence, related configuration may be obtained in operation 804.
In implementation 1 of operation 804, the path reconfiguration parameter includes the destination BAP address and path identifier of the first path. Hence, if some of the original path data do not need routing change, or in a case where the child node does not know which original paths need routing change, the donor-CU may configure paths needing the child node to perform routing change.
In implementation 2 of operation 804, the path reconfiguration parameter includes mapping between the destination BAP address of the first path and the destination BAP address of the second path, or include mapping between the destination BAP address and path identifier of the first path and the destination BAP address and path identifier of the second path. Hence, different first paths may be routed by using different second paths and routed to different donor-CUs, thereby meeting different QoS requirements of the uplink data.
In implementation 3 of operation 804, the path reconfiguration parameter includes the destination BAP address of the second path, the path identifier of the second path and an identifier of a backhaul RLC channel from the child node to a next hop of node of the second path. The destination BAP address of the second path and the path identifier of the second path are used for replacing the destination BAP address and the path identifier in the BAP packet header of the first path data, and the backhaul RLC channel from the child node to the next hop of node of the second path is an uplink backhaul RLC channel used for transmitting the first path data to the next hop of node of the second path.
In implementation 3 of operation 804, the destination BAP address of the second path is a destination BAP address used for uplink F1-C and non-F1 data, and the path identifier of the second path is a path identifier used for the uplink F1-C and non-F1 data; or, the destination BAP address of the second path is a destination BAP address used for the uplink F1-U data, and the path identifier of the second path is a path identifier used for the uplink F1-U data. Hence, if the second path routing for the uplink F1-C and non-F1 data is already configured in the child node, the second path routing of the F1-C and non-F1 data may be used as the routing of the first path data; and when the child node is further configured with second path routing for the uplink F1-U data, the second path routing of the F1-U data may be used as the routing for the first path data.
In implementation 3 of operation 804, the backhaul RLC channel identifier to the next hop of node of the second path is an RLC channel identifier used for the uplink F1-C and non-F1 data, or, an RLC channel identifier used for the uplink F1-C data. Hence, if the child node is configured with the RLC channel identifier used for the uplink F1-C and non-F1 data, the RLC channel identifier used for the uplink F1-C and non-F1 data may be used as a channel for transmitting the first path data; and if the child node is further configured with the RLC channel identifier used for the uplink F1-C data, the RLC channel identifier used for the uplink F1-C data may be used as the channel for transmitting the first path data.
In a first example of implementations 1-3 of operation 804, if the situation where the destination BAP address of the first path is unreachable is situation 1, i.e. the destination BAP address of the first path is unreachable due to the switching of the IAB-node to a new parent node, the path reconfiguration parameter may be transmitted by an RRC reconfiguration message before handover of the IAB-node, and the child node triggers routing change of the first path data when it receives a handover success indication transmitted by the IAB-node after completing random access to the new parent node.
In a second example of implementations 1-3 of operation 804, if the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 1, the path reconfiguration parameter may be transmitted from an F1AP message received from the donor-CU after the IAB-node completes handover, and the transmission of the first path data is stopped when the child node receives a handover success indication transmitted by the IAB-node after completing random access to the new parent node, for example, the child node may stop transmitting an SR or an BSR, or stop scheduling an uplink resource grant of the downstream node. The child node may trigger routing change of the first path data in receiving the F1AP message. As the first path data are unable to reach the destination donor-DU after the IAB-node is handed over, stopping transmitting the first path data immediately after the handover of the IAB-node may avoid loss of data.
In a third example of implementations 1-3 of operation 804, if the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 2, i.e. the destination BAP address of the first path is unreachable due to radio link failure occurring in the link between the IAB-node and the parent node, the path reconfiguration parameter may be transmitted via an RRC reconfiguration message transmitted by the donor-CU after a radio link failure occurs in the IAB-node, and the child node triggers routing change of the first path data when it receives a reestablishment success indication transmitted by the IAB-node after completing random access to the new parent node. As the child node has saved the parameters related to routing change when the IAB-node complete random access, the child node may immediately trigger routing change of the first path data.
In a fourth example of implementations 1-3 of operation 804, if the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 2, the path reconfiguration parameter may be transmitted from the RRC reconfiguration message or F1AP message received from the donor-CU after the IAB-node completes reestablishment to the new parent node, and the child node stops transmitting the first path data when it receives a reestablishment success indication transmitted by the IAB-node after completing random access to the new parent node. For example, the child node may stop transmitting an SR or a BSR to the parent node, or stop scheduling an uplink resource grant of the downstream node. The child node triggers routing change of the first path data after receiving the path reconfiguration parameter. As the first path data are unable to reach the destination donor-DU after the IAB-node is reestablished to the new parent node, stopping transmitting the first path data immediately after the reestablishment of the IAB-node may avoid loss of data.
In a fifth example of implementations 1-3 of operation 804, if the situation where the destination BAP address of the first path of the IAB-node is unreachable is situation 2, the path reconfiguration parameter may be transmitted from the F1AP message received from the donor-CU after the IAB-node reports radio link failure information to the donor-CU, and the child node stops transmitting the first path data when it receives an RLF indication transmitted by the IAB-node when a radio link failure occurs in a link between the IAB-node and the first parent node, and the child node triggers routing change of the first path data in receiving the F1AP message. In addition, in at least one embodiment, if a second path route already exists in the child node, routing change may be performed on the first path data while executing operation 804. For example, the IAB-node forms a dual connection with the first parent node and second parent node, wherein a radio link failure occurs in a link between the IAB-node and the first parent node, and no radio link failure occurs in a link between the IAB-node and the second parent node. In this case, the child node triggers routing change of the first path data immediately after the child node receives an RLF indication occurs transmitted when a radio link failure (RLF) occurs in the link between IAB-node and the first parent node, and a destination BAP address in a BAP packet header of a path passing the link between IAB-node and the first parent node is replaced with a destination BAP address of a path passing the link between the IAB-node and the second parent node, or, a destination BAP address and path identifier are respectively replaced with a destination BAP address and path identifier of the path passing the link between the IAB-node and the second parent node. Hence, the first path is the path passing the link between the IAB-node and the first parent node, and the second path is the path passing the link between the IAB-node and the second parent node. Hence, when an RLF occurs in the IAB-node, the child node may learn which paths are affected by the RLF and need routing change.
In the embodiment of the second aspect, reference may be made to the explanations of embodiments 1 to 3 in the embodiment of the first aspect for examples of the behaviors of the child node.
According to the embodiment of the second aspect of this disclosure, routing change is performed on the first path data. Hence, the child node may transmit the data based on the changed route, thereby avoiding loss of data.
At least addressed to the same problem as the embodiment of the first aspect, the embodiment of the third aspect of this disclosure provides a method for transmitting and receiving a signal, which corresponds to the method of the embodiment of the first aspect. The method for transmitting and receiving a signal of the embodiment of the third aspect of this disclosure is applicable to a donor centralized unit (donor-CU) of an integrated access and backhaul node (IAB-node).
In operation 901, the path reconfiguration parameter is used for the IAB-node or the child node to change routes of unsuccessfully transmitted first path data or received first path data.
According to the embodiment of the third aspect of this disclosure, the IAB-node or its child node may change the route of the first path data by using the path reconfiguration parameter. Hence, the IAB-node or its child node may transmit the data based on the changed route, so as to avoid loss of data.
In at least one embodiment, the situation where the destination BAP address of the first path of the IAB-node is unreachable includes the following situation 1 or 2:
In implementation 1 of operation 901, the path reconfiguration parameter includes a destination BAP address and a path identifier of the first path.
In implementation 2 of operation 901, the path reconfiguration parameter includes a mapping between the destination BAP address of the first path data and the destination BAP address of the second path, or include a mapping between the destination BAP address and the path ID of the first path data and the destination BAP address and the path ID of the second path.
In implementation 3 of operation 901, the path reconfiguration parameter includes the destination BAP address of the second path, the path ID of the second path and an ID of a backhaul RLC channel between the IAB-node and a next hop of node of the second path, wherein the destination BAP address of the second path is a destination BAP address used for uplink F1-C and non-F1 data, and the path ID of the second path is a path ID used for the uplink F1-C and non-F1 data, or the destination BAP address of the second path is a destination BAP address used for uplink F1-U data, and the path ID of the second path is a path ID used for the uplink F1-U data.
In implementation 3 of operation 901, an ID of the backhaul RLC channel to the next hop of node of the second path is: an ID of a backhaul RLC channel used for uplink F1-C and non-F1 data, or an ID of a backhaul RLC channel used for uplink F1-U data.
In a first example of implementations 1-3 of operation 901, when the situation where the destination BAP address of the first path is unreachable is situation 1 (i.e. the destination BAP address of the first path is unreachable due to the switching of the IAB-node to a new parent node), the donor-CU transmits an RRC reconfiguration message containing the path reconfiguration parameter to the IAB-node or the child node before the IAB-node is handed over, or, the donor-CU transmits an F1 AP message containing the path reconfiguration parameter to the IAB-node or the child node after the IAB-node is handed over to the new parent node.
In a second example of implementations 1-3 of operation 901, when the situation where the destination BAP address of the first path is unreachable is situation 1, the donor-CU transmits an RRC reconfiguration message or F1 AP message containing the path reconfiguration parameter to the IAB-node or the child node after the IAB-node reports radio link failure information to the donor-CU.
In a third example of implementations 1-3 of operation 901, when the situation where the destination BAP address of the first path is unreachable is situation 2 (i.e. the destination BAP address of the first path is unreachable due to a radio link failure occurring in a link between the IAB-node and a first parent node, the donor-CU transmits an RRC reconfiguration message containing the path reconfiguration parameter or an F1AP message to the child node after the IAB-node completes reestablishment to a new parent node.
In a fourth example of implementations 1-3 of operation 901, when the situation where the destination BAP address of the first path is unreachable is situation 2, the donor-CU transmits an RRC reconfiguration message containing the path reconfiguration parameter to the child node before the radio link failure occurs in the IAB-node.
In the embodiment of the third aspect, reference may be made to the explanations of embodiments 1 to 3 in the embodiment of the first aspect for examples of the behaviors of the child node.
According to the embodiment of the third aspect of this disclosure, the IAB-node or its child node may perform routing change on the first path data by using the routing reconfiguration parameter. Hence, the IAB-node or its child node may transmit the data based on the changed route, thereby avoiding loss of data.
The embodiment of this disclosure provides an apparatus for transmitting and receiving a signal. The apparatus may be, for example, an integrated access and backhaul node, or may be one or some components of assemblies configured in the integrated access and backhaul node. The integrated access and backhaul node may be, for example, IAB-node 3 in
a first processing unit 1001 configured to, when a destination BAP address of a first path of the IAB-node is unreachable, change routes of unsuccessfully transmitted first path data or received first path data; and
The transmitting the first path data includes:
In at least one embodiment, that a destination BAP address of a first path of the IAB-node is unreachable includes that:
In at least one embodiment, the first processing unit 1001 further performs the following operations:
In at least one embodiment, when the IAB-node receives an end indication transmitted by the downlink child node, the first processing unit 1001 determines that the downlink child node transmits the unsuccessfully transmitted first path data.
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable resulted after radio link failure occurs in a link between the IAB-node and a first parent node, the second path is a path passing a link between the IAB-node and a second parent node, wherein no radio link failure occurs in the link between the IAB-node and the second parent node.
In at least one embodiment, after the radio link failure (RLF) occurs in the link between the IAB-node and the first parent node, the first processing unit 1001 triggers the IAB-node to change routes of the first path data.
In at least one embodiment, the first transceiving unit 1002 further receives a path reconfiguration parameter transmitted by the donor-CU, the path reconfiguration parameter including the destination BAP address and the path identifier of the first path data.
In at least one embodiment, the first transceiving unit 1002 further receives a path reconfiguration parameter transmitted by the donor-CU, the path reconfiguration parameter including the destination BAP address of the second path and the path ID of the second path, or including an ID of the backhaul RLC channel between the IAB-node and the next hop of node of the second path.
In at least one embodiment, the first transceiving unit 1002 further receives a path reconfiguration parameter transmitted by the donor-CU, the path reconfiguration parameter including the destination BAP address of the second path, the path ID of the second path and an ID of the backhaul RLC channel between the IAB-node and the next hop of node of the second path.
In at least one embodiment, the destination BAP address of the second path is a destination BAP address used for uplink F1-C and non-F1 data, and the path ID of the second path is a path ID used for the uplink F1-C and non-F1 data, or, the destination BAP address of the second path is a destination BAP address used for uplink F1-U data, and the path ID of the second path is a path ID used for the uplink F1-U data.
In at least one embodiment, the ID of the backhaul RLC channel between the IAB-node and the next hop of node of the second path is:
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to the switching of the IAB-node to the new parent node, the path reconfiguration parameter is transmitted by an RRC reconfiguration message for handover transmitted by the donor-CU, wherein when the IAB-node completes handover to the new parent node, the first processing unit 1001 triggers routing change of the first path data.
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to the switching of the IAB-node to the new parent node, the path reconfiguration parameter is transmitted from an F1AP message received from the donor-CU after the IAB-node completes handover to the new parent node, wherein when the IAB-node is handed over to the new parent node, the first transceiving unit 1002 stops transmitting the first path data, and when the IAB-node receives the F1AP message, the first processing unit 1001 triggers routing change of the first path data.
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to a radio link failure occurring in a link between the IAB-node and a first parent node, the path reconfiguration parameter is transmitted from an RRC reconfiguration message or F1 AP message received by the donor-CU after the IAB-node completes reestablishment to the new parent node, wherein the first transceiving unit 1002 stops transmitting the first path data when a radio link failure occurs in the link between the IAB-node and the first parent node, and after the first transceiving unit 1002 receives the path reconfiguration parameter, the first processing unit 1001 triggers changing the routes of the first path data.
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to a radio link failure occurring in a link between the IAB-node and a first parent node, the path reconfiguration parameter may be transmitted from the F1AP message received from the donor-CU after the IAB-node reports radio link failure information to the donor-CU, wherein,
According to the embodiment of the fourth aspect of this disclosure, routing change is performed on the first path data, thereby transmitting the data based on the changed route, and avoiding loss of data.
The embodiment of this disclosure provides an apparatus for transmitting and receiving a signal. The apparatus may be, for example, a child node of an integrated access and backhaul node, or may be one or some components of assemblies configured in the child node. The integrated access and backhaul node may be, for example, IAB-node 3 in
In at least one embodiment, the changing routes of the first path data includes:
In at least one embodiment, the transmitting the first path data includes:
In at least one embodiment, that a destination BAP address of a first path of the IAB-node is unreachable includes that:
In at least one embodiment, the second processing unit 1101 further performs the following operations:
In at least one embodiment, upon receiving an end indication transmitted by a downstream child node of the child node, the second processing unit 1101 determines that the downstream child node completes in transmission of the unsuccessfully transmitted first path data
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to a radio link failure occurring in a link between the IAB-node and a first parent node, the second path is a path passing a link between the IAB-node and a second parent node, wherein no radio link failure occurs in the link between the IAB-node and the second parent node.
In at least one embodiment, when the second transceiving unit 1102 receives a radio link failure (RLF) indication transmitted when the radio link failure occurs in the link between the IAB-node and the first parent node, the second processing unit 1101 triggers the child node to change the routes of the first path data.
In at least one embodiment, the RLF indication contains the destination BAP address and path ID of the first path.
In at least one embodiment, the second transceiving unit 1102 further receives path reconfiguration parameter transmitted by the donor-CU, the path reconfiguration parameter including the destination BAP address and path ID of the first path.
In at least one embodiment, the second transceiving unit 1102 further receives path reconfiguration parameter transmitted by the donor-CU, the path reconfiguration parameter including mapping between the destination BAP address of the first path and the destination BAP address of the second path, or including mapping between the destination BAP address and path identifier of the first path and the destination BAP address and path identifier of the second path.
In at least one embodiment, the second transceiving unit 1102 further receives path reconfiguration parameter transmitted by the donor-CU, the path reconfiguration parameter including the destination BAP address of the second path, the path identifier of the second path and an identifier of a backhaul RLC channel from the child node to a next hop of node of the second path.
In at least one embodiment, the destination BAP address of the second path is a destination BAP address used for uplink F1-C and non-F1 data, and the path identifier of the second path is a path identifier used for the uplink F1-C and non-F1 data; or, the destination BAP address of the second path is a destination BAP address used for the uplink F1-U data, and the path identifier of the second path is a path identifier used for the uplink F1-U data.
In at least one embodiment, the backhaul RLC channel identifier to the next hop of node of the second path is:
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to the switching of the IAB-node to a new parent node, the path reconfiguration parameter is transmitted by an RRC reconfiguration message before the IAB-node is handed over, wherein after the second transceiving unit 1102 receives a handover success indication transmitted by the IAB-node after completing random access to the new parent node, the second processing unit 1101 triggers changing the routes of the first path data.
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to the switching of the IAB-node to a new parent node, the path reconfiguration parameter may be transmitted from an F1AP message received from the donor-CU after the IAB-node completes handover, wherein,
In at least one embodiment, in the case where the situation where the destination BAP address of the first path of the IAB-node is unreachable due to radio link failure occurring in the link between the IAB-node and the first parent node, the path reconfiguration parameter is transmitted from the RRC reconfiguration message or F1AP message received from the donor-CU after the IAB-node completes reestablishment to the new parent node, wherein,
In at least one embodiment, in the case where the situation where the destination BAP address of the first path of the IAB-node is unreachable due to radio link failure occurring in the link between the IAB-node and the first parent node, the path reconfiguration parameter is transmitted from the F1AP message received from the donor-CU after the IAB-node reports radio link failure information to the donor-CU, wherein,
According to the embodiment of the fifth aspect of this disclosure, routing change is performed on the first path data, thereby transmitting the data based on the changed route, and avoiding loss of data.
The embodiment of this disclosure provides an apparatus for transmitting and receiving a signal. The apparatus may be, for example, an integrated access and backhaul donor node centralized unit (IAB-donor CU), or may be one or some components of assemblies configured in the IAB-donor CU. The IAB-donor CU may be, for example, the donor-CU in
In at least one embodiment, the path reconfiguration parameter includes a destination BAP address and path identifier of the first path.
In at least one embodiment, the path reconfiguration parameter includes mapping between the destination BAP address of the first path and a destination BAP address of the second path, or includes mapping between the destination BAP address and path identifier of the first path and the destination BAP address and path identifier of the second path.
In at least one embodiment, the situation where the destination BAP address of the first path of the IAB-node is unreachable includes that:
In at least one embodiment, the path reconfiguration parameter includes the destination BAP address, the path identifier of the second path and identifier of a backhaul RLC channel from the IAB-node to a next hop of node of the second path.
In at least one embodiment, the destination BAP address of the second path is a destination BAP address used for uplink F1-C and non-F1 data, and the path ID of the second path is a path ID used for the uplink F1-C and non-F1 data, or,
In at least one embodiment, the identifier of the backhaul RLC channel to the next hop of node of the second path is:
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to the switching of the IAB-node to a new parent node,
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to a radio link failure occurring in the link between the IAB-node and the first parent node, the third transceiving unit 1201 transmits an RRC reconfiguration message or F1 AP message containing the path reconfiguration parameter to the IAB-node or the child node after the IAB-node complete completes reestablishment to a new parent node.
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to a radio link failure occurring in the link between the IAB-node and the first parent node, the third transceiving unit 1201 transmits an RRC reconfiguration message or F1 AP message containing the path reconfiguration parameter to the IAB-node or the child node after the IAB-node reports radio link failure information to the donor-CU.
In at least one embodiment, in the case where the destination BAP address of the first path is unreachable due to a radio link failure occurring in the link between the IAB-node and the first parent node, the third transceiving unit 1201 transmits an RRC reconfiguration message containing the path reconfiguration parameter to the child node before the radio link failure occurs in the IAB-node.
According to the embodiment of the third aspect of this disclosure, the IAB-node or its child node may perform routing change on the first path data by using the routing reconfiguration parameter. Hence, the IAB-node or its child node may transmit the data based on the changed route, thereby avoiding loss of data.
The above implementations only illustrate the embodiment of this disclosure. However, this disclosure is not limited thereto, and appropriate variants may be made on the basis of these implementations. For example, the above implementations may be executed separately, or one or more of them may be executed in a combined manner.
The embodiment of this disclosure provides a communication system, and reference may be made to
In some embodiments, the communication system may include:
An integrated access and backhaul node may include an IAB-MT functional unit and an IAB-DU functional unit, the IAB-MT functional unit having a structure identical to a terminal equipment, and the IAB-DU functional unit and the integrated access and backhaul donor centralized unit (IAB-donor CU) having a structure identical to a network device.
For example, the processor 1310 may be configured to execute a program to carry out the method executed by the IAB-DU in the embodiment of the first aspect or the method executed by the IAB-donor DU in the embodiment of the second aspect.
Furthermore, as shown in
As shown in
An embodiment of this disclosure provides a computer readable program, which, when executed in an IAB, causes the IAB to carry out the method for transmitting and receiving a signal as described in the embodiment of the first aspect.
An embodiment of this disclosure provides a computer storage medium, including a computer readable program, which causes an IAB to carry out the method for transmitting and receiving a signal as described in the embodiment of the first aspect.
An embodiment of this disclosure provides a computer readable program, which, when executed in a child node of an IAB-node, causes the child node to carry out the method as described in the embodiment of the second aspect.
An embodiment of this disclosure provides a computer storage medium, including a computer readable program, which causes a child node of an IAB-node to carry out the method as described in the embodiment of the second aspect.
An embodiment of this disclosure provides a computer readable program, which, when executed in a donor-CU, causes the donor-CU to carry out the method as described in the embodiment of the third aspect.
An embodiment of this disclosure provides a computer storage medium, including a computer readable program, which causes a donor-CU to carry out the method as described in the embodiment of the third aspect.
The above apparatuses and methods of this disclosure may be implemented by hardware, or by hardware in combination with software. This disclosure relates to such a computer-readable program that when the program is executed by a logic device, the logic device is enabled to carry out the apparatus or components as described above, or to carry out the methods or steps as described above. This disclosure also relates to a storage medium for storing the above program, such as a hard disk, a floppy disk, a CD, a DVD, and a flash memory, etc.
The methods/apparatuses described with reference to the embodiments of this disclosure may be directly embodied as hardware, software modules executed by a processor, or a combination thereof. For example, one or more functional block diagrams and/or one or more combinations of the functional block diagrams shown in the drawings may either correspond to software modules of procedures of a computer program, or correspond to hardware modules. Such software modules may respectively correspond to the steps shown in the drawings. And the hardware module, for example, may be carried out by firming the soft modules by using a field programmable gate array (FPGA).
The soft modules may be located in an RAM, a flash memory, an ROM, an EPROM, and EEPROM, a register, a hard disc, a floppy disc, a CD-ROM, or any memory medium in other forms known in the art. A memory medium may be coupled to a processor, so that the processor may be able to read information from the memory medium, and write information into the memory medium; or the memory medium may be a component of the processor. The processor and the memory medium may be located in an ASIC. The soft modules may be stored in a memory of a mobile terminal, and may also be stored in a memory card of a pluggable mobile terminal. For example, if equipment (such as a mobile terminal) employs an MEGA-SIM card of a relatively large capacity or a flash memory device of a large capacity, the soft modules may be stored in the MEGA-SIM card or the flash memory device of a large capacity.
One or more functional blocks and/or one or more combinations of the functional blocks in the drawings may be realized as a universal processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware component or any appropriate combinations thereof carrying out the functions described in this application. And the one or more functional block diagrams and/or one or more combinations of the functional block diagrams in the drawings may also be realized as a combination of computing equipment, such as a combination of a DSP and a microprocessor, multiple processors, one or more microprocessors in communication combination with a DSP, or any other such configuration.
This disclosure is described above with reference to particular embodiments. However, it should be understood by those skilled in the art that such a description is illustrative only, and not intended to limit the protection scope of the present disclosure. Various variants and modifications may be made by those skilled in the art according to the spirits and principle of the present disclosure, and such variants and modifications fall within the scope of the present disclosure.
As to implementations containing the above embodiments, following supplements are further disclosed.
A method at an IAB-node side:
A method at a child node of an IAB-node side:
A method at a donor-CU side:
This application is a continuation application of International Application PCT/CN2021/084795 filed on Mar. 31, 2021, and designated the U.S., the entire contents of which are incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2021/084795 | Mar 2021 | US |
| Child | 18372189 | US |
