Patent Description:
The Third Generation Partnership Project (3GPP) introduced carrier aggregation (CA) in 3GPP Release <NUM> as a method for a radio device (i.e., a user equipment, UE) to connect via multiple carriers to a single node (i.e., a base station) of a radio access network (RAN). A medium access control (MAC) entity in the MAC layer of the node functions as an aggregation point of the CA, allowing a centralized scheduler (also: scheduling entity) in the MAC layer to distribute packets and allocate radio resources, e.g. depending on a channel state (e.g., a channel estimate) among all carriers. This requires a tight integration of the radio protocols involved, e.g., between the MAC layer and a physical (PHY) layer. For CA, the MAC layer multiplexes data (e.g., packets) of a logical channel to the different radio resources of the aggregated carriers.

With dual-connectivity (DC), which expression shall encompass Multi-Connectivity (MC) herein, the aggregation point is at a packet data convergence protocol (PDCP) layer, meaning that PDCP packets are distributed among multiple radio link control (RLC) entities (and/or among multiple MAC entities). In this way, two MAC entities with their separate scheduling entities can be executed in two distinct nodes, without strict requirements on their interconnection while still allowing for realizing increased user throughput.

In 3GPP Release <NUM> for LTE and NR, both architecture concepts of CA and DC are used to improve radio transmission reliability. The improved reliability is achieved by means of packet duplication, which is performed by the PDCP layer in either cases of CA and DC. The PDCP duplicates an incoming data packet, e.g. a data packet of an ultra-reliable low-latency (URLLC) service. Each of the duplicates (i.e., the packets resulting from the duplication) undergoes procedures on protocol layers (e.g., RLC, MAC, and/or PHY) that are lower than the PDCP layer. Hence, the duplicates individually benefit from schemes for transmission reliability of these layers, e.g. retransmission reliability schemes. Eventually, the data packet will thus be transmitted via different frequency carriers to the radio device, which ensures uncorrelated transmission paths due to frequency diversity. Furthermore, the DC transmissions from or receptions at different sites provide spatial diversity.

A control element (CE) of the MAC layer defined in the 3GPP document TS <NUM>, version <NUM>. <NUM>, clause <NUM>. <NUM>, allows to selectively activate and deactivate configured RLC entities, e.g., dynamically as a scheduling tool.

The 3GPP document R2-<NUM> discusses an "Option <NUM>" in which gNBs and UEs construct and interpret duplication activation/deactivation MAC CEs. The MAC CEs are used to manage duplicated DRBs, including both CA and DC DRBs that are configured for the UE. In this option, the network node that sends the MAC CE includes all bits corresponding to all duplicate DRBs for the UE, including CA duplicate DRBs of the other network node. The discussion acknowledges that it does not make sense for the Secondary Cell Group (SCG) to control the activation/deactivation of CA duplicated DRBs of the MCG (Master Cell Group), and vice versa. As a result, the UE should always disregard these bits and identify which bits are relevant based on the MAC entity transmitting the MAC CE.

However, in the case of packet duplication using two nodes, the radio device follows the received MAC CE, even if the RLC field in the MAC CE received from one of the two nodes belongs to the other one of the two nodes. For example, it is possible that a first node (e.g., a master cell group, MCG) indicates the activation or deactivation state of the secondary RLC entity of the second node (e.g., for the secondary cell group, SCG). Activating or deactivating the RLC entities associated with the SCG by means of the MAC CE transmitted from the MCG is problematic, since this may not be the intention of the radio resource management at the SCG.

Accordingly, there is a need for a technique that allows to dynamically control a packet duplication using more than one node of a radio access network.

As to a first method aspect, a method of transmitting a control element (CE) for selectively activating and deactivating one or more secondary radio link control (RLC) entities configured for packet duplication in a radio communication between a radio device and a radio access network (RAN) is provided according to claim <NUM>. The RAN comprises a first node and a second node. The first node comprises a primary RLC entity configured for the packet duplication and the second node comprises at least one of the one or more secondary RLC entities. A control message is exchanged between the first node and the second node, the control message being indicative of which one of the first node and the second node is to perform the step of transmitting the CE to the radio device. The method further comprises or initiates a step of transmitting the CE from the RAN to the radio device. The CE is indicative of an activity state of each of the one or more secondary RLC entities configured for the packet duplication.

In at least some embodiments, the activating or deactivating of the (e.g., secondary) RLC entities associated with the second node (e.g., a SCG) by means of the CE transmitted from the second node and not transmitted from the first node (e.g., an MCG) may enable a radio resource management at the second node (e.g., the SCG) to determine the activity states of its secondary RLC entities, e.g., without signaling coordination or with minimum signaling coordination between the first node and the second node. For example, transmitting the CE from the second node may result in consistent activity states for the secondary RLC entities.

Same or further embodiments may enable to dynamically control a packet duplication using more than one node of a radio access network. The technique may be implemented for 3GPP Release <NUM>, in the absence of a timely coordination between the first node (e.g., a master node, MN) and the second node (e.g., a secondary node, SN) related to dynamic MAC CE. Herein, the coordination between the first node and the second node may mean that each node is aware of what MAC CE the other node indicates or transmits to the radio device.

Alternatively or in addition, an embodiment of the technique can provide a solution so that one node is appointed to be in control of MAC CE transmission to UE for RLC activation for PDCP duplication. Only the information about the activity state of RLC entities (also: RLC activation status) for the packet duplication from the node not in control needs to be reported to the controlling node.

Alternatively or in addition, an embodiment of the technique can provide a solution to control the CE when both the first node and the second node are allowed to transmit the CE.

Same or further embodiments of the technique also provide a solution that in some PDCP duplication configuration the CE can be transmitted (e.g., used for dynamic scheduling of the packet duplication) without coordination between the first node (e.g., the MN) and the second node (e.g., the SN), e.g., if it is clear which one of the first node and the second node controls the transmission of the CE.

The first method aspect may comprise, alternatively or in addition, any one of the features or steps referring to the first independent claim in the list.

As to a second method aspect, a method of assisting in transmitting a control element (CE) for selectively activating and deactivating one or more secondary radio link control (RLC) entities configured for packet duplication in a radio communication between a radio device and a radio access network (RAN) is provided. The RAN comprises a first node and a second node. The first node comprises a primary RLC entity configured for the packet duplication and the second node comprises at least one of the one or more secondary RLC entities. The method comprises or initiates sending assistance information to one of the first node and the second node, which transmits the CE to the radio device. The CE is indicative of an activity state of each of the one or more secondary RLC entities configured for the packet duplication depending on the assistance information.

