Delivering services in integrated access and backhaul communications

By sending target service requests and configuration information between IAB donors, service routing in IAB communication is realized, the connection interruption problem caused by IAB node handover is solved, the reliability and robustness of communication is improved, and the routing path is increased usability.

CN114667757BActive Publication Date: 2024-12-06ALCATEL LUCENT SHANGHAI BELL CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080022458.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-10-22
Publication Date
2024-12-06
Estimated Expiration
2040-10-22

AI Technical Summary

Technical Problem

In IAB communication, due to backhaul connection failure or topological changes, the IAB node may need to switch the service node, resulting in connection interruption. In traditional solutions, only one F1 interface can be activated during topological adaptation between donors, affecting communication reliability and robustness, which affects communication reliability and robustness. .

Method used

By sending target service requests and configuration information between IAB donors, services are allowed to route between donors, using the DU of the target IAB donor to route services to IAB nodes, and even continue to send and receive services before topological adaptation, reducing the impact of interruptions. And add available routing paths in topological redundancy scenarios.

Benefits of technology

Improves the reliability and robustness of IAB communications, reduces the impact on end devices during topological adaptation between donors, increases the availability of routing paths, and reduces the risk of connection disruption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114667757B_ABST
    Figure CN114667757B_ABST
Patent Text Reader

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses, and computer-readable storage media for delivering services in integrated access and backhaul (IAB) communications. According to an embodiment of the present disclosure, a first central unit control plane (CU‑CP) of a first IAB donor sends a request to a second CU‑CP of a second IAB donor to deliver a target service via a distributed unit (DU) of the second IAB donor. The request includes first information of the target service. The first CU‑CP receives second information from the second CU‑CP to be used to configure the target service. This solution can improve the reliability and robustness of IAB communications.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to devices, methods, apparatuses, and computer-readable media for delivering traffic in Integrated Access and Backhaul (IAB) communications. Background Art

[0002] IAB has been introduced in Release 16 (Rel-16) of the 3GPP specification as a key enabler for fast and cost-effective deployment. IAB nodes use the same or different spectrum and air interface for access and backhaul to create a hierarchical wireless multi-hop (multiple backhaul links) network between sites. These jumps eventually terminate at the IAB donor, which is connected to the core network by means of a conventional fixed backhaul. The IAB node includes a mobile terminal (MT) part that serves as a user equipment (UE) toward its parent distributed unit (DU), and a DU part that serves as a base station toward a mobile terminal and / or a child IAB node. The IAB donor includes a central unit (CU) part and a DU part. The IAB DU can provide one or more cells to serve the UE.

[0003] Due to possible failures on the backhaul (BH) connection or changes in the IAB topology or IAB mobility, the IAB node may need to change its serving node, which may be under the same or different IAB donors (multiple). In the latter case, the process of switching and connecting to the new IAB donor is time consuming. This may result in connection and service interruption at the UE connected to the IAB node. Summary of the invention

[0004] In general, example embodiments of the present disclosure provide devices, methods, apparatuses, and computer-readable media for delivering traffic in IAB communications.

[0005] In a first aspect, a method is provided. The method includes: sending, at a first central unit control plane (CU-CP) of a first integrated access and backhaul (IAB) donor to a second CU-CP of a second IAB donor, a request for delivering a target service via a distributed unit (DU) of the second IAB donor, the request including first information of the target service; and receiving, from the second CU-CP, second information to be used for configuring the target service.

[0006] In a second aspect, a method is provided. The method includes: receiving, at a second central unit control plane (CU-CP) of a second integrated access and backhaul (IAB) donor, from a first CU-CP of a first IAB donor, a request to deliver a target service via a distributed unit (DU) of a second IAB donor, the request including first information of the target service; determining second information to be used for the target service based on the first information; and sending the second information to the first CU-CP.

[0007] In a third aspect, a method is provided. The method includes: receiving, at a central unit user plane (CU-UP) of a first integrated access backhaul (IAB) donor from a first central unit control plane (CU-CP) of a first IAB donor, fourth information for updating quality of service mapping information for a user plane service of an interface between the CU-UP and an IAB node, the user plane service to be delivered to the IAB node; and sending a user plane service including at least a portion of the fourth information to the IAB node via a distributed unit (DU) of the first IAB donor or the second IAB donor.

[0008] In a fourth aspect, a first device is provided. The first device includes at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the first device to send a request to deliver a target service via a distributed unit (DU) of a second IAB donor to a second CU-CP of a second IAB donor at a first central unit control plane (CU-CP) of a first integrated access and backhaul (IAB) donor, the request including first information of the target service; and receive second information to be used to configure the target service from the second CU-CP.

[0009] In a fifth aspect, a second device is provided. The second device includes at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, enable the second device to receive, at a second central unit control plane (CU-CP) of a second integrated access and backhaul (IAB) donor, a request from a first CU-CP of a first IAB donor to deliver a target service via a distributed unit (DU) of a second IAB donor, the request including first information of the target service; determine second information to be used for the target service based on the first information; and send the second information to the first CU-CP.

[0010] In a sixth aspect, a third device is provided. The third device includes at least one processor; and at least one memory including computer program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the third device to receive fourth information from a first central unit control plane (CU-CP) of a first integrated access backhaul (IAB) donor at a central unit user plane (CU-UP) of a first IAB donor, the fourth information being used to update the quality of service mapping information of the user plane service of the interface between the CU-UP and the IAB node, the user plane service to be delivered to the IAB node; and send a user plane service including at least a portion of the fourth information to the IAB node via a distributed unit (DU) of the first IAB donor or the second IAB donor.

[0011] In a seventh aspect, a first device is provided. The first device includes: a component for sending a request for delivering a target service via a distributed unit (DU) of a second IAB donor to a second CU-CP of a second IAB donor at a first central unit control plane (CU-CP) of a first integrated access and backhaul (IAB) donor, the request including first information of the target service; and a component for receiving second information to be used for configuring the target service from the second CU-CP.

[0012] In an eighth aspect, a second device is provided. The second device includes: a component for receiving, at a second central unit control plane (CU-CP) of a second integrated access and backhaul (IAB) donor, a request for delivering a target service via a distributed unit (DU) of a second IAB donor from a first CU-CP of a first IAB donor, the request including first information of the target service; a component for determining second information to be used for the target service based on the first information; and a component for sending the second information to the first CU-CP.

[0013] In a ninth aspect, a third device is provided. The third device includes: a component for receiving fourth information from a first central unit control plane (CU-CP) of a first integrated access backhaul (IAB) donor at a central unit user plane (CU-UP) of the first IAB donor, the fourth information being used to update quality of service mapping information for user plane services of an interface between the CU-UP and the IAB node, the user plane services to be delivered to the IAB node; and a component for sending user plane services including at least a portion of the fourth information to the IAB node via a distributed unit (DU) of the first IAB donor or the second IAB donor.

[0014] In a tenth aspect, a computer-readable storage medium including program instructions stored thereon is provided. When the instructions are executed by a device, the device performs the method according to the first, second or third aspect.

[0015] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some example embodiments of the present disclosure in the accompanying drawings, in which:

[0017] Figure 1 A block diagram of a system for IAB communications is illustrated;

[0018] Figure 2a and Figure 2b illustrates an example IAB environment in which embodiments of the present disclosure may be implemented;

[0019] Figure 3 A flow chart illustrating an example process for delivering a service according to some embodiments of the present disclosure is shown;

[0020] Figure 4 illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0021] Figure 5a illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0022] Figure 5b illustrates a flow chart of an example method according to some example embodiments of the present disclosure;

[0023] Figure 6 illustrates a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure; and

[0024] Figure 7 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is illustrated.

[0025] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0026] The principles of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for illustrative purposes, and help those skilled in the art to understand and implement the present disclosure, without any limitation to the scope of the present disclosure. The disclosure described herein can be implemented in various other ways except for the way described below.

[0027] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0028] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. In addition, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other example embodiments (whether or not explicitly described).

[0029] It should be understood that although the terms "first" and "second" etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the exemplary embodiment, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0030] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will be further understood that when used herein, the terms "include", "comprising", "having", "with", "including" and / or "comprising" specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0031] As used in this application, the term "circuitry" may refer to one, more, or all of the following:

