Packet duplication control
Wireless communications are described. A central unit control plane (CU-CP) node of a base station may activate and/or deactivate packet duplication based on status information from self-monitoring, from a distributed unit (DU), from a wireless device, and/or from a central unit user plane (CU-UP) node. The CU-UP node and/or the DU may activate and/or deactivate packet duplication based on status information from self-monitoring, from each other, from the wireless device, and/or from the CU-CP node. The CU-UP node and/or the DU, after activating and/or deactivating packet duplication, may report the activation and/or deactivation to the CU-CP node.
1. A method comprising:
receiving, by a central unit user plane (CU-UP) node from a central unit control plane (CU-CP) node, a message comprising:
an indication of configuration of packet duplication for a bearer associated with a wireless device, and
an indication of activation of the packet duplication; and
sending, by the CU-UP node, via at least one distributed unit (DU), to the wireless device, and based on the message, packets and duplicated versions of the packets.
2. The method of claim 1 , wherein the message comprises a bearer configuration request for the wireless device.
3. The method of claim 1 , wherein the message further comprises logical channel information, for the bearer, comprising:
a first logical channel identifier of a first logical channel for the packets, and
a second logical channel identifier of a second logical channel for the duplicated versions of the packets.
4. The method of claim 1 , further comprising:
after receiving the message, sending, by the CU-UP node to the CU-CP node, one or more second messages comprising uplink tunnel information, for the bearer, comprising:
a first uplink tunnel endpoint identifier for a first tunnel for uplink packets, and
a second uplink tunnel endpoint identifier for a second tunnel for duplicated uplink packets.
5. The method of claim 4 , further comprising:
after sending the one or more second messages, receiving, from the CU-CP node, a configuration update message indicating downlink tunnel information for the bearer.
6. The method of claim 1 , further comprising:
receiving, by the CU-UP node from the CU-CP node, one or more messages indicating deactivation of the packet duplication; and
based on the one or more messages indicating the deactivation, discontinuing the sending of the duplicated versions of the packets.
7. The method of claim 1 , further comprising:
based on status information associated with the CU-CP node, deactivating, by the CU-UP node, the packet duplication.
8. The method of claim 1 , further comprising:
based on status information associated with the at least one DU, deactivating, by the CU-UP node, the packet duplication.
9. The method of claim 1 , further comprising:
based on status information received by the CU-UP node, deactivating the packet duplication, wherein the status information comprises an indication of at least one of:
a hardware load,
a load of an N2 interface between the CU-UP node and a core network entity,
a load of an F1 interface between the CU-UP node and the at least one DU,
a composite available capacity group, or
a network slice overload.
10. The method of claim 1 , further comprising:
deactivating, by the CU-UP node, the packet duplication; and
sending, by the CU-UP node to the CU-CP node, one or more messages indicating the deactivation of the packet duplication.
11. The method of claim 1 , further comprising:
activating, by the CU-UP node and based on status information received by the CU-UP node, the packet duplication, wherein the status information comprises at least one of:
status information associated with the CU-CP node, or
status information associated with the at least one DU; and
sending, by the CU-UP node to the CU-CP node, one or more messages indicating the activation by the CU-UP node.
12. The method of claim 1 , wherein the packet duplication comprises packet data convergence protocol (PDCP) packet duplication.
13. The method of claim 1 , further comprising:
based on the receiving the message, discarding, by the CU-UP node, duplicated uplink packet data convergence protocol (UL PDCP) packets received from at least one of: the at least one DU or the wireless device.
14. A method comprising:
receiving, by a central unit user plane (CU-UP) node from a central unit control plane (CU-CP) node, a message comprising:
an indication of configuration of packet duplication for a bearer associated with a wireless device, and
an indication of activation of the packet duplication;
sending, by the CU-UP node, via at least one distributed unit (DU), to the wireless device, and based on the message, packets and duplicated versions of the packets;
receiving, by the CU-UP node from the CU-CP node, one or more messages indicating deactivation of the packet duplication; and
based on the one or more messages indicating the deactivation, discontinuing the sending of the duplicated versions of the packets.
15. The method of claim 14 , further comprising:
determining, by the CU-UP node and based on status information received by the CU-UP node after a second activation of the packet duplication, to perform a second deactivation of the packet duplication, wherein the status information comprises status information associated with one or more of the CU-CP node or the at least one DU.
16. The method of claim 14 , further comprising:
activating, by the CU-UP node, the packet duplication; and
sending, by the CU-UP node to the CU-CP node, one or more messages indicating the activation by the CU-UP node.
17. The method of claim 14 , further comprising:
based on additional status information received by the CU-UP node, activating, by the CU-UP node, the packet duplication, wherein the additional status information comprises at least one of:
additional status information associated with the CU-CP node, or
additional status information associated with the at least one DU.
18. A method comprising:
based on status information received by a central unit user plane (CU-UP) node from a central unit control plane (CU-CP) node, activating, by the CU-UP node, packet duplication, wherein the status information comprises at least one of:
status information associated with the CU-CP node, or
status information associated with a distributed unit (DU);
sending, by the CU-UP node to the CU-CP node, one or more messages indicating the activation; and
based on the activation, sending, via the DU and to a wireless device, packets and duplicated versions of the packets.
19. The method of claim 18 , wherein the status information comprises indications of at least one of:
a hardware load,
a load of an N2 interface between the CU-UP node and a core network entity,
a load of an F1 interface between the CU-UP node and the DU,
a composite available capacity group, or
a network slice overload.
20. The method of claim 18 , further comprising:
deactivating, by the CU-UP node, the packet duplication; and
sending, by the CU-UP node to the CU-CP node, one or more messages indicating the deactivation of the packet duplication.
21. A central unit user plane (CU-UP) node comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the CU-UP node to:
receive, from a central unit control plane (CU-CP) node, a message comprising:
an indication of configuration of packet duplication for a bearer associated with a wireless device, and
an indication of activation of the packet duplication; and
send, via at least one distributed unit (DU), to the wireless device, and based on the message, packets and duplicated versions of the packets.
22. The CU-UP node of claim 21 , wherein the message comprises a bearer configuration request for the wireless device.
23. The CU-UP node of claim 21 , wherein the message further comprises logical channel information, for the bearer, comprising:
a first logical channel identifier of a first logical channel for the packets, and
a second logical channel identifier of a second logical channel for the duplicated versions of the packets.
24. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
after receiving the message, send, to the CU-CP node, one or more second messages comprising uplink tunnel information, for the bearer, comprising:
a first uplink tunnel endpoint identifier for a first tunnel for uplink packets, and
a second uplink tunnel endpoint identifier for a second tunnel for duplicated uplink packets.
25. The CU-UP node of claim 24 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
after sending the one or more second messages, receive, from the CU-CP node, a configuration update message indicating downlink tunnel information for the bearer.
26. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
receive, from the CU-CP node, one or more messages indicating deactivation of the packet duplication; and
based on the one or more messages indicating the deactivation, discontinue sending of the duplicated versions of the packets.
27. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
based on status information associated with the CU-CP node, deactivate the packet duplication.
28. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
based on status information associated with the at least one DU, deactivate the packet duplication.
29. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
based on status information received by the CU-UP node, deactivate the packet duplication, wherein the status information comprises an indication of at least one of:
a hardware load,
a load of an N2 interface between the CU-UP node and a core network entity,
a load of an F1 interface between the CU-UP node and the at least one DU,
a composite available capacity group, or
a network slice overload.
30. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
deactivate the packet duplication; and
send, to the CU-CP node, one or more messages indicating the deactivation of the packet duplication.
31. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
activate, based on status information received by the CU-UP node, the packet duplication, wherein the status information comprises at least one of:
status information associated with the CU-CP node, or
status information associated with the at least one DU; and
send, to the CU-CP node, one or more messages indicating the activation by the CU-UP node.
32. The CU-UP node of claim 21 , wherein the packet duplication comprises packet data convergence protocol (PDCP) packet duplication.
33. The CU-UP node of claim 21 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
based on the message, discard duplicated uplink packet data convergence protocol (UL PDCP) packets received from at least one of: the at least one DU or the wireless device.
34. A central unit user plane (CU-UP) node comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the CU-UP node to:
receive, from a central unit control plane (CU-CP) node, a message comprising:
an indication of configuration of packet duplication for a bearer associated with a wireless device, and
an indication of activation of the packet duplication;
send, via at least one distributed unit (DU), to the wireless device, and based on the message, packets and duplicated versions of the packets;
receive, from the CU-CP node, one or more messages indicating deactivation of the packet duplication; and
based on the one or more messages indicating the deactivation, discontinue sending of the duplicated versions of the packets.
35. The CU-UP node of claim 34 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
determine, based on status information received by the CU-UP node after a second activation of the packet duplication, to perform a second deactivation of the packet duplication, wherein the status information comprises status information associated with at least one of the CU-CP node or the at least one DU.
36. The CU-UP node of claim 34 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
activate the packet duplication; and
send, to the CU-CP node, one or more messages indicating the activation by the CU-UP node.
37. The CU-UP node of claim 34 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
based on additional status information received by the CU-UP node, activate the packet duplication, wherein the additional status information comprises at least one of:
additional status information associated with the CU-CP node, or
additional status information associated with the at least one DU.
38. A central unit user plane (CU-UP) node comprising:
one or more processors; and
memory storing instructions that, when executed by the one or more processors, cause the CU-UP node to:
based on status information received by the CU-UP node from a central unit control plane (CU-CP) node, activate packet duplication, wherein the status information comprises at least one of:
status information associated with the CU-CP node, or
status information associated with a distributed unit (DU);
send, to the CU-CP node, one or more messages indicating the activation; and
based on the activation, send, via the DU and to a wireless device, packets and duplicated versions of the packets.
39. The CU-UP node of claim 38 , wherein the status information comprises indications of at least one of:
a hardware load,
a load of an N2 interface between the CU-UP node and a core network entity,
a load of an F1 interface between the CU-UP node and the DU,
a composite available capacity group, or
a network slice overload.
40. The CU-UP node of claim 38 , wherein the instructions, when executed by the one or more processors, further cause the CU-UP node to:
deactivate the packet duplication; and
send, to the CU-CP node, one or more messages indicating the deactivation of the packet duplication.