Patent Description:
The standardization organization Third Generation Partnership Project (3GPP) is currently in the process of specifying a new Radio Interface called <NUM> New Radio (<NUM> NR) as well as a Next Generation Packet Core Network (NG-CN or NGC). The <NUM> NR will have three main components: a <NUM> Access Network (<NUM>-AN), a <NUM> Core Network (5GC), and a User Equipment (UE). In order to facilitate the enablement of different data services and requirements, the elements of the 5GC, also called Network Functions, have been simplified with some of them being software based so that they could be adapted according to need. <CIT>, <CIT> and <CIT> are related prior art documents.

The following acronyms are used throughout the present disclosure:.

<FIG> illustrates a block diagram of an example wireless communication system <NUM> for transmitting and receiving wireless communication signals (e.g., OFDM/OFDMA signals) in accordance with some embodiments of the present solution. The system <NUM> may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system <NUM> can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment <NUM> of <FIG>, as described above.

To ensure ultra-reliable low latency communications (uRLLC) over <NUM> wireless network, packet duplication functionality at the packet data convergence protocol (PDCP) layer may be introduced in <NUM>. When duplication is configured for a dedicated radio bearer (DRB) with more than two radio link control (RLC) entities associated with the PDCP entity, the radio resource control (RRC) may inform the initial state of UL PDCP duplication (either activated or deactivated for per RLC entity) to a user equipment (UE). The transmitting PDCP entity at UE side can duplicate the PDCP protocol data unit (PDU) and submit the copy to each activated RLC entity indicated by the initial state information as soon as the DRB setup. However, without coordination between radio access network (RAN) nodes, the RAN network cannot configure initial state of UL PDCP duplication for each RLC entity for user equipment (UE). This may be because the RLC entities associated with the PDCP entity may be located at different RAN node, such as at a master node (MN) or a secondary node (SN) in the case of dual connectivity (DC) split bearer, or at different a distributed unit (DU) in the case of a CU-DU split architecture.

In 3GPP release <NUM>, the PDCP duplication activation or deactivation may be configured per DRB. Referring now to <FIG>, depicted is a block diagram of a system <NUM> for uplink packet duplication transmission. The system <NUM> may include a node (e.g., the RAN node) hosting PDCP <NUM>. When a DRB that is configured with UL PDCP duplication is added to a UE, the UE will establish two RLC entities in order to support the UL PDCP duplication, one RLC entity is primary RLC entity, and the other RLC entity is secondary RLC entity. The logical channel corresponding to the primary RLC entity 310A may be referred to as the primary logical channel 315A, and the logical channel corresponding to the secondary RLC entity 310B may be the secondary logical channel 315B.

Since the PDCP duplication activation or deactivation is configured for per DRB in R15, the RAN node hosting PDCP entity can directly sign the initial state of the UL PDCP duplication for this established DRB to UE through RRC message. As such, no coordination between RAN nodes may be involved. If the initial state of the UL PDCP duplication is activated for the DRB, the PDCP entity in UE may duplicate PDCP PDU and submit the duplicated PDUs to both RLC entities for initial data transmission. Otherwise, If the initial state of the UL PDCP duplication for the DRB is deactivated, the PDCP entity in UE may submit the PDCP PDU to the primary RLC entity.

In 3GPP release <NUM>, the PDCP duplication may support more than two RLC entities. Where there are one primary RLC entity and more than one secondary RLC entities 310B, the PDCP duplication activation/deactivation may be configured for per RLC entity 310A and 310B. The primary RLC entity 310A may be always activated. However, without coordination between RAN nodes, the RAN network cannot configure initial state of UL PDCP duplication for each RLC entity for UE. This may be because the RLC entities associated with the PDCP entity are located at different RAN node For example, at MN <NUM> in a MCG <NUM> and SN <NUM> in a SCG <NUM> in the case of DC split bearer (as shown in system <NUM> depicted in <FIG> and system <NUM> in <FIG>), or at different DU 610A and 610B communicatively coupled with a CU <NUM> hosting the PCDP in the case of CU DU split architecture (as shown in system <NUM> of <FIG>). In the examples, the logical channels may be supported via MAC1 425A and MAC2 425B.