[0032] (a) Pure hardware circuit implementation (such as implementation in analog and / or digital circuit systems only)

[0033] now); and

[0034] (b) a combination of hardware circuitry and software such as (where applicable):

[0035] (i) a combination of analog and / or digital hardware circuits and software / firmware, and

[0036] (ii) any portion of hardware processor(s) (including digital signal processor(s)), software and memory(s) with software that work in conjunction to cause a device such as a mobile phone or server to perform various functions; and

[0037] (c) Hardware circuit(s) and / or processor(s) that require software (e.g., firmware) to operate (but the software may be absent when not required for operation), such as microprocessor(s) or portion(s) of microprocessor(s).

[0038] This definition of "circuitry" applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term "circuitry" also covers an implementation of a pure hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuitry" also covers (for example and if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing or network device.

[0039] As used herein, the term "communication network" refers to a network that follows any suitable communication standard such as long term evolution (LTE), advanced LTE (LTE-A), wideband code division multiple access (WCDMA), high speed packet access (HSPA), narrowband Internet of Things (NB-IoT), new radio (NR), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to the communication protocol of any suitable generation, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocol, and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, there will certainly be communication technologies and systems that can embody future types of the present disclosure. It should not be considered that the scope of the present disclosure is limited to the above-mentioned system.

[0040] As used herein, the term "network device" refers to a node in a communication network, via which a terminal device accesses the network and receives services therefrom. A network device may refer to a base station (BS) or an access point (AP), such as a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low-power node (such as a femto, a micro), depending on the terminology and technology applied. In addition, an IAB node or an IAB-DU is an example of a network device. In the following description, the terms "network device", "BS" and "node" may be used interchangeably.

[0041] The term "terminal device" refers to any terminal device that can perform wireless communication. As an example and not limitation, the terminal device may also be referred to as a communication device, a user equipment (UE), a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop-mounted device (LME), a USB dongle, a smart device, a wireless user premises equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices running in industrial and / or automated processing chain environments), consumer electronic devices, equipment operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0042] Example embodiments of the present disclosure relate to a radio access network with a wireless backhaul of an access point. The backhaul may be multi-hop or meshed. An important application of the embodiments of the present disclosure is for IAB communications in a 3GPP IAB network with a terminal device, an IAB node, and a wired IAB donor node. The embodiments of the present disclosure are described below with reference to a 3GPP IAB network. It is understood that the embodiments of the present disclosure may also be applied to any other network with a wireless backhaul.

[0043] Figure 1 1 shows a block diagram of a system 100 for IAB communication. Figure 1As shown, system 100 includes a core network (CN) 110, an IAB donor 120, IAB nodes 130-1 and 130-2 (collectively referred to as "IAB nodes 130" or individually referred to as "IAB nodes 130"), and terminal devices 150-1, 150-2, and 150-3 (collectively referred to as "terminal devices 150" or individually referred to as "terminal devices 150"). As used herein, the terms "IAB nodes" and "IAB devices" may be used interchangeably. The terms "IAB donor nodes", "IAB donors", and "IAB donor devices" may be used interchangeably.

[0044] In such Figure 1 In the illustrated architecture, the CN interface terminates at the IAB donor 120, so the relay is only a radio access network (RAN) function. The architecture utilizes a split gNB architecture for CU and DU, such that the CU functionality is at the IAB donor 120 and the DU functionality is at the IAB donor DU 122 or IAB node 130. For connection establishment and communication with the parent node (which can be another IAB node or an IAB donor), the IAB node 130 hosts the MT functionality corresponding to the UE operation or a portion of the UE operation.

[0045] The IAB donor 120 may include a CU 121 (also referred to as “IAB donor CU 121”) and a DU 122 (also referred to as “IAB donor DU 122”). It should be understood that the CU 121 and the DU 122 may be implemented in the same device or in different devices. The CU 121 may also include a CU control plane (CU-CP) 123 and one or more CU user planes (CU-UP) 124. It should be understood that the CU-CP 123 and the CU-UP 124 may be implemented in the same device or in different devices. The IAB node 130-1 may include an MT portion 131-1 and a DU 132-1. The IAB node 130-2 may include an MT portion 131-2 and a DU 132-2. The MT portion 131-1 and the MT portion 131-2 are also collectively referred to as “IAB MT 131” or individually referred to as “IAB MT 131”. DU 132-1 and DU 132-2 are also collectively referred to as "IAB DU 132" or individually referred to as "IAB DU 132".

[0046] The IAB donor DU 122 or each IAB DU 132 may provide one or more cells to serve the terminal device and / or one or more IAB-MTs 131. For example, Figure 1 As shown, IAB donor DU 122 serves terminal device 150-1, IABDU 132-1 serves terminal device 150-2, and IAB DU 132-2 serves terminal device 150-3.

[0047] The IAB MT 131 of the IAB node 130 may be used as a UE toward its parent node. For example, the IAB MT 131-1 may be used as a UE toward the IAB donor 120 (i.e., the IAB donor DU 122), and the IAB MT 131-2 may be used as a UE toward the IAB node 130-1 (i.e., the IAB DU 132-1). On the sublink, the IAB DU 132 of the IAB node 130 may be used as a network device (such as a gNB) toward its next-hop IAB node. For example, the IAB donor DU 122 may be used as a gNB toward the IAB node 130-1, and the IAB DU 132-1 may be used as a gNB toward the IAB node 130-2. On the access link, the IAB donor 120 and the IAB node 130 may be used as ordinary network devices to provide a radio interface for the terminal device 150 within its coverage area.

[0048] (Multiple) BH radio link control (RLC) channels can be established between the IAB MT 131 and the DU of the parent node, and an adaptation layer called a backhaul adaptation protocol (BAP) is agreed to be located above the RLC layer. The IAB DU 132 is connected to the IAB donor CU 121 through an F1 interface that supports the IAB function. For example, the IAB DU 132-1 is connected to the IAB donor CU 121 via the F1 interface 190, and the IAB DU 132-2 is connected to the IAB donor CU 121 via the F1 interface 180. The F1 interface may include an F1-C interface and an F1-U interface. The IAB DU 132 is connected to the IAB donor CU-CP 123 via the F1-C interface, and the IAB DU 132 is connected to the IAB donor CU-UP 124 via the F1-U interface.

[0049] The F1 interface traffic includes traffic of the F1-U interface (also referred to as "F1-U traffic") and traffic of the F1-C interface (also referred to as "F1-C traffic"). The F1 interface traffic is sent over the adaptation layer. Therefore, the IAB implements L2 relaying. In order to enable downlink (DL) F1 traffic to be routed to the serving IAB donor DU 122 for the IAB node 130, the IAB node 130 is allocated with (multiple) Internet Protocol (IP) addresses (e.g., external IP addresses when the IPSec tunnel is enabled) anchored in the IAB donor DU 122. When the IAB donor CU 121 sends DL F1 traffic to the IAB node 130, the F1 traffic is routed to the IAB donor DU 122 based on the IP address. The IAB donor DU 122 maps the DL F1 traffic to the relevant BH RLC channel based on the configuration previously configured by the IAB donor CU 121. The configuration includes a Differentiated Services Code Point (DSCP) and / or Internet Protocol Version 6 (IPv6) flow label and / or IP address to identify DL F1 traffic, and related BH RLC channel information. This requires the IAB donor CU 121 (e.g., donor CU-CP or donor CU-UP) to use specific DSCP and / or IPv6 flow label and / or IP address to support traffic mapping in the IAB donor DU 122.

[0050] Furthermore, during topology adaptation, the serving IAB donor DU for the IAB node 130 may change from a source IAB donor DU to a target IAB donor DU. Therefore, the IAB node 130 may acquire the new IP address(es) anchored in the target IAB donor DU.

[0051] Communications in environment 100 may be implemented according to any appropriate communications protocol, including but not limited to cellular communications protocols of the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G), fifth generation (5G), etc., wireless local area network communications protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocols currently known or to be developed in the future. In addition, communications may utilize any appropriate wireless communications technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplexer (FDD), time division duplexer (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDMA), and / or any other currently known or to be developed in the future.