The second method aspect may comprise, alternatively or in addition, any one of the features or steps referring to the second independent claim in the list.

In any aspect, the technique may be implemented for handling inter-node coordination for packet duplication, preferably for PDCP duplication.

The sending of the control message and/or the assistance information from one of the first and second nodes may be received by the other one of the first and second nodes. While the technique is described herein for one second node, the technique may be implemented for more than one second node. For example, each of the second nodes may comprise secondary RLC entities configured for the packet duplication.

The first method aspect may be performed at or by the second node and/or the controlling node.

The second method aspect may be performed at or by the first node and/or the non-controlling node.

Any one of the first and second nodes may be a base station of the RAN. Any one of the first and second nodes may form, or may be part of, the RAN, e.g., according to the Third Generation Partnership Project (3GPP) or according to the standard family IEEE <NUM> (Wi-Fi). The first and second method aspects may be performed by one or more embodiments of the nodes in the RAN. The RAN may comprise one or more base stations, e.g., acting as the first and second nodes.

The radio device may be a 3GPP user equipment (UE) or a Wi-Fi station (STA). The radio device may be a mobile or portable station, a device for machine-type communication (MTC), a device for narrowband Internet of Things (NB-loT) or a combination thereof. Examples for the UE and the mobile station include a mobile phone, a tablet computer and a self-driving vehicle. Examples for the portable station include a laptop computer and a television set. Examples for the MTC device or the NB-loT device include robots, sensors and/or actuators, e.g., in manufacturing, automotive communication and home automation. The MTC device or the NB-loT device may be implemented in a manufacturing plant, household appliances and consumer electronics.

Any of the radio devices may be wirelessly connected or connectable (e.g., according to a radio resource control, RRC, state or active mode) with any of the first and second nodes, e.g., with the first node using the primary RLC entity.

The base station may encompass any station that is configured to provide radio access to any of the radio devices. The base stations may also be referred to as transmission and reception point (TRP), radio access node or access point (AP). The base station or one of the radio devices functioning as a gateway (e.g., between the radio network and the RAN and/or the Internet) may provide a data link to a host computer providing the first and/or second data. Examples for the base stations may include a <NUM> base station or Node B, <NUM> base station or eNodeB, a <NUM> base station or gNodeB, a Wi-Fi AP and a network controller (e.g., according to Bluetooth, ZigBee or Z-Wave).

The RAN may be implemented according to the Global System for Mobile Communications (GSM), the Universal Mobile Telecommunications System (UMTS), 3GPP Long Term Evolution (LTE) and/or 3GPP New Radio (NR).

Any aspect of the technique may be implemented on a Physical Layer (PHY), a Medium Access Control (MAC) layer, a Radio Link Control (RLC) layer and/or a Radio Resource Control (RRC) layer of a protocol stack for the radio communication. Herein, the PDCP layer, the RLC layer, the MAC layer and the PHY layer are also briefly referred to by PDCP, RLC, MAC and PHY, respectively.

For example, the MAC layer may be implemented according to or based on the 3GPP document TS <NUM> (e.g., for Release <NUM>). Alternatively or in addition, the RRC layer may be implemented according to or based on the 3GPP document TS <NUM> (e.g., for Release <NUM>). Alternatively or in addition, the PHY layer may be implemented according to or based on the 3GPP document TS <NUM> (e.g., for Release <NUM>) and/or the 3GPP document TS <NUM> (e.g., for Release <NUM>).

Alternatively or in addition, the technique may be implemented in the first and/or second node as a Layer <NUM> module or MAC entity and/or a Layer <NUM> module or PDCP entity.

As to another aspect, a computer program product is provided. The computer program product comprises program code portions for performing any one of the steps of the method aspects disclosed herein when the computer program product is executed by one or more computing devices. The computer program product may be stored on a computer-readable recording medium. The computer program product may also be provided for download, e.g., via the radio network, the RAN, the Internet and/or the host computer. Alternatively, or in addition, the method may be encoded in a Field-Programmable Gate Array (FPGA) and/or an Application-Specific Integrated Circuit (ASIC), or the functionality may be provided for download by means of a hardware description language.

As to a further first device aspect, a controlling node (e.g., a base station) is provided. The controlling node is configured to perform the first method aspect.

As to a further second device aspect, a non-controlling node (e.g., a base station) is provided. The non-controlling node is configured to perform the second method aspect.

The UE comprises a radio interface and processing circuitry, which is configured to communicate with each of the first node and the second node.

The communication system may further include the UE. Alternatively, or in addition, the cellular network may further include one or more base stations configured for radio communication with the UE and/or to provide a data link between the UE and the host computer using the first and/or second method aspects.

The processing circuitry of the host computer may be configured to execute a host application, thereby providing the user data and/or any host computer functionality described herein. Alternatively, or in addition, the processing circuitry of the UE may be configured to execute a client application associated with the host application.

Further details of embodiments of the technique are described with reference to the enclosed drawings, wherein:.

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as a specific network environment in order to provide a thorough understanding of the technique disclosed herein. It will be apparent to one skilled in the art that the technique may be practiced in other embodiments that depart from these specific details. Moreover, while the following embodiments are primarily described for a 3GPP New Radio (NR) or <NUM> implementation, it is readily apparent that the technique described herein may also be implemented for any other radio communication technique, including a Wireless Local Area Network (WLAN) implementation according to the standard family IEEE <NUM>, 3GPP LTE (e.g., LTE-Advanced or a related radio access technique such as MulteFire).

Moreover, those skilled in the art will appreciate that the functions, steps, units and modules explained herein may be implemented using software functioning in conjunction with a programmed microprocessor, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), a Digital Signal Processor (DSP) or a general purpose computer, e.g., including an Advanced RISC Machine (ARM). It will also be appreciated that, while the following embodiments are primarily described in context with methods and devices, the invention may also be embodied in a computer program product as well as in a system comprising at least one computer processor and memory coupled to the at least one processor, wherein the memory is encoded with one or more programs that may perform the functions and steps or implement the units and modules disclosed herein.

<FIG> schematically illustrates a block diagram of an embodiment of a device for transmitting a control element (CE) for selectively activating and deactivating one or more secondary radio link control (RLC) entities configured for packet duplication in a radio communication between a radio device and a radio access network (RAN). The device is generically referred to by reference sign <NUM>.

