Copy PDCP PDU for radio bearer

By implementing dynamic replication management of PDCP protocol entities and RLC protocol entities in radio bearers, the flexibility of PDCP replication configuration under CA and DC architectures is solved, and the transmission reliability and delay performance are improved, meeting the requirements of URLLC services.

CN114401217BActive Publication Date: 2024-11-29MOTOROLA MOBILITY LLC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210117823.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2018-04-24
Publication Date
2024-11-29
Estimated Expiration
2038-04-24

AI Technical Summary

Technical Problem

The existing radio bearer PDCP PDU replication technology lacks flexible and dynamic configuration and activation/deactivation processes in CA and DC-based architectures, resulting in difficult transmission reliability and delay requirements, especially in case of carrier interruptions or errors.

Method used

Receive control signals to activate or deactivate PDCP replication and perform data transmission and discard operations based on RLC status reports and PDCP status reports and PDCP status reports by establishing radio bearers at remote units, including PDCP protocol entities, RLC protocol entities associated with it, and logical channels, receiving control signals to activate or deactivate PDCP replication, and performing data transmission and discarding operations based on RLC status reports and PDCP status reports , ensure redundant transmission on different carriers.

Benefits of technology

It realizes dynamic activation and deactivation of PDCP replication under CA and DC architectures, improves transmission reliability and delay performance, adapts to carrier changes, and meets the reliability and delay requirements of URLLC services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114401217B_ABST
    Figure CN114401217B_ABST
Patent Text Reader

Abstract

The present application relates to duplicating PDCP PDUs for radio bearers. An apparatus (300) includes a processor (305) and a transceiver (325) for communicating with a mobile communication network. The processor (305) establishes (705) a radio bearer to communicate with the network, the radio bearer including a PDCP entity, a first and a second RLC entity associated with the PDCP entity, and a first and a second logical channel associated with the first and the second RLC entity, respectively. The processor (305) receives (710) a control signal from the network, duplicates (715) PDCP data PDUs in the PDCP entity, and submits (720) them to the first and the second RLC entity for transmission. In response to successfully delivering a corresponding PDCP data PDU through another RLC entity, the processor (305) indicates (725) to one of the first and the second RLC entities to discard the duplicated PDCP data PDU.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This application is a divisional application of the Chinese patent application with an application date of April 24, 2018, an international application number of PCT / US2018 / 029194, a Chinese application number of 201880024198.3, and an invention name of “Replicating PDCP PDU for Radio Bearing”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. Provisional Patent Application No. 62 / 489,332, entitled “Efficient Schemes for Packet Replication in NR” and filed on April 24, 2017 in the name of Joachim Loehr, Prateek Basu Mallick, and Ravi Kuchibhotla, which is incorporated herein by reference. Technical Field

[0004] The subject matter disclosed herein relates to electronic communications, and more particularly to replicating PDCP PDUs for radio bearers. Background Art

[0005] The following abbreviations and acronyms are defined herein, at least some of which are referenced in the following description.

[0006] 3rd Generation Partnership Project (“3GPP”), Access and Mobility Management Function (“AMF”), Access Point Name (“APN”), Access Stratum (“AS”), Carrier Aggregation (“CA”), Clear Channel Assessment (“CCA”), Control Channel Element (“CCE”), Channel State Information (“CSI”), Common Search Space (“CSS”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Downlink Control Information (“DCI”), Downlink (“DL”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Evolved Packet Core (“EPC”), Evolved UMTS Terrestrial Radio Access Network (“E-UTRAN”), European Telecommunications Standards Institute (“ETSI”), Frame-based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”) ”), Globally Unique Temporary UE Identity (“GUTI”), Hybrid Automatic Repeat Request (“HARQ”), Home Subscriber Server (“HSS”), Internet of Things (“IoT”), Key Performance Indicator (“KPI”), License Assisted Access (“LAA”), Load-Based Equipment (“LBE”), Listen Before Talk (“LBT”), Long Term Evolution (“LTE”), LTE Advanced (“LTE-A”), Medium Access Control (“MAC”), Multiple Access (“MA”), Modulation and Coding Scheme (“MCS”), Machine Type Communication (“MTC”), Massive MTC (“mMTC”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Multiple Input Multiple Output (“MIMO”), Multipath TCP (“MPTCP”), Multi-User Shared Access (“MUSA”), Non-Access Stratum (“NAS”), Narrowband (“NB”), Network Function (“NF”), Next Generation (e.g.,5G) Node B (“gNB”), Next Generation Radio Access Network (“NG-RAN”), New Radio (“NR”), Policy Control and Charging (“PCC”), Policy Control Function (“PCF”), Policy Control and Charging Rules Function (“PCRF”), Packet Data Network (“PDN”), Packet Data Unit (“PDU”), PDN Gateway (“PGW”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Radio Access Network (“RAN”), Radio Access Technology (“RAT”), Radio Resource Control (“RRC”), Reception (“RX”), Handover / Split Function (“SSF”), Scheduling Request (“SR”) , Serving Gateway (“SGW”), Session Management Function (“SMF”), System Information Block (“SIB”), Transport Block (“TB”), Transport Block Size (“TBS”), Time Division Duplex (“TDD”), Time Division Multiplexing (“TDM”), Transmission and Reception Point (“TRP”), Transmission (“TX”), Uplink Control Information (“UCI”), Unified Data Management (“UDM”), User Entity / Equipment (Mobile Terminal) (“UE”), Uplink (“UL”), User Plane (“UP”), Universal Mobile Telecommunications System (“UMTS”), Ultra-Reliable and Low Latency Communications (“URLLC”), and Worldwide Interoperability for Microwave Access (“WiMAX”). ,

[0007] Some wireless communication systems support packet duplication of user plane data as well as control plane data in order to increase the reliability of transmission, i.e., by having diversity gain. Duplication is a function of the PDCP layer, e.g., PDCP PDUs are arranged. Services that benefit from duplication include URLLC or signaling radio bearers ("SRBs"). Summary of the invention

[0008] A method for duplicating a PDCP PDU for a radio bearer is disclosed. The apparatus and system also perform the functions of the method. A method (e.g., a method of a user equipment) for duplicating a PDCP PDU for a radio bearer includes establishing a radio bearer at a remote unit to communicate with a mobile communication network. Here, the radio bearer includes a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity associated with the PDCP protocol entity, a first logical channel associated with the first RLC protocol entity, and a second logical channel associated with the second RLC protocol entity. The method includes receiving a first control signal from the mobile communication network at the remote unit, duplicating a PDCP data PDU in the PDCP protocol entity at the remote unit in response to the first control signal, and submitting the duplicated PDCP data PDU to the first RLC protocol entity and the second RLC protocol entity for transmission. The method includes: in response to receiving a confirmation that the corresponding one or more PDCP data PDUs are successfully transmitted by another RLC protocol entity, indicating to one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicated PDCP data PDUs. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] A more particular description of the embodiments briefly described above will be presented by reference to specific embodiments illustrated in the accompanying drawings. Understanding that these drawings depict only some embodiments and are therefore not to be considered limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0010] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for replicating a PDCP PDU for a radio bearer;

[0011] Figure 2 is a schematic block diagram illustrating another embodiment of a network process for replicating a PDCP PDU for a radio bearer;

[0012] Figure 3 is a schematic block diagram illustrating one embodiment of a user equipment apparatus for replicating a PDCP PDU for a radio bearer;

[0013] Figure 4 is a schematic block diagram illustrating one embodiment of a network equipment apparatus for replicating a PDCP PDU for a radio bearer;

[0014] Figure 5 is a diagram illustrating one embodiment of a protocol stack for duplicating PDCP PDUs for radio bearers in a dual connectivity environment;

[0015] Figure 6is a diagram illustrating one embodiment of a protocol stack for duplicating PDCP PDUs for radio bearers in a carrier aggregation environment; and

[0016] Figure 7 is a flow chart illustrating one embodiment of a method for duplicating a PDCP PDU for a radio bearer. DETAILED DESCRIPTION

[0017] As will be appreciated by those skilled in the art, aspects of the embodiments may be embodied as systems, devices, methods or program products. Thus, the embodiments may take the form of full hardware embodiments, full software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects.

[0018] For example, the disclosed embodiments may be implemented as hardware circuits including custom very large scale integration ("VLSI") circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. The disclosed embodiments may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices, etc. As another example, the disclosed embodiments may include, for example, one or more physical or logical blocks including executable code, which may be organized, for example, as an object, procedure, or function.

[0019] In addition, embodiments may take the form of a program product embodied in one or more computer-readable storage devices stored in machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmitting. The storage device may not embody a signal. In a certain embodiment, the storage device employs only a signal for accessing the code.

[0020] Any combination of one or more computer readable media may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, apparatus or device, or any suitable combination of the foregoing.