[0052] On the one hand, due to possible failures on the BH connection or changes in the IAB topology or IAB mobility, the IAB node may need to change its serving node. This change in backhaul topology may involve a change in the parent IAB node of the IAB node or even the IAB donor. The latter case of an IAB donor change can be considered as an inter-donor topology adaptation. On the other hand, topology redundancy has been proposed to achieve robust operation, for example, in the event of backhaul link congestion, and to balance the load between backhaul links. In an inter-donor topology redundancy scenario, an IAB node with multiple IAB DUs can have multiple F1 interfaces with multiple IAB donor CUs, where the IAB DUs interface with the corresponding IAB donor CUs.

[0053] Figure 2a and Figure 2b 2 illustrates an example IAB environment 200 and environment 205 in which embodiments of the present disclosure may be implemented. Figure 2a and Figure 2b As shown, environment 200 and environment 205 include an IAB donor 210 (hereinafter also referred to as "first IAB donor" or "source donor" or "donor 1"), an IAB donor 220 (hereinafter also referred to as "second IAB donor" or "target donor" or "donor 2"), an IAB node 250 (also referred to as "source parent unit" or "source parent"), an IAB node 260 (also referred to as "target parent unit" or "target parent"), an IAB node 240, and terminal devices 270-1 and 270-2 (collectively referred to as "terminal devices 270" or individually referred to as "terminal devices 270").

[0054] The IAB donor 210 includes a CU 211 (hereinafter also referred to as "IAB donor CU 211" or "donor 1 CU 211") and a DU 212 (hereinafter also referred to as "IAB donor DU 212" or "donor 1 DU 212"). The IAB donor CU 211 may include a CU-CP 213, hereinafter also referred to as "donor 1 CU-CP 213", and a CU-UP 214, hereinafter also referred to as "donor 1 CU-UP 214".

[0055] The IAB donor 220 includes a CU 221 (hereinafter also referred to as an "IAB donor CU 221" or a "donor 2CU 221") and a DU 222 (hereinafter also referred to as an "IAB donor DU 222" or a "donor 2DU 222"). The IAB donor CU 221 may include a CU-CP 223, hereinafter also referred to as a "donor 2CU-CP 223", and a CU-UP 224, hereinafter also referred to as a "donor 2CU-UP 224".

[0056] The IAB node 250 serving as an intermediate node between the IAB donor 210 and the IAB node 240 includes a MT 251 and a DU 252. Likewise, the IAB node 260 serving as an intermediate node between the IAB donor 220 and the IAB node 240 includes a MT 261 and a DU 262.

[0057] The IAB node 240 includes an MT 241 (hereinafter also referred to as “IAB MT 241”) and at least one DU 242-1 (hereinafter also referred to as “IAB DU 242-1”). Figure 2a As shown, in some example embodiments, IAB node 240 may further include DU 242-2 (hereinafter also referred to as "IAB DU 242-2"). DU 242-1 and 242-2 may be collectively referred to as "IAB DU 242" or individually referred to as "IAB DU 242". It should be understood that Figure 2a and Figure 2b The number of DUs in the IAB node 240 shown is for illustration purposes only and does not impose any limitation on the scope of the present disclosure.

[0058] Figure 2a 2 shows a topology adaptation scenario. IAB node 240 is initially connected to IAB node 250, so IAB donor 210 serves as a serving IAB donor for IAB node 240. During topology adaptation, IAB node 240 migrates from source IAB node 250 to target IAB node 260 of a different CU. Figure 2a As shown, an F1 interface 280 (including an F1-C interface and an F1-U interface) is established between the IAB DU 242 (e.g., DU 242-1) and the IAB donor CU 211, and a BH link is also established between the IAB MT 241 and the DU 252. After topology adaptation, an F1 interface 291 is established between the IAB DU 242 (e.g., DU 242-2) and the IAB donor CU 221, and a BH link is also established between the IAB MT 241 and the DU 262.

[0059] Figure 2b The topology redundancy scenario is shown. Figure 2bAs shown, the IAB node 240 is connected to both IAB nodes 250 and 260, so the IAB donors 210 and 220 act as serving IAB donors for the IAB node 240. An F1 interface 280 is established between the IAB DU 242-1 and the IAB donor CU 211. A BH link is also established between the IAB MT 241 and the DU 252. An F1 interface 292 is established between the IAB DU 242-2 and the IAB donor CU 221. A BH link is also established between the IAB MT 241 and the DU 262. It is also possible that the IAB node 240 has only one DU, and the DU in the IAB node 240 has only the F1 interface 280 or the F1 interface 292.

[0060] It should be understood that the number of IAB donors, IAB nodes, and terminal devices connected to the IAB nodes is for illustrative purposes only, without any limitation on the scope of the present disclosure. It should also be understood that the number of CUs, DUs, and MTs is for illustrative purposes only, without any limitation on the scope of the present disclosure. The communication system may include any suitable number of IAB donors, IAB nodes, and terminal devices suitable for implementing the exemplary embodiments of the present disclosure. For example, in some exemplary embodiments, the IAB node 240 may be directly connected to an IAB donor, such as the IAB donor 210 or 220. For another example, in some exemplary embodiments, there may be more than one intermediate IAB node between the IAB node 240 and the IAB donor (e.g., the IAB donor 210 or 220). The transmission path via DU212 and one or more intermediate IAB nodes (e.g., the IAB node 250) is referred to as a "source path". The transmission path via DU222 and one or more intermediate IAB nodes (e.g., the IAB node 260) is referred to as a "target path".

[0061] Conventionally, traffic between a CU of an IAB donor and an IAB node cannot be sent and routed via a DU of another IAB donor. Figure 2a and Figure 2b, the services of F1 interface 280 can only be sent via the source path, and the services of F1 interface 291 or F1 interface 292 can only be sent via the target path. In a topology adaptation scenario where the service IAB donor for the IAB node changes from the source IAB donor to the target IAB donor, the CU of the source IAB donor cannot send its DL F1 services to the IAB node via the target path (i.e., via the DU of the target IAB donor), and the CU of the target IAB donor cannot send its DL F1 services to the IAB node via the source path (i.e., via the DU of the source IAB donor). This means that only one of the F1 interfaces (F1 interface 280 or F1 interface 291 / 292) can be activated at any given time. Since the establishment of a secure connection between the IAB node and the target IAB donor is time-consuming, it may cause interruption of connection and service at the terminal device connected to the IAB node. Therefore, in the topology adaptation scenario, it is expected that the F1 traffic between the CU of the source IAB donor and the IAB node can be sent and routed via the DU of the target IAB donor, so that the IAB node can first switch to the target donor before establishing a secure connection via the target path, establish a BH RLC channel with the target parent cell, and continue the F1 traffic between the source IAB donor and the IAB node routed via the target path. For example, according to some embodiments of the present disclosure, by setting the target IP address of the IP header to the IP address of the IAB node 240 anchored in the DU 222, the traffic sent from the IAB donor CU 211 to the IAB node 240 is routed to the DU 222 and further sent to the IAB node 260. When the IAB 240 node sends uplink traffic to the CU 211, the traffic is sent via the target path, that is, the traffic is sent to the intermediate IAB node 260 and further sent to the DU 222, and then the DU 222 forwards the traffic to the CU 211. By using the target path for traffic of the F1 interface 280, this enables the IAB donor CU 211 to first switch the IAB to the target donor, while the F1 traffic for the F1 interface 280 can still be sent via the target path. This can reduce disruption to the UE.

[0062] According to some other embodiments of the present disclosure, the interruption can be reduced by first establishing the F1 interface 291 on the source path. The business of the F1 interface between the target donor and the IAB node can be sent through the source path (i.e., via the DU of the source donor). For example, by setting the target IP address of the IP header to the IP address of the IAB node 240 anchored in the DU 212, the business sent from the IAB donor CU 221 to the IAB node 240 is routed to the DU 212 and further sent to the IAB node 240. When the IAB 240 node sends an uplink business to the CU 221, the business is sent via the source path, that is, the business is sent to the intermediate IAB node 250 and further sent to the DU 212, and the DU 212 then forwards the business to the CU 221. By using the source path for the F1 interface 291, this enables the IAB donor CU 211 to initiate a handover process for the UE connected to the IAB node 240, while the IAB node 240 is still connected to the IAB donor 210. This allows the source donor to first handover the UE to the target donor and then handover the IAB node to the target donor, thereby reducing disruption.

