Traffic offloading

Abstract

Example embodiments of the present disclosure relate to traffic offloading in a communication network. A first device receives, from a second device in a radio access network, a context of traffic to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device. The traffic includes a first traffic to be transmitted between a second device and a third device in the radio access network. The first device selects a second target device for the first traffic based on the context, wherein the second target device is associated with the first device. The first device sends first configuration information to the second device for transmitting the first traffic between the second device and the third device via the second target device.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to the field of telecommunications, and more particularly to devices, methods, apparatuses, and computer-readable storage media for offloading traffic in a communication network. Background Art

[0002] The communication system may include one or more integrated access and backhaul (IAB) nodes. The IAB donor has connectivity (e.g., fiber connectivity) to the core network. The IAB donor may be implemented as a gNB that terminates a wireless backhaul radio interface from one or more IAB nodes. The IAB donor may serve directly connected IAB nodes and IAB nodes linked via multiple wireless backhaul hops. The IAB donor may also serve directly connected terminal devices. The IAB donor may include a central unit (CU) and one or more distributed units (DUs).

[0003] The IAB node may serve one or more terminal devices directly connected to the IAB node. The IAB node may also serve one or more child IAB nodes connected to the IAB node. The IAB node may include a DU (also referred to as an IAB-DU) and a mobile terminal (also referred to as an IAB-MT) that maintains connectivity (e.g., using dual connectivity) with one or more parent nodes.

[0004] The IAB topology in the communication system may be non-static, as migration may be performed. For example, a handover may be performed on an IAB-MT based on signal strength, signal quality, or other factors. Summary of the invention

[0005] In general, the exemplary embodiments of the present disclosure provide a solution for offloading traffic in a communication network. Embodiments (if any) that do not fall within the scope of the claims should be interpreted as examples that are helpful for understanding the various embodiments of the present disclosure.

[0006] In a first aspect, a first device in a radio access network is provided. The first device includes at least one processor; and 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 first device to: receive a context of a service to be offloaded via a first target device in the radio access network from a second device in the radio access network, wherein the first target device is associated with the first device, and wherein the service includes a first service to be transmitted between the second device and a third device in the radio access network; based on the context, select a second target device for the first service, wherein the second target device is associated with the first device; and send first configuration information to the second device for transmitting the first service between the second device and the third device via the second target device.

[0007] In a second aspect, a second device in a radio access network is provided. The second device includes at least one processor; and 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 second device to: send a context of a service to be offloaded via a first target device in the radio access network to a first device in the radio access network, wherein the first target device is associated with the first device, and wherein the service includes a first service to be transmitted between a second device and a third device in the radio access network; receive first configuration information from the first device for transmitting the first service between the second device and the third device via a second target device, wherein the second target device is associated with the first device; and transmit the first service using the first configuration information.

[0008] In a third aspect, a third device in a radio access network is provided. The third device includes at least one processor; and 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 third device to: receive first configuration information from a first device or a second device in the radio access network for transmitting a first service between the second device in the radio access network and the third device in the radio access network via a second target device in the radio access network, wherein the second target device is associated with the first device; and transmit the first service using the first configuration information.

[0009] In a fourth aspect, a method is provided. The method may be performed by a first device, comprising: receiving, at a first device in a radio access network, from a second device in the radio access network, a context of a service to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the service comprises a first service to be transmitted between the second device and a third device in the radio access network; selecting a second target device for the first service based on the context, wherein the second target device is associated with the first device; and sending first configuration information to the second device for transmitting the first service between the second device and the third device via the second target device.

[0010] In a fifth aspect, a method is provided. The method may be performed by a second device, comprising: sending a context of a service to be offloaded via a first target device in the radio access network from the second device in the radio access network to a first device in the radio access network, wherein the first target device is associated with the first device, and wherein the service comprises a first service to be transmitted between the second device and a third device in the radio access network; receiving first configuration information for transmitting the first service between the second device and the third device via a second target device from the first device, wherein the second target device is associated with the first device; and transmitting the first service using the first configuration information.

[0011] In a sixth aspect, a method is provided. The method may be performed by a third device, comprising: receiving, at a third device in a radio access network, first configuration information from a first device or a second device in the radio access network, for transmitting a first service between the second device in the radio access network and the third device in the radio access network via a second target device in the radio access network, wherein the second target device is associated with the first device; and transmitting the first service using the first configuration information.

[0012] In a seventh aspect, a first apparatus is provided. The first apparatus comprises: a component for receiving a context of a service to be offloaded via a first target device in the radio access network from a second device in a radio access network, wherein the first target device is associated with the first device, and wherein the service comprises a first service to be transmitted between the second device and a third device in the radio access network; a component for selecting a second target device for the first service based on the context, wherein the second target device is associated with the first device; and a component for sending first configuration information to the second device for transmitting the first service between the second device and the third device via the second target device.

[0013] In an eighth aspect, a second apparatus is provided. The second apparatus comprises: a component for sending a context of a service to be offloaded via a first target device in the radio access network to a first device in a radio access network, wherein the first target device is associated with the first device, and wherein the service comprises a first service to be transmitted between a second device and a third device in the radio access network; a component for receiving first configuration information for transmitting the first service between the second device and the third device via a second target device from the first device, wherein the second target device is associated with the first device; and a component for transmitting the first service using the first configuration information.

[0014] In a ninth aspect, a third apparatus is provided, comprising: a component for receiving first configuration information from a first device or a second device in a radio access network for transmitting a first service between the second device in the radio access network and a third device in the radio access network via a second target device in the radio access network, wherein the second target device is associated with the first device; and a component for transmitting the first service using the first configuration information.

[0015] In a tenth aspect, a computer readable medium is provided, wherein the computer readable medium comprises program instructions, which, when executed by at least one processor, cause an apparatus to perform at least the method according to the fourth aspect.

[0016] In an eleventh aspect, a computer readable medium is provided, wherein the computer readable medium comprises program instructions, and when the program instructions are executed by at least one processor, the apparatus executes at least the method according to the fifth aspect.

[0017] In a twelfth aspect, a computer readable medium is provided, wherein the computer readable medium comprises program instructions, which, when executed by at least one processor, cause an apparatus to perform at least the method according to the sixth aspect.

[0018] 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

[0019] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0020] Figure 1 shows an example communication network in which example embodiments of the present disclosure may be implemented;

[0021] Figure 2 A signaling diagram illustrating a process for offloading traffic according to some example embodiments of the present disclosure;

[0022] Figure 3 A signaling diagram showing a process for offloading traffic according to some other example embodiments of the present disclosure;

[0023] Figure 4 A flowchart showing a method implemented at a first device according to some example embodiments of the present disclosure is shown;

[0024] Figure 5 A flowchart showing a method implemented at a second device according to some example embodiments of the present disclosure is shown;

[0025] Figure 6A flowchart showing a method implemented at a third device according to some example embodiments of the present disclosure is shown;

[0026] Figure 7 shows a simplified block diagram of an apparatus suitable for implementing an example embodiment of the present disclosure; and

[0027] Figure 8 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.

[0028] Throughout the drawings, the same or similar reference numerals denote the same or similar elements. DETAILED DESCRIPTION

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

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

[0031] References in this disclosure to "one embodiment," "an embodiment," "example embodiment," etc. indicate that the embodiment may include a particular feature, structure, or characteristic, but not every embodiment includes the particular feature, structure, or characteristic. In addition, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it should be understood that those skilled in the art may affect such feature, structure, or characteristic in conjunction with other embodiments, whether or not explicitly described.

[0032] 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, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element without departing from the scope of the example embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0033] The terms used herein are only used to describe specific embodiments and are not intended to limit the purpose of the example embodiments. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the terms "comprises", "comprising", "has", "having", (includes) and / or "including" when used herein 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.

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