The RAN comprises a first node and a second node, wherein the first node comprises a primary RLC entity configured for the packet duplication and the second node comprises at least one of the one or more secondary RLC entities.

The device <NUM> comprises a transmitting module <NUM> that transmits the CE from the RAN to the radio device, wherein the CE is indicative of an activity state of each of the one or more secondary RLC entities configured for the packet duplication.

Optionally, the device <NUM> comprises a determining module <NUM> that determines which of the one or more secondary RLC entities is to be activated or deactivated.

Any of the modules of the device <NUM> may be implemented by units configured to provide the corresponding functionality.

The device <NUM> may also be referred to as, or may be embodied by, a controlling node among the first node and the second node. The other one among the first node and the second node may be referred to as a non-controlling node. The controlling node <NUM> and the non-controlling node may be in communication, e.g., at least for exchanging the control message and/or the assistance information. The non-controlling node may be embodied by the device <NUM>.

<FIG> schematically illustrates a block diagram of an embodiment of a device for assisting in transmitting a control element (CE) for selectively activating and deactivating one or more secondary radio link control (RLC) entities configured for packet duplication in a radio communication between a radio device and a radio access network (RAN). The device is generically referred to by reference sign <NUM>.

The device <NUM> comprises a sending module <NUM> that sends assistance information to one of the first node and the second node, which transmits the CE to the radio device, wherein the CE is indicative of an activity state of each of the one or more secondary RLC entities configured for the packet duplication depending on the assistance information.

Optionally, the device <NUM> comprises a determining module <NUM> that determines a preference as to which of the one or more secondary RLC entities is to be activated or deactivated.

The device <NUM> may also be referred to as, or may be embodied by, a non-controlling node among the first node and the second node. The other one among the first node and the second node may be referred to as a controlling node. , the one of the first node and the second node, which transmits the CE to the radio device, may be the controlling node. The non-controlling node <NUM> and the controlling node may be in communication, e.g., at least for exchanging the control message and/or the assistance information. The controlling node may be embodied by the device <NUM>.

<FIG> shows an example flowchart for a method <NUM> of transmitting a control element (CE) for selectively activating and deactivating one or more secondary radio link control (RLC) entities configured for packet duplication in a radio communication between a radio device and a radio access network (RAN).

In a step <NUM> of the method <NUM>, the CE is transmitted from the RAN to the radio device, wherein the CE is indicative of an activity state of each of the one or more secondary RLC entities configured for the packet duplication.

Optionally, a step <NUM> of the method <NUM> determines which of the one or more secondary RLC entities is to be activated or deactivated prior to the transmission <NUM>.

The method <NUM> may be performed by the device <NUM>. For example, the modules <NUM> and <NUM> may perform the steps <NUM> and <NUM>, respectively.

<FIG> shows an example flowchart for a method <NUM> of assisting in transmitting a control element (CE) for selectively activating and deactivating one or more secondary radio link control (RLC) entities configured for packet duplication in a radio communication between a radio device and a radio access network (RAN).

In a step <NUM> of the method <NUM>, assistance information is sent to one of the first node and the second node, which transmits the CE to the radio device, wherein the CE is indicative of an activity state of each of the one or more secondary RLC entities configured for the packet duplication depending on the assistance information.

Optionally, a step <NUM> of the method <NUM> determines a preference as to which of the one or more secondary RLC entities is to be activated or deactivated prior to the sending <NUM>.

In any aspect, a control message may be exchanged between the first node and the second node, the control message being indicative of which one of the first node and the second node is to perform the step of transmitting the CE to the radio device, i.e., which one of the first node and the second node is the controlling node <NUM>.

The technique may be applied to uplink (UL) and/or downlink (DL).

Each of the controlling node <NUM> and non-controlling node <NUM> may be a base station or radio node of the RAN.

Herein, any radio device (e.g., the radio device) may be a mobile or portable station and/or any radio device wirelessly connectable to a base station or RAN, or to another radio device. For example, the radio device may be a user equipment (UE), a device for machine-type communication (MTC) or a device for (e.g., narrowband) Internet of Things (IoT). Two or more radio devices may be configured to wirelessly connect to each other, e.g., in an ad hoc radio network or via a 3GPP SL connection. Furthermore, any base station may be a station providing radio access, may be part of a radio access network (RAN) and/or may be a node connected to the RAN for controlling the radio access. For example, the base station may be an access point, for example a Wi-Fi access point.

The CE <NUM> may be transmitted from one of the first node and the second node.

The CE <NUM> may be transmitted from only one of the first node and the second node. The node transmitting the CE may also be referred to as the controlling node or the one of the first node and the second node. The other node not transmitting the CE may also be referred to as the non-controlling node or the other one of the first node and the second node.

The method <NUM> may further comprise or initiate exchanging a control message <NUM> between the first node and the second node, the control message <NUM> being indicative of which one of the first node and the second node is to perform the step of transmitting <NUM> the CE <NUM> to the radio device.

The method <NUM> may be performed by the second node.

The CE <NUM> may be transmitted from the second node to the radio device.

The second node may comprise all of the secondary RLC entities.

The second node may determine the activity state of the secondary RLC entities without additional information from the first node.

The method <NUM> further comprises or initiate a step of sending a control message <NUM> from the second node to the first node or receiving a control message <NUM> from the first node at the second node. The control message <NUM> may trigger the second node to transmit <NUM> the CE <NUM> to the radio device.

The CE may be transmitted from the second node to the radio device in response to the control message.

Alternatively or in addition, the method <NUM> may further comprise or initiate a step of sending a control message <NUM> from the second node to the first node or receiving a control message <NUM> from the first node at the second node. The control message <NUM> may prevent the first node from transmitting the CE <NUM> to the radio device.

Each of the first node and the second node may comprise a central unit (CU) and a distributed unit (DU).

The DU of the first node may comprise the primary RLC entity. Alternatively or in addition, the DU of the second node may comprise the at least one of the one or more secondary RLC entities.

Each of the DUs may comprise a medium access control (MAC) layer that is configured for transmitting the CE.

The first node may comprise a packet data convergence protocol (PDCP) entity.

The PDCP entity may be an aggregation point of the packet duplication.

The packet duplication may be a PDCP duplication. The PDCP entity may perform the packet duplication. Alternatively or in addition, the PDCP entity may split the DRB between the first node and the second node.

The method may be performed by at least one of the CU of the second node and the DU of the second node.

The control message <NUM> may be sent from the CU of the second node to the CU of the first node or received from the CU of the first node at the CU of the second node.