[0063] In a topology redundancy scenario in which an IAB node is connected to at least two IAB donors and a BH RLC channel is established between the IAB node and a source parent cell (e.g., between IAB node 240 and IAB node 250) and between the IAB node and a target parent cell (e.g., between IAB node 240 and IAB node 260), according to a conventional solution, traffic between a CU of a first IAB donor and an IAB node cannot be sent and routed via a DU of a second IAB donor, and traffic between a CU of a second IAB donor and an IAB node cannot be sent and routed via a DU of a first IAB donor. For example, if a path from a DU of a first IAB donor to an IAB node is blocked, DL F1 traffic of the first IAB donor cannot be routed to the IAB node. Therefore, the benefit of topology redundancy is lost. Therefore, in a topology redundancy scenario, it is expected that traffic between the CU of the first IAB donor and the IAB node can be sent and routed via the DU of the second IAB donor, and traffic between the CU of the second IAB donor and the IAB node can be sent and routed via the DU of the first IAB donor.

[0064] Embodiments of the present disclosure provide a scheme for delivering services in IAB communications to solve the above problems and one or more other potential problems. In this solution, a first IAB donor (e.g., a CU-CP of a first IAB donor) sends a request to a second IAB donor (e.g., a CU-CP of a second IAB donor) to deliver a target service via a DU of a second IAB donor. The target service may include an F1 service between a first IAB donor and an IAB node. In some example embodiments, the target service may include an F1-C service between a CU-CP of a first IAB donor and an IAB node. Alternatively or additionally, in some example embodiments, the target service may include an F1-U service between a CU-UP of a first IAB donor and an IAB node. The request includes characteristic information of the target service. The first IAB donor then receives service identification information to be used to configure the target service from the second IAB donor. This solution enables an IAB donor to route a service to an IAB node via another IAB donor (e.g., via a DU of another IAB donor). In this way, the solution can improve the reliability and robustness of IAB communications. For example, in a topology adaptation scenario, the solution can allow the UE to continue to send and receive before the F1-C interface and the F1-U interface are migrated to the target donor, thereby reducing the impact on the UE served by the migrated IAB node during the inter-donor topology adaptation. For another example, in a topology redundancy scenario, the solution can increase the number of available routing paths.

[0065] Some example embodiments are described in detail below. Figure 3 A flow chart illustrating an example process 300 for delivering a service according to some embodiments of the present disclosure is shown. For the purpose of discussion, reference will be made to Figure 2a and 2b 3. Process 300 is described below. Process 300 involves at least IAB donor 210 and IAB donor 220. In some example embodiments, process 300 may further involve IAB node 240.

[0066] like Figure 3 As shown in block 301 of FIG. 1 , in some example embodiments, the IAB node 240 may initially connect to the IAB donor 210. For example, the F1 interface 280 is provided between the donor CU 211 and the DU 242. In this case, the F1 traffic may be sent from the donor CU 211 to the IAB node 240, for example, as Figure 2a and 2b304. The IAB DU 242 is shown. For example, F1-C traffic from the CU-CP 213 to the IAB DU 242 in the IAB node 240 may be routed 302 to the donor 1DU 212. The donor 1DU 212 may then perform traffic mapping to the relevant BH RLC channels and send 304 the F1-C traffic to the IAB DU 242 over the wireless backhaul. Similarly, F1-U traffic from the CU-UP 214 to the IAB DU 242 in the IAB node 240 may be routed 306 to the donor 1DU 212. The donor 1DU 212 may perform traffic mapping to the relevant BH RLC channels and then send 308 the F1-U traffic to the IAB DU 242.

[0067] In some example embodiments, such as in a topology redundancy scenario, IAB node 240 may be connected to both IAB donor 210 and IAB donor 220, or directly to the donor DUs of IAB donor 210 and IAB donor 220, or through one or more intermediate nodes between IAB node 240 and the donor DUs of IAB donor 210 and IAB donor 220. In this case, F1-C / U traffic may be sent from donor 1 CU 211 to IAB node 240 and from donor 2 CU 221 to IAB node 240.

[0068] In the example process 300, the IAB donor 210 sends 305 to the IAB donor 220 a request for a target service of an interface between the IAB donor 210 and the IAB node 240 to be delivered via the donor 2DU 222 of the IAB donor 220. The target service may include an F1 service between the IAB donor 210 and the IAB node 240. In some example embodiments, the target service may include an F1-C service between the CU-CP 213 of the IAB donor 210 and the IAB node 240. Alternatively or additionally, the target service may include an F1-U service between the CU-UP 214 of the IAB donor 210 and the IAB node 240. Hereinafter, such a request may be referred to as a "routing request" for the purpose of discussion without any limitation on the scope of the present disclosure. For example, the CU-CP 213 of the donor 1 CU 211 may send a routing request to the CU-CP 223 of the donor 2 CU 221. The routing request may request the IAB donor 220 to enable delivery of target traffic (eg, F1-C / U traffic from the donor 1CU 211 ) to the IAB node 240 via the donor 2DU 222 .

[0069] The trigger for sending a routing request may depend on the specific scenario. Figure 2aIn the topology adaptation scenario shown, IAB node 240 may migrate from IAB node 250 to IAB node 260. Therefore, IAB MT 241 may be connected to DU 262 of IAB node 260. In this scenario, the trigger for sending the routing request may be a switching decision made by donor ICU 211, for example, due to load balancing reasons or any other reasons. Figure 2b In the illustrated topology redundancy scenario, the IAB node 240 may be connected to both the IAB donor 210 and the IAB donor 220. In this scenario, the trigger for sending a routing request may be the establishment of a connection to the IAB donor 220. Alternatively or additionally, the trigger for sending a routing request may be a backhaul link congestion or a load balance across backhaul links in a routing path from the IAB donor 210 to the IAB node 240. It should be understood that the above triggers are provided as examples, and the scope of the present disclosure is not limited thereto.

[0070] The routing request may include identification information of the IAB node 240. For example, the routing request may include the identification of the IAB MT 241.

[0071] The routing request may include characteristic information (also referred to as "first information") of the target service to be routed. In some example embodiments, the characteristic information may include a service type indicating whether the target service includes a control plane service or a user plane service. For example, the service type may indicate that the target service includes an F1-C service, or an F1-U service, or other services other than the F1-C service and the F1-U service. In some other example embodiments, the service type may not be included or the service type may indicate that the target service includes both the F1-C service and the F1-U service, which means that the F1-C service and the F1-U service are processed in the same manner. If the target service includes an F1-C service, the service type may also indicate whether the F1-C service includes F1-C signaling associated with the UE or F1-C signaling not associated with the UE.

[0072] Alternatively or additionally, in some example embodiments, the characteristic information may include quality of service (QoS) parameters for the target service. QoS parameters may include, but are not limited to, 5G QoS identifier (5QI), priority level, maximum stream bit rate downlink, maximum stream bit rate uplink, guaranteed stream bit rate downlink, guaranteed stream bit rate uplink, packet delay budget, packet error rate, etc. If the target service includes F1-U service, the characteristic information may include at least one of the above QoS parameters for the F1-U service. F1-C service may also require QoS parameters.

[0073] In some example embodiments, the target service may be directed to at least one terminal device, such as a UE, that communicates with the IAB node 240. Accordingly, the characteristic information may also include an identifier of at least one terminal device. For example, a service type and / or QoS parameters may be provided for each UE in the UE, so the characteristic information may also include an identifier of each UE in the UE. Alternatively or additionally, the characteristic information may also include an identifier of a data radio bearer (DRB) for at least one terminal device. For example, a service type and / or QoS parameters may be provided for each DRB of the UE, so the characteristic information may also include an identifier of the DRB for the UE. Similarly, the characteristic information may include an identifier of a tunnel for at least one terminal device. For example, a service type and / or QoS parameters may be provided for each F1-U tunnel of the UE, so the characteristic information may also include an identifier of the F1-U tunnel for the UE.