There may be two solution to solve how to configure the initial state of UL duplication of RLC entities at different RAN nodes. The first solution may entail the node hosting PDCP signal sending the initial state of UL duplication to assisting node as detailed in conjunction with <FIG>. The second solution may involve an assisting node determine own initial state of UL duplication as detailed in conjunction with <FIG>.

Referring now to <FIG>, depicted is a communication diagram of a data flow <NUM> in a scenario of a node hosting a PDCP signal sending the initial state of uplink (UL) duplication to a MN terminated bearer as an assisting node. For the MN-terminated DRB to be setup under DC architecture as seen in data flow <NUM>, illustrated is how the node (e.g., gNB MN <NUM>) hosting PDCP (MN) signal send the initial state of UL duplication of RLC entities to assisting node (e.g., gNB SN <NUM>).

At <NUM>, for the MN terminated DRB to be setup, the MN node determines the following for the DRB: the location of primary RLC entity (at MN or SN), and the initial state of UL duplication (RLC activated or deactivated) of all secondary RLC entities.

At <NUM>, MN sends SN addition request message to the SN to setup DRB, including the following information for the MN terminated DRB: the information of the initial state of UL duplication of assisting node (which is used to indicate every secondary RLC entity at SN is activated or deactivated), and the information of the primary RLC indication (which is used to indicate whether the primary RLC entity is located at SN). The indication may be an explicit indication, such as true or false value, or an implicit indication, such as the number of secondary RLC entities at the assisting node or the number of secondary RLC entities at the host node combined with the number of total secondary RLC entities of the DRB. The assisting node can infer whether the primary RLC entity is located at the assisting node based on such number information.

At <NUM>, after receiving SN addition request message sent by MN, for the DRB to be setup, if the information of the primary RLC indication indicates the primary RLC entity is not at SN, the SN may apply and store initial state of all own RLC entities indicated by the information of the initial state of UL duplication of assisting node. Otherwise, if the primary RLC entity is at SN, the SN may apply and store initial state of own RLC entities excluding the primary RLC entity referred to as the primary logical channel of SCG. The primary RLC entity is always activated for UL duplication. The SN may send SN addition response to the MN.

At <NUM>, the MN may send RRC Reconfiguration message to UE, including initial state of UL duplication of all secondary RLCs in both MCG and SCG for the DRB. At <NUM>, the UE may send RRC Reconfiguration complete message to RAN network. At <NUM>, after the DRB has been established, the transmitting PDCP entity at UE side can duplicate the PDCP PDU and send the copy to each activated RLC entity indicated by the initial state of UL duplication configuration.

At <NUM>, after the configuration, the RAN network can dynamically control the PDCP UL duplication during the transmission. At <NUM>, the RAN node can send MAC CE to UE. The MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated (e.g., which of the RLC entities shall be used for UL duplicate transmission). The primary RLC entity cannot be deactivated. The UE applies the received MAC CE commands regardless of the origin UL duplication state.

Referring now to <FIG>, depicted is a communication diagram of a data flow <NUM> in a scenario of a node hosting a PDCP signal sending the initial state of UL duplication to a SN terminated split bearer as an assisting node. At <NUM>, the MN node send SN addition request message to the SN. At <NUM>, for the SN terminated DRB to be setup, the SN may determine the following for the DRB: the location of primary RLC entity (at MN or SN), and the initial state of UL duplication (RLC activated or deactivated) of all secondary RLC entities of the DRB.