[0035] (a) hardware circuit implementation only (e.g., implementation only in analog and / or digital circuitry) and

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

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

[0038] (ii) any portion of hardware processor(s) with software (including digital signal processor(s), software and memory(s) that work together to enable the device (such as a mobile phone or server) to perform various functions and (c) hardware circuit(s) and / or processor(s) (such as microprocessor(s) or portion(s) of microprocessor(s)) that requires software (e.g., firmware) to operate, but where the software is not required for operation, the software may not be present.

[0039] This definition of circuitry applies to all uses of the term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" also covers an implementation of only a 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, 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.

[0040] As used herein, the term "communication network" refers to a network that complies with any appropriate communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. In addition, the communication between the terminal device and the network device in the communication network or the communication between the network devices can be performed according to any appropriate generation communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G) communication protocol and / or any other protocol currently known or to be developed in the future. The embodiments of the present disclosure can be applied to various communication systems or networks. In view of the rapid development of communication technology, there will certainly be future types of communication technology, networks and systems that can embody the present disclosure. This should not be regarded as limiting the scope of the present disclosure to the above-mentioned system / network.

[0041] 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. Depending on the terminology and technology applied, a network device may refer to a base station (BS) or an access point (AP), for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated access backhaul (IAB) node, an IAB-DU and an IAB-CU, a low power node (such as a femto node, a pico node), a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, a low earth orbit (LEO) satellite and a geosynchronous orbit (GEO) satellite), an aircraft network equipment, etc.

[0042] 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, user equipment (UE), user station (SS), portable user station, mobile station (MS) or 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 client device (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 operating in the context of an industrial and / or automated processing chain), consumer electronic devices, equipment operating on a commercial and / or industrial wireless network, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0043] Figure 1 An example communication environment 100 is shown in which example embodiments of the present disclosure may be implemented. The communication environment 100 may include a core network (CN) 105, a first device 110, a second device 120, a third device 130, a first target device 140, a second target device 150, parent devices 160 and 170, a source device 180, and a terminal device 190.

[0044] exist Figure 1 In the example of FIG. 1 , the third device 130 is connected to the second device 120 via the parent device 160 and the source device 180. After the migration, the third device 130 is connected to the first device 110 via the parent device 170 and the first target device 140 and / or via the parent device 170 and the second target device 150. The terminal device 190 accesses the communication environment 100 via the third device 130.

[0045] In some embodiments, communication environment 100 may include one or more intermediate devices between source device 180 and parent device 160 , one or more intermediate devices between first target device 140 and parent device 170 , and / or one or more intermediate devices between second target device 150 and parent device 170 .

[0046] In some embodiments, the communication environment 100 may be implemented as an IAB network. In such an embodiment, each of the first device 110 and the second device 120 may be implemented as an IAB-donor-CU, each of the source device 180, the first target device 140 and the second target device 150 may be implemented as an IAB-donor-DU, and each of the third device 130, the parent device 160 and the parent device 170 may be implemented as an IAB-node.

[0047] In an embodiment where the communication environment 100 is implemented as an IAB network, the IAB donor CU and one or more IAB donor DUs may be collectively referred to as an IAB donor. Figure 1 In the example of , the second device 120 and the source device 180 can be collectively referred to as one IAB donor. Similarly, the first device 110, the first target device 140, and the second target device 150 can be collectively referred to as another IAB donor.

[0048] Each of the IAB donors may have connectivity (e.g., fiber connectivity) with the CN 105. Each IAB donor may serve directly connected IAB nodes (not shown) and IAB nodes linked through multiple wireless backhaul hops. For example, an IAB-donor device including a first device 110, a first target device 140, and a second target device 150 may serve a parent device 170 serving as an IAB-node.

[0049] An IAB-node, such as devices 130, 160, and 170 used as IAB-nodes, can serve one or more terminal devices directly connected thereto. Figure 1 As shown, the third device 130 can serve the terminal device 190 directly connected to the third device 130, and the F1 interface for the F1 service (such as F1 control plane service, or F1 user plane service) of the terminal device 190 is terminated at the third device 130 and the second device 120.

[0050] Hereinafter, the CU of the IAB-donor is also referred to as a donor CU or a donor central unit or an IAB-donor-CU, and the DU of the IAB-donor is also referred to as a donor DU or a donor distributed unit or an IAB-donor-DU.

[0051] In an embodiment where the communication environment 100 is implemented as an IAB network, an IAB node (e.g., each of the devices 130, 160, and 170) may include a DU (IAB-DU) and a mobile terminal (IAB-MT) that maintains connectivity with one or more parent nodes (e.g., using dual connectivity). Similar to conventional user equipment, the MT of the IAB node may use radio resource control (RRC) signaling, for example, to provide radio link measurements of an alternative parent node to its current serving donor CU. The RRC terminates at the IAB-MT and the donor CU. Migration may be performed, for example, a handover is performed for the IAB-MT based on signal strength, signal quality, or other factors. Thus, the IAB topology (such as, for example, Figure 1 As a result of the migration, the third device 130 may change the parent node from the parent device 160 (also referred to as the source parent IAB node 160) to the migrated parent device 170 (also referred to as the target parent IAB node 170), as shown by Figure 1 In other words, before the migration, the F1 traffic for the terminal device 190 is transmitted via the parent device 160 and the source device 180; after the migration, the F1 traffic for the terminal device 190 is transmitted via the parent device 170 and the first target device 140 and / or via the parent device 170 and the second target device 150. The IAB topology may change over time as radio conditions fluctuate and IAB nodes are moved, added, or removed.

[0052] A CU (such as a donor CU) may be a logical node that may include functions such as transmission of user data, mobility control, radio access network sharing, positioning, session management, etc. (e.g., gNB functions), in addition to functions specifically assigned to a DU. A CU may control the operation of one or more DUs via a fronthaul (F1) interface. A DU is a logical node that may include a subset of functions (e.g., gNB functions).

[0053] It should also be understood that Figure 1 The architecture shown is for illustrative purposes only and does not represent any limitation. In addition, it should be understood that Figure 1 The number of devices shown and their connections are for illustrative purposes only and do not represent any limitation. Communication environment 100 may include any suitable number of devices suitable for implementing embodiments of the present disclosure. Although not shown, it is understood that one or more additional devices may be deployed in communication environment 100.

[0054] The communication in the communication environment 100 can be implemented according to any appropriate (multiple) communication protocols, including but not limited to cellular communication protocols of the first generation (1G), second generation (2G), third generation (3G), fourth generation (4G) and fifth generation (5G), wireless local area network communication protocols (such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc.) and / or any other protocol currently known or to be developed in the future. In addition, the communication can utilize any appropriate wireless communication technology, including but not limited to: code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), frequency division duplex (FDD), time division duplex (TDD), multiple input multiple output (MIMO), orthogonal frequency division multiple access (OFDM), discrete Fourier transform spread spectrum OFDM (DFT-s-OFDM) and / or any other technology currently known or to be developed in the future.

[0055] During IAB node migration, when the target donor DU is different from the source donor DU, inter-donor DU migration is performed. When the source donor DU and the target donor DU belong to the same donor CU, intra-donor DU inter-donor DU migration occurs. When the source donor DU and the target donor DU belong to different donor CUs or the source donor DU and the target donor DU are connected to different donor CUs, inter-donor CU migration occurs.