[0074] In these example embodiments, which (which) identifiers of the terminal device, DRB, and tunnel are included in the characteristic information may depend on the mapping of the UE bearer to the BH RLC channel. For example, in the case of a 1:1 mapping of the UE bearer to the BH RLC channel, a service type and / or QoS parameters may be provided for each DRB of the UE. Accordingly, the characteristic information may include an identifier of the UE and an identifier of each DRB or F1-U tunnel of the UE. In the following, the identifier of the DRB is also referred to as a "DRB identifier", and the identifier of the F1-U tunnel is also referred to as an "F1-U tunnel identifier".

[0075] In some example embodiments, the routing request may also include a suggestion for delivering the target service. For example, the routing request may include a suggested value for a DSCP for the target service or an Internet Protocol version 6 (IPv6) flow label for the target service, which may be provided by the donor 1CU 211. The suggested value may be a value used by the donor 1CU 211 to send the same or similar type of target service. For example, the DSCP and / or IPv6 flow label is used for F1-C service or F1-U service (which is routed via the donor 1DU 212) sent from the donor 1CU 211 to the IAB node 240. As another example, the routing request may include other information or preferences related to the QoS of the target service.

[0076] The route request may be implemented in any suitable manner. A route request may reuse another request. For example, the route request may be an Xn HANDOVER REQUEST message or an Xn S-NODEADDITION REQUEST message for the IAB MT 241. Alternatively, the route request may be a request dedicated to delivering services via DUs of different IAB donors.