At <NUM>, the SN may send SN addition response message to the MN, including the following information for the SN terminated DRB: the information of the initial state of UL duplication of assisting node (which is used to indicate every secondary RLC entity at MN is activated or deactivated), and the information of the primary RLC indication (which is used to indicate whether the primary RLC entity is located at MN). The indication may be an explicit indication, such as true or false value, or an implicit indication, such as the number of secondary RLC entities at the assisting node or the number of secondary RLC entities at the host node combined with the number of total secondary RLC entities of the DRB. The assisting node can infer whether the primary RLC entity is located at the assisting node based on such number information.

After receiving SN addition response message sent by SN, for the DRB to be setup, if the information of the primary RLC indication indicates the primary RLC entity is not at MN, the MN may apply and store initial state of all own RLC entities indicated by the information of the initial state of UL duplication of assisting node. Otherwise, if the primary RLC entity is at MN, the MN may apply and store initial state of own RLC entities excluding the primary RLC entity referred to as the primary logical channel of MCG. The primary RLC entity is always activated for UL duplication.

At <NUM>, the SN may send RRC Reconfiguration message to UE, including initial state of UL duplication of all secondary RLCs in both MCG and SCG for the DRB. At <NUM>, the UE may send RRC Reconfiguration complete message to RAN network. At <NUM>, after the DRB has been established, the transmitting PDCP entity at UE side can duplicate the PDCP PDU and submit the copy to each activated RLC entity indicated by the initial state of UL duplication configuration. At <NUM>, after the configuration, the RAN network can dynamically control the PDCP UL duplication during the transmission.

At <NUM>, the RAN node can send MAC CE to UE. The MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated (e.g., which of the RLC entities shall be used for UL duplicate transmission). The primary RLC entity cannot be deactivated. The UE may apply the received MAC CE commands regardless of the origin UL duplication state.

Referring now to <FIG>, depicted is a communication diagram of a data flow <NUM> in a scenario of a node hosting a PDCP signal sending the initial state of UL duplication to CU-DU split entities as an assisting node. At <NUM>, for the DRB to be setup at more than one DUs, the CU may determine the following for the DRB: the location of primary RLC entity (which DU), and the initial state of UL duplication (RLC activated or deactivated) of all secondary RLC entities of the DRB.

At <NUM>, the CU may send UE context setup message to the different DU to setup UE context of the DRB, including the following information for the DRB: the information of the initial state of UL duplication of assisting node (which is used to indicate every secondary RLC entity at this DU is activated or deactivated), and the information of the primary RLC indication (which is used to indicate whether the primary RLC entity is located at this DU). The indication may be an explicit indication, such as true or false value, or an implicit indication, such as the number of secondary RLC entities at the assisting node or the number of secondary RLC entities at the host node combined with the number of total secondary RLC entities of the DRB. The assisting node can infer whether the primary RLC entity is located at the assisting node based on such number information.

At <NUM>, after receiving UE context setup message sent by CU, for the DRB to be setup, if the information of the primary RLC indication indicates the primary RLC entity is not at this DU, the DU may apply and store initial state of all own RLC entities indicated by the information of the initial state of UL duplication of assisting node. Otherwise, if the primary RLC entity is at this DU, the DU may apply and store initial state of own RLC entities excluding the primary RLC entity referred to as the primary logical channel. The primary RLC entity may be always activated for UL duplication. The DU may send UE context setup response to the CU.

At <NUM>, the RAN node may send RRC Reconfiguration message to UE, including initial state of UL duplication of all secondary RLCs in DU1 and DU2 for the DRB. At <NUM>, the UE send RRC Reconfiguration complete message to RAN network. At <NUM>, after the DRB has been established, the transmitting PDCP entity at UE side can duplicate the PDCP PDU and submit the copy to each activated RLC entity indicated by the initial state of UL duplication configuration.

At <NUM>, after the configuration, the RAN network can dynamically control the PDCP UL duplication during the transmission. At <NUM>, the RAN node can send MAC CE to UE. The MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated (e.g., which of the RLC entities shall be used for UL duplicate transmission). The primary RLC entity cannot be deactivated. The UE may apply the received MAC CE commands regardless of the origin UL duplication state.