[0021] More specific examples of storage devices (a non-exhaustive list) would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0022] References to "one embodiment", "embodiment" or similar language in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in at least one embodiment. Therefore, unless otherwise expressly stated, the phrases "in one embodiment", "in an embodiment" and similar language appearing throughout the specification may but do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments". Unless otherwise expressly stated, the terms "including", "comprising", "having" and their variations mean "including but not limited to". Unless otherwise expressly stated, the list of items listed does not imply that any or all items are mutually exclusive. Unless otherwise expressly stated, the terms "a / an" and "the" also refer to "one or more".

[0023] In addition, the features, structures or characteristics of the described embodiments may be combined in any suitable manner. In the following description, many specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of the embodiments. However, those skilled in the relevant art will recognize that the embodiments may be practiced without one or more of the specific details, or using other methods, components, materials, etc. In other cases, well-known structures, materials or operations are not shown or described in detail to avoid obscuring some aspects of the embodiments.

[0024] Various aspects of the embodiments are described below with reference to schematic flow charts and / or schematic block diagrams of the methods, devices, systems, and program products according to the embodiments. It will be understood that each block of the schematic flow charts and / or schematic block diagrams and the combination of blocks in the schematic flow charts and / or schematic block diagrams can be implemented by code. This code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by the processor of the computer or other programmable data processing device create a means for implementing the functions / operations specified in the schematic flow charts and / or schematic block diagrams.

[0025] The code may also be stored in a storage device that is capable of instructing a computer, other programmable data processing apparatus, or other device to operate in a specific manner so that the instructions stored in the storage device produce an article of manufacture including instructions that implement the functions / operations specified in the schematic flowchart and / or schematic block diagram.

[0026] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / operations specified in the schematic flowchart and / or schematic block diagram.

[0027] The schematic flow charts and / or schematic block diagrams in the accompanying drawings illustrate possible implementations of the apparatus, system, method, and program product according to various embodiments, architecture, functions, and operations. In this regard, each block in the schematic flow charts and / or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing a specified logical function.

[0028] It should also be noted that in some alternative implementations, the functions annotated in the blocks may not occur in the order annotated in the drawings. For example, two blocks shown in succession may actually be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods are contemplated that are equivalent in function, logic, or effect to one or more blocks or portions thereof of the illustrated drawings.

[0029] The description of an element in each figure may refer to an element of the previous figure. The same numerals refer to the same elements in all figures, including alternative embodiments of the same elements.

[0030] Figure 1 A wireless communication system 100 for duplicating PDCP PDUs for radio bearers according to an embodiment of the present disclosure is depicted. In one embodiment, the wireless communication system 100 includes at least one remote unit 105, an access network 120 including at least two base units 110, a wireless communication link 115, and a mobile core network 140. Even in Figure 1 Although a specific number of remote units 105, access networks 120, base units 110, wireless communication links 115, and mobile core networks 140 are depicted in the wireless communication system 100, one skilled in the art will recognize that any number of remote units 105, access networks 120, base units 110, wireless communication links 115, and mobile core networks 140 may be included in the wireless communication system 100. In another embodiment, the access network 120 includes one or more WLANs (e.g., Wi-FiTM ) access point.

[0031] In one embodiment, the wireless communication system 100 complies with the 5G system specified in the 3GPP specification. However, more generally, the wireless communication system 100 may implement some other open or proprietary communication network, such as LTE or WiMAX, among other networks. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0032] In one embodiment, the remote unit 105 may include a computing device such as a desktop computer, a laptop computer, a personal digital assistant (“PDA”), a tablet computer, a smart phone, a smart TV (e.g., a TV connected to the Internet), a smart device (e.g., a device connected to the Internet), a set-top box, a game console, a security system (including a security camera), a car computer, a network device (e.g., a router, a switch, a modem), etc. In some embodiments, the remote unit 105 includes a wearable device such as a smart watch, a fitness band, an optical head-mounted display, etc. In addition, the remote unit 105 may be referred to as a subscriber unit, a mobile device, a mobile station, a user, a terminal, a mobile terminal, a fixed terminal, a subscriber station, a UE, a user terminal, a device, or other terms used in the art. The remote unit 105 can communicate directly with one or more base units 110 via uplink (“UL”) and downlink (“DL”) communication signals. In addition, the UL and DL communication signals can be carried by the wireless communication link 115.

[0033] In some embodiments, the remote unit 105 can communicate with the remote host 151 via the data path 125 that passes through the mobile core network 140 and the data network 150. For example, the remote unit 105 can establish a PDU connection (or data connection) to the data network 150 via the mobile core network 140 and the access network 120. The mobile core network 140 then relays traffic between the remote unit 105 and the remote host 151 using the PDU connection to the data network 150.

[0034] The base units 110 may be distributed over a geographic area. In some embodiments, the base units 110 may also be referred to as access terminals, access points, bases, base stations, node Bs, eNBs, gNBs, home node Bs, relay nodes, devices, or any other term used in the art. The base units 110 are typically part of a radio access network (“RAN”), such as an access network 120, which may include one or more controllers communicatively coupled to one or more corresponding base units 110. These and other elements of the radio access network are not illustrated, but are generally well known to those of ordinary skill in the art. The base units 110 are connected to a mobile core network 140 via the access network 120.

[0035] The base unit 110 can serve multiple remote units 105 within a service area, such as a cell or a cell sector, via a wireless communication link 115. The base unit 110 can communicate directly with one or more of the remote units 105 via communication signals. Typically, the base unit 110 sends DL communication signals in the time, frequency, and / or spatial domains to serve the remote units 105. In addition, the DL communication signals can be carried by the wireless communication link 115. The wireless communication link 115 can be any suitable carrier in the licensed or unlicensed radio spectrum. The wireless communication link 115 facilitates communication between one or more remote units 105 and / or one or more base units 110.

[0036] In one embodiment, mobile core network 140 is a 5G core ("5GC") or an evolved packet core ("EPC"), which can be coupled to data network 150, such as the Internet and private data networks, among other data networks. Each mobile core network 140 can belong to a single public land mobile network ("PLMN"). The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0037] The mobile core network 140 includes several network functions ("NFs"). As depicted, the mobile core network 140 includes a plurality of control plane functions, including, but not limited to, an access and mobility management function ("AMF") 143, a session management function ("SMF") 145, and a policy control function ("PCF"). In addition, the mobile core network 140 includes a user plane function ("UPF") 141 and a unified data management ("UDM") 147. Although Figure 1 Although a specific number and type of network functions are depicted in FIG. 1 , those skilled in the art will recognize that any number and type of network functions may be included in the mobile core network 140 .

[0038] Disclosed herein are methods, systems, and apparatus for effective activation / deactivation of PDCP duplication for both CA and DC based architectures. In order to effectively activate and / or deactivate packet duplication (e.g., PDCP duplication), the base unit 110 signals the remote unit 105, e.g., a first control signal. The signaling may be PDCP control signaling, MAC control signaling, or RRC signaling. For 3GPP networks, the 5G radio RAT (referred to as New Radio, "NR") supports packet duplication of data on the user plane and control plane, e.g., by having a diversity gain to increase the reliability of transmission. As described above, the packet duplication is a function of the PDCP layer such that the PDCP PDU is duplicated.

[0039] PDCP duplication is beneficial for services such as URLLC, where transmission reliability and latency enhancement are two key aspects. In addition, redundancy / diversity schemes in carrier aggregation (“CA”) scenarios can be used to achieve the reliability and latency requirements of URLLC. For URLLC, for services such as 10 -5 to 10 -9 Extreme reliability situations with error rates of 100% or less may require two independent transmission channels on different carriers. Here, CA-based replication is a tool available to the scheduler to further improve transmission reliability. However, in situations where the reliability of one of the carriers cannot be guaranteed, it is therefore beneficial to have an additional carrier available. As an example, this situation may be a temporary outage / fading due to unexpected changes or erroneous channel state information.

[0040] Packet replication may also be applied based on a dual connectivity ("DC") architecture, e.g., split bearer operation with PDCP replication. In a general sense, packet replication may be used with different diversity schemes involving more than one radio link to serve a UE. Although the following embodiments focus on DC and CA scenarios, the present disclosure is not intended to be limited to those implementations.

[0041] Typically, packet duplication is limited to those situations where additional reliability is required, such as dynamic activation / deactivation. Here, PDCP control signaling or MAC control signaling (e.g., MAC Control Element ("CE")) can be used to activate / deactivate PDCP duplication. Advantageously, this also reduces the overhead of activation / deactivation of PDCP duplication. Currently, there is no process for configuring PDCP duplication in CA and DC based architectures, let alone a process for activating / deactivating duplication in a flexible, dynamic manner.