[0056] In some embodiments, the third device 130 may perform a donor-CU inter-migration process, for example due to a handover. In such an embodiment, the third device 130 may be referred to as a migration IAB node. Using the migration process, the third device 130 may change the communication connection (or communication path) from the topology of the second device 120 (e.g., the communication path between the third device 130 and the second device 120 using the source device 180 and the parent device 160) to the topology of the first device 110 (e.g., the communication path between the third device 130 and the second device 120 using the first target device 140 and the parent device 170, and / or using the second target device 150 and the parent device 170) by migrating from the parent device 160 to the parent device 170. In such an embodiment, the second device 120 may be referred to as a source IAB-donor-CU, the parent device 160 may be referred to as a source parent IAB-node of the third device 130, each of the first target device 140 and the second target device 150 may be referred to as a target IAB-donor-DU, and the parent device 170 may be referred to as a target parent IAB node of the third device 130.

[0057] During the inter-donor CU migration process, the traffic between the migrating IAB node and the source IAB-donor-CU can be offloaded to the topology of the target IAB-donor. The current inter-CU topology adaptation process imposes restrictions on inter-donor CU migration and may cause more failures. This is because the target IAB-donor-CU selects the target IAB-donor-DU during the Xn switching preparation process, which is before the QoS information of the traffic to be offloaded is sent to the target IAB-donor-CU. Without knowing the QoS information of the traffic to be offloaded, the target IAB-donor-CU may blindly select a target IAB-donor-DU that may not be able to support the traffic.

[0058] When the target IAB-donor-CU selects the target IAB-donor-DU and assigns the transport network layer (TNL) address anchored at the target IAB-donor-DU, the TNL address will be further sent to the migration IAB node. During the migration management process, the source IAB-donor-CU includes the TNL address in the REQUEST message (e.g., IAB TRANSPORT MIGRATION MANAGEMENTREQUEST message). When the target IAB-donor-CU receives the REQUEST message, it will try to establish a backhaul (BH) for the communication path between the migration IAB node and the target IAB-donor-DU. If the BH between the migration IAB node and the target IAB-donor-DU cannot support the service, the target IAB-donor-CU will reject the REQUEST, causing the migration to fail.

[0059] According to some example embodiments of the present disclosure, a solution for offloading a service in a communication network is provided. In the solution, if a first device (e.g., a target IAB-donor-CU) determines that a first target device (e.g., a first target IAB-donor-DU) cannot support the service to be offloaded, the first device selects a second target device (e.g., a second target IAB-donor-DU) for the first service based on the context of the service. In this way, the migration success rate can be improved.

[0060] Example embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings.

[0061] Figure 2 A signaling diagram of a process 200 for offloading traffic according to some example embodiments of the present disclosure is shown. For the purpose of discussion, the process 200 will refer to Figure 1 Process 200 may involve Figure 1 The first device 110, the second device 120, the third device 130, the first target device 140 and the second target device 150 in the embodiment.

[0062] A first device 110 in a radio access network receives 210 a context of a traffic to be offloaded via a first target device 140 in the radio access network from a second device 120 in the radio access network. The first target device 140 is associated with the first device 110, and the traffic includes first traffic to be transmitted between the second device 120 and a third device 130 in the radio access network. The first traffic includes downlink (DL) traffic and uplink (UL) traffic.

[0063] The first device 110 may determine 220 whether the first target device 140 supports the first service based on the context. If the first target device 140 cannot support the first service, the first device 110 selects 230 a second target device 150 for the first service based on the context. The second target device 150 is associated with the first device 110 .

[0064] The first device 110 sends 240 first configuration information to the second device 120. The first configuration information is used to transmit the first traffic between the second device 120 and the third device 130 via the second target device 150. For example, the second device 120 sends the downlink traffic to the third device via the topology of the second target device 150 and the first device 110 using the first configuration information (e.g., IPv6 flow label, TNL address, etc.).

[0065] In an example embodiment, the third device 130 is still connected to the source parent device (e.g., the RRC of the MT of the third device 130 is terminated at the second device 120). After receiving the first configuration information, the second device 120 sends 250 the first configuration information to the third device 130. In some embodiments, the second device 120 may send the first configuration information to the third device 130 via an intermediate IAB node (if any).

[0066] In another example embodiment, the third device 130 is connected to the target parent device (eg, the RRC of the MT of the third device 130 is terminated at the first device 110), and the first device 110 may send 260 the first configuration information to the third device 130 via an intermediate IAB node (if any).

[0067] In some embodiments, optionally, the second device 120 may send 265 an indication to the third device 130 via an intermediate IAB node (if any) to apply the first configuration information to transmit the first service. The indication may be sent via F1AP signaling, for example, as an F1AP message that may configure UL mapping for the third device 130 (i.e., mapping a given F1-U tunnel with a given UL BAP routing ID and a given BH RLC channel), and based on the mapping, the third device 130 (e.g., IAB node) may know which source IP address to use for UL data.

[0068] In turn, the second device 120 transmits the first service using the first configuration information. For example, the second device 120 may send 270 a downlink (DL) first service using the first configuration information. The first service is transmitted to the third device 130 via the second target device 150. Therefore, the third device 130 receives the downlink first service using the first configuration information. Similarly, the third device 130 may send 280 an uplink (UL) first service using the first configuration information. The first service is sent to the second device 120 via the second target device 150. Therefore, the second device 120 receives the uplink first service using the first configuration information.

[0069] Using process 200 , the migration success rate may be improved by allowing a first device (eg, a target IAB-donor-CU) to modify a previously selected first target device (eg, a target IAB-donor-DU).

[0070] In some embodiments, the context may include quality of service (QoS) information associated with the traffic to be offloaded. In such an embodiment, the context may include QoS information associated with all traffic to be offloaded. In other words, the traffic may include traffic on multiple F1-U tunnels between the second device 120 and the third device 130, and the QoS information may be aggregated QoS information.

[0071] In some embodiments, the service to be offloaded may include at least one of a user plane service and a control plane service, and the context may include QoS information associated with the user plane service. In such an embodiment, the context may include QoS information associated with the service on each F1-U tunnel. In other words, the service may include services on multiple F1-U tunnels, and the services on each F1-U tunnel have associated QoS information.

[0072] In some embodiments, the first device 110 may receive the context of the service to be offloaded from the second device 120 after receiving a handover request message or a secondary node addition request message for offloading the service from the second device 120. In such an embodiment, the first device 110 may receive the context of the service in an IAB TRANSPORT MIGRATIONMANAGEMENT REQUEST message from the second device 120.

[0073] Alternatively, the first device 110 may receive the context of the service to be offloaded from the second device 120 in a handover request message or a secondary node addition request message for offloading the service.

[0074] For example, the first device 110 may receive the context of the service via Traffic To Be AddedList in an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message, a HANDOVER REQUEST message, or an S-NODE ADDITION REQUEST message. Table 1 shows an example of a service list to be added.

[0075] Table 1

[0076]

[0077] In Table 1, the service index may identify a service that is offloaded to a topology of a non-F1 terminated IAB-donor-CU, such as the first device 110. The service profile may indicate service QoS parameters for an F1 user plane interface (F1-U) service or a non-UP service type. The F1 termination topology BH information provides BH information for services used in the topology of the F1 termination donor. For example, the F1 termination topology BH information may include at least a BH information index and a DL transport network layer (TNL) address for the third device 130. The DL TNL address of the third device 130 may be assigned by a target device (e.g., the first target device 140). The first device 110 may understand the target device (e.g., the first target device 140) based on the DL TNL address.

[0078] In some embodiments, the traffic to be offloaded may include at least one of user plane traffic and control plane traffic.

[0079] In some embodiments, the context includes QoS information associated with at least user plane traffic. For example, user plane traffic may include F1-U traffic. The context may include QoS information for each F1-U tunnel.

[0080] In some embodiments, the first configuration information may include at least one of the following items related to the second target device 150:

[0081] a TNL address of the third device 130 anchored at the second target device 150,

[0082] Internet Protocol version 6 (IPv6) flow labels,

[0083] Differentiated Services Code Point (DSCP),

[0084] a Backhaul Adaptation Protocol (BAP) routing identifier (ID) associated with the second target device 150,