The control message <NUM> may be forwarded from the CU of the second node to the DU of the second node.

The DU of the second node, optionally a medium access control (MAC) layer of the second node, may transmit <NUM> the CE <NUM> to the radio device in response to the control message <NUM>.

A copy of the control message <NUM> may be sent from the CU of the first node to the DU of the first node.

The DU of the first node, optionally a MAC layer of the first node, may refrain from transmitting the CE <NUM> in response to the copy of the control message <NUM>.

The control message <NUM> may be sent or received according to an application protocol and/or on an Xn interface between the first node and the second node.

The control message may comprise an Information Element (IE) for controlling (e.g., coordinating) the transmission of the CE. The control message may be implemented as a MAC CE control IE.

The control message <NUM> may be indicative of exclusive control for the node receiving the control message as to the determining <NUM> of the activity state of the secondary RLC entities and/or as to the transmitting <NUM> of the CE. Alternatively or in addition, the control message <NUM> may be indicative of no control for the node receiving the control message as to the determining <NUM> of the activity state of the secondary RLC entities and/or as to the transmitting <NUM> of the CE. Alternatively or in addition, the control message <NUM> may be indicative of direct control for the node receiving the control message as to the determining <NUM> of the activity state of the secondary RLC entities based on received assistance information and/or exclusive control as to the transmitting <NUM> of the CE. Alternatively or in addition, the control message <NUM> may be indicative of indirect control for the node receiving the control message as to the determining <NUM> of the activity state of the secondary RLC entities based on sent assistance information and/or no control as to the transmitting <NUM> of the CE.

The activity state indicated by the CE for each of the one or more secondary RLC entities may comprise either activating or deactivating the respective one of the one or more secondary RLC entities.

The CE may be a Duplication RLC Activation/Deactivation MAC CE, e.g., according to the 3GPP document TS <NUM>, version <NUM>. <NUM>, clause <NUM>.

The method <NUM> may further comprise or initiate receiving assistance information from the first node at the second node. The determination may depend on the assistance information.

The radio communication between the radio device and the RAN may comprise a data radio bearer (DRB). The primary RLC entity and the one or more secondary RLC entities may be configured for the packet duplication of the DRB.

The radio communication may comprise a DRB. The method <NUM> may further comprise or initiate transmitting, to the radio device, an initial control message indicative of activating the packet duplication for the DRB.

The initial control message for activating the packet duplication may be a Duplication Activation/Deactivation MAC CE, e.g., according to the 3GPP document TS <NUM>, version <NUM>. <NUM>, clause <NUM>. Alternatively or in addition, the initial control message may comprise radio resource control (RRC) signaling.

Each of the RLC entities may be associated with a different carrier and/or a different cell and/or a different logical channel and/or a different RLC path.

The RLC path may also be referred to as leg or route.

One of the first node and the second node may be a master node (MN) comprising a radio resource control (RRC) layer. The other one of the first node and the second node may be a secondary node (SN). The method <NUM> may comprise transmitting, to the radio device, or receiving, from the radio device, RRC signaling for at least one of establishment, configuration, maintenance, and release of a data radio bearer of the packet duplication.

The MN may provide radio access to the radio device in a master cell group (MCG). The SN may provide radio access to the radio device in a secondary cell group (SCG).

The first node may comprise a packet data convergence protocol (PDCP) entity. The PDCP entity may be an aggregation point of the packet duplication.

The PDCP entity may perform the packet duplication and/or the splitting of the DRB between the first node and the second node.

The first node may comprise a packet data convergence protocol (PDCP) entity. The method <NUM> may further comprise or initiate a step of determining a number of the secondary RLC entities configured for the packet duplication. Alternatively or in addition, the method <NUM> may further comprise or initiate a step of transmitting, to the second node, an initial control message indicative of activating the packet duplication and/or a number of the at least one secondary RLC entity at the second node and/or an initial state of the activity state for each of the at least one secondary RLC entity. Alternatively or in addition, the method <NUM> may further comprise or initiate a step of performing the packet duplication by the PDCP entity.

Herein, the expression "packet duplication", "duplicated transmission" and "dual connectivity" (DC) may encompass a "packet multiplication", a "multiplicated transmission" and a "multi-connectivity" (MC), respectively.

The radio communication may comprise at least one of a downlink from the RAN to the radio device and an uplink from the radio device to the RAN.

The packet duplication may be based on at least one of dual connectivity (DC) and carrier aggregation (CA).

One or two secondary RLC entities at the first node may be configured for the packet duplication using CA. One, two or three secondary RLC entities at the second node may be configured for the packet duplication using DC.

The CE may be a medium access control (MAC) CE.

The MAC CE may be indicative of the activity state of each of the RLC entities configured for the packet duplication other than the primary RLC entity.

The CE may be indicative of the activity state of each of <NUM> secondary RLC entities or up to <NUM> secondary RLC entities.

The CE may comprise a bit field that is sized to indicate the activity state of each of <NUM> secondary RLC entities or up to <NUM> secondary RLC entities. The CE may comprise an octet. A portion of the CE (e.g., <NUM> bits of the octet) may be indicative of an identifier of the DRB of the packet duplication.

The first node may further comprise at least one of the one or more secondary RLC entities. The method <NUM> may further comprise or initiate a step of exchanging a control message between the first node to the second node. The control message may be indicative of which one of the first node and the second node is to perform the step of transmitting <NUM> the CE to the radio device.

The first node may further comprise at least one of the one or more secondary RLC entities. The method <NUM> may further comprise or initiate a step of determining which one of the first node and the second node is to perform the step of transmitting <NUM> the CE to the radio device. The determination may be based on a condition.

The condition may require that the one of the first node and the second node, which comprises the PDCP entity for the packet duplication, performs the step of transmitting <NUM>.

The condition may require that the one of the first node and the second node, which comprises more RLC entities configured for the packet duplication than the other one, performs the step of transmitting <NUM>.

The packet duplication may be based on a split bearer. The condition may require that the first node comprising the primary RLC entity performs the step of transmitting <NUM>.

The one of the first node and the second node, which performs the step of transmitting <NUM>, may perform the step of determining <NUM> which of the one or more secondary RLC entities is to be activated or deactivated.

The method <NUM> may further comprise or initiate a step of receiving assistance information from the other one of the first node and the second node, which does not perform the step of transmitting <NUM>, wherein the determination <NUM> may depend on the assistance information.

The assistance information may be indicative of a preference of the other node as to which of the one or more secondary RLC entities at the other node is to be activated or deactivated.

