US-20230284246-A1 - DEVICES, METHODS, APPARATUSES AND COMPUTER READABLE MEDIA FOR TOPOLOGY REDUNDANCY

US20230284246A1US 20230284246 A1US20230284246 A1US 20230284246A1US-20230284246-A1

Abstract

Embodiments of the present disclosure relate to for topology redundancy. A first device transmits to a second device a request for setup of a context of a third device served by the first device. The first device receives the context from the second device. The first device transmits the context to the third device for communication between the third device and the first device via a fourth device. The fourth device is managed by the second device.

Inventors

XU XIANG
GEBERT JENS
BLUME OLIVER

Assignees

NOKIA TECHNOLOGIES OY

Dates

Publication Date: 20230907
Application Date: 20200805
Priority Date: 20200805

Claims (20)

1 . A first device, comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the first device to: transmit to a second device a request for information related to a third device served by the first device; receive the information from the second device; and transmit the information to the third device for communication between the third device and the first device via a fourth device, the fourth device managed by the second device.
2 . The first device of claim 1 , wherein the information comprises at least one of the following: a backhaul adaptation protocol address of the third device assigned by the second device, a transport layer address of the third device assigned by the second device, a backhaul adaptation protocol address of the fourth device assigned by the second device, a flow label for a traffic of the third device assigned by the second device, a differentiated services code point or traffic class code point for a traffic of the third device assigned by the second device, or a routing identity for an uplink traffic of the third device assigned by the second device.
3 . The first device of claim 1 , wherein the first device is caused to transmit the information to the third device by: transmitting the information in a radio resource control message or an F1 application protocol message; and wherein the first device is further caused to configure the third device to use the information in the communication between the third device and the first device.
4 . The first device of claim 1 , wherein the request comprises at least one of the following: an identity of the third device assigned by the first device, information of the fourth device, information concerning a transport layer address to be assigned by the second device, or information concerning traffic of the third device to be routed via the fourth device.
5 . The first device of claim 1 , wherein the third device is in communication with the first device via a fifth device.
6 . The first device of claim 5 , wherein the request further comprises an identity of the fifth device.
7 . The first device of claim 5 , wherein the first device is caused to transmit the request to the second device by: in accordance with a determination that the fifth device has been in communication with both the first device and the second device, when the third device initiates communication with the first device via the fifth device, transmitting the request to the second device; in accordance with a determination that the fifth device becomes in communication with both the first device and the second device after the third device has been in communication with the first device via the fifth device, transmitting the request to the second device; or in accordance with a determination that traffic between the first device and the third device needs to be offloaded via the fourth device, transmitting the request to the second device after the fifth device has been in communication with both the first device and the second device, and the third device has been in communication with the first device via the fifth device.
8 . The first device of claim 1 , wherein the first device comprises a centralized unit of a first integrated access and backhaul donor, the second device comprises a centralized unit of a second integrated access and backhaul donor, the third device comprises a first integrated access and backhaul node, the fourth device comprises a distributed unit of the second integrated access and backhaul donor.
9 . (canceled)
10 . A second device, comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the second device to: receive from a first device a request for information related to a third device served by the first device; determine the information of the third device; and transmit the information to the first device for communication between the third device and the first device via a fourth device, the fourth device managed by the second device.
11 . The second device of claim 10 , wherein the information comprises at least one of the following: a backhaul adaptation protocol address of the third device assigned by the second device, a transport layer address of the third device assigned by the second device, a backhaul adaptation protocol address of the fourth device assigned by the second device, a flow label for a traffic of the third device assigned by the second device, a differentiated services code point or traffic class code point for a traffic of the third device assigned by the second device, or a routing identity for an uplink traffic of the third device assigned by the second device.
12 . The second device of claim 10 , wherein the request comprises at least one of the following: an identity of the third device assigned by the first device, information of the fourth device, information concerning a transport layer address to be assigned by the second device, or information concerning traffic of the third device to be routed via the fourth device.
13 . The second device of claim 12 , wherein the second device is caused to determine the information of the third device by: in accordance with a determination that there are backhaul resources for the traffic based on the information concerning the traffic, determining the information of the third device.
14 . The second device of claim 12 , wherein the second device is further caused to: configure a mapping of the traffic to a backhaul radio link control channel in the fourth device based on the information concerning the traffic; and configure a routing of the traffic via the fourth device in the fourth device based on the information concerning the traffic.
15 . The second device of claim 10 , wherein the third device is in communication with the first device via a fifth device.
16 . The second device of claim 15 , wherein the request further comprises an identity of the fifth device.
17 . (canceled)
18 . A third device, comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the third device to: receive information relating to the third device from a first device serving the third device, the information being determined by a second device; and use the information in communication with the first device via a fourth device, the fourth device managed by the second device.
19 . The third device of claim 18 , wherein the information comprises at least one of the following: a backhaul adaptation protocol address of the third device assigned by the second device, a transport layer address of the third device assigned by the second device, a backhaul adaptation protocol address of the fourth device assigned by the second device, a flow label for a traffic of the third device assigned by the second device, a differentiated services code point or traffic class code point for a traffic of the third device assigned by the second device, or a routing identity for an uplink traffic of the third device assigned by the second device.
20 . The third device of claim 18 , wherein the third device is caused to receive the information by: receiving the information in a radio resource control message or an F1 application protocol message.