[0085] Backhaul radio link control channel configuration, or

[0086] BAP layer configuration.

[0087] In some embodiments, the first device 110 may send the first configuration information to the second device 120 in an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message, a HANDOVER REQUEST ACKNOWLEDGE message, or an S-NODE ADDITION REQUEST ACKNOWLEDGE message.

[0088] In some embodiments, the first device 110 may send the first configuration information via Traffic Added List in an IAB TRANSPORT MIGRATION MANAGEMENT RESPONSE message. Table 2 shows an example of an added service list.

[0089] Table 2

[0090]

[0091] In Table 2, the service index may identify a service that is offloaded to a topology of a non-F1 terminated IAB-donor-CU (eg, the first device 110). The non-F1 terminated topology BH information IE may provide BH information of a service used in a topology of a non-F1 terminated donor. Table 3 shows an example of a non-F1 terminated topology BH information IE.

[0092] Table 3

[0093]

[0094]

[0095] In Table 3, the first configuration information may include a new TNL address IE, which may indicate an IPv4 or IPv6 address or an IPv6 address prefix assigned to an IAB node (e.g., the third device 130). The first configuration information may include other information not shown in Table 3, such as BAP-related configuration. Table 4 shows an example of a new TNL address IE.

[0096] Table 4

[0097]

[0098] Figure 3 FIG. 2 is a signaling diagram of a process 300 for offloading traffic according to some example embodiments of the present disclosure. The process 300 may be considered as an example implementation of the process 200. For the purpose of discussion, the process 300 will refer to Figure 1 Process 300 may involve Figure 1The CN 105, the first device 110, the second device 120, the third device 130, the first target device 140, the second target device 150, the parent devices 160 and 170, and the terminal device 190.

[0099] In some example embodiments, process 300 may be performed in an IAB inter-CU topology adaptation process for third device 130 (also referred to as migration device 130). Therefore, process 300 will be described in conjunction with the IAB inter-CU topology adaptation process. However, process 300 may be performed independently of the IAB inter-CU topology adaptation process.

[0100] The second device 120 sends 301 a HANDOVER REQUEST message to the first device 110 through an Xn interface. The message may include TNL address information of the third device 130 in a radio resource control (RRC) container.

[0101] In some embodiments, the HANDOVER REQUEST message may include the context of the traffic to be offloaded (e.g., the QoS requirements of the traffic to be offloaded). The QoS requirements may be indicated as QoS flow level, F1-U tunnel level QoS parameters, or the source donor may determine an aggregate QoS requirement for all migrated traffic. The aggregate QoS requirement may be, for example, an aggregate data rate of the traffic to be offloaded.

[0102] After receiving the HANDOVER REQUEST message, the first device 110 may select the first target device 140 for the first service, and request the first target device 140 to assign at least one TNL address anchored at the first target device 140 to the third device 130 .

[0103] The first device 110 sends 302 a UE CONTEXT SETUP REQUEST message to the parent device 170 to create a UE context for the migrated IAB-MT and set up one or more bearers in the third device 130. These bearers can be used by the migrated IAB-MT for its own signaling. Optionally, these bearers can be used by the migrated IAB-MT for data services.

[0104] The parent device 170 responds 303 to the first device 110 with a UE CONTEXT SETUP RESPONSE message.

[0105] The first device 110 performs 304 admission control and provides a new RRC configuration as part of a HANDOVER REQUESTACKNOWLEDGE message. The RRC configuration includes a BAP address for the third device 130 in the topology of the first device 110, a default BH RLC channel, and a default BAP routing ID configuration for UL F1-C / non-F1 traffic mapping on the target path. The RRC configuration may include (multiple) new TNL addresses anchored on the target device 140 for the third device 130.

[0106] The second device 120 sends 305 a UE CONTEXT MODIFICATION REQUEST message to the parent device 160 . The message includes the RRCReconfiguration message received from the first device 110 .

[0107] The parent device 160 forwards 306 the received RRCReconfiguration message to the third device 130 .

[0108] The parent device 160 responds 307 to the second device 120 using a UE CONTEXT MODIFICATION RESPONSE message.

[0109] A random access procedure is performed 308 at the parent device 170 .

[0110] The third device 130 responds 309 to the parent device 170 using an RRCReconfigurationComplete message.

[0111] The parent device 170 sends 310 a UL RRC MESSAGE TRANSFER message to the first device 110 to convey the received RRCReconfigurationComplete message.

[0112] If necessary, the first device 110 triggers 311 a path switching procedure for the third device 130 .

[0113] The first device 110 sends 312 a UE CONTEXT RELEASE message to the second device 120 .

[0114] It should be noted that as long as the target path is used for transmitting traffic between the third device 130 and the second device 120 , the XnAP UE ID of the third device 130 is retained at the first device 110 and the second device 120 .

[0115] The second device 120 may release 313 the BH RLC channel and the BAP sublayer routing entry on the source path between the parent device 160 and the source device 180 .

[0116] The first device 110 configures 314 for the third device a BH RLC channel and a BAP sublayer routing entry on a target path between the third device 130 and the target device 140, and a DL mapping on the target device 140 for the target path of the third device 130. These configurations support the transmission of F1-C traffic on the target path.

[0117] The F1-C connection between the third device 130 and the second device 120 may be switched 315 to a target path using the new TNL address information of the third device 130. The third device 130 may report to the second device 120 via a gNB-DU CONFIGURATION UPDATE message that it wants to use the new TNL address information for each F1-U tunnel and non-UP traffic type.

[0118] The second device 120 sends 316 an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the first device 110 to provide the context of the service to be offloaded. The service includes the first service to be sent between the second device 120 and the third device 130 via the target device 140. The message may include new DL TNL address information required for the first device 110 to configure or modify the DL mapping on the target device 140.

[0119] In some embodiments, the second device 120 may use a service index for each of the first service and the second service. In such an embodiment, the context of the service may include the following information:

[0120] Business Index = #1

[0121] - BH information index #101 for the second service, for the DL TNL address of the third device 130 assigned by the first target device 140

[0122] QoS, for example, 40 Mbps for service index #1

[0123] Business Index = #2

[0124] - BH information index #102 for the first service, for the DL TNL address of the third device 130 assigned by the first target device 140

[0125] QoS, for example, 60 Mbps for service index #2

[0126] In some embodiments, the second device 120 may use one service index for both the first service and the second service. In such an embodiment, the context of the service may include the following information:

[0127] Business Index = #1

[0128] - BH information index #101 for the second service, DL TNL address of the third device 130 assigned by the first target device 140, QoS (e.g., 40 Mbps)

[0129] - BH information index #102 for the first service, DL TNL address of the third device 130 assigned by the first target device 140, QoS (e.g., 60 Mbps)

[0130] QoS, for example, for service index #1 is 100Mbps

[0131] At 317 , the first device 110 determines whether the first target device 140 supports the first service based on the context received at 316 . When the first device 110 receives the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message, it will attempt to establish a BH between the parent device 170 and the first target device 140 .

[0132] For example, the QoS for service index #1 (e.g., 40 Mbps), the QoS for service index #2 (e.g., 60 Mbps), and the BH between the parent device 170 and the first target device 140 only support 40 Mbps. In this case, the first device 110 determines that the first target device 140 cannot support the service identified by service index #2.

[0133] For another example, QoS for service index #1 is 100 Mbps, but the BH between the parent device 170 and the first target device 140 only supports 40 Mbps. In this case, the first device 110 determines that the first target device 140 cannot support the service identified by service index #1.

[0134] If the first target device 140 cannot support the first service, the first device 110 selects the second target device 150 for the first service based on the context.