The assistance information may be indicative of the activity state, or a preference of the activity state, of at least one or each of the RLC entities configured for the packet duplication at the other one of the first node and the second node. Optionally the assistance information may be based on a link quality of the at least one or each of the RLC entities configured for the packet duplication at the other one of the first node and the second node.

The other one of the first node and the second node may indicate the activation or the preference of activating a secondary RLC entity at the other one of the first node and the second node, e.g., responsive to a reduction of the link quality of an active (e.g., primary or secondary) RLC entity at the other one of the first node and the second node. The one of the first node and the second node may activate the secondary RLC entity according to the preference indicated in the assistance information and/or may deactivate the active (e.g., primary or secondary) RLC entity in response to the reduction in the link quality.

The assistance information may be indicative of a link quality of at least one or each of the RLC entities configured for the packet duplication at the other one of the first node and the second node.

Herein, the link quality of any RLC entity may be the link quality of a radio link associated with said RLC entity.

The link quality may comprise at least one of: a channel state estimate; a channel quality indicator (CQI); a reference signal received power (RSRP) reported by the radio device; a reference signal received quality (RSRQ) reported by the radio device; a hybrid automatic repeat request (HARQ) failure rate; a rate of RLC retransmissions and/or retransmission failures; a latency and/or reliability measured for the data radio bearer or logical channel associated with the respective RLC entity; a load status; a number of connected radio devices; a number of used sub-bands used; and a QoS requirement associated with the packet duplication.

The one of the first node and the second node may perform the step of transmitting <NUM> responsive to determining a change in the activity state of at least one of the secondary RLC entities at the one of the first node and the second node.

The method <NUM> may be performed by the first node.

The method <NUM> may further comprise any one of the steps of the method <NUM>, or any step corresponding thereto.

The <FIG> schematically illustrate DC and CA, respectively.

<FIG> schematically illustrates a first embodiment of a RAN <NUM> performing packet duplication <NUM> in an embodiment of the first node <NUM> or <NUM> of the RAN <NUM> (e.g., a master node of the RAN) providing multi-connectivity (MC), e.g., dual connectivity (DC), to a radio device <NUM> (e.g., a UE). A Master Cell Group (MCG) of the RAN (e.g., a group of serving cells associated with the master access node) and at least one Secondary Cell Group (SCG) of the RAN (e.g., a group of serving cells associated with a secondary access node) provide the MC to the radio device <NUM> though a primary leg <NUM> using a primary RLC entity <NUM> and a secondary leg <NUM> using a secondary RLC entity <NUM>. The first embodiment of the RAN <NUM> may be applicable to LTE and/or NR (which is illustrated).

<FIG> schematically illustrates a second embodiment of a RAN <NUM> performing packet duplication <NUM> in an embodiment of the first node <NUM> or <NUM> of the RAN <NUM> providing carrier aggregation (CA) to a radio device <NUM> (e.g., a UE) though a primary leg <NUM> using a primary RLC entity <NUM> and a secondary leg <NUM> using a secondary RLC entity <NUM>. The second embodiment of the RAN <NUM> may be combined with the first embodiment or may be extended by the first embodiment. The second embodiment of the RAN <NUM> may be applicable to LTE and/or NR (which is illustrated).

<FIG> schematically illustrates a third embodiment of the RAN <NUM>. The third embodiment may be combined or interchanged with the first and/or second embodiment. Same reference signs may indicate equivalent or interchangeable features.

To support PDCP duplication <NUM> in CA, a secondary RLC entity <NUM> is configured for a radio bearer used in support of the packet duplication <NUM> realized in the context of a single radio technology (i.e. non-split radio bearer operation using either NR or LTE). See <FIG> wherein, for CA-based duplication, the same PDCP PDU <NUM> is sent using RLC_0 <NUM> and RLC_1 <NUM>, wherein each PDCP PDU is required (through configuration restrictions) to be transmitted using a different carrier for the primary leg <NUM> and the secondary legs <NUM> to <NUM>. To ensure the diversity gain, restrictions can be defined for the logical channels associated with these RLC entities <NUM>, <NUM>, <NUM> and <NUM>, so that transmissions of each RLC entity are only allowed on a configured carrier (primary cell for <NUM> or secondary cells for <NUM> to <NUM>).

Furthermore, the RAN <NUM> (e.g., a node <NUM> or <NUM> of the RAN <NUM> serving the radio device) may configure the PDCP duplication. An initial control message for activating (or deactivating) may be a medium access control (MAC) control element (CE), e.g., specified for controlling a configuration at the radio device to receive the PDCP duplication. The PDCP duplication may be controlled to allow using PDCP duplication as a "scheduling tool", i.e. allowing to selectively activate and deactivate the PDCP duplication, e.g., dynamically by the scheduler. Herein, "dynamically" may refer to a configuration that is controlled by the scheduler and/or controlled by means of the MAC CE. The PDCP duplication may be controlled to activate PDCP duplication only when necessary.

The initial control message for activating the packet duplication for a data radio bearer (DRB) may be a MAC CE according to 3GPP Release <NUM> and/or the 3GPP document TS <NUM>, version <NUM>. <NUM>, e.g. clause <NUM>.

Alternatively or in addition, the initial control message for activating the packet duplication may be a MAC CE for selectively activating and deactivating the PDCP duplication. The MAC CE may have a fixed size and/or may comprise a single octet containing eight D-fields (e.g., eight bits), e.g., one field for one data radio bearer (DRB). Each D-field indicates the activity status (briefly: status) of the PDCP duplication of (e.g., dedicated) Data Radio Bearer (DRB) i being either activation or deactivation, optionally wherein i is the ascending order of the DRB ID among the DRBs configured with PDCP duplication and with at least one RLC entity associated with this MAC entity. In other words, the MAC CE indicates only the RLC entity within the MAC entity in which the MAC CE is received.

In 3GPP Release <NUM>, PDCP duplication is enhanced to support more than two radio links, e.g. up to four radio links. PDCP duplication for MC (also referred to as MC-based duplication, e.g., for DC) and PDCP duplication for CA (also referred to as CA-based duplication) may be used together, e.g., as illustrated in <FIG>. Alternatively or in addition, the CA-based duplication may use more than two carriers, e.g., as illustrated by the doted branch in the MAC below RLC_2.

<FIG> schematically illustrates a third embodiment of the RAN <NUM> for PDCP duplication in 3GPP Release <NUM> with up to <NUM> copies (e.g., RLC entities).