[0077] like Figure 3 As shown, after receiving a routing request from the IAB donor 210, the IAB donor 220 (e.g., donor 2CU 221) determines 310 service identification information or service mapping information (also referred to as "second information") based on characteristic information of the target service. The service identification information will be used to configure and deliver the target service. For example, at least a portion of the service identification information may be incorporated into the IP packet header of the F1 packet by the donor 1CU 211, so that the IAB donor 220 (e.g., DU 222) can identify the F1 packet and map the F1 packet to an appropriate BH RLC channel. After receiving a routing request from the IAB donor 210, the IAB donor 220 (e.g., donor 2CU 221) may establish a routing table between the IAB node and the target parent node (e.g., in a manner such as Figure 2a and Figure 2b (a) BH RLC channel(s) are established between the IAB node 240 and the IAB node 260 shown in FIG. 1 . The establishment of the BH RLC channel(s) may take into account the characteristic information of the target service. The establishment of the BH RLC channel(s) may also be performed in advance, for example, in a topology redundancy scenario, when a parent cell is added as a secondary node for the IAB node. The IAB node 240 is configured with uplink service mapping and routing information, which will be used to send the target service. The intermediate IAB node(s) are also configured with service mapping and routing information, which will be used to send / route the target service.

[0078] The IAB donor 220 may allocate a transport layer address for the IAB node 240. For example, the CU-CP 223 of the donor 2CU 221 may allocate an IP address to the IAB node 240. In some example embodiments, the CU-CP 223 may allocate a backhaul adaptation protocol (BAP) address to be used by the IAB node 240. For example, the IAB node 240 may identify a BAP packet that needs to be terminated at the IAB node 240 by checking the BAP address of the route identifier portion against a previously allocated BAP address. The CU-CP 223 may also allocate a route identifier to be used by a service of a terminal device. The CU-CP 223 may also allocate a BAP path identifier.

[0079] The IAB donor 220 may also assign a DSCP for the target service. The DSCP for the target service may be assigned by the donor 2CU 221 based on characteristic information (e.g., QoS parameters). As an example, a service with QoS #A may be assigned a DSCP of #C, and a service with QoS #B may be assigned a DSCP of #D.

[0080] Alternatively or additionally, the IAB donor 220 may allocate a flow label for the target traffic, for example, an IPv6 flow label for the target traffic. The flow label for the target traffic may be allocated by the donor 2CU 221 based on characteristic information (eg, QoS parameters).

[0081] In the case of 1:1 mapping of UE bearers to BH RLC channels, service identification information may be determined for each DRB or F1-U tunnel of the terminal device. For example, the donor 2CU 221 may allocate a DSCP or flow label for the service of each DRB of the UE.

[0082] In an example embodiment where the routing request includes a suggestion for delivering the target service, the donor 2CU 221 may determine the service identification information by taking into account the suggestion. For example, if the routing request includes a suggested DSCP for the target service, the donor 2CU 221 may assign the suggested DSCP to the target service. Alternatively, the donor 2CU 221 may not take into account the suggestion and determine the service identification information based on its own configuration. For example, the donor 2CU 221 may assign a DSCP different from the suggested DSCP to the target service.

[0083] In some example embodiments, Figure 3 As shown, in response to determining the service identification information, the donor 2CU 221 may configure 315 the donor 2DU 222 to prepare to route the target service. The donor 2CU 221 may also configure a BAP routing table for all IAB nodes along the path from the DU 222 to the IAB node 240, for example, for Figure 2a and 2b The IAB nodes 240 and nodes 260 shown in FIG. 2 are shown in FIG. 241 . For example, the donor 2CU 221 may send configuration information (also referred to as "third information") for configuring the donor 2DU 222 to route the target service to the donor 2DU 222. The configuration information may at least indicate a rule for mapping the target service to the BH RLC channel based on the service identification information. As an example, the configuration information may indicate that the F1 service with a DSCP of #E should be mapped to the BHRLC channel #1. The configuration information may also indicate a BAP routing table.

[0084] Continuing with the example process 300, the IAB donor 220 sends 320 service identification information to the IAB donor 210. For example, the CU-CP 223 of the donor 2 CU 221 may send the service identification information to the CU-CP 213. The service identification information may be sent in response to a routing request.

[0085] The service identification information may include a transport layer address of the IAB node 240. For example, the service identification information may include an IP address of the IAB node 240 assigned by the donor 2CU 221. Alternatively or additionally, the service identification information may include a BAP address and / or a BAP path identifier of the IAB node 240.

[0086] The service identification information may also include a DSCP for the target service assigned by the donor 2CU 221. Alternatively or additionally, the service identification information may include a flow label for the target service, for example, an IPv6 flow label for the target service.

[0087] In the case of 1:1 mapping of UE bearer to BH RLC channel, service identification information may be provided for each DRB or F1-U tunnel of the terminal device. For example, a DSCP or flow label may be provided for the service of each DRB of the UE. The service identification information may also include an identification of the terminal device, a DRB identification or an F1-U tunnel identification related to the terminal device. The service identification information may also include a routing identification for the terminal device.

[0088] After receiving the service identification information from the IAB donor 220, the IAB donor 210 may deliver the target service, which is routed to the donor 2DU 222, to the IAB node 240 by using the service identification information. Specifically, the donor 1CU 211 may incorporate at least a portion of the service identification information into the target service, and transmit the target service (which is routed to the donor 2DU 222) to the IAB node 240. The target service is routed to the donor 2DU 222, and further transmitted to the IAB node 240. For example, the donor 1CU 211 may insert the DSCP and / or IPv6 flow label assigned by the donor 2CU 221 and the IP address of the IAB node 240 into the IP header of the IP packet including the F1 packet. The donor 1CU 211 may then transmit the IP packet including the F1 packet, which is routed to the donor 2DU 222. Donor 2DU 222 performs traffic mapping and sends the IP packet including the F1 packet to IAB node 240, for example, IAB DU 242. In this manner, the F1 traffic is routed from IAB donor 210 to IAB node 240 via DU 222 of IAB donor 220.

[0089] In some example embodiments, the target service may include a user plane service. The CU-CP 213 of the IAB donor 210 may send 325 at least a portion of the service identification information about the user plane service to the CU-UP 214. At least a portion of the service identification information about the user plane service may be referred to as "fourth information". For example, the IP address of the IAB node 240, the DSCP and / or flow label, the identifier of the terminal device, the DRB identifier, or the F1-U tunnel identifier for the F1-U service may be sent from the CU-CP 213 to the CU-UP 214. In some other example embodiments, the CU-CP 213 of the IAB donor 210 may send 325 an update request to the CU-UP 214, the update request including at least a portion of the service identification information about the user plane service to be updated (also referred to as "quality of service mapping information"). The update request indicates the old service identification information (or quality of service mapping information) to be updated by the new service identification information (or quality of service mapping information), for example, the old DSCP value to be updated by the new DSCP value, or the old IPv6 flow label value to be updated by the new IPv6 flow label value. The update process can be initiated by CU-CP213, for example, when the same type of service has been sent from CU-UP 214 to IAB node 240 via donor 1DU (e.g., DU 212), and CU-CP 213 now decides to route the same type of service via donor 2DU (e.g., DU 222). In response to receiving an update request including service identification information (or quality of service mapping information), CU-UP 214 should replace the old service identification information (or quality of service mapping information) with the new service identification information (or quality of service mapping information) for all relevant user plane services. CU-UP 214 then uses the new service identification information (or quality of service mapping information) for additional user plane services to IAB node 240.

[0090] In these example embodiments, CU-UP 214 of IAB donor 210 may send 340 user plane traffic to IAB node 240, which is routed to donor 2DU 222, by using at least a portion of the traffic identification information. Donor 2DU 222 performs traffic mapping and then sends 345 the user plane traffic to IAB node 240. The user plane traffic may include a portion of the traffic identification information. For example, the IP address of IAB node 240 and the DSCP and / or flow label may be inserted into the IP packet header of the IP packet including the F1-U packet at CU-UP 214. The IP packet including the F1-U packet may then be sent from CU-UP 214 to donor 2DU 222. Donor 2DU 222 may perform traffic mapping and then send the IP packet including the F1-U packet to IAB node 240.

[0091] In some example embodiments, the target service may include a control plane service. The CU-CP 213 of the IAB donor 210 may send 330 the control plane service to the IAB node 240 using at least a portion of the service identification information, which is routed to the IAB donor DU 222. The donor 2DU 222 may perform service mapping and then send 335 the control plane service to the IAB node 240. For example, the IP address of the IAB node 240 and the DSCP and / or flow label for the F1-C service may be inserted into the IP packet header of the IP packet including the F1-C packet at the CU-CP 213. The IP packet including the F1-C packet may then be sent from the CU-CP 213 to the donor 2DU 222. The donor 2DU 222 may map the F1-C packet to the BH RLC channel and then send the IP packet including the F1-C packet to the IAB node 240.

[0092] Although not in Figure 3 2, but it should be understood that the donor 2DU 222 may be provided via Figure 2a and 2b The intermediate IAB node 260 shown in the figure sends 335 control plane traffic to the IAB node 240 and sends 345 user plane traffic.

[0093] From the above, it can be seen that in the proposed solution, both user plane traffic and control plane traffic from an IAB donor can be routed to an IAB node via a DU of another IAB donor. It should be understood that the proposed solution is applicable regardless of whether the IAB node is directly or indirectly connected to the IAB donor.

[0094] In the example process 300, the donor 2CU 221 may configure 315 the donor 2DU 222 to route the target traffic in response to determining the traffic identification information. In some example embodiments, the donor 2CU 221 may first send the traffic identification information to the donor 1CU 211, for example, to complete a handshake between the donor 2CU 221 and the donor 1CU 211. If a confirmation message is received from the donor 1CU 211, the donor 2CU 221 may configure the donor 2DU 222 to route the target traffic. If a rejection message is received from the donor 1CU 211, the donor 2CU 221 may not configure the donor 2DU 222 to route the target traffic.

[0095] In these example embodiments, donor 1 CU 211 is enabled to refuse to route the target service via DU 222. For example, in a topology adaptation scenario, if the reason for the topology adaptation is not mobility, such as load balancing, the source donor CU is enabled to refuse topology adaptation. The reason for the refusal may be that the service identification information received from CU 221 supports a DSCP or QoS level that is lower than the acceptable DSCP or QoS level of CU 211. After CU 211 refuses to route the target service via DU 222, a new request is sent to CU 221 or a different node. Alternatively, for example, if there is no radio link problem or a new trigger for topology adaptation, the IAB operation continues to use the original topology.

[0096] although Figure 3 The actions performed by specific elements of IAB donor 210 and IAB donor 220 are shown, but they are only for discussion purposes. These actions can be performed by any suitable elements of IAB donor 210 and IAB donor 220. The elements of IAB donor 210 and IAB donor 220 are described in detail below. Figure 2a , Figure 2b and Figure 3 2 and 3. In some example embodiments, two or more of these elements may be implemented by the same device or apparatus. For example, the DU 222 and CU 221 of the IAB donor 220 may be implemented by the same device or apparatus. For another example, the CU-CP 213 and CU-UP 214 of the IAB donor 210 may be implemented by the same device or apparatus.

[0097] Figure 4 4 is a flowchart of an example method 400 for IAB communication according to some example embodiments of the present disclosure. The method 400 can be implemented at any suitable device. For example, the method 400 can be implemented at Figure 2a and / or Figure 2b The IAB donor 210 is shown as being implemented at the CU-CP 213. For the purposes of this discussion, reference will be made to Figure 2a and / or Figure 2b 4 is used to describe the method 400. Hereinafter, the CU-CP 213 of the IAB donor 210 is also referred to as the “first CU-CP 213”, and the CU-CP 223 of the IAB donor 220 is also referred to as the “second CU-CP 214”. It should be understood that the method 400 may include additional blocks not shown and / or some of the shown blocks may be omitted, and the scope of the present disclosure is not limited in this regard.

[0098] In block 410, the first CU-CP 213 sends a request to the second CU-CP 214 to send a target service of an interface between the first IAB donor 210 and the IAB node 240 via the DU 222 of the second IAB donor 220. The request includes first information of the target service.

[0099] In some example embodiments, the first information includes at least one of the following: a service type indicating whether the target service includes user plane service or control plane service, or a quality of service parameter for the target service.

[0100] In some example embodiments, the target traffic is directed to at least one device (e.g., at least one UE) in communication with IAB node 240, and the first information further includes at least one of: an identification of the at least one device, an identification of a data radio bearer for the at least one device, or an identification of a user plane tunnel for the at least one device.

[0101] In block 420 , the first CU-CP 213 receives second information to be used to configure the target service from the second CU-CP 214 to be routed via the DU 222 .

[0102] In some example embodiments, the second information includes at least one of the following: a differentiated service code point for the target service, an IPv6 flow label for the target service, a transport layer address of the IAB node 240, a backhaul adaptation protocol (BAP) address of the IAB node 240, a BAP path identifier, an identifier of at least one device (e.g., at least one UE) communicating with the IAB node 240, an identifier of a data radio bearer for the at least one device, an identifier of a user plane tunnel for the at least one device, or a routing identifier for the at least one terminal device.

[0103] In some example embodiments, the target traffic includes user plane traffic of an interface between CU-UP 214 of first IAB donor 210 and IAB node 240. First CU-CP 213 transmits at least a portion of second information about the user plane traffic to CU-UP 214.

[0104] In some example embodiments, the target traffic includes control plane traffic of an interface between the first CU-CP 213 and the IAB node 240. The first CU-CP 213 transmits the control plane traffic including at least a portion of the second information to the IAB node 240 via the DU 222 of the second IAB donor 220. In some example embodiments, before transmitting the control plane traffic, the first CU-CP 213 configures a packet header of the control plane traffic using at least a portion of the second information.

[0105] Figure 5a1 shows a flow chart of an example method 500 for IAB communication according to some example embodiments of the present disclosure. The method 500 can be implemented at any suitable device. For example, the method 500 can be implemented at a Figure 2a and / or Figure 2b The IAB donor 220 is shown as being implemented at the CU-CP 223. For the purpose of discussion, reference will be made to Figure 2a and / or Figure 2b 5 is used to describe the method 500. Hereinafter, the CU-CP 213 of the IAB donor 210 is also referred to as the “first CU-CP 213”, and the CU-CP 223 of the IAB donor 220 is also referred to as the “second CU-CP 214”. It should be understood that the method 500 may include additional blocks not shown and / or some of the shown blocks may be omitted, and the scope of the present disclosure is not limited thereto.

[0106] In block 510, the second CU-CP 223 receives a request from the first CU-CP 213 to transfer a target service of an interface between the first IAB donor 210 and the IAB node 240 via the DU 222 of the second IAB donor 220. The request includes first information of the target service.

[0107] In some example embodiments, the first information includes at least one of the following: a service type indicating whether the target service includes user plane service or control plane service, or a quality of service parameter for the target service.

[0108] In some example embodiments, the target traffic is directed to at least one device (e.g., at least one UE) in communication with IAB node 240, and the first information further includes at least one of: an identification of the at least one device, an identification of a data radio bearer for the at least one device, or an identification of a user plane tunnel for the at least one device.

[0109] In block 520 , the second CU-CP 223 determines second information to be used for the target service based on the first information.

[0110] In some example embodiments, the second information includes at least one of the following: a differentiated service code point for the target service, an IPv6 flow label for the target service, a transport layer address of the IAB node 240, a BAP address of the IAB node 240, a BAP path identifier, an identifier of at least one device (e.g., at least one UE) communicating with the IAB node 240, an identifier of a data radio bearer for at least one device, an identifier of a user plane tunnel for at least one device, or a routing identifier for at least one terminal device.

[0111] In block 530 , the second CU-CP 223 sends second information to the first CU-CP 213 .

[0112] In some example embodiments, the second CU-CP 223 transmits third information to the DU 222 of the second IAB donor 220 , the third information being used to configure the DU 222 of the second IAB donor 220 to perform traffic mapping and route the target traffic to the IAB node 240 .

[0113] Figure 5b 1 shows a flow chart of an example method 505 for IAB communication according to some example embodiments of the present disclosure. The method 505 can be implemented at any suitable device. For example, the method 505 can be implemented at a Figure 2a and / or Figure 2b The IAB donor 210 is shown as being implemented at the CU-UP 214. For the purposes of this discussion, reference will be made to Figure 2a and / or Figure 2b 5 is used to describe the method 505. Hereinafter, the CU-CP 213 of the IAB donor 210 is also referred to as the “first CU-CP 213”, and the CU-CP 223 of the IAB donor 220 is also referred to as the “second CU-CP 214”. It should be understood that the method 505 may include additional blocks not shown and / or some of the blocks shown may be omitted, and the scope of the present disclosure is not limited in this regard.

[0114] At block 560, CU-UP 214 receives fourth information from CU-CP 213, the fourth information being used to update quality of service mapping information for user plane traffic of the interface between CU-UP 214 and IAB node 240. User plane traffic is to be delivered to IAB node 240.

[0115] In some example embodiments, the fourth information includes at least one of the following: a first differentiated service code point used by CU-UP 214 for user plane traffic, a first IPv6 flow label used by CU-UP 214 for user plane traffic, a second differentiated service code point to be used by CU-UP 214 for user plane traffic, a second IPv6 flow label to be used by CU-UP 214 for user plane traffic, a transport layer address of the IAB node 240, a BAP address of the IAB node, a BAP path identifier, an identifier of at least one device (e.g., at least one UE) communicating with the IAB node 240, an identifier of a data radio bearer for at least one device, an identifier of a user plane tunnel for at least one device, or a routing identifier for at least one device.

[0116] At block 570 , the CU-UP 214 sends user plane traffic including at least a portion of the fourth information to the IAB node 240 , for example, via a distributed unit (DU) of the first IAB donor or the second IAB donor.

[0117] In some example embodiments, before sending the user plane traffic, CU-UP 214 updates the quality of service mapping information using at least a portion of the fourth information. CU-UP 214 configures a packet header of the user plane traffic with the updated quality of service mapping information.

[0118] In some example embodiments, a first device (e.g., CU-CP 213) capable of performing method 400 may include a component for performing the corresponding operation of method 400. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The first device may be implemented as CU-CP 213 or included in CU-CP 213.

[0119] In some example embodiments, the first device includes: a component for sending a request for delivering a target service via a DU of the second IAB donor to a second CU-CP of the second IAB donor at a first CU-CP of the first IAB donor, the request including first information of the target service; and a component for receiving second information to be used for configuring the target service from the second CU-CP.

[0120] In some example embodiments, the target traffic comprises user plane traffic of an interface between a CU-UP of the first IAB donor and the IAB node, and the first apparatus further comprises means for sending at least a portion of the second information about the user plane traffic to the CU-UP.

[0121] In some example embodiments, the target traffic comprises control plane traffic of an interface between the first CU-CP and the IAB node, and the first device further comprises: means for sending the control plane traffic comprising at least a portion of the second information to the IAB node via the DU of the second IAB donor. In some example embodiments, the first device further comprises: means for configuring a packet header of the control plane traffic using at least a portion of the second information before sending the control plane traffic.

[0122] In some example embodiments, the first information includes at least one of the following: a service type indicating whether the target service includes user plane service or control plane service, or a quality of service parameter for the target service. In some example embodiments, the target service is directed to at least one device in communication with the IAB node, and the first information further includes at least one of the following: an identification of the at least one device, an identification of a data radio bearer for the at least one device, or an identification of a user plane tunnel for the at least one device.

[0123] In some example embodiments, the second information includes at least one of the following: a differentiated service code point for the target service, an IPv6 flow label for the target service, a transport layer address of the IAB node, a BAP address of the IAB node, a BAP path identifier, an identifier of at least one device communicating with the IAB node, an identifier of a data radio bearer for at least one device, an identifier of a user plane tunnel for at least one device, or a routing identifier for at least one device.

[0124] In some example embodiments, a second device (e.g., CU-CP 223) capable of performing method 500 may include a component for performing the corresponding operation of method 500. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The second device may be implemented as CU-CP 223 or included in CU-CP 223.

[0125] In some example embodiments, the second device includes: a component for receiving, at a second CU-CP of the second IAB donor, from a first CU-CP of the first IAB donor, a request for delivering a target service via a DU of the second IAB donor, the request including first information of the target service; a component for determining second information to be used for the target service based on the first information; and a component for sending the second information to the first CU-CP.

[0126] In some example embodiments, the first information includes at least one of the following: a service type indicating whether the target service includes user plane service or control plane service, or a quality of service parameter for the target service. In some example embodiments, the target service is directed to at least one device in communication with the IAB node, and the first information further includes at least one of the following: an identification of the at least one device, an identification of a data radio bearer for the at least one device, or an identification of a user plane tunnel for the at least one device.

[0127] In some example embodiments, the second information includes at least one of the following: a differentiated service code point for the target service, an IPv6 flow label for the target service, a transport layer address of the IAB node, a BAP address of the IAB node, a BAP path identifier, an identifier of at least one device communicating with the IAB node, an identifier of a data radio bearer for at least one device, an identifier of a user plane tunnel for at least one device, or a routing identifier for at least one device.

[0128] In some example embodiments, the second apparatus further includes means for sending third information to the DU of the second IAB donor, the third information being used to configure the DU of the second IAB donor to perform traffic mapping and route the target traffic to the IAB node.

[0129] In some example embodiments, a third device (e.g., CU-UP 214) capable of performing method 505 may include a component for performing the corresponding operation of method 505. The component may be implemented in any suitable form. For example, the component may be implemented in a circuit system or a software module. The third device may be implemented as CU-UP 214 or included in CU-UP 214.

[0130] In some example embodiments, the third device includes: a component for receiving fourth information from a first CU-CP of the first IAB donor at a CU-UP of the first IAB donor, the fourth information being used to update quality of service mapping information for user plane services of an interface between the CU-UP and the IAB node, the user plane services to be sent to the IAB node; and a component for sending user plane services including at least a portion of the fourth information to the IAB node.

[0131] In some example embodiments, the third apparatus further comprises: means for updating quality of service mapping information using at least a portion of the fourth information before sending the user plane traffic; and means for configuring a packet header of the user plane traffic using the updated quality of service mapping information.

[0132] In some example embodiments, the fourth information includes at least one of the following: a first differentiated service code point used by the CU-UP for user plane traffic, a first Internet Protocol version 6 (IPv6) flow label used by the CU-UP for user plane traffic, a second differentiated service code point to be used by the CU-UP for user plane traffic, a second Internet Protocol version 6 (IPv6) flow label to be used by the CU-UP for user plane traffic, a transport layer address of the IAB node, a backhaul adaptation protocol (BAP) address of the IAB node, a backhaul adaptation protocol (BAP) path identifier, an identifier of at least one device communicating with the IAB node, an identifier of a data radio bearer for at least one device, an identifier of a user plane tunnel for at least one device, or a routing identifier for at least one device.

[0133] Figure 6 is a simplified block diagram of a device 600 suitable for implementing embodiments of the present disclosure. For example, Figure 2a and / or Figure 2a The IAB node 240, IAB donor 210, IAB donor 220, CU-CP 213, CU-UP 214, CU 211, CU-CP 223, CU 221, and DU 222 are shown. Figure 2bIt can be implemented by the device 600. As shown in the figure, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor 610, and one or more communication modules 640 coupled to the processor 610.

[0134] The communication module 640 is used for two-way communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.

[0135] Processor 610 may be of any type suitable for use in a local technology network, and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 600 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock of a synchronized master processor.

[0136] The memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist over the duration of a power outage.

[0137] Computer program 630 includes computer executable instructions that are executed by associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any suitable actions and processes by loading program 630 into RAM 622.

[0138] The embodiments of the present disclosure may be implemented by a program 630, so that the device 600 may execute the Figure 3-Figure 5b The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0139] In some example embodiments, the program 630 may be tangibly embodied in a computer-readable medium, which may be included in the device 600 (e.g., in the memory 620) or in other storage devices accessible to the device 600. The device 600 may load the program 630 from the computer-readable medium to the RAM 622 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 7An example of a computer readable medium 700 in the form of a CD or DVD is shown. The computer readable medium has a program 630 stored thereon.