[0135] For example, if the QoS for service index #1 is 40 Mbps, the QoS for service index #2 is 60 Mbps, and the BH between the parent device 170 and the second target device 150 only supports 70 Mbps, the first device 110 determines that the second target device 150 supports the service identified by service index #2. Conversely, the first device 110 selects the second target device 150 for the service identified by service index #2.

[0136] For another example, the QoS for service index #1 is 100 Mbps, and the BH between the parent device 170 and the second target device 150 supports 110 Mbps. In this case, the first device 110 determines that the second target device 150 supports the service identified by service index #1. In turn, the first device 110 selects the second target device 150 for the service identified by service index #1.

[0137] In addition, at 317, the first device 110 may configure or modify a BH RLC channel and a BAP sublayer routing entry on a target path between the third device 130 and the second target device 150 and a DL mapping of the target path for the third device 130 on the second target device 150. These configurations may support the transmission of UP and non-UP traffic on the target path.

[0138] Furthermore, at 317 , the first device 110 may request the second target device 150 to assign a new TNL address for the third device 130 . The new TNL address for the third device 130 is anchored at the second target device 150 .

[0139] At 318 , the first device 110 responds to the second device 120 with an IAB transmit migration management response message to provide first configuration information for transmitting the first service between the second device 120 and the third device 130 via the second target device 150 .

[0140] The first configuration information may include a new TNL address assigned by the second target device 150. The first configuration information may also include a BAP layer configuration used in the IAB topology of the first device 110 and required to configure the third device 130 with the UL mapping of the traffic indicated at 316.

[0141] The first configuration information may also include a DSCP / IPv6 flow label value to be used by the second device 120 to send the offloaded downlink traffic, and also to be used to configure the DL mapping of the traffic indicated at 317 .

[0142] In an embodiment in which the second device 120 uses one service index for each of the first service and the second service, the first configuration information for transmitting the first service between the second device 120 and the third device 130 via the second target device 150 may include the following information:

[0143] Business Index = #1

[0144] - BH information index #101 is accepted, and the first target device 140 continues to be used

[0145] Business Index = #2

[0146] - BH information index #102 is accepted, but a new TNL address is assigned by the second target device 150

[0147] In an embodiment in which the second device 120 uses one service index for both the first service and the second service, the first configuration information for transmitting the first service between the second device 120 and the third device 130 via the second target device 150 may include the following information:

[0148] Business Index = #1

[0149] - BH information index #101 is accepted, and the first target device 140 continues to be used

[0150] - BH information index #102 is accepted, but a new TNL address is assigned by the second target device 150

[0151] In such an embodiment, different services identified by one service index may use different target IAB-Donor-DUs even though they use the same IAB-Donor-DU before topology adaptation.

[0152] After receiving the first configuration information, the second device 120 may replace the TNL address assigned by the first target device 140 with a new TNL address assigned by the second target device 150 for the service identified by BH Info Index #102. This TNL address is used as part of the DL FTEID when sending DL F1-U services.

[0153] It should be noted that such an embodiment does not assume an IPsec tunnel. In case IPsec tunnel mode is used, the TNL address is an external IP address. The third device 130 needs to inform the second device 120 of the new internal TNL address for DL ​​FTEID.

[0154] At 318a, the first device 110 sends a UE CONTEXT MODIFICATION REQUEST message to the parent device 170. The message includes an RRCReconfiguration message to be further sent to the third device 130. The RRCReconfiguration message includes first configuration information used by the third device 130 for sending uplink offload traffic.

[0155] At 318b, the parent device 170 forwards the received RRCReconfiguration message to the third device 130. Therefore, the third device 130 sends the uplink offload traffic using the first configuration information.

[0156] At 319, the F1-U connection of the third device 130 with the second device 120 may be switched to use the new TNL address(es) of the third device 130. The second device 120 provides updated UL BH information for the service indicated at 316 to the third device 130 based on the UL BH information received from the first device 110 at 318. The second device 120 may also update the UL BH information associated with non-UP services. This action may use UE-associated signaling or non-UE-associated signaling in the E1 and / or F1 interfaces. The implementation must ensure that potential race conditions are avoided, i.e., no conflicting configurations are performed concurrently using UE-associated and non-UE-associated processes.

[0157] In addition, at 319 , the second device 120 sends an indication to the third device 130 that the third device 130 uses the first configuration to transmit the first service.

[0158] After receiving the instruction, the third device 130 transmits the first service using the first configuration. For example, the third device 130 may replace the TNL address assigned by the first target device 140 for the first service with a new TNL address assigned by the second target device 150 for the first service.

[0159] When the second device 120 transmits the DL F1-U traffic to the third device 130, the IP packet uses the new TNL address assigned by the second target device 150 as the destination address. The IP packet is routed to the second target device 150.

[0160] When the third device 130 transmits UL F1-U traffic, the BAP header includes a UL routing ID including the BAP address of the second target device 150. The source IP address is a new TNL address assigned by the second target device 150. The BAP packet is routed to the second target device 150.

[0161] The actions at 316 to 319 are repeated as needed, wherein the second device 120 may request to add, modify, or release QoS information for non-UP and UP services.