In the third embodiment, e.g., as depicted in <FIG>, four radio links (i.e., four RLC entities <NUM> to <NUM>) are configured in a way that MC-based duplication (i.e., the MCG and the at least one SCG) is configured and combined with CA-based duplication in each of the MCG (i.e., route <NUM> of leg <NUM> and route <NUM> of leg <NUM>) and the SCG (i.e. route <NUM> of leg <NUM> and route <NUM> of leg <NUM>).

When PDCP duplication according to 3GPP Release <NUM> is configured, the RAN <NUM> (e.g., the first access node) provides a set of RLC entities, which will be associated to a PDCP entity. By means of RRC signaling, the RAN <NUM> (e.g., the first access node) may configure the activation status of the PDCP duplication and the activated RLC entities to which the PDCP of the radio device (e.g., UE) should deliver PDCP data PDUs (e.g., PDUs of the PDCP layer comprising data of the radio device).

The RAN <NUM> may dynamically control the activation state of the PDCP duplication and/or the activity state of the RLC entities configured for the PDCP duplication (i.e., the RLC entities used to deliver duplicates according to the PDCP duplication) by means of MAC CEs defined in the 3GPP document TS <NUM>, version <NUM>. <NUM>, in clauses <NUM>. <NUM> and <NUM>. <NUM>, respectively. The MAC CE defined in the 3GPP document TS <NUM>, version <NUM>. <NUM>, in clause <NUM>. <NUM>, allows to activate and deactivate any of the configured RLC entities (e.g., the secondary RLC entities), except for one of the RLC entities (e.g., the primary RLC entity).

The PDCP duplication state of the associated RLC entity may always be activated for a signaling radio bearer (SRB). Thus, the subject technique is preferably applied to a DRB.

<FIG> schematically illustrates a data structure of an embodiment of the CE <NUM>.

The CE <NUM> may be implemented by the 3GPP Release <NUM> Duplication RLC Activation/Deactivation MAC CE. The CE may have a fixed size and/or may comprise a single octet, e.g., defined as illustrated in <FIG> and/or according to the 3GPP document TS <NUM>, version <NUM>. <NUM>, clause <NUM>.

The DRB ID field indicates the identity of DRB for which the MAC CE applies. The length of the field is <NUM> bits. The RLC field indicates the activation/deactivation status of PDCP duplication for the RLC entity i, wherein i is ascending order of logical channel ID of secondary RLC entities in the order of MCG and SCG, for the DRB.

It is possible that an MCG indicates the activation/deactivation state of RLC entities for the SCG. The UE just follows the received MAC CE, even if the RLC field belongs to the other node.

In 3GPP Release <NUM>, in addition to MAC CE, the network can configure by RRC the activation/deactivation status of the RLC entities. This is controlled by the field duplicationState
<IMG>.

The field duplicationState indicates the initial uplink PDCP duplication state for the associated RLC entities. If set to true, the initial PDCP duplication state is activated for the associated RLC entity. The index for the indication is determined by ascending order of logical channel ID of all RLC entities other than the primary RLC entity indicated by primaryPath in the order of MCG and SCG, e.g. according to the 3GPP document TS <NUM>, version <NUM>. If the number of associated RLC entities other than the primary RLC entity is two, UE ignores the value in the largest index of this field.

The field splitSecondaryPath is a pointer to a secondary RLC entity to identify which of the multiple configured RLC entities shall be used to fallback to split bearer operation.

The MAC CE activates and deactivates any of the configured RLC entities except for one of the RLC entities. This RLC entity (i.e., the primary RLC entity) will be configured as the primary path. The primary path, like in 3GPP Release <NUM>, defines the RLC entity to which the UE's PDCP delivers PDCP Control PDUs. PDCP will also deliver PDCP Data PDUs to the RLC entity configured as the primary path.

When PDCP duplication is deactivated, the UE will fall back to its initial configuration. This means that the UE will fall back to 3GPP Release <NUM> DC, or to single carrier combined or not with CA. If the fallback is DC, the network should have provided in the RRC configuration the secondary RLC entity, among all RLC entities configured for PDCP duplication, which will be used in DC. The primary path will be the primary RLC entity in the fallback case.

In what follows, node means MCG/MN or SCG/SN. The nodes are involved in the PDCP duplication.

In one embodiment, one of the nodes controls the MAC CE transmission. This node is called the "MAC CE Controlling Node" or briefly "Controlling Node". The node not in control is called the "MAC CE Non-Controlling Node" or briefly "Non-Controlling Node".

In one follow-up embodiment, it is communicated between the MN and the SN which node is the Controlling Node.

The node hosting the PDCP entity decides how many RLC duplications (up to <NUM>) are used in the manner combining DC and CA, and the initial state of the RLC activation. It initiates the communication between the two nodes related to how to use the dynamic MAC CE.

Two cases of the configuration of the PDCP duplication are described.

In a case <NUM>, there is one primary RLC path in one node (first node) and up to <NUM> (e.g., secondary) RLC paths in another node (second node). The node hosting the PDCP entity (briefly: the PDCP-hosting node, e.g., the first node) indicates to the first node, or it is determined without further coordination by the first node, that the first node is "the Non-controlling node", i.e., it does not send the dynamic MAC CE to the UE (and/or does not provide feedback as to RLC activation or deactivation). The PDCP-hosting node (e.g., the first node) indicates, e.g., at the same time, to the second node that the second node is "the controlling node" and it is in full control, i.e., it does not need any additional information from the other (e.g., the first) node. This solution works as the primary RLC path is always activated. If the rest of the RLC paths (e.g., the up to <NUM> secondary paths) are controlled by the second node, the second node may make decisions on the dynamic MAC CE.

An example to implement the case <NUM> is either via Control Plane, XnAP and F1AP, or via NR User Plane, by introducing an Indication, e.g., "MAC CE Control Information" IE. This IE can indicate if the node hosting the RLC entity is the Non-Controlling Node <NUM> or a Full Controlling Node <NUM> (or controlling node <NUM>). It is further specified that the Non-Controlling Node <NUM> means that the node hosting the RLC entity should not transmit MAC CE, and it does not need to provide any assistance information for the MAC CE coordination. The "Full Controlling Node" (or controlling node <NUM>) means that the node hosting the RLC entity does not need any assistance information from other nodes when making the MAC CE decision. Refer to <FIG>.