Referring now to <FIG>, depicted is a communication diagram of a data flow <NUM> in a scenario of an assisting node determining the initial state of UL duplication with a MN terminated bearer. At <NUM>, for the MN terminated DRB to be setup, the MN node may determine the following for the DRB: the location of primary RLC entity (at MN or SN), and the initial state of UL duplication (RLC activated or deactivated) of secondary RLC entities of MN.

At <NUM>, the MN may send SN addition request message to the SN to setup DRB, including the following information for the MN terminated DRB: the information of the number of activated secondary RLCs of assisting node (which is used to indicate how may secondary RLC entities shall be activated for UL duplication at SN), and the information of the primary RLC indication (which is used to indicate whether the primary RLC entity is located at SN). The indication may be an explicit indication, such as true or false value, or an implicit indication, such as the number of secondary RLC entities at the assisting node or the number of secondary RLC entities at the host node combined with the number of total secondary RLC entities of the DRB. The assisting node can infer whether the primary RLC entity is located at the assisting node based on such number information. It should be noted that if the information of the number of activated secondary RLCs of assisting node is absent, the assisting node may determine how may secondary RLCs of assisting node need to activated for UL duplication. For example, when the minimum number of activation is zero, the maximum number of activation may be the number of the secondary RLC entities at assisting node.

At <NUM>, after receiving SN addition request message sent by MN, for the DRB to be setup, the SN may take the information of the primary RLC indication and the information of the number of activated secondary RLCs of assisting node into account to determine the initial state of each of RLC entity at SN (e.g., either activated or deactivated). The primary RLC entity may always be configured as activated for UL duplication.

At <NUM>, the SN may send SN addition response to the MN, including the following information for the MN terminated DRB: the information of the initial state of UL duplication of assisting node (which is used to indicate every secondary RLC entity at SN is activated or deactivated). At <NUM>, the MN may send RRC Reconfiguration message to UE, including initial state of UL duplication of all secondary RLCs in both MCG and SCG for the DRB. At <NUM>, the UE may send RRC Reconfiguration complete message to RAN network.

At <NUM>, after the DRB has been established, the transmitting PDCP entity at UE side can duplicate the PDCP PDU and submit the copy to each activated RLC entity indicated by the initial state of UL duplication configuration. At <NUM>, after the configuration, the RAN network may dynamically control the PDCP UL duplication during the transmission.

At <NUM>, the RAN node can send MAC CE to UE. The MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated (e.g., which of the RLC entities shall be used for UL duplicate transmission). Primary RLC entity may not be deactivated. The UE may apply the received MAC CE commands regardless of the origin UL duplication state.

Referring now to <FIG>, depicted is a communication diagram of a data flow <NUM> in a scenario of an assisting node determining the initial state of UL duplication with a SN terminated bearer. At <NUM>, the MN node send SN addition request message to the SN. At <NUM>, for the SN terminated DRB to be setup, the SN may determine the following for the DRB: the location of primary RLC entity (at MN or SN), and the initial state of UL duplication (RLC activated or deactivated) of secondary RLC entities at SN.

At <NUM>, the SN may send SN addition response message to the MN, including the following information for the SN terminated DRB: the information of the number of activated secondary RLCs of assisting node (which is used to indicate how may secondary RLC entities shall be activated for UL duplication at MN), and the information of the primary RLC indication (which is used to indicate whether the primary RLC entity is located at MN). The indication may be an explicit indication, such as true or false value, or an implicit indication, such as the number of secondary RLC entities at the assisting node or the number of secondary RLC entities at the host node combined with the number of total secondary RLC entities of the DRB. The assisting node can infer whether the primary RLC entity is located at the assisting node based on such number information. It should be noted that if the information of the number of activated secondary RLCs of assisting node is absent, the assisting node may determine how may secondary RLCs of assisting node need to activated for UL duplication. For example, when the minimum number of activation is zero, the maximum number of activation may be the number of the secondary RLC entities at assisting node.