[0162] In some embodiments, if multiple IP addresses or IPv6 prefixes are allocated for the third device 130 for the F1-U service, the first device 110 can transmit the IP address and / or prefix allocated to the third device 130 in the RRC reconfiguration messages at 318a and 318b. The third device 130 derives the complete IP address from the IPv6 prefix and selects an IP address for the F1-U tunnel, and transmits the selected IP address to the target IAB donor DU in the RRC reconfiguration complete message ( Figure 3It should be noted that in such an embodiment, the actions at 318a and 318b are performed before the action at 318.

[0163] It should be understood that process 300 is provided as an example only, and not as a limitation. In some embodiments, a similar mechanism for offloading traffic may be used in a different process with a different signaling flow.

[0164] In an embodiment in which the first device 110 receives the context of the service in the handover request message or the secondary node addition request message, the service may also include a second service. The first device 110 may select a third target device for the first service and a fourth target device for the second service based on the context. The third and fourth target devices are associated with the first device 110. In turn, the first device 110 may send the second configuration information and the third configuration information to the second device 120. The second configuration may be used to transmit the first service between the second device 120 and the third device 130 via the third target device. The third configuration may be used to transmit the second service between the second device 120 and the third device 130 via the fourth target device.

[0165] In some embodiments, the first device 110 may send the second configuration information and the third configuration information in a handover request confirmation message.

[0166] In some embodiments, each of the third target device and the fourth target device may include an IAB-donor-DU. For example, the third target device and the fourth target device may be implemented as the first target device 140 and the second target device 150, respectively. Alternatively, each of the third target device and the fourth target device may be implemented as other devices other than the first target device 140 and the second target device 150.

[0167] In some embodiments, each of the second configuration information and the third configuration information may include information items similar to those in the first configuration information. For example, the second configuration information may include at least one of the following items related to the third target device:

[0168] a TNL address of the third device 130 anchored on the third target device,

[0169] Internet Protocol version 6 (IPv6) flow labels,

[0170] Differentiated Services Code Point (DSCP),

[0171] a Backhaul Adaptation Protocol (BAP) routing identifier (ID) associated with a third target device,

[0172] Backhaul radio link control channel configuration, or

[0173] BAP layer configuration.

[0174] For example, the first device 110 may have pre-selected a third target device for the first service and a fourth target device for the second service. For example, the IAB MIGRATION MANAGEMENT REQUEST message includes the following information:

[0175] Service index #1, QoS=40Mbps, DL TNL address=#A1 anchored at the fourth target device

[0176] Service index #2, QoS=60 Mbps, DL TNL address=#A2 anchored at the third target device.

[0177] Without the embodiments of the present disclosure, since the third target device only supports QoS=40 Mbps, service index #2 will be rejected.

[0178] Using an embodiment of the present disclosure, the first device 110 determines that the third target device only supports QoS=40Mbps, while the fourth target device can support 60Mbps. Therefore, the first device 110 can use the third target device for the service identified by service index #1, and use the fourth target device for the service identified by service index #2, and both service indexes are accommodated. In such an embodiment, Figure 3 At 318 in the IAB MIGRATION MANAGEMENT RESONSE message, the IAB MIGRATION MANAGEMENT RESONSE message may include a service addition list IE, which also includes the following information:

[0179] • Service index #1, including the UL routing ID of the BAP address of the third target device, anchored at the new TNL address #A3 at the third target device.

[0180] Service index #2, UL routing ID includes the BAP address of the fourth target device, and a new TNL address #A4 anchored at the fourth target device.

[0181] In summary, such embodiments improve the migration success rate by allowing the target IAB-donor-CU to modify the previously selected IAB-donor-DU and use multiple IAB-donor-DUs (eg, the third target device and the fourth target device in the above example) in the target topology.

[0182] Figure 4 A flowchart of an example method 400 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purpose of discussion, the method 400 will refer to Figure 1 It is described from the perspective of the first device 110 .

[0183] At block 410, the first device 110 receives a context of traffic to be offloaded via a first target device in the radio access network from a second device in the radio access network. The first target device is associated with the first device, and the traffic includes first traffic to be transmitted between the second device and a third device in the radio access network.

[0184] At block 420 , the first device 110 selects a second target device for the first service based on the context, wherein the second target device is associated with the first device.

[0185] At block 430 , the first device 110 sends first configuration information to the second device for transmitting the first service between the second device and the third device via the second target device.

[0186] In some embodiments, the first device 110 receives the context of the service from the second device after receiving a switching request message or a secondary node adding request message for offloading the service from the second device.

[0187] In some embodiments, the first device 110 receives the context of the service from the second device in a handover request message or a secondary node addition request message for offloading the service.

[0188] In some embodiments, the service also includes a second service. Method 400 also includes: selecting a third target device for the first service and a fourth target device for the second service based on the context, wherein the third and fourth target devices are associated with the first device; and sending second configuration information and third configuration information to the second device. The second configuration information is used to transmit the first service between the second device and the third device via the third target device, and the third configuration information is used to transmit the second service between the second device and the third device via the fourth target device.

[0189] In some embodiments, the first device 110 sends the second configuration information and the third configuration information to the second device in a handover request confirm message or a secondary node add request confirm message.

[0190] In some embodiments, the context includes quality of service information associated with the traffic to be offloaded.

[0191] In some embodiments, the traffic comprises at least one of user plane traffic and control plane traffic.

[0192] In some embodiments, the context includes QoS information associated with the user plane traffic.

[0193] In some embodiments, the method 400 further includes: sending, to the third device, first configuration information for transmitting the first service between the second device and the third device via the second target device.

[0194] In some embodiments, the first configuration information includes at least one of the following related to the second target device: a transport network layer address of a third device anchored at the second target device, an Internet Protocol version 6 flow label, a differentiated services code point, a backhaul adaptation protocol routing identifier associated with the second target device, a backhaul radio link control channel configuration; or a backhaul adaptation protocol layer configuration.

[0195] In some embodiments, the first device includes a target IAB-donor-CU, the second device includes a source IAB-donor-CU, the third device includes an IAB node, and each of the first and second target devices includes a target IAB-donor-DU.

[0196] In some embodiments, each of the third target device and the fourth target device comprises a target IAB-Donor-DU.

[0197] Figure 5 FIG. 5 is a flowchart of an example method 500 implemented at a second device according to some example embodiments of the present disclosure. For ease of discussion, the method 500 will refer to Figure 1 It is described from the perspective of the second device 120 .

[0198] At block 510, the second device 120 sends a context of traffic to be offloaded via a first target device in the radio access network to a first device in the radio access network. The first target device is associated with the first device, and the traffic includes first traffic to be transmitted between the second device and a third device in the radio access network.

[0199] At block 520 , the second device 120 receives first configuration information from the first device for transmitting the first traffic between the second device and a third device via a second target device, wherein the second target device is associated with the first device.

[0200] At block 530 , the second device 120 transmits the first service using the first configuration information.

[0201] In some embodiments, after sending a switching request message or a secondary node adding request message for offloading the service to the first device, the second device 120 sends the context of the service to the first device.

[0202] In some embodiments, the second device 120 sends the context of the service to the first device in a handover request message or a secondary node addition request message for offloading the service.

[0203] In some embodiments, the service also includes a second service. In such an embodiment, the method 500 further includes: receiving second configuration information and third configuration information from the first device. The second configuration information is used to transmit the first service between the second device and the third device via a third target device, and the third configuration information is used to transmit the second service between the second device and the third device via a fourth target device. The third and fourth target devices are associated with the first device.

[0204] In some embodiments, the second device 120 receives the second configuration information and the third configuration information in a handover request confirmation message or a secondary node addition request confirmation message from the first device.

[0205] In some embodiments, the traffic comprises at least one of user plane traffic and control plane traffic.

[0206] In some embodiments, the context includes QoS information associated with the user plane traffic.

[0207] In some embodiments, the first configuration information includes at least one of the following related to the second target device: a transport network layer address of a third device anchored at the second target device, an Internet Protocol version 6 flow label, a differentiated services code point, a backhaul adaptation protocol routing identifier associated with the second target device, a backhaul radio link control channel configuration; or a backhaul adaptation protocol layer configuration.

[0208] In some embodiments, the first device includes a target IAB-donor-CU, the second device includes a source IAB-donor-CU, the third device includes an IAB node, and each of the first and second target devices includes a target IAB-donor-DU.

[0209] In some embodiments, each of the third target device and the fourth target device comprises a target IAB-Donor-DU.

[0210] In some embodiments, the method 500 further includes: sending an instruction to a third device to apply the first configuration information to transmit the first service.

[0211] Figure 6 FIG. 6 is a flowchart showing an example method 600 implemented at a third device according to some example embodiments of the present disclosure. For the purpose of discussion, the method 600 will refer to FIG. Figure 1 It is described from the perspective of the third device 130 .

[0212] At block 610, the third device 130 receives first configuration information from a first device or a second device in the radio access network for transmitting a first service between the second device in the radio access network and a third device in the radio access network via a second target device in the radio access network. The second target device is associated with the first device.

[0213] At block 620 , the third device 130 transmits the first service using the first configuration information.

[0214] In some embodiments, the method 600 further includes: receiving an instruction from the second device to apply the first configuration information to transmit the first service.

[0215] In some embodiments, the first device includes a target IAB-donor-CU, the second device includes a source IAB-donor-CU, the third device includes an IAB node, and each of the first and second target devices includes a target IAB-donor-DU.

[0216] In some example embodiments, a first device (e.g., first device 110) in a radio access network capable of performing any of the methods 400 may include a component for performing the corresponding operation of the 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 the first device 110 or included in the first device 110. In some example embodiments, the component may include a processor and a memory.

[0217] In some example embodiments, a first apparatus includes: means for receiving, from a second device in a radio access network, a context of a service to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the service includes a first service to be transmitted between the second device and a third device in the radio access network; means for selecting a second target device for the first service based on the context, wherein the second target device is associated with the first device; and means for sending first configuration information to the second device to transmit the first service between the second device and the third device via the second target device.

[0218] In some embodiments, the means for receiving includes means for receiving the context of the service from the second device after receiving a handover request message or a secondary node addition request message for offloading the service from the second device.

[0219] In some embodiments, the means for receiving includes means for receiving, from the second device, a context of the service in a handover request message or a secondary node addition request message for offloading the service.

[0220] In some embodiments, the service also includes a second service. The first device also includes: a component for selecting a third target device for the first service and a fourth target device for the second service based on the context, wherein the third and fourth target devices are associated with the first device; and sending second configuration information and third configuration information to the second device. The second configuration information is used to transmit the first service between the second device and the third device via the third target device, and the third configuration information is used to transmit the second service between the second device and the third device via the fourth target device.

[0221] In some embodiments, the first apparatus further includes: a component for sending the second configuration information and the third configuration information to the second device in a handover request confirmation message or a secondary node addition request confirmation message.

[0222] In some embodiments, the context includes quality of service information associated with the traffic to be offloaded.

[0223] In some embodiments, the traffic comprises at least one of user plane traffic and control plane traffic.

[0224] In some embodiments, the context includes QoS information associated with the user plane traffic.

[0225] In some embodiments, the first apparatus further includes: a component for sending first configuration information to a third device, where the first configuration information is used to transmit the first service between the second device and the third device via the second target device.

[0226] In some embodiments, the first configuration information includes at least one of the following related to the second target device: a transport network layer address of a third device anchored at the second target device, an Internet Protocol version 6 flow label, a differentiated services code point, a backhaul adaptation protocol routing identifier associated with the second target device, a backhaul radio link control channel configuration; or a backhaul adaptation protocol layer configuration.

[0227] In some embodiments, the first device includes a target IAB-donor-CU, the second device includes a source IAB-donor-CU, the third device includes an IAB node, and each of the first target device and the second target device includes a target IAB-donor-DU.

[0228] In some embodiments, each of the third target device and the fourth target device comprises a target IAB-Donor-DU.

[0229] In some example embodiments, a second device (e.g., second device 120) in a radio access network capable of performing any of the methods 500 may include a component for performing the corresponding operations of the 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 the second device 120 or included in the second device 120. In some example embodiments, the component may include a processor and a memory.

[0230] In some example embodiments, the second apparatus includes: means for sending, to a first device in a radio access network, a context of a service to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the service includes a first service to be transmitted between a second device and a third device in the radio access network; means for receiving, from the first device, first configuration information for transmitting the first service between the second device and the third device via a second target device, wherein the second target device is associated with the first device; and means for transmitting the first service using the first configuration information.

[0231] In some embodiments, the means for sending includes means for sending the context of the service to the first device after sending a handover request message or a secondary node addition request message for offloading the service to the first device.

[0232] In some embodiments, the means for sending includes means for sending the context of the service to the first device in a handover request message or a secondary node addition request message for offloading the service.

[0233] In some embodiments, the service also includes a second service. In such an embodiment, the second device also includes: a component for receiving second configuration information and third configuration information from the first device. The second configuration information is used to transmit the first service between the second device and the third device via a third target device, and the third configuration information is used to transmit the second service between the second device and the third device via a fourth target device. The third and fourth target devices are associated with the first device.

[0234] In some embodiments, the second apparatus further includes: a component for receiving the second configuration information and the third configuration information in a handover request confirmation message or a secondary node addition request confirmation message from the first device.

[0235] In some embodiments, the traffic comprises at least one of user plane traffic and control plane traffic.

[0236] In some embodiments, the context includes QoS information associated with the user plane traffic.

[0237] In some embodiments, the first configuration information includes at least one of the following related to the second target device: a transport network layer address of a third device anchored at the second target device, an Internet Protocol version 6 flow label, a differentiated services code point, a backhaul adaptation protocol routing identifier associated with the second target device, a backhaul radio link control channel configuration; or a backhaul adaptation protocol layer configuration.

[0238] In some embodiments, the first device includes a target IAB-donor-CU, the second device includes a source IAB-donor-CU, the third device includes an IAB node, and each of the first and second target devices includes a target IAB-donor-DU.

[0239] In some embodiments, each of the third target device and the fourth target device comprises a target IAB-Donor-DU.

[0240] In some embodiments, the second apparatus further comprises: a component for sending an instruction to a third device to apply the first configuration information to transmit the first service.

[0241] In some example embodiments, a third device (e.g., third device 130) in a radio access network capable of performing any of the methods 600 may include a component for performing the corresponding operation of the method 600. 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 the third device 130 or included in the third device 130. In some example embodiments, the component may include a processor and a memory.

[0242] In some example embodiments, the third apparatus includes: a component for receiving first configuration information from a first device in a radio access network to transmit a first service between a second device in the radio access network and a third device in the radio access network via a second target device in the wireless point access network, wherein the second target device is associated with the first device; and a component for transmitting the first service using the first configuration information.

[0243] In some embodiments, the third apparatus further comprises: a component for receiving an instruction from the second device to apply the first configuration information to transmit the first service.

[0244] In some embodiments, the first device includes a target IAB-donor-CU, the second device includes a source IAB-donor-CU, the third device includes an IAB node, and each of the first and second target devices includes a target IAB-donor-DU.

[0245] Figure 7is a simplified block diagram of a device 700 suitable for implementing an example embodiment of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1 The first device 110, the second device 120 or the third device 130 is shown. As shown in the figure, the apparatus 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0246] The communication module 740 is used for two-way communication. The communication module 740 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface may represent any interface necessary for communication with other network elements. In some example embodiments, the communication module 740 may include at least one antenna.

