Processing

Please wait...

Settings

Settings

Goto Application

1. WO2020194271 - IAB NODE RELEASE PROCEDURE

Note: Text based on automatic Optical Character Recognition processes. Please use the PDF version for legal matters

[ EN ]

CLAIMS

1. A method performed by a first Integrated Access Backhaul (IAB)-donor central unit (CU), the method comprising:

receiving a mobile termination (MT) context release associated with an IAB-node, wherein a MT function of the IAB-node is served by the first IAB-donor CU;

identifying a distributed unit (DU) function for the IAB-node;

determining if at least one user equipment (UE) or child IAB-node is served by the IAB-node DU;

initiating a release of an F1 interface resource associated with the IAB-node DU; and releasing a radio resource control (RRC) connection associated with the IAB-node MT.

2. The method of claim 1, further comprising, determining that the IAB-node DU function is served by a second IAB-donor CU.

3. The method of any one of claims 1 to 2, further comprising, responsive to determining that a UE is served by the IAB-node DU, initiating a handover or release of the UE.

4. The method of claim 3, wherein initiating the handover or release of the UE includes transmitting a Xn handover request message to the second IAB-donor CU.

5. The method of claim 3, wherein initiating the handover or release of the UE includes transmitting a RRC release message to the second IAB-donor CU.

6. The method of any one of claims 1 to 5, further comprising, responsive to determining that a child IAB-node is served by the IAB-node DU, initiating a handover or release of the child IAB-node.

7. The method of claim 6, wherein initiating the handover or release of the child IAB-node includes transmitting a Xn handover request message to the second IAB-donor CU.

8. The method of claim 6, wherein initiating the handover or release of the child IAB-node includes transmitting a RRC release message to the second IAB-donor CU.

9. The method of any one of claims 1 to 8, wherein initiating the release of the F1 interface resource includes releasing a non-UE associated context associated with the IAB-node DU.

10. The method of any one of claims 1 to 9, wherein initiating the release of the F1 interface resource includes transmitting a message to the second IAB-donor CU.

11. The method of any one of claims 1 to 10, further comprising, transmitting a UE/MT context release message to at least one parent IAB-node of the IAB-node.

12. The method of claim 11, wherein the parent IAB-node is an IAB-donor DU.

13. A first Integrated Access Backhaul (IAB)-donor central unit (CU) comprising a radio interface and processing circuitry configured to:

receive a mobile termination (MT) context release associated with an IAB-node, wherein a MT function of the IAB-node is served by the first IAB-donor CU;

identify a distributed unit (DU) function for the IAB-node;

determine if at least one user equipment (UE) or child IAB-node is served by the IAB-node DU;

initiate a release of an F1 interface resource associated with the IAB-node DU; and release a radio resource control (RRC) connection associated with the IAB-node MT.

14. The first IAB-donor CU of claim 13, further configured to determine that the IAB-node DU function is served by a second IAB-donor CU.

15. The first IAB-donor CU of any one of claims 13 to 14, further configured to, responsive to determining that a UE is served by the IAB-node DU, initiate a handover or release of the UE.

16. The first IAB-donor CU of claim 15, wherein initiating the handover or release of the UE includes transmitting a Xn handover request message to the second IAB-donor CU.

17. The first IAB-donor CU of claim 15, wherein initiating the handover or release of the UE includes transmitting a RRC release message to the second IAB-donor CU.

18. The first IAB-donor CU of any one of claims 13 to 17, further configured to, responsive to determining that a child IAB-node is served by the IAB-node DU, initiate a handover or release of the child IAB-node.

19. The first IAB-donor CU of claim 18, wherein initiating the handover or release of the child IAB-node includes transmitting a Xn handover request message to the second IAB-donor CU.

20. The first IAB-donor CU of claim 18, wherein initiating the handover or release of the child IAB-node includes transmitting a RRC release message to the second IAB-donor CU.

21. The first IAB-donor CU of any one of claims 13 to 20, wherein initiating the release of the F1 interface resource includes releasing a non-UE associated context associated with the IAB-node DU.

22. The first IAB-donor CU of any one of claims 13 to 21, wherein initiating the release of the F1 interface resource includes transmitting a message to the second IAB-donor CU.

23. The first IAB-donor CU of any one of claims 13 to 22, further comprising, transmitting a UE/MT context release message to at least one parent IAB-node of the IAB-node.

24. The first IAB-donor CU of claim 23, wherein the parent IAB-node is an IAB-donor DU.