[0042] In one embodiment, the remote unit 105 is configured with a split bearer, e.g., for dual connectivity. In such an embodiment, a default state of PDCP duplication at the split bearer may be deactivated, wherein the base unit 110 explicitly activates PDCP duplication by sending a first control signal. In another embodiment, the remote unit 105 communicates with the access network 120 using carrier aggregation, and the remote unit 105 is configured with at least one bearer having a PDCP entity associated with two logical channels / RLC entities mapped to different serving cells. In such an embodiment, a default state of PDCP duplication of the bearer may be deactivated, wherein the base unit 110 explicitly activates PDCP duplication by sending a first control signal.

[0043] In one embodiment, when duplication is activated, the remote unit 105 removes PDCP PDUs from a transmission buffer associated with a logical channel / RLC entity that has been successfully transmitted through another logical channel / RLC entity, for example, to avoid transmission buffers from being piled up. According to one embodiment, the removal (discarding) of packets may be based on a received RLC status report. Here, the RLC layer at the remote unit 105 notifies the PDCP layer of the successfully transmitted PDCP PDUs. The PDCP layer may then send a PDCP discard notification to another RLC entity.

[0044] Alternatively, the removal / discarding of packets may be based on a received PDCP status report. In such an embodiment, the remote unit 105 sends a PDCP status report for the DL to the base unit 110, which uses this information to discard packets from the DL transmit buffer that have been successfully received by the remote unit 105. Similarly, for the UL, the PDCP layer in the remote unit 105 receives the PDCP status report from the base unit 110 and instructs the appropriate RLC entity to discard packets that have been successfully transmitted (e.g., by another RLC entity). In one embodiment, the remote unit 105 expires a PDCP discard timer for those PDCP SDUs indicated as successfully transmitted in the PDCP status report, and then sends a discard notification to the RLC layer accordingly in response to the expiration of the PDCP discard timer.

[0045] Figure 2 A network process 200 for duplicating a PDCP PDU of a radio bearer according to an embodiment of the present disclosure is depicted. The network process 200 involves a UE 205 and a network entity, depicted here as a gNB 210. The UE 205 may be an embodiment of the remote unit 105 described above. Likewise, the gNB 210 may be an embodiment of the base unit 110 described above.

[0046] Here, it is assumed that UE 205 has established a radio bearer with gNB 210. Here, the radio bearer may include a PDCP entity, a first RLC entity and a second RLC entity associated with the PDCP entity, a first logical channel associated with the first RLC entity, and a second logical channel associated with the second RLC protocol entity. In one embodiment, the radio bearer includes a separate bearer at UE 205 (e.g., for dual connectivity with gNB 210 and another network entity (not shown)). In another embodiment, the radio bearer may be used in a carrier aggregation deployment.

[0047] The network process 200 begins with the gNB 210 sending a first control signal to the UE 205 for activating packet duplication for the radio bearer (see signaling 215). Here, the first control signal may be a PDCP control signal, a MAC control signal, and / or an RRC signal. As described above, packet duplication may be deactivated by default, so an explicit signal (here, the first control signal) from the gNB 210 is required to activate duplication of the radio bearer.

[0048] In certain embodiments, gNB 210 optionally sends an indication to UE 205 as to which RLC entity to use for transmitting PDCP PDUs when packet duplication is deactivated (see signaling 220). In one embodiment, the unused RLC entities are deactivated until duplication is activated again. In another embodiment, when packet duplication is deactivated, the unused RLC entities become available for transmitting (non-duplicated) data.

[0049] In response to the first control signal, the UE 205 starts packet duplication by duplicating the PDCP data PDU in the PDCP entity (see block 225). Here, copies of the same PDCP data PDU are sent to the first and second RLC entities. In other words, the PDCP PDUs received by the first and second RLC entities contain the same information. Therefore, the RLC entities further process the duplicated packets for transmission. Here, routing of the PDCP data PDUs to the two RLC entities may be based on the received UL grant. As depicted, the UE 205 sends the duplicated PDCP data PDU to the gNB 210 via the first and second RLC entities (see messaging 230).

[0050] In various embodiments, gNB 210 indicates successful transmission of (certain) PDCP data PDUs to the RLC entity (see signaling 235). Here, gNB 210 may send an RLC status report indicating successful transmission of the RLC PDUs corresponding to the PDCP data PDUs. Alternatively, gNB 210 may send a PDCP status report to indicate successful transmission of the PDCP data PDUs.

[0051] In response to successfully sending the PDCP data PDU via one RLC entity, UE 205 removes the corresponding PDCP data PDU from the buffer of the other RLC entity (see block 240). In some embodiments, successful transmission is indicated via an RLC status report, and the PDCP entity receives an indication of successful delivery from the RLC entity and signals the other RLC entity to discard the corresponding PDCP data PDU. In other embodiments, the PDCP entity receives an indication of successful delivery via a PDCP status report. Note that UE 205 continues to send duplicate PDCP data PDUs to gNB 210 and continues to receive indications of successful delivery.

[0052] At some later point in time, gNB 210 sends a second control signal to UE 205 to deactivate packet duplication (see signaling 245). Again, PDCP control signaling, MAC control signaling, and / or RRC signaling may be used to send the second control signal. In response to receiving the second control signal, UE 205 stops duplicating PDCP data PDUs in the PDCP entity of the radio bearer (see block 250). Note that UE 205 uses the RLC entity / logical channel that was (previously) configured for PDCP data transmission after deactivating packet duplication.

[0053] In some embodiments, in response to the second control signal, the UE 205 cancels a scheduling request triggered by data arrival of an RLC entity / logical channel that is configured not to be used for PDCP data transmission when duplication is disabled. In some embodiments, in response to the second control signal, the UE 205 cancels a buffer status report ("BSR") triggered by data arrival of a logical channel that is configured not to be used for PDCP data transmission when duplication is disabled. In addition, the MAC / HARQ entity in the UE 205 may discard packets associated with the disabled RLC entity. In some embodiments, the UE 205 clears the RLC transmission buffer of the disabled RLC entity as a response to receiving the second control signal.

[0054] Figure 3 An embodiment of a user equipment device 300 that can be used to replicate a PDCP PDU for a radio bearer according to an embodiment of the present disclosure is depicted. The user equipment device 300 can be an embodiment of a remote unit 105 and / or a UE 205. In addition, the user equipment device 300 may include a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver. In some embodiments, the input device 315 and the output device 320 are combined into a single device, such as a touch screen. In some embodiments, the user equipment device 300 does not include any input device 315 and / or output device 320.

[0055] As depicted, the transceiver 325 includes at least one transmitter 330 and at least one receiver 335. In addition, the transceiver 325 may support at least one network interface 340. Here, the at least one network interface 340 facilitates communication with an eNB or gNB (e.g., using a Uu interface). In addition, the at least one network interface 340 may include an interface for communicating with a UPF and / or an AMF.

[0056] In one embodiment, processor 305 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 305 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, processor 305 executes instructions stored in memory 310 to perform the methods and routines described herein. Processor 305 is communicatively coupled to memory 310, input device 315, output device 320, and transceiver 325.

[0057] In some embodiments, the processor 305 establishes a radio bearer to communicate with the mobile communication network. Here, the radio bearer includes a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity associated with the PDCP protocol entity, a first logical channel associated with the first RLC protocol entity, and a second logical channel associated with the second RLC protocol entity. In various embodiments, the radio bearer may include a MAC entity associated with the first RLC protocol entity and a MAC entity associated with the second RLC protocol entity.

[0058] In response to receiving the first control signal, the processor 305 starts packet duplication. Here, the processor 305 duplicates the PDCP data PDU in the PDCP protocol entity in response to the first control signal. The duplicated PDCP data PDU is submitted to the first RLC protocol entity and the second RLC protocol entity for transmission. In addition, the processor 305 indicates to the first RLC protocol entity to discard one or more duplicated PDCP data PDUs in response to the second RLC protocol entity receiving a confirmation of successful transmission of the corresponding one or more PDCP data PDUs, and also indicates to the second RLC protocol entity to discard one or more duplicated PDCP data PDUs in response to receiving a confirmation of successful transmission of the corresponding one or more PDCP data PDUs through the first RLC protocol entity.

[0059] In some embodiments, an RLC protocol entity indicates that one or more PDCP data PDUs corresponding to the RLC status report received from the mobile communication network are successfully delivered to the PDCP protocol entity. In response to receiving the indication of successful delivery, the PDCP protocol entity indicates to the other of the first and second RLC protocol entities to discard one or more duplicated PDCP data PDUs. In certain embodiments, the processor 305 discards one or more PDCP data PDUs in the appropriate RLC entity in response to receiving a discard indication from the PDCP protocol entity. In some embodiments, the processor 305 discards one or more PDCP data PDUs in one of the first RLC protocol entity and the second RLC protocol entity based on the PDCP status report received from the mobile communication network.