Description

FIELD Embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to devices, methods, apparatuses and computer readable media for topology redundancy. BACKGROUND Integrated Access and Backhaul (IAB) enables wireless relaying for New Radio (NR) access by using NR for backhauling. A relaying node is referred to as an IAB-node. The terminating node of NR backhauling on network side is referred to as an IAB-donor. The IAB-donor represents a gNB with additional functionality to support IAB. Backhauling may occur via a single or via multiple hops. In the IAB topology, topology redundancy is enabled. The topology redundancy has the goal to enable robust operation, for example, in case of backhaul link blockage, and to balance load across backhaul links. In Release 16 of the 3rd Generation Partnership Project (3GPP) specifications, the intra-centralized-unit (CU) topology redundancy procedure enables establishment and release of redundant paths in the IAB-topology underneath the same IAB-donor-CU. Inter-Donor Topology Adaptation (inter-donor TA) is one objective of Release 17. Inter-Donor topology redundancy is a related feature. Inter-donor redundancy is also referred to as inter-CU redundancy. Inter-CU redundancy differs from intra-CU redundancy in that a Master Cell Group (MCG) link and a Secondary Cell Group (SCG) link belong to different IAB-donors. However, it is unclear how topology redundancy is supported in inter-donor New Radio-Dual Connection. SUMMARY In general, example embodiments of the present disclosure provide a solution for topology redundancy. In a first aspect, there is provided a first device. The first device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the first device to: transmit to a second device a request for setup of a context of a third device served by the first device; receive the context from the second device; and transmit the context to the third device for communication between the third device and the first device via a fourth device, the fourth device managed by the second device. In a second aspect, there is provided a second device. The second device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the second device to: receive from a first device a request for setup of a context of a third device served by the first device; establish the context of the third device; and transmit the context to the first device for communication between the third device and the first device via a fourth device, the fourth device managed by the second device. In a third aspect, there is provided a third device. The third device comprises at least one processor; and at least one memory including computer program codes; the at least one memory and the computer program codes are configured to, with the at least one processor, cause the third device to: receive a context of the third device from a first device serving the third device, the context established by a second device; and use the context information in communication with the first device via a fourth device, the fourth device managed by the second device. In a fourth aspect, there is provided a method implemented at a device. The method comprises: transmitting from a first device to a second device a request for setup of a context of a third device served by the first device; receiving the context from the second device; and transmitting the context to the third device for communication between the third device and the first device via a fourth device, the fourth device managed by the second device. In a fifth aspect, there is provided a method implemented at a device. The method comprises: receiving, at a second device from a first device, a request for setup of a context of a third device served by the first device; setting up the context of the third device; and transmitting the context to the first device for communication between the third device and the first device via a fourth device, the fourth device managed by the second device. In a sixth aspect, there is provided a method implemented at a device. The method comprises: receiving, at a third device from a first device a context of the third device, the first device serving the third device, the context established by a second device; and using the context information in communication with the first device via a fourth device, the fourth device managed by the second device. In a seventh aspect, there is provided an apparatus comprising: means for transmitting from a first device to a second device a request for setup of a context of a third device served by the first device; means for receiving the context from the sec