At <NUM>, after receiving SN addition response message sent by SN, for the DRB to be setup, the SN may take the information of the primary RLC indication and the information of the number of activated secondary RLCs of assisting node into account to determine the initial state of each of RLC entity at MN (e.g., either activated or deactivated). The primary RLC entity may always be configured as activated for UL duplication.

At <NUM>, the MN may send SN modification request to the SN, including the following information for the SN terminated DRB: the information of the initial state of UL duplication of assisting node (which is used to indicate every secondary RLC entity at MN is activated or deactivated). At <NUM>, the SN may send RRC Reconfiguration message to UE, including initial state of UL duplication of all secondary RLCs in both MCG and SCG for the DRB. At <NUM>, the UE may send RRC Reconfiguration complete message to RAN network. At <NUM>, after the DRB has been established, the transmitting PDCP entity at UE side can duplicate the PDCP PDU and submit the copy to each activated RLC entity indicated by the initial state of UL duplication configuration.

At <NUM>, after the configuration, the RAN network can dynamically control the PDCP UL duplication during the transmission. At <NUM>, the RAN node can send MAC CE to UE. The MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated (e.g., which of the RLC entities shall be used for UL duplicate transmission). Primary RLC entity cannot be deactivated. The UE may apply the received MAC CE commands regardless of the origin UL duplication state.

Referring now to <FIG>, depicted is a communication diagram of a data flow <NUM> in a scenario of an assisting node determining the initial state of UL duplication with CU-DU split entities. At <NUM>, for the DRB to be setup at more than one DUs, the CU may determine the following for the DRB: the location of primary RLC entity (which DU).

At <NUM>, the CU may send UE context setup message to the different DU to setup UE context of the DRB, including the following information for the DRB: the information of the number of activated secondary RLCs of assisting node (which is used to indicate how may secondary RLC entities shall be activated for UL duplication at this DU), and the information of the primary RLC indication (which is used to indicate whether the primary RLC entity is located at this DU). The indication may be an explicit indication, such as true or false value, or an implicit indication, such as the number of secondary RLC entities at the assisting node or the number of secondary RLC entities at the host node combined with the number of total secondary RLC entities of the DRB. The assisting node can infer whether the primary RLC entity is located at the assisting node based on such number information. It should be noted that if the information of the number of activated secondary RLCs of assisting node is absent, the assisting node may determine how may secondary RLCs of assisting node need to activated for UL duplication. For example, the minimum number of activation is zero, the maximum number of activation may be the number of the secondary RLC entities at assisting node.

At <NUM>, after receiving UE context setup message sent by CU, for the DRB to be setup, for the DRB to be setup, the DU may take the information of the primary RLC indication and the information of the number of activated secondary RLCs of assisting node into account to determine the initial state of each of RLC entity at DU (e.g., either activated or deactivated). The primary RLC entity may be always configured as activated for UL duplication.

At <NUM>, the DU may send UE context setup response to the CU. At <NUM>, the RAN node may send RRC Reconfiguration message to UE, including initial state of UL duplication of all secondary RLCs in DU1 and DU2 for the DRB. At <NUM>, the UE may send RRC Reconfiguration complete message to RAN network. At <NUM>, after the DRB has been established, the transmitting PDCP entity at UE side can duplicate the PDCP PDU and submit the copy to each activated RLC entity indicated by the initial state of UL duplication configuration.

At <NUM>, After the configuration, the RAN network can dynamically control the PDCP UL duplication during the transmission. At <NUM>, the RAN node can send MAC CE to UE. The MAC CE can be used to dynamically control whether each of the configured secondary RLC entities for a DRB should be activated or deactivated (e.g., which of the RLC entities shall be used for UL duplicate transmission). The primary RLC entity cannot be deactivated. The UE may apply the received MAC CE commands regardless of the origin UL duplication state.