[0060] In various embodiments, the processor 305 indicates the amount of data packets (e.g., PDCP data PDUs) in the PDCP protocol entity to a MAC entity associated with the first RLC protocol entity and a MAC entity associated with the second RLC protocol entity for reporting buffer status of logical channels associated with the first RLC protocol entity and the second RLC protocol entity in response to the first control signal. Here, the same number of data packets is indicated for both RLC entities.

[0061] In some embodiments, the first control signal instructs the user equipment device 300 to start duplicating the PDCP data PDU. In various embodiments, the first control signal is one of the following: a PDCP control signal, a MAC control signal, and an RRC signal. At some time after receiving the first control signal, the processor 305 may also receive a second control signal instructing the user equipment device 300 to stop duplicating the PDCP data PDU. It is assumed here that the user equipment device 300 uses the first RLC protocol entity to transmit the PDCP data PDU when packet duplication is deactivated.

[0062] In one embodiment, the processor 305 may cancel a scheduling request associated with the second logical channel in response to the second control signal. Here, the scheduling request is triggered by the arrival of data for the second logical channel. In another embodiment, the processor 305 may cancel a buffer status report associated with the second logical channel in response to the second control signal. Here, the buffer status report is triggered by the arrival of data for the second logical channel.

[0063] In certain embodiments, the user equipment device 300 communicates with a mobile communication network using dual connectivity. In a dual connectivity use case, each RLC protocol entity belongs to a different cell group in the mobile communication network. In addition, the MAC entity associated with the first RLC protocol entity is a first MAC entity, and the MAC entity associated with the second RLC protocol entity is a second MAC entity different from the first RLC protocol entity. In such an embodiment, the processor 305 indicates the same amount of PDCP data PDUs in the PDCP protocol entity to the first MAC entity and the second MAC entity for reporting buffer status of the first logical channel and the second logical channel.

[0064] In addition, for a dual connectivity use case, establishing the radio bearer may include establishing a split bearer in the user equipment device. Here, the split bearer supports dual connectivity. In some embodiments, the first control signal includes an indication to replicate the PDCP data PDU on the split bearer. In some embodiments, the processor sets the uplink data split threshold to a zero value in response to receiving the first control signal, and sets the uplink data split threshold to infinity in response to receiving the second control signal, wherein the first control signal activates packet replication and the second control signal deactivates packet replication.

[0065] In certain embodiments, the user equipment device 300 communicates with the mobile communication network using carrier aggregation. In the carrier aggregation use case, the first RLC protocol entity and the second RLC protocol entity belong to the same cell group. In addition, each RLC protocol entity is associated with the same (e.g., shared) MAC entity. In such an embodiment, the processor 305 indicates the same amount of PDCP data PDUs in the PDCP protocol entity to the MAC entity for reporting buffer status of the first logical channel and the second logical channel.

[0066] In yet another embodiment, the processor 305 receives a second control signal and deactivates packet duplication. Here, in response to the second control signal, the processor 305 may indicate to zero the amount of PDCP data PDUs available for transmission in the PDCP protocol entity to a MAC entity associated with the second RLC protocol entity for reporting a buffer status of the second logical channel. Note here that the first RLC protocol entity continues to send packets (e.g., PDCP data PDUs) after deactivating packet duplication. In addition, the processor 305 may receive a third control signal prior to the second control signal, the third control signal indicating that the first RLC protocol entity is used to transmit the PDCP data PDU when packet duplication is deactivated.

[0067] In some embodiments, the processor 305 initializes a token bucket status for a previously inactive logical channel (e.g., in response to the first control signal). Here, the amount of tokens in the token bucket may be incremented periodically. In addition, the previously inactive logical channel may be one of the first logical channel and the second logical channel. In response to receiving the second control signal to deactivate packet replication, the processor 305 does not maintain a token bucket associated with the second logical channel.

[0068] In one embodiment, the memory 310 is a computer-readable storage medium. In some embodiments, the memory 310 includes a volatile computer storage medium. For example, the memory 310 may include a RAM, including a dynamic RAM ("DRAM"), a synchronous dynamic RAM ("SDRAM"), and / or a static RAM ("SRAM"). In some embodiments, the memory 310 includes a non-volatile computer storage medium. For example, the memory 310 may include a hard drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 310 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 310 stores data related to duplicating PDCP PDUs for radio bearers, such as storing indications for activating / deactivating packet duplication, indications for successful transmission of PDCP data PDUs, etc. In some embodiments, the memory 310 also stores program code and related data, such as an operating system or other controller algorithm operating on the user equipment device 300 and one or more software applications.

[0069] In one embodiment, input device 315 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 315 may be integrated with output device 320, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 315 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 315 includes two or more different devices, such as a keyboard and a touchpad.

[0070] In one embodiment, output device 320 may include any known electronically controllable display or display device. Output device 320 may be designed to output visual, auditory and / or tactile signals. In some embodiments, output device 320 includes an electronic display capable of outputting visual data to a user. For example, output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 320 may include a wearable display, such as a smart watch, smart glasses, a head-up display, etc. In addition, output device 320 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0071] In some embodiments, output device 320 includes one or more speakers for producing sound. For example, output device 320 can produce an audible alarm or notification (e.g., a beep or ringtone). In some embodiments, output device 320 includes one or more tactile devices for producing vibration, motion or other tactile feedback. In some embodiments, all or part of output device 320 can be integrated with input device 315. For example, input device 315 and output device 320 can form a touch screen or similar touch-sensitive display. In other embodiments, all or part of output device 320 can be located near input device 315.

[0072] The transceiver 325 communicates with one or more network functions of the mobile communication network. The transceiver 325 operates under the control of the processor 305 to send messages, data and other signals, and also receives messages, data and other signals. For example, the processor 305 can selectively activate the transceiver (or part thereof) at a specific time to send and receive messages. The transceiver 325 may include one or more transmitters 330 and one or more receivers 335.

[0073] Figure 4 An embodiment of a network device apparatus 400 that can be used to replicate a PDCP PDU of a radio bearer according to an embodiment of the present disclosure is depicted. The network device apparatus 400 can be an embodiment of a base unit 110 and / or a gNB 210. In addition, the network device apparatus 400 may include a processor 405, a memory 410, an input device 415, an output device 420, and a transceiver 425. In some embodiments, the input device 415 and the output device 420 are combined into a single device, such as a touch screen. In some embodiments, the network device apparatus 400 does not include any input device 415 and / or output device 420.

[0074] As depicted, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435. In addition, the transceiver 425 may support at least one network interface 440. Here, the at least one network interface 440 facilitates communication between a remote unit 105, such as a UE 205, and other network functions in the mobile core network 140, such as UPF 141, AMF 143, etc.

[0075] In one embodiment, processor 405 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, processor 405 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or a similar programmable controller. In some embodiments, processor 405 executes instructions stored in memory 410 to perform the methods and routines described herein. Processor 405 is communicatively coupled to memory 410, input device 415, output device 420, and transceiver 425.

[0076] In various embodiments, the processor 405 establishes a radio bearer for communication with a UE such as the UE 205. Here, the radio bearer may include a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity associated with the PDCP protocol entity, a first logical channel associated with the first RLC protocol entity, and a second logical channel associated with the second RLC protocol entity.

[0077] In some embodiments, the processor 405 sends a first control signal to the UE, the first control signal instructing the UE to start packet duplication. In some embodiments, the first control signal is one of the following: a PDCP control signal, a MAC control signal, and an RRC signal. In response to sending the first control signal, the processor 405 receives a duplicate packet (e.g., a duplicated PDCP data PDU from the UE). In addition, the processor 405 indicates to the UE the successful transmission of one or more UL PDCP data PDUs.

[0078] In some embodiments, the processor 405 also receives an indication of successfully received DL PDCP data PDUs from the UE. In the case of packet duplication on the DL, the processor 405 may discard one or more PDCP data PDUs in the first RLC protocol entity in response to a successful transmission of the corresponding one or more second RLC protocol entities, and vice versa.

[0079] At some time after sending the first control signal, the processor 405 may also send a second control signal instructing the UE to stop duplicating the PDCP data PDUs.In various embodiments, the processor 405 sends an indication to the UE of which RLC protocol entity to use for transmitting the PDCP data PDUs when packet duplication is deactivated.

[0080] In one embodiment, the memory 410 is a computer-readable storage medium. In some embodiments, the memory 410 includes a volatile computer storage medium. For example, the memory 410 may include a RAM, which includes a dynamic RAM ("DRAM"), a synchronous dynamic RAM ("SDRAM"), and / or a static RAM ("SRAM"). In some embodiments, the memory 410 includes a non-volatile computer storage medium. For example, the memory 410 may include a hard drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 410 includes volatile and non-volatile computer storage media. In some embodiments, the memory 410 stores data related to duplicating PDCP PDUs for radio bearers, such as storing instructions for activating / deactivating packet duplication, instructions for successful transmission of PDCP data PDUs, etc. In some embodiments, the memory 410 also stores program code and related data, such as an operating system or other controller algorithm operating on the network device device 400 and one or more software applications.