[0247] Processor 710 may be of any type suitable for the 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 700 may have multiple processors, such as application specific integrated circuit chips, which are time-slaved to a clock synchronized with a main processor.

[0248] The memory 720 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) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), optical disk, laser disk, and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist over the duration of a power outage.

[0249] Computer program 730 includes computer executable instructions that can be executed by associated processor 710. Program 730 can be stored in a memory, such as ROM 724. Processor 710 can perform any suitable actions and processes by loading program 730 into RAM 722.

[0250] The exemplary embodiments of the present disclosure may be implemented by the program 730 so that the device 700 may perform any process of the present disclosure, such as referring to Figures 2 to 6 The exemplary embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0251] In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium that may be included in the device 700 (such as in the memory 720) or in other storage devices accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium into the RAM 722 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 8 An example of a computer readable medium 800 is shown, which may be in the form of a CD, DVD or other optical storage disk. The computer readable medium has a program 730 stored thereon.

[0252] 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, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described in block diagrams, flow charts, or using some other graphical representations, it should be understood that, as non-limiting examples, the blocks, 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.

[0253] 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 those included in a program module, which are executed in a device on a target physical or virtual processor to perform the above-referenced Figures 2 to 6 Any method described. Typically, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. The functions of program modules can be combined or split between program modules as needed in various embodiments. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0254] 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 the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely 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.

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

[0256] 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, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, device or apparatus, or any suitable combination of the above. More specific examples of computer readable storage media include an electrical connection with one or more wires, a portable computer 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 of the above.

[0257] It should be understood that, although some embodiments can be implemented by / at the IAB node, the solution including the method and apparatus proposed in the present disclosure can also be applied to other communication systems with similar technical problems. In addition, although the operation is described in a specific order, it should not be understood as requiring these operations to be performed in the specific order or sequential order shown, or requiring all the operations shown to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limiting 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 separate embodiments 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 separately in multiple embodiments or implemented in any suitable sub-combination.

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

Claims

1. A first device in a radio access network, comprising: at least one processor; as well as 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 first device to: receiving, from a second device in the radio access network, a context for traffic to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the traffic comprises: first traffic to be transmitted between the second device and a third device in the radio access network; Based on the context, selecting a second target device for the first service, wherein the second target device is associated with the first device; and First configuration information is sent to the second device, so as to transmit the first service between the second device and the third device via the second target device.

2. The first device according to claim 1, wherein the first device is further configured to: After receiving a switching request message or a secondary node adding request message for offloading the service from the second device, the context of the service is received from the second device.

3. The first device according to claim 1, wherein the first device is further configured to: The context of the service is received from the second device in a handover request message or an auxiliary node addition request message for offloading the service.