[0140] It should be understood that future networks may utilize network function virtualization (NFV), which is a network architecture concept that proposes to virtualize network node functions into "building blocks" or entities that can be operationally connected or linked together to provide services. Virtualized network functions (VNFs) may include one or more virtual machines that run computer program code using standard or general-purpose servers rather than custom hardware. Cloud computing or data storage may also be utilized. In radio communications, this may mean that node operations are at least partially performed in a central / centralized unit CU (e.g., a server, host, or node) that is operationally coupled to a distributed unit DU (e.g., a radio head / node). Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the distribution of work between core network operations and base station operations may vary depending on the implementation.

[0141] In one embodiment, the server can generate a virtual network through which the server communicates with the distributed unit. In general, virtual networking can involve the process of combining hardware and software network resources and network functions into a single software-based management entity (i.e., a virtual network). Such a virtual network can provide a flexible distribution of operations between the server and the radio head / node. In practice, any digital signal processing task can be performed in the CU or DU, and the boundary of the responsibility transfer between the CU and the DU can be selected according to the implementation.

[0142] Thus, in one embodiment, a CU-DU architecture is implemented. In this case, the device 600 may be included in a central unit (e.g., a control unit, an edge cloud server, a server) that is operatively coupled (e.g., via a wireless or wired network) to a distributed unit (e.g., a remote radio head / node). That is, the central unit (e.g., an edge cloud server) and the distributed units may be independent devices that communicate with each other via a radio path or via a wired connection. Alternatively, they may be in the same entity that communicates via a wired connection, etc. The edge cloud or edge cloud server may serve multiple distributed units or radio access networks. In one embodiment, at least some of the processes may be performed by the central unit. In another embodiment, the device 600 may instead be included in a distributed unit, and at least some of the described processes may be performed by the distributed unit.