[0081] In one embodiment, input device 415 may include any known computer input device, including a touchpad, button, keyboard, stylus, microphone, etc. In some embodiments, input device 415 may be integrated with output device 420, for example, as a touch screen or similar touch-sensitive display. In some embodiments, input device 415 includes a touch screen so that text can be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. In some embodiments, input device 415 includes two or more different devices, such as a keyboard and a touchpad.

[0082] In one embodiment, output device 420 may include any known electronically controllable display or display device. Output device 420 may be designed to output visual, auditory and / or tactile signals. In some embodiments, output device 420 includes an electronic display capable of outputting visual data to a user. For example, output device 420 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc. to a user. As another non-limiting example, output device 420 may include a wearable display, such as a smart watch, smart glasses, a head-up display, etc. In addition, output device 420 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0083] In some embodiments, output device 420 includes one or more speakers for producing sound. For example, output device 420 can produce an audible alarm or notification (e.g., a beep or a ringtone). In some embodiments, output device 420 includes one or more tactile devices for producing vibration, motion or other tactile feedback. In some embodiments, all or part of output device 420 can be integrated with input device 415. For example, input device 415 and output device 420 can form a touch screen or similar touch-sensitive display. In other embodiments, all or part of output device 420 can be located near input device 415.

[0084] The transceiver 425 operates under the control of the processor 405 to send messages, data and other signals, and also receive messages, data and other signals. For example, the processor 405 can selectively activate the transceiver (or part thereof) at a particular time to send and receive messages. The transceiver 425 may include one or more transmitters 430 and one or more receivers 435.

[0085] Figure 5A protocol stack 500 for replicating PDCP PDUs for radio bearers in a dual connectivity environment is depicted in accordance with an embodiment of the present disclosure. Here, the protocol stack 500 is depicted as part of a UE 205. As described, the protocol stack 500 includes a first PDCP entity 505 and a second PDCP entity 510. Here, there is one PDCP entity per radio bearer such that the first PDCP entity 505 belongs to the first radio bearer and the second PDCP entity 510 belongs to the second radio bearer. The PDCP entities 505-510 are located in the PDCP layer of the protocol stack 500 and perform PDCP functions, including (but not limited to) header compression, security (integrity protection and encryption), and support for reordering and retransmission, for example, during switching. Note that the PDCP layer handles RRC messages in the control plane and IP packets in the user plane.

[0086] The protocol stack 500 also includes a first RLC entity 515, a second RLC entity 520, and a third RLC entity 525. Multiple RLC entities may exist for each radio bearer. In the depicted embodiment, the first RLC entity 515 and the second RLC entity 520 belong to the same radio bearer as the first PDCP entity 505. Note that the third RLC entity 525 is associated with the second PDCP entity 510. The RLC entities 515-525 are located in the RLC layer of the protocol stack 500 and perform RLC functions, including (but not limited to) segmenting and reassembling packets to make them suitable for the size of the radio interface. Note that the RLC layer exists below the PDCP layer and above the MAC layer. The protocol stack 500 includes three different logical channels, a first logical channel 530 on a MAC entity 540 associated with a primary cell group ("MAC MCG") associated with the third RLC entity 525, and a second logical channel 535 associated with the second RLC entity 520. The protocol stack 500 also includes a first logical channel 550 on the MAC entity 545 that is associated with a secondary cell group (“MAC SCG”) to which the first RLC entity 515 is associated.

[0087] In the depicted embodiment, the UE 205 is configured with a split bearer and therefore has a MAC entity 540 associated with a primary cell group and a MAC entity 545 associated with a secondary cell group. Here, the first RLC entity 515 is associated with a MAC SCG 545, while the second RLC entity 520 and the third RLC entity 525 are associated with a MAC MCG 540. The MAC entities 540-545 are located in the MAC layer of the protocol stack 500 and perform MAC functions, including (but not limited to) multiplexing between logical channels and (PHY) transport channels. The MAC entities 540-545 construct transport blocks ("TBs") based on the SDUs received from the RLC layer. As used herein, a service data unit ("SDU") refers to data received from a higher layer, while a protocol data unit ("PDU") refers to data delivered to a lower layer. Therefore, the PDCP entities 505-510 output PDCP PDUs, which are referred to as RLC SDUs when received at the RLC entities 515-525. Likewise, the RLC entities 515-525 output RLC PDUs, which when received at the corresponding MAC entities are called MAC SDUs.

[0088] In various embodiments, PDCP duplication is used in scenarios supported by a DC-based architecture such as the protocol stack 500. Here, a network entity (“NE”) such as a base unit or gNB configures a split bearer for the UE 205. At the network side, the PDCP layer for the split bearer may be located in a master node (“MN”) or a secondary node (“SN”). In addition, the UE 205 may also be configured with a primary cell group (“MCG”) bearer or a secondary cell group (“SCG”) bearer. Here, the MCG bearer is multiplexed (and demultiplexed) by the MAC MCG 540, while the SCG bearer is multiplexed (and demultiplexed) by the MAC SCG 545.

[0089] The NE, such as the MN or SN, signals the PDCP duplication configuration, such as activation / deactivation of duplication, to the UE 205. Note that the default state of duplication is deactivated. Therefore, when configuring a split bearer for duplication, the NE, such as the MN or SN, needs to explicitly activate the PDCP duplication. As described above, the signaling may be PDCP control signaling or MAC control signaling. Alternatively, RRC signaling may be used.

[0090] According to one embodiment, the NE configures the UE 205 with a radio link, e.g., MCG or SCG, that the UE 205 will use for data transmission when PDCP duplication is disabled. In some embodiments, this configuration can be done through RRC signaling. For example, the ul-DataSplitDRB-ViaSCG information element ("IE") can be used to define whether the UE 205 sends UL data via the SCG or MCG of the configured split bearer.

[0091] For the case of NE activated PDCP duplication, the UE 205 reports the same PDCP buffer occupancy for the replicated split bearers in the buffer status report (BSR) to the MAC entities 540-545 to both the MN and the SN, respectively. Here, the routing of the PDCP data PDUs to the first and second RLC entities 515-520 may be based on the received UL grant. For example, when a UL grant is received for one CG, the corresponding PDCP PDU is generated, replicated, and (optionally) forwarded to the first and second RLC entities 515-520.

[0092] Note that the UE 205 and / or NE may use a threshold associated with the split bearer to control PDCP PDU duplication, such as a threshold ul-DataSplitThreshold. Here, when the data available for transmission in PDCP is greater than or equal to ul-DataSplitThreshold, the UE 205 reports the same amount of PDCP data to both (all) network entities for buffer status reporting.

[0093] In some embodiments, the UE 205 activates duplication in response to receiving a first control signal from the NE, i.e., MN or SN, setting the ul-DataSplitThreshold to zero. Setting the ul-DataSplitThreshold to zero ensures that the data in the first PDCP entity 505 is reported to both network nodes, i.e., both the MN and the SN. Here, the UE 205 indicates the data available for transmission in the PDCP to the MAC entity 545 configured as an SCG configuration and the MAC entity 540 configured as an MCG. In other embodiments, the NE, e.g., MN or SN, configures the ul-DataSplitThreshold to zero when activating PDCP duplication. The configuration may be signaled via PDCP control signaling or MAC control signaling or alternatively RRC signaling.

[0094] The transmission of the PDCP PDU occurs according to the received uplink grant. For example, the UE 205 submits the generated PDCP PDU to the first RLC entity 515 configured for SCG or the second RLC entity 520 configured for MCG, whichever PDU is requested. In addition, the UE 205 can copy the generated PDCP PDU and can submit them to another RLC entity.

[0095] In some embodiments, the UE 205 sets the ul-DataSplitThreshold to infinity in response to receiving a second control signal from the NE instructing the UE to deactivate duplication. Here, setting the ul-DataSplitThreshold to infinity ensures that only one radio link, for example configured by the ul-DataSplitDRB-ViaSCG, is used for data transmission. In some embodiments, the UE 205 clears the RLC transmission buffers of the "inactive" RLC entities, i.e., the RLC entities of the inactive radio links. Here, once the radio link is reactivated (when duplication is activated again), flushing the PDCP PDUs / RLC PDUs stored in the transmission buffers ensures that those PDUs are not retransmitted, as this may cause TCP to reduce the link rate and / or HFN to lose synchronization. In other embodiments, when duplication is deactivated, the RLC entities of the "inactive" radio links are reestablished.