In a case <NUM>, the primary RLC path is not the only RLC path hosted by one node. In this case, node coordination is needed. One node is appointed as the control node (or controlling node <NUM>), and it receives the coordination assistance information from the other node. The other node is appointed as no control node (or non-controlling node <NUM>), and it sends the assistance information to the control node (or controlling node <NUM>). The node receives the indication and can accept or reject the role in the response. The role is negotiated between two nodes or appointed by the PDCP hosting node. The PDCP hosting node thus triggers the "No Control node" (or non-controlling node <NUM>) to report information related to MAC CE and forwards the information to the controlling node to process.

In another follow-up embodiment to Case <NUM> in which the Controlling Node is determined by some conditions, the node hosting the primary RLC path is the Controlling Node. The primary RLC path is configured by the field primaryPath in the IE PDCP-Config in RRC. Another example is that the Node has the most configured RLC entities for PDCP duplication is the Controlling Node. In another example, if the bearer is a split bearer and both the primary path and split secondary path are configured in RRC, then the node hosting the primary path is the Control Node (or controlling node <NUM>).

The MAC CE controlling node is the only node that is in control of sending the MAC CE to the UE, while the non-controlling node does not send MAC CE.

The MAC CE controlling node requests the non-controlling node to report. The MAC CE controlling node makes the decision and sends the MAC CE containing the activation status of all RLC entities to the UE.

The non-controlling node <NUM> may base its decision on activating/deactivating RLC entities for activation, or indicating RLC entities for activating/deactivating to the controlling node based on the following criteria.

A first criterion comprises channel state estimates and/or CQI, and/or measurement reports indicative of RSRP and/or RSRQ, and/or HARQ failure rates, and/or RLC retransmissions and/or retransmission failures. A second criterion comprises measured latency and reliability for the radio bearer associated with the RLC entity. A third criterion comprises a load status, i.e. number of UEs <NUM> connected, sub-bands used, or estimates on future use. A fourth criterion comprises QoS requirements, e.g., latency and/or reliability communicated for the radio bearer associated with the RLC entities.

The triggering of the report can be done, e.g., by triggering the polling of the non-controlling node. The non-controlling node, when it needs to change the activation status of its RLC entities, sends the part of MAC CE related to the RLC entities under its control to the MAC CE controlling node. The MAC CE controlling node makes the decision and sends the MAC CE for all the RLC entities to the UE.

In one variant, instead of sending the activation status of the RLC entities, the non-controlling node indicates to the Control Node (or controlling node <NUM>) the preference of the activation/deactivation of the RLC entities. This can be due to, e.g., the radio quality. One example is that if the radio quality of the serving cells for the activated RLC entities drops significantly, then the non-controlling node can indicate to the controlling node that it would be preferable to enable other RLC entities to fulfil the targeted reliability requirement. However, the controlling node makes the final decision in that it can choose to deactivate the RLC entities associated with the cell of a bad radio quality instead of activating new RLC entities in the non-controlling node. In another example, if there have been multiple RLC entities activated in the non-controlling node, the non-controlling node can indicate to deactivate one of them if both RLC entities have been sending/receiving packets with a very success probability.

The non-controlling node could also indicate to the controlling node and/or report to the control node (or controlling node <NUM>) the assistant information, so that the control node (or controlling node <NUM>) makes a final MAC CE decision.

One example of the implementation is via XnAP, the nodes communicate and determine which node is the MAC CE controlling node. The MAC CE controlling node thus triggers the reporting of the MAC CE from the non-controlling node, by periodic reporting, or reporting upon the change. The reporting could be implemented via UP data frame protocol when the Uplink Data frame is sent, or via XnAP.

The MAC CE controlling Node determines when to send the MAC CE to the UE, e.g. when there is a change for its own RLC entities, or there is a change for the RLC entities controlled by the non-controlling node.

The MAC CE controlling Node could give away the control to another node, e.g. involved RLC entities are mostly controlled by the other node.

In one embodiment, after the MAC CE Controlling Node sends the MAC CE to the UE, it indicates to the non-controlling node the activation/deactivation status of all RLC entities. This indication is necessary, since the final decision on which RLC entities is activated/deactivated is made at the MAC CE controlling node and they can be different from what the Non-controlling Node has indicated to the MAC CE Controlling Node. In another embodiment, the MAC CE controlling Node indicates only the status of the RLC entities under the control or assistance of the non-controlling node <NUM>.

In yet another embodiment the other node indicates to the controlling node a preference of duplication activation of RLC entities hosted in the other node. The preference may be updated based on criteria listed above.

In addition to the MAC CE, the network can configure the activation/deactivation status of the RLC entities through RRC configuration. The above embodiments can be extended and applied to the case where the activation/deactivation status of the RLC entities are controlled by the RRC configuration. In one embodiment, the PDCP entity hosting node is the controlling node.

In another deployment scenario, the activation/deactivation status of the RLC entities is controlled jointly by MAC CE and RRC configuration. Since the MAC CE is sent in a faster time scale than the RRC configuration, the MAC CE controlling node is the node that finally determines the activation/deactivation of the RLC entities. All assistant information is collected at the MAC CE controlling node and the decision is forwarded to the entity that transmits the RRC configuration message.

<FIG> schematically illustrates a PDCP hosting node <NUM>, which may be a Master NG-RAN node (M-NG-RAN Node), as the non-controlling node. Furthermore, the example may be an example of case <NUM>.

The control message <NUM> is implemented as the "MAC CE Control IE" over the control plane, e.g., transmitted from the non-controlling node <NUM> to the controlling node <NUM>.

Each of the controlling node <NUM> and the non-controlling node <NUM> may be split into a centralized unit (CU) 100A and 200A, respectively, and a distributed unit 100B and 200B, respectively.

The control message may be exchanged between the CUs 100A and 100B.

<FIG> schematically illustrates the PDCP hosting node, which may be a Secondary NG-RAN node (S-NG-RAN node), as the non-controlling node <NUM>. The control message <NUM> is introduced to indicate how the MAC CE <NUM> should be used. The approach is similar to <FIG> (e.g., with the roles of master and secondary node interchanged). The control message <NUM> is implemented by a "MAC CE Control Information IE".

<FIG> schematically illustrates an example of implementing the control message <NUM>, e.g., as a MAC CE Control Information IE, preferably over the Control Plane (e.g., using XnAP and/or F1AP).

The control message <NUM> is indicative of at least two out of the four enumerated values. Enumerated value "full control" and "No control" are for the case <NUM>, so that one node would be in "full control", and the other node would be in "No control". Enumerated value "control and receive assistance info" and "no control and send assistance info" are for case <NUM>.