4. The first device according to claim 3, wherein: The service also includes a second service; and The first device is also configured to: Based on the context, selecting a third target device for the first service and selecting a fourth target device for the second service, wherein the third target device and the fourth target device are associated with the first device; Second configuration information and third configuration information are sent to the second device, wherein the second configuration information is used to transmit the first service between the second device and the third device via the third target device, and the third configuration information is used to transmit the second service between the second device and the third device via the fourth target device.

5. The first device according to claim 4, wherein the first device is further configured to: The second configuration information and the third configuration information are sent to the second device in a switching request confirmation message or a secondary node adding request confirmation message. 6 . The first device according to claim 1 , wherein the context comprises quality of service information associated with the service.

7. The first device according to any one of claims 1 to 6, wherein the traffic comprises at least one of the following: user plane traffic and control plane traffic.

8. The first device of claim 7, wherein the context comprises QoS information associated with the user plane traffic.

9. The first device according to claim 1, wherein the first device is further caused to: The first configuration information for transmitting the first service between the second device and the third device via the second target device is sent to the third device.

10. The first device according to any one of claims 1 to 9, wherein the first configuration information includes at least one of the following items related to the second target device: a transport network layer address of said third device for anchoring at said second target device, Internet Protocol Version 6 Flow Labels, Differentiated Services Code Point, a backhaul adaptation protocol routing identifier associated with the second target device, Backhaul radio link control channel configuration; or Backhaul Adaptation Protocol layer configuration.

11. The first device of claim 1 , wherein the first device comprises a target set access and backhaul donor central unit (IAB-donor-CU), the second device comprises a source IAB-donor-CU, the third device comprises an IAB node, and each of the first target device and the second target device comprises: Target Integrated Access and Backhaul Donor Distributed Unit IAB-Donor-DU.

12. The first device of claim 4, wherein each of the third target device and the fourth target device comprises: Target Integrated Access and Backhaul Donor Distributed Unit IAB-Donor-DU.

13. A second device in a radio access network, comprising: at least one processor; as well as 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 second device to: sending, to a first device in the radio access network, a context of traffic to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the traffic comprises: first traffic to be transmitted between the second device and a third device in the radio access network; receiving, from the first device, first configuration information for transmitting the first service between the second device and the third device via a second target device, wherein the second target device is associated with the first device; and The first service is transmitted using the first configuration information.

14. The second device according to claim 13, wherein the second device is further caused to: After sending a switching request message or a secondary node adding request message for offloading the service to the first device, the context of the service is sent to the first device.

15. The second device according to claim 13, wherein the second device is further caused to: The context of the service is sent to the first device in a switching request message or a secondary node adding request message for offloading the service.

16. The second device according to claim 15, wherein: The service also includes a second service; and The second device is further configured to: Second configuration information and third configuration information are received from the first device, wherein the second configuration information is used to transmit the first service between the second device and the third device via a third target device, and the third configuration information is used to transmit the second service between the second device and the third device via a fourth target device, wherein the third target device and the fourth target device are associated with the first device.

17. The second device according to claim 16, wherein the second device is further caused to: The second configuration information and the third configuration information are received from the first device in a handover request confirmation message or a secondary node addition request confirmation message.

18. The second device according to any one of claims 13 to 17, wherein the context comprises quality of service information associated with the service.

19. The second device according to any one of claims 13 to 18, wherein the traffic comprises at least one of the following: user plane traffic and control plane traffic.

20. The second device of claim 19, wherein the context comprises QoS information associated with the user plane traffic.

21. The second device according to any one of claims 13 to 20, wherein the first configuration information comprises at least one of the following items related to the second target device: a transport network layer address of said third device for anchoring at said second target device, Internet Protocol Version 6 Flow Labels, Differentiated Services Code Point, a backhaul adaptation protocol routing identifier associated with the second target device, Backhaul radio link control channel configuration; or Backhaul Adaptation Protocol layer configuration.

22. The second device of claim 13, wherein the first device comprises a target Integrated Access and Backhaul Donor Central Unit (IAB-Donor-CU), the second device comprises a source IAB-Donor-CU, the third device comprises an IAB node, and each of the first target device and the second target device comprises: Target Integrated Access and Backhaul Donor Distributed Unit IAB-Donor-DU.

23. The second device of claim 16, wherein each of the third target device and the fourth target device comprises: Target Integrated Access and Backhaul Donor Distributed Unit IAB-Donor-DU.

24. The second device of claim 13, wherein the second device is further caused to: An instruction is sent to the third device to apply the first configuration information to transmit the first service.

25. A third device in a radio access network, comprising: at least one processor; as well as 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: receiving first configuration information from a first device or a second device in the radio access network for transmitting a first service between the second device in the radio access network and the third device in the radio access network via a second target device in the radio access network, wherein the second target device is associated with the first device; as well as The first service is transmitted using the first configuration information.

26. The third device according to claim 25, wherein the third device is further caused to: An instruction is received from the second device to apply the first configuration information to transmit the first service.

27. The third device according to any one of claims 25 to 26, wherein the first device includes a target integrated access and backhaul donor central unit IAB-donor-CU, the second device includes a source IAB-donor-CU, the third device includes an IAB node, and the second target device includes a target integrated access and backhaul donor distributed unit IAB-donor-DU.

28. A method comprising: receiving, at a first device in a radio access network, a context for traffic to be offloaded via a first target device in the radio access network from a second device in the radio access network, wherein the first target device is associated with the first device, and wherein the traffic comprises: first traffic to be transmitted between the second device and a third device in the radio access network; Based on the context, selecting a second target device for the first service, wherein the second target device is associated with the first device; and First configuration information is sent to the second device, so as to transmit the first service between the second device and the third device via the second target device.

29. A method comprising: sending, from a second device in a radio access network to a first device in the radio access network, a context of traffic to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the traffic comprises: first traffic to be transmitted between the second device and a third device in the radio access network; receiving, from the first device, first configuration information for transmitting the first service between the second device and the third device via a second target device, wherein the second target device is associated with the first device; and The first service is transmitted using the first configuration information.

30. A method comprising: receiving, at a third device in a radio access network, first configuration information from a first device or a second device in the radio access network for transmitting a first service between the second device in the radio access network and the third device in the radio access network via a second target device in the radio access network, wherein the second target device is associated with the first device; as well as The first service is transmitted using the first configuration information.

31. A first device, comprising: means for receiving, from a second device in a radio access network, a context for traffic to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the traffic comprises: first traffic to be transmitted between the second device and a third device in the radio access network; means for selecting a second target device for the first service based on the context, wherein the second target device is associated with the first device; and A component for sending first configuration information to the second device for transmitting the first service between the second device and the third device via the second target device.

32. A second device, comprising: means for sending, to a first device in a radio access network, a context of traffic to be offloaded via a first target device in the radio access network, wherein the first target device is associated with the first device, and wherein the traffic comprises: first traffic to be communicated between the second device and a third device in the radio access network; means for receiving, from the first device, first configuration information for transmitting the first service between the second device and the third device via a second target device, wherein the second target device is associated with the first device; and Means for transmitting the first service using the first configuration information.

33. A third device, comprising: means for receiving first configuration information from a first device or a second device in a radio access network for transmitting a first service between the second device in the radio access network and the third device in the radio access network via a second target device in the radio access network, wherein the second target device is associated with the first device; as well as Means for transmitting the first service using the first configuration information.

34. A computer readable medium comprising program instructions which, when executed by at least one processor, cause an apparatus to perform at least the method of claim 28.

35. A computer readable medium comprising program instructions which, when executed by at least one processor, cause an apparatus to perform at least the method of claim 29.

36. A computer readable medium comprising program instructions which, when executed by at least one processor, cause an apparatus to perform at least the method of claim 30.

Images