[0096] In some embodiments, logical channels 530, 535, and 550 may be associated with a token bucket for controlling uplink transmissions. Here, the MAC entities 540-545 maintain a variable Bj for each logical channel j, where Bj represents the state of the token bucket for the logical channel, e.g., the amount of tokens accumulated for the logical channel. In various embodiments, the token bucket state Bj is initialized to zero when the associated logical channel is established, and is incremented by the product PBR×TTI duration for each TTI, where PBR is the priority bit rate of the logical channel j. In some embodiments, when replication is activated, the UE 205 initializes Bj of the previously "inactive" logical channel j to zero (e.g., sets the number of tokens in the bucket of logical channel j to zero). In some embodiments, when replication is disabled, the value of Bj may be initialized to zero for the "inactive" logical channel. In various embodiments, when replication is disabled, the UE 205 does not maintain the token bucket state of the "inactive" logical channel j, e.g., the UE 205 stops incrementing the token bucket state Bj.

[0097] In some embodiments, when duplication is disabled, the UE 205 cancels the triggered scheduling requests and / or buffer status reports, if any, caused by the arrival of data for the "inactive" logical channel. Note that the scheduling requests and / or buffer status reports are triggered by the arrival of data for the now "inactive" logical channel.

[0098] In one embodiment, when duplication is disabled, RLC entities of inactive radio links / cell groups, e.g., a "branch" of a split bearer, are suspended. Here, the corresponding MAC entity does not report buffer status information for the suspended branch of the split bearer. In certain embodiments, the UE 205 flushes the RLC buffer or alternatively reestablishes the "suspended" RLC entity. In one embodiment, the MAC entity (or HARQ entity) discards packets received for the RLC entity of the inactive branch of the split bearer when duplication is disabled. The RLC PDUs of the "inactive" RLC entity / logical channel may still be subject to HARQ retransmissions and therefore arrive after duplication is disabled.

[0099] Figure 6 A protocol stack 600 for duplicating PDCP PDUs for radio bearers in a carrier aggregation environment according to an embodiment of the present disclosure is depicted. Here, the protocol stack 600 is depicted as part of the UE 205. As depicted, the protocol stack 600 includes a first PDCP entity 505 and a second PDCP entity 510. Here, there is one PDCP entity per radio bearer. The PDCP entities 505-510 are located in the PDCP layer of the protocol stack 600 and perform PDCP functions.

[0100] The protocol stack 600 also includes a first RLC entity 515, a second RLC entity 520, and a third RLC entity 525. In the depicted embodiment, the first RLC entity 515 and the second RLC entity 520 belong to the same radio bearer as the first PDCP entity 505. Note that the third RLC entity 525 is associated with the second PDCP entity 510 belonging to the second radio bearer. The RLC entities 515-525 are located in the RLC layer of the protocol stack 500 and perform RLC functions, including (but not limited to) segmenting and reassembling packets to make them suitable for the size of the radio interface. The protocol stack 600 includes a first logical channel 610 associated with the first RLC entity 515, a second logical channel 615 associated with the second RLC entity 520, and a third logical channel 620 associated with the third RLC entity 525.

[0101] In the depicted embodiment, the UE 205 is configured for carrier aggregation and therefore has a single MAC entity 605 associated with the logical channels 610 - 615. The MAC entity 605 is located in the MAC layer of the protocol stack 600 and performs MAC functions.

[0102] In various embodiments, PDCP duplication is used in a CA-based architecture such as supported by the protocol stack 600. A NE such as a gNB configures a UE 205 with a first PDCP entity 505 mapped to two RLC entities 515-520. Here, the PDCP PDU may be mapped to two different logical channels (e.g., logical channels 610-615). In one embodiment, for buffer status reporting purposes, the two logical channels are mapped to different logical channel groups, e.g., separate buffer status is reported for the two logical channels 610-615. The MAC entity 605 ensures that the duplicated PDCP PDU is mapped to different carriers or optionally to different transport blocks (TBs) during the LCP procedure.

[0103] The NE, e.g., gNB, signals the UE 205 with a PDCP duplication configuration, e.g., activation / deactivation of packet duplication. In some embodiments, this signaling may be PDCP control signaling or MAC control signaling. Alternatively, the signaling may be RRC signaling. According to one embodiment, the NE configures the UE 205 with an RLC entity for PDCP data transmission when packet duplication is deactivated. In some embodiments, this configuration may be accomplished via RRC signaling.

[0104] In one embodiment, when duplication is activated, the UE 205 reports the same PDCP buffer occupancy within the buffer status report (BSR) of the two logical channels 610-615 associated with the first PDCP entity 505. Routing of the PDCP PDUs to the two RLC entities is based on the received UL grant, i.e., when the UE 205 receives an UL grant and the MAC entity 605 indicates the amount of data for transmission to one of the two RLC entities / logical channels (as a result of the LCP procedure), the corresponding PDCP PDU is generated, duplicated and may be forwarded to the indicated RLC entity, and may also be forwarded to the other RLC entity / logical channel.

[0105] According to some embodiments, the NE signals to the UE a configuration that directs the UE 205 to use only one RLC entity / logical channel or two RLC entities / logical channels, e.g., to deactivate / activate duplication. As described above, this configuration may be signaled via PDCP control signaling, MAC control signaling, or RRC signaling. In certain embodiments, when the PDCP entity is configured with two logical channels / RLC entities, the default state for duplication is deactivated. Therefore, the NE may need to explicitly activate PDCP duplication.

[0106] In some embodiments, in response to receiving an indication from the NE directing the UE 205 to deactivate repetition, the UE 205 flushes the RLC transmission buffers of the deactivated RLC entities (e.g., RLC entities / logical channels that are not used for data transmission as indicated by the configuration). In some embodiments, the data available for transmission in the PDCP of the "deactivated" logical channels / RLC entities is set to zero. Alternatively, the MAC entity 605 may not report the buffer status information of the deactivated RLC entities / logical channels. According to another embodiment, the UE 205 may reestablish the RLC entities that are not used for data transmission.

[0107] In some embodiments, when the NE instructs the UE 205 to deactivate duplication, the UE 205 suspends the logical channels / RLC entities not used for data transmission. Here, the MAC entity 605 does not report the buffer status information of the suspended logical channels. Alternatively, as described above, the UE 205 can re-establish the RLC entity of the suspended logical channel or flush the RLC buffer.

[0108] In some embodiments, the logical channels 610-620 may be associated with a token bucket for controlling transmission. Here, the MAC entity 605 may maintain a variable Bj for each logical channel j, where Bj represents the state of the token bucket for the logical channel. In various embodiments, the token bucket state Bj is initialized to zero when the relevant logical channel is established, and is incremented by the product PBR×TTI duration for each TTI, where PBR is the priority bit rate of the logical channel j. In some embodiments, when replication is activated (e.g., the number of tokens in the bucket of logical channel j is set to zero), the UE 205 initializes Bj to zero for the previously "inactive" (or suspended) logical channel j. In some embodiments, when replication is disabled, the value of Bj may be initialized to zero for the inactive / suspended logical channels. In various embodiments, when replication is disabled, the UE 205 does not maintain the token bucket state of the "inactive" logical channel j, for example, the UE 205 stops incrementing the token bucket state Bj.

[0109] In some embodiments, if any, the UE 205 cancels the scheduling requests and / or buffer status reports triggered by the arrival of data for the inactivated / suspended logical channels when duplication is deactivated. Note that the scheduling requests and / or buffer status reports are triggered by the arrival of data for the now "inactivated" logical channels.

[0110] In some embodiments, the MAC entity 605 discards packets received for an RLC entity that is suspended or "inactive" when duplication is disabled. Note that RLC PDUs for an "inactive" RLC entity / logical channel may still be subject to HARQ retransmissions and thus arrive after duplication has been disabled.

[0111] Figure 7 A method 700 for duplicating a PDCP PDU of a radio bearer according to an embodiment of the present disclosure is depicted. In some embodiments, the method 700 is performed by a remote unit, such as the remote unit 105, UE 205, and / or user equipment device 300 described above. In some embodiments, the method 700 is performed by a processor executing program code, such as a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, an FPGA, etc.

[0112] The method 700 starts and establishes 705 a radio bearer to communicate with a mobile communication network. Here, the radio bearer includes a PDCP entity, first and second RLC entities associated with the PDCP entity, a first logical channel associated with the first RLC entity, and a second logical channel associated with the second RLC entity.

[0113] The method 700 includes receiving 710 a control signal from a mobile communication network. Here, the control signal activates PDCP duplication at the remote unit. In various embodiments, the control signal may be a PDCP control signal, a MAC control signal, or an RRC signal. In certain embodiments, the first control signal initializes a token bucket state for a previously inactive logical channel, an amount of tokens in the token bucket that is periodically incremented, wherein the previously inactive logical channel is one of the first logical channel and the second logical channel.