<FIG> shows a schematic block diagram for an embodiment of the device <NUM>. The device <NUM> comprises one or more processors <NUM> for performing the method <NUM> and memory <NUM> coupled to the processors <NUM>. For example, the memory <NUM> may be encoded with instructions that implement at least one of the modules <NUM> and <NUM>.

The one or more processors <NUM> may be a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, microcode and/or encoded logic operable to provide, either alone or in conjunction with other components of the device <NUM>, such as the memory <NUM>, base station functionality. For example, the one or more processors <NUM> may execute instructions stored in the memory <NUM>. Such functionality may include providing various features and steps discussed herein, including any of the benefits disclosed herein. The expression "the device being operative to perform an action" may denote the device <NUM> being configured to perform the action.

As schematically illustrated in <FIG>, the device <NUM> may be embodied by a controlling node <NUM>, e.g., functioning as a base station. The controlling node <NUM> comprises a radio interface <NUM> coupled to the device <NUM> for radio communication with one or more UEs.

As schematically illustrated in <FIG>, the device <NUM> may be embodied by a non-controlling node <NUM>, e.g., functioning as a base station. The non-controlling node <NUM> comprises a radio interface <NUM> coupled to the device <NUM> for radio communication with one or more UEs.

With reference to <FIG>, in accordance with an embodiment, a communication system <NUM> includes a telecommunication network <NUM>, such as a 3GPP-type cellular network, which comprises an access network <NUM>, such as a radio access network, and a core network <NUM>. The access network <NUM> comprises a plurality of base stations 1312a, 1312b, 1312c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 1313a, 1313b, 1313c. Each base station 1312a, 1312b, 1312c is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first user equipment (UE) <NUM> located in coverage area 1313c is configured to wirelessly connect to, or be paged by, the corresponding base station 1312c. A second UE <NUM> in coverage area 1313a is wirelessly connectable to the corresponding base station 1312a.

Any of the base stations <NUM> and the UEs <NUM>, <NUM> may embody the device <NUM>.

The communication system <NUM> of <FIG> as a whole enables connectivity between one of the connected UEs <NUM>, <NUM> and the host computer <NUM>. For example, a base station <NUM> need not be informed about the past routing of an incoming downlink communication with data originating from a host computer <NUM> to be forwarded (e.g., handed over) to a connected UE <NUM>.

By virtue of the method <NUM> being performed by any one of the base stations <NUM>, the performance of the OTT connection <NUM> can be improved, e.g., in terms of increased throughput and/or reduced latency.

Example implementations, in accordance with an embodiment of the UE, base station and host computer discussed in the preceding paragraphs, will now be described with reference to <FIG>. In providing the service to the remote user, the host application <NUM> may provide user data, which is transmitted using the OTT connection <NUM>. The user data may depend on the location of the UE <NUM>. The user data may comprise auxiliary information or precision advertisements (also: ads) delivered to the UE <NUM>. The location may be reported by the UE <NUM> to the host computer, e.g., using the OTT connection <NUM>, and/or by the base station <NUM>, e.g., using a connection <NUM>.

The connection <NUM> may be direct, or it may pass through a core network (not shown in <FIG>) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.

It is noted that the host computer <NUM>, base station <NUM> and UE <NUM> illustrated in <FIG> may be identical to the host computer <NUM>, one of the base stations 1312a, 1312b, 1312c and one of the UEs <NUM>, <NUM> of <FIG>, respectively. This is to say, the inner workings of these entities may be as shown in <FIG>, and, independently, the surrounding network topology may be that of <FIG>.

In <FIG>, the OTT connection <NUM> has been drawn abstractly to illustrate the communication between the host computer <NUM> and the UE <NUM> via the base station <NUM>, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

The wireless connection <NUM> between the UE <NUM> and the base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may reduce the latency and improve the data rate and thereby provide benefits such as better responsiveness and improved QoS.

A measurement procedure may be provided for the purpose of monitoring data rate, latency, QoS and other factors on which the one or more embodiments improve. The measurements may be implemented in that the software <NUM>, <NUM> causes messages to be transmitted, in particular empty or "dummy" messages, using the OTT connection <NUM> while it monitors propagation times, errors etc..

For simplicity of the present disclosure, only drawing references to <FIG> will be included in this paragraph.

For simplicity of the present disclosure, only drawing references to <FIG> will be included in this paragraph.

As has become apparent from above description, embodiments of the technique allow using a dynamic MAC CE, e.g., without signaling overloading. Alternatively or in addition, the activity state can be controlled more robustly.

Furthermore, in 3GPP Release <NUM>, there is no inter-node coordination, which means the MAC CE according to 3GPP Release <NUM> is not useful or could lead to activity states for secondary RLC entities that are inconsistent between the node comprising the secondary RLC entity and the radio device receiving the MAC CE. Embodiments of the technique can, at least for some PDCP duplication deployment, benefit from the dynamic MAC CE, e.g. already according to 3GPP Release <NUM>.

Any one of the embodiments may be implemented based on or as an extension of the 3GPP document TS <NUM>, version <NUM>. <NUM>; and/or the 3GPP document TS <NUM>, version <NUM>. <NUM>; and/or the 3GPP document TS <NUM>, version <NUM>.

Claim 1:
A method (<NUM>) of transmitting a control element, CE (<NUM>), for selectively activating and deactivating one or more secondary radio link control, RLC, entities (<NUM>; <NUM>; <NUM>) configured for packet duplication in a radio communication between a radio device (<NUM>) and a radio access network, RAN, the RAN comprising a first node (<NUM>; <NUM>) and a second node (<NUM>; <NUM>), wherein the first node (<NUM>; <NUM>) comprises a primary RLC entity (<NUM>) configured for the packet duplication and the second node (<NUM>; <NUM>) comprises at least one of the one or more secondary RLC entities (<NUM>; <NUM>; <NUM>), the method (<NUM>) characterised by:
exchanging a control message (<NUM>) between the first node (<NUM>; <NUM>) and the second node (<NUM>; <NUM>), the control message (<NUM>) being indicative of which one of the first node (<NUM>; <NUM>) and the second node (<NUM>; <NUM>) is to perform the step of transmitting (<NUM>) the CE (<NUM>) to the radio device (<NUM>); and
transmitting (<NUM>) the CE (<NUM>) from the RAN to the radio device (<NUM>),
wherein the CE (<NUM>) is indicative of an activity state of each of the one or more secondary RLC entities (<NUM>; <NUM>; <NUM>) configured for the packet duplication.