[0143] In one embodiment, the execution of at least some functions of the device 600 can be shared between two physically separated devices (DU and CU) that form an operational entity. Therefore, the device can be regarded as depicting an operational entity including one or more physically separated devices for performing at least some of the processes in the process. In one embodiment, this CU-DU architecture can provide a flexible distribution of operations between the CU and the DU. In practice, any digital signal processing task can be performed in the CU or the DU, and the boundary of the transfer of responsibilities between the CU and the DU can be selected according to the implementation. In one embodiment, the device 1000 controls the execution of the process regardless of the location of the device and where the process / function is executed.

[0144] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the block diagrams, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0145] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as computer executable instructions included in a program module, which are executed in a device on a target real or virtual processor to perform the above reference Figure 4 The method 400 described above refers to Figure 5a The method 500 and the above reference Figure 5b The method 505 described. Typically, program modules include routines, programs, libraries, objects, classes, components, data types, etc. that perform specific tasks or implement specific abstract data structures. The functions of program modules can be combined or split between program modules as needed in various embodiments. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0146] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that these program codes cause the functions / operations specified in the flow chart and / or block diagram to be implemented when executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, executed as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0147] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0148] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination thereof. More specific examples of computer readable storage media include an electrical connection with one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0149] In addition, although the operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in a continuous order or to perform all the operations shown to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes several specific implementation details, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments or in any suitable sub-combination, respectively.

[0150] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A method of communication, comprising: Sending, at a first central unit control plane (CU-CP) of a first integrated access and backhaul (IAB) donor, to a second CU-CP of a second IAB donor, a request for delivering a target service via a distributed unit (DU) of the second IAB donor, the request comprising first information of the target service, wherein the first information comprises at least one of the following: a service type indicating whether the target service comprises a user plane service or a control plane service, or a quality of service parameter for the target service; as well as Second information to be used for configuring the target service is received from the second CU-CP, the target service to be routed via the DU of the second IAB donor, wherein the second information is determined by the second CU-CP based on the first information.

2. The method of claim 1, wherein the target traffic comprises user plane traffic of an interface between a central unit user plane (CU-UP) of the first IAB donor and an IAB node, and the method further comprises: and sending at least a portion of the second information about the user plane service to the CU-UP.

3. The method according to claim 1, wherein the target service comprises a control plane service of an interface between the first CU-CP and an IAB node, and the method further comprises: The control plane traffic including at least a portion of the second information is sent to the IAB node via the DU of the second IAB donor.

4. The method according to claim 3, further comprising: Before sending the control plane traffic, a packet header of the control plane traffic is configured using the at least a portion of the second information.

5. The method according to claim 1, wherein the target service is directed to at least one device in communication with an IAB node, and the first information further includes at least one of the following: an identification of the at least one device, an identification of a data radio bearer for the at least one device, or An identification of a user plane tunnel for the at least one device.

6. The method according to claim 1, wherein the second information comprises at least one of the following: a differentiated services code point for the target service, an Internet Protocol version 6 (IPv6) flow label for the target traffic, The transport layer address of the IAB node, a Backhaul Adaptation Protocol (BAP) address of the IAB node, Backhaul Adaptation Protocol (BAP) path identification, an identification of at least one device in communication with the IAB node, an identification of a data radio bearer for the at least one device, an identification of a user plane tunnel for the at least one device, or A routing identifier for the at least one device.

7. A method of communication, comprising: receiving, at a second central unit control plane (CU-CP) of a second integrated access and backhaul (IAB) donor, from a first CU-CP of a first IAB donor, a request for delivering a target service via a distributed unit (DU) of the second IAB donor, the request comprising first information of the target service, wherein the first information comprises at least one of: a service type indicating whether the target service comprises a user plane service or a control plane service, or a quality of service parameter for the target service; Determining second information to be used for the target service based on the first information; as well as The second information is sent to the first CU-CP.

8. The method according to claim 7, wherein the target service is directed to at least one device in communication with an IAB node, and the first information further includes at least one of the following: an identification of the at least one device, an identification of a data radio bearer for the at least one device, or An identification of a user plane tunnel for the at least one device.

9. The method according to claim 7, wherein the second information comprises at least one of the following: a differentiated services code point for the target service, an Internet Protocol version 6 (IPv6) flow label for the target traffic, The transport layer address of the IAB node, a Backhaul Adaptation Protocol (BAP) address of the IAB node, Backhaul Adaptation Protocol (BAP) path identification, an identification of at least one device in communication with the IAB node, an identification of a data radio bearer for the at least one device, an identification of a user plane tunnel for the at least one device, or A routing identifier for the at least one device.

10. The method according to claim 7, further comprising: Sending third information to the DU of the second IAB donor, the third information being used to configure the DU of the second IAB donor to perform service mapping and route the target service to an IAB node.

11. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the apparatus to perform the method according to any one of claims 1 to 6 or the method according to any one of claims 7 to 10.

12. An apparatus for communication, comprising means for performing the method according to any one of claims 1 to 6 or means for performing the method according to any one of claims 7 to 10.

13. A computer-readable medium comprising program instructions, wherein the program instructions are used to cause an apparatus to at least execute the method according to any one of claims 1 to 6 or the method according to any one of claims 7 to 10.