[0114] The method 700 includes copying 715 a PDCP data PDU in a PDCP entity. In some embodiments, copying 715 the PDCP data PDU may include indicating the amount of the PDCP data PDU in the PDCP entity to a MAC entity associated with the first RLC entity and a MAC entity associated with the second RLC entity for reporting a buffer status of a logical channel associated with the first RLC entity and the second RLC entity. In one embodiment, the MAC entity associated with the first RLC entity is different from the MAC entity associated with the second RLC entity, for example, where the remote unit is configured with a split bearer. In another embodiment, the MAC entity associated with the first RLC entity is the same as the MAC entity associated with the second RLC entity, for example, where the remote unit is configured for carrier aggregation.

[0115] The method 700 includes submitting 720 the duplicated PDCP data PDU to the first RLC entity and the second RLC entity for transmission. The transmission may be performed according to a UL grant for the first RLC entity and the second RLC entity.

[0116] The method 700 includes: in response to receiving a confirmation of successful transmission of the corresponding one or more PDCP data PDUs through another RLC entity, indicating 725 to one of the first RLC entity and the second RLC protocol entity to discard the one or more duplicate PDCP data PDUs. In some embodiments, the other RLC protocol entity indicates the successful delivery of the corresponding one or more PDCP data PDUs to the PDCP protocol entity based on the RLC status report received from the mobile communication network, and the PDCP protocol entity sends a discard indication to one of the first RLC protocol entity and the second RLC protocol entity in response to receiving the indication of successful delivery to discard the one or more duplicate PDCP data PDUs. The method 700 ends.

[0117] A first device for duplicating a PDCP PDU of a radio bearer is disclosed herein. The first device includes a processor and a transceiver that communicates with a mobile communication network. The processor establishes a radio bearer to communicate with the mobile communication network, and the radio bearer includes a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity associated with the PDCP protocol entity, a first logical channel associated with the first RLC protocol entity, and a second logical channel associated with the second RLC protocol entity. The processor receives a first control signal from the mobile communication network, duplicates a PDCP data protocol data unit ("PDU") in the PDCP protocol entity, and submits the duplicated PDCP data PDU to the first RLC protocol entity and the second RLC protocol entity for transmission in response to the first control signal. In addition, in response to receiving a confirmation that the corresponding one or more PDCP data PDUs are successfully delivered through another RLC protocol entity, the processor instructs one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicated PDCP data PDUs.

[0118] In certain embodiments of the first device, another RLC protocol entity indicates to the PDCP protocol entity the successful delivery of the corresponding one or more PDCP data PDUs based on the RLC status report received from the mobile communication network, and the PDCP protocol entity sends a discard indication to one of the first RLC protocol entity and the second RLC protocol entity in response to receiving the indication of successful delivery to discard the one or more duplicated PDCP data PDUs. In such an embodiment, in response to receiving the discard indication from the PDCP protocol entity, the processor may also discard one or more PDCP data PDUs in one of the first RLC protocol entity and the second RLC protocol entity. In other embodiments of the first device, the processor discards one or more PDCP data PDUs in one of the first RLC protocol entity and the second RLC protocol entity based on the PDCP status report received from the mobile communication network.

[0119] In certain embodiments of the first device, the processor, in response to the first control signal, further indicates the amount of PDCP data PDUs in the PDCP protocol entity to a MAC entity associated with the first RLC protocol entity and a MAC entity associated with the second RLC protocol entity for reporting buffer status of logical channels associated with the first RLC protocol entity and the second RLC protocol entity.

[0120] In some such embodiments, each RLC protocol entity belongs to a different cell group in a mobile communication network, wherein the MAC entity associated with the first RLC protocol entity is a first MAC entity, and the MAC entity associated with the second RLC protocol entity is a second MAC entity different from the first MAC entity, wherein the processor indicates the same amount of PDCP data PDUs in the PDCP protocol entity to the first MAC entity and the second MAC entity for reporting the buffer status of the first logical channel and the second logical channel in the PDCP protocol entity. Here, a separate bearer can be established in the device, and wherein the first control signal includes an indication to copy the PDCP data PDU on the separate bearer. In addition, the processor can set the uplink data separation threshold to zero in response to receiving the first control signal, the first control signal activates packet replication, and set the uplink data separation threshold to infinity in response to receiving the second control signal, the second control signal deactivates data packet replication.

[0121] In other such embodiments, the first RLC protocol entity and the second RLC protocol entity belong to the same cell group, wherein the MAC entity associated with the first RLC protocol entity and the MAC entity associated with the second RLC protocol entity are the same MAC entity, wherein the processor indicates the same amount of PDCP data PDUs in the PDCP protocol entity to the same MAC entity for reporting buffer status of the first logical channel and the second logical channel. Here, the processor may receive a second control signal and deactivate packet duplication, wherein the processor indicates to the MAC entity associated with the second RLC protocol entity for reporting the buffer status of the second logical channel in response to the second control signal that the amount of PDCP data PDUs available for transmission in the PDCP protocol entity is zero. In addition, the processor may receive a third control signal prior to the second control signal, the third control signal indicating the use of the first RLC protocol entity to transmit the PDCP data PDU when packet duplication is deactivated.

[0122] In certain embodiments of the first apparatus, the first control signal instructs the apparatus to begin copying the PDCP data PDU. Here, the processor may receive a second control signal instructing the apparatus to stop copying the PDCP data PDU. In some such embodiments, the processor cancels a scheduling request associated with the second logical channel in response to the second control signal, the scheduling request being triggered by the arrival of data for the second logical channel. In other embodiments, the processor may cancel a buffer status report associated with the second logical channel in response to the second control signal, the buffer status report being triggered by the arrival of data for the second logical channel.

[0123] In some embodiments of the first apparatus, the first control signal initializes a token bucket state for a previously inactive logical channel, the amount of tokens in the token bucket being periodically incremented, wherein the previously inactive logical channel is one of the first logical channel and the second logical channel. In such embodiments, the processor further receives a second control signal that deactivates packet duplication, wherein the processor does not maintain a token bucket associated with the second logical channel in response to the second control signal.

[0124] In some embodiments of the first apparatus, the first control signal is one of: a PDCP control signal, a MAC control signal, and an RRC signal.

[0125] A first method for duplicating PDCP PDUs of a radio bearer is disclosed herein. The first method includes establishing a radio bearer for communicating with a mobile communication network at a remote unit, the radio bearer including a PDCP protocol entity, a first RLC protocol entity and a second RLC protocol entity associated with the PDCP protocol entity, a first logical channel associated with the first RLC protocol entity, and a second logical channel associated with the second RLC protocol entity. The first method includes receiving a first control signal from the mobile communication network at the remote unit, duplicating a PDCP data PDU in the PDCP protocol entity at the remote unit, and submitting the duplicated PDCP PDU to the first RLC protocol entity and the second RLC protocol entity for transmission in response to the first control signal. The first method also includes: in response to receiving a confirmation that the corresponding one or more PDCP data PDUs are successfully transmitted by another RLC protocol entity, instructing one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicated PDCP data PDUs.

[0126] In certain embodiments of the first method, another RLC protocol entity indicates to the PDCP protocol entity the successful delivery of the corresponding one or more PDCP data PDUs based on the RLC status report received from the mobile communication network. Here, the PDCP protocol entity indicates to one of the first RLC protocol entity and the second RLC protocol entity to discard one or more duplicated PDCP data PDUs in response to receiving the indication of successful delivery. In such an embodiment, the first method includes discarding one or more PDCP data PDUs in one of the first RLC protocol entity and the second RLC protocol entity in response to receiving a discard indication from the PDCP protocol entity. In other embodiments, the first method includes discarding one or more PDCP data PDUs in one of the first RLC protocol entity and the second RLC protocol entity based on the PDCP status report received from the mobile communication network.

[0127] In certain embodiments, the first method includes indicating, in response to a first control signal, to a MAC entity associated with the first RLC protocol entity for reporting buffer status of logical channels associated with the first RLC protocol entity and the second RLC protocol entity, and to a MAC entity associated with the second RLC protocol entity, the amount of PDCP data PDUs in the PDCP protocol entity.

[0128] In certain embodiments of the first method, each RLC protocol entity belongs to a different cell group in a mobile communication network, wherein a MAC entity associated with a first RLC protocol entity is a first MAC entity and a MAC entity associated with a second RLC protocol entity is a second MAC entity different from the first MAC entity, wherein a remote unit indicates to a first MAC entity and a second MAC entity for reporting buffer status of a first logical channel and a second logical channel the same amount of PDCP data PDUs in a PDCP protocol entity. In such an embodiment, a separate bearer is established in the remote unit, wherein the first control signal includes an indication to copy the PDCP data PDUs on the separate bearer. In some embodiments, the first method includes setting an uplink data separation threshold to zero in response to receiving a first control signal and setting the uplink data separation threshold to infinity in response to receiving a second control signal, wherein the first control signal activates packet copying and the second control signal deactivates packet copying.