Referring now to <FIG>, depicted is a flow diagram of a process or a method <NUM> of uplink packet duplication transmissions. The method <NUM> may be implemented or performed by any of the components described herein in conjunction with <FIG>. In brief overview, a host radio access network (RAN) node may determine a location of a primary radio link control (RLC) entity (<NUM>). The host RAN node may transmit the location of the primary RLC entity (<NUM>). An assisting RAN node may receive the location of the primary RLC entity (<NUM>). The host RAN node and the assisting RAN node may handle an initial state of uplink (UL) duplication (<NUM> and <NUM>'). The host RAN node and the assisting RAN node may transmit the initial state of UL duplication (<NUM> and <NUM>').

In further detail, a host radio access network (RAN) node may identify or determine a location of a primary radio link control (RLC) entity (<NUM>). The host RAN node may store, maintain, or otherwise host a packet data convergence protocol (PDCP) entity (e.g., PDCP entity <NUM>). The primary RLC entity (e.g., primary RLC entity 310A) may be established and maintained from a radio resource control (RRC) layer. The location of primary RLC entity may be referenced using an address in accordance with RLC. The PDCP entity may be established and maintained by the host RAN node on the PDCP protocol layer.

The host RAN node may send, provide, or transmit the location of the primary RLC entity (<NUM>). The location of the primary RLC entity may be transmitted to an assisting RAN node. In some embodiments, the hos RAN node may transmit the location of the primary RLC entity included in a sending node addition request (e.g., <NUM>, <NUM>, <NUM>, and <NUM>). In some embodiments, the host RAN node may transmit the location of the primary RLC entity included in a UE context setup request (e.g., <NUM> and <NUM>). The assisting RAN node may in turn retrieve, identify, or otherwise receive the location of the primary RLC entity (<NUM>). In some embodiments, the assisting RAN node may receive the sending node addition request (e.g., <NUM>, <NUM>, <NUM>, and <NUM>) including the location of primary RLC entity from the host RAN node. In some embodiments, the assisting RAN node may transmit the location of the primary RLC entity included in a UE context setup request (e.g., <NUM> and <NUM>). In some embodiments, the host RAN node may include, be, or correspond to a master node (MN) and the assisting RAN node may include, be, or correspond to a secondary node (SN). Vice-versa, in some embodiments, the host RAN node may include, be, or correspond to a secondary node (SN) and the assisting RAN node may include, be, or correspond to a master node (MN). In some embodiments, the host RAN node may include, be, or correspond to a central unit (CU) and the assisting RAN node may include, be, or correspond to a distributed unit (DU).