[0129] In certain embodiments of the first method, the first RLC protocol entity and the second RLC protocol entity belong to the same cell group, wherein a MAC entity associated with the first RLC protocol entity and a MAC entity associated with the second RLC protocol are the same MAC entity. In such an embodiment, the first method includes indicating the same amount of PDCP data PDUs in the PDCP protocol entity to the same MAC entity used to report the buffer status of the first logical channel and the second logical channel. In some embodiments, the first method includes receiving a second control signal and deactivating packet duplication, wherein the remote unit indicates to the MAC entity associated with the second RLC protocol entity used to report the buffer status of the second logical channel in response to the second control signal that the amount of PDCP data PDUs available for transmission in the PDCP protocol entity is zero. In some embodiments, the first method includes receiving a third control signal prior to the second control signal, the third control signal indicating that the first RLC protocol entity is used to transmit the PDCP data PDUs when packet duplication is deactivated.

[0130] In certain embodiments of the first method, the first control signal instructs the remote unit to start copying the PDCP data PDU, and the first method further comprises receiving a second control signal instructing the remote unit to stop copying the PDCP data PDU. In some embodiments, the first method comprises: in response to the second control signal, canceling a scheduling request associated with the second logical channel, the scheduling request being triggered by the arrival of data for the second logical channel. In some embodiments, the first method comprises canceling a buffer status report associated with the second logical channel in response to the second control signal, the buffer status report being triggered by the arrival of data for the second logical channel.

[0131] In some embodiments, the first method includes initializing a token bucket state for a previously inactive logical channel, the amount of tokens in the token bucket being periodically incremented, wherein the previously inactive logical channel is one of a first logical channel and a second logical channel. In such an embodiment, the first method may include receiving a second control signal that deactivates packet duplication, wherein the remote unit does not maintain a token bucket associated with the second logical channel in response to the second control signal. In various embodiments of the first method, the first control signal is one of: a PDCP control signal, a MAC control signal, and an RRC signal.

[0132] Embodiments may be practiced in other specific forms. The described embodiments should be considered in all respects as merely illustrative and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than the preceding description. All changes within the meaning and equivalent range of the claims are included within their scope.

Claims

1. A method for replicating a packet data convergence protocol PDCP protocol data unit PDU, comprising: At a user equipment UE, a radio bearer is established, the radio bearer comprising a PDCP entity, a first radio link control RLC entity and a second RLC entity associated with the PDCP entity, a first logical channel associated with the first RLC entity, and a second logical channel associated with the second RLC entity; At the UE, receiving a first control signal; In response to the received first control signal, duplicating, at the UE, a PDCP data PDU in the PDCP entity, and submitting the duplicated PDCP data PDU to the first RLC entity and the second RLC entity for transmission, respectively; receiving, at the PDCP entity and from one of the first RLC entity and the second RLC entity, an acknowledgement of successful transmission of the PDCP data PDU, and The other of the first RLC entity and the second RLC entity is instructed to discard a duplicated PDCP data PDU corresponding to a successfully transmitted PDCP data PDU.

2. The method according to claim 1, wherein: One of the first RLC entity and the second RLC entity indicates the successful transmission of the PDCP data PDU to the PDCP entity based on an RLC status report.

3. The method according to claim 1, further comprising: The duplicated PDCP data PDU in the other of the first RLC entity and the second RLC entity is discarded based on a PDCP status report confirming the successful transmission of the PDCP data PDU.

4. The method according to claim 1, further comprising: indicating to a media access control MAC entity associated with the first RLC entity an amount of PDCP data PDUs in the PDCP entity for reporting a first buffer status of the first logical channel, and The amount of the PDCP data PDUs in the PDCP entity is indicated to a MAC entity associated with the second RLC entity for reporting a second buffer status of the second logical channel.

5. The method according to claim 4, in, Each of the RLC entities belongs to a different cell group, wherein the MAC entity associated with the first RLC entity is a first MAC entity and the MAC entity associated with the second RLC entity is a second MAC entity different from the first MAC entity, Therein, indicating the amount of the PDCP data PDU in the PDCP entity includes indicating the same amount of PDCP data PDU to the first MAC entity and the second MAC entity.

6. The method according to claim 5, wherein: The radio bearer comprises a split bearer, and wherein the first control signal comprises an indication to activate PDCP duplication on the split bearer.

7. The method according to claim 4, in, The first RLC entity and the second RLC entity belong to the same cell group, wherein the MAC entity associated with the first RLC entity and the MAC entity associated with the second RLC entity are the same MAC entity, Wherein, indicating the amount of the PDCP data PDU in the PDCP entity includes indicating the same amount of PDCP data PDU to the same MAC entity.

8. The method according to claim 4, further comprising: receiving a second control signal and deactivating packet duplication, In response to the second control signal, indicating to a MAC entity associated with the second RLC entity that the amount of PDCP data PDUs available for transmission in the PDCP entity for reporting a buffer status of the second logical channel is zero.

9. The method according to claim 8, further comprising: A third control signal is received prior to the second control signal, the third control signal indicating to use the first RLC entity for transmission of PDCP data PDUs when packet duplication is deactivated.

10. The method according to claim 1, wherein: The first control signal indicates activation of PDCP duplication, and the method further includes receiving a second control signal indicating deactivation of the PDCP duplication.

11. The method according to claim 10, further comprising: In response to receiving the first control signal, setting an uplink data separation threshold of the radio bearer to zero, and In response to receiving the second control signal, an uplink data separation threshold of the radio bearer is set to infinity.

12. The method according to claim 10, further comprising: In response to the second control signal, a scheduling request associated with the second logical channel is cancelled, the scheduling request being triggered by arrival of data of the second logical channel.

13. The method according to claim 10, further comprising: In response to the second control signal, a buffer status report associated with the second logical channel is cancelled, the buffer status report being triggered by arrival of data of the second logical channel.

14. The method according to claim 1, wherein: The first control signal is one of the following: a PDCP control signal, a MAC control signal, and an RRC signal.

15. A user equipment UE for replicating a packet data convergence protocol PDCP protocol data unit PDU, comprising: a transceiver for communicating with a mobile communications network; as well as A processor, the processor: establishing a radio bearer, the radio bearer comprising a PDCP entity, a first radio link control RLC entity and a second RLC entity associated with the PDCP entity, a first logical channel associated with the first RLC entity, and a second logical channel associated with the second RLC entity; receiving a first control signal; In response to the received first control signal, copy the PDCP data PDU in the PDCP entity, and submit the copied PDCP data PDU to the first RLC entity and the second RLC entity for transmission, respectively, wherein the PDCP entity receives a confirmation of successful transmission of the PDCP data PDU from one of the first RLC entity and the second RLC entity, and The PDCP entity instructs the other of the first RLC entity and the second RLC entity to discard a duplicate PDCP data PDU corresponding to the successfully transmitted PDCP data PDU.

16. The UE according to claim 15, wherein: One of the first RLC entity and the second RLC entity indicates successful transmission of the PDCP data PDU to the PDCP entity based on an RLC status report.

17. The UE according to claim 15, wherein: The processor discards the duplicated PDCP data PDU in the other of the first RLC entity and the second RLC entity based on a PDCP status report.

18. The UE according to claim 15, wherein: The processor also indicates the amount of PDCP data PDUs in the PDCP entity to a media access control MAC entity associated with the first RLC entity, and indicates the amount of PDCP data PDUs in the PDCP entity to a MAC entity associated with the second RLC, for reporting buffer status of logical channels associated with the first RLC entity and the second RLC entity.

19. The UE according to claim 18, wherein: Each of the RLC entities belongs to a different cell group, wherein the MAC entity associated with the first RLC entity is a first MAC entity and the MAC entity associated with the second RLC entity is a second MAC entity different from the first MAC entity, wherein the processor indicates to the first MAC entity and the second MAC entity the same amount of PDCP data PDUs in the PDCP entity for reporting the buffer status of the first logical channel and the second logical channel.

20. The UE according to claim 18, wherein: The first RLC entity and the second RLC entity belong to the same cell group, wherein a MAC entity associated with the first RLC entity and a MAC entity associated with the second RLC entity are the same MAC entity, wherein the processor indicates to the same MAC entity the same amount of PDCP data PDUs in the PDCP entity for reporting the buffer status of the first logical channel and the second logical channel.

Citation Information

Patent Citations

  • Wireless communication in multi-RAT system

    CN104782223A

  • Method and apparatus for improved multi-carrier communication

    CN106464465A