The host RAN node and the assisting RAN node may handle an initial state of uplink (UL) duplication (<NUM> and <NUM>'). In some embodiments, the host RAN node may identify or determine the initial state of UL duplication of one or more the secondary nodes at the assisting RAN node. In some embodiments, the host RAN node may identify or determine the initial state of UL duplication of at least one secondary RLC entity (e.g., secondary RLC 310B) at the assisting RAN node. In some embodiments, the host RAN node may identify or determine the initial state of UL duplication of all secondary includes including the secondary RLC entity at the assisting RAN node. In some embodiments, upon determination, the host RAN node may transmit the initial state of the UL duplication to the assisting RAN node.

In turn, the assisting RAN node may retrieve, identify, or receive the initial state of UL duplication of the one or more secondary nodes at the assisting node from the host RAN node. In some embodiments, the assisting RAN node may identify or determine the initial state of UL duplication of at least one secondary RLC entity (e.g., secondary RLC 310B) at the assisting RAN node. In some embodiments, the assisting RAN node may retrieve, identify, or receive the initial state of UL duplication of all secondary includes including the secondary RLC entity at the assisting RAN node.

In some embodiments, the host RAN node may identify or determine the initial state of UL duplication of at least one secondary RLC entity at another assisting RAN node. The other assisting RAN node may include, for example, another distributed unit (e.g., DU2). In some embodiments, the host RAN node may send, provide, or transmit the initial state of UL duplication of at least one secondary RLC entity at the other assisting RAN node. The other assisting RAN node may perform the same functionary as the first assisting RAN node.

Upon receipt of the initial state of UL duplication from the host RAN node, the assisting RAN node may determine whether the location of the primary RLC entity is at the assisting RAN node. When the location of the primary RLC entity is at not at the assisting RAN node, the assisting RAN node may maintain or store the initial state of UL duplication of at least one secondary RLC entity at the assisting node. On the other and, when the location of the primary RLC entity is at the assisting RAN node, the assisting RAN node may maintain or store the initial state of UL duplication of at least one secondary RLC entity at the assisting RAN node. The storage of the initial state of UL duplication may be except that of the primary RLC entity.

In some embodiments, the host RAN node may identify or determine an initial state of UL duplication of at least one secondary RLC entity at the host RAN node itself. In some embodiments, the host RAN node may send, provide, or transmit the initial state of UL duplication at the host RAN node to the assisting RAN node. The assisting RAN node may in turn retrieve, identify, or receive the initial state of UL duplication at the host RAN node from the host RAN node. In some embodiments, the host RAN node may identify, calculate, or determine a number secondary RLC entities to be activated at the assisting RAN node. The host RAN node may send, provide, transmit the number of secondary RLC entities to the assisting RAN node. In some embodiments, the assisting RAN node may in turn retrieve, identify, or receive the number of secondary RLC entities to be activated from the host RAN node.

In some embodiments, the assisting node may identify or determine the initial state of UL duplication of at least one secondary RLC node at the assisting RAN node. The determination of the initial state of UL duplication may be in accordance with the location of the primary RLC entity and the number of secondary RLC entities to be activated at the assisting RAN node. In some embodiments, the assisting RAN node may send, provide, or transmit the determined initial state of UL duplication of at least one secondary RLC entity at the assisting RAN node to the host RAN node. The host RAN node may in turn retrieve, identify, or receive the initial state of UL duplications of at least one secondary RLC entity at the assisting RAN node from the assisting RAN node.

The host RAN node and the assisting RAN node may send, provide, or transmit the initial state of UL duplication (<NUM> and <NUM>'). In some embodiments, the host RAN node may send, provide, or transmit the initial state of UL duplication of the one or more RLC entities at the assisting node to a wireless communication device (e.g., UE <NUM>). In some embodiments, the host RAN node may send, provide, or transmit the initial state of UL duplication of the one or more secondary RLC entities at the host RAN node to the wireless communication device (e.g., UE <NUM>). The initial state of UL duplication at the assisting RAN node may transmitted directly or via the assisting node from the host RAN node to the wireless communication devices using a radio resource control (RRC) message (e.g., MAC-CE <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>). The initial state of UL duplication at the host RAN node may transmitted directly or via the assisting node from the host RAN node to the wireless communication devices using the RRC message (e.g., MAC-CE <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>).

Thus, the scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

Claim 1:
A method, comprising:
determining (<NUM>),
by a host radio access network, RAN, node hosting a packet data convergence protocol, PDCP, entity (<NUM>), a location of a primary radio link control, RLC, entity;
determining (<NUM>), by the host RAN node (<NUM>), an initial state of uplink duplication of at least one secondary RLC entity (310B) at the assisting RAN node (<NUM>) as one of RLC activated or deactivated;
transmitting (<NUM>), by the host RAN node (<NUM>) to an assisting RAN node (<NUM>), the location of the primary RLC entity (<NUM>10A) to indicate whether the primary RLC is at the assisting RAN node (<NUM>); and
transmitting (<NUM>), by the host RAN node (<NUM>) to the assisting RAN node (<NUM>), the initial state of uplink duplication of the at least one secondary RLC entity (310B) at the assisting RAN node (<NUM>).