Measuring the performance of packet data convergence protocol repetition

Abstract

In summary, various aspects of the present disclosure relate to wireless communications. In some aspects, a wireless communication device may detect a trigger for initiating a determination of a performance parameter for a Packet Data Convergence Protocol (PDCP) repetition procedure associated with a PDCP instance. The wireless communication device may receive packets of the PDCP instance via multiple radio link control (RLC) entities according to the PDCP repetition procedure. The wireless communication device may determine the performance parameter based at least in part on whether the packets of the PDCP instance are successfully received via one or more of the multiple RLC entities. A number of other aspects are provided.

Description

Technical Field

[0001]

[0006] Generally speaking, aspects of the present disclosure relate to wireless communications and to techniques and apparatus for measuring performance of Packet Data Convergence Protocol (PDCP) repetitions. Background Art

[0002] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single carrier frequency division multiple access (SC-FDMA) systems, time division synchronous code division multiple access (TD-SCDMA) systems, and long term evolution (LTE). LTE / LTE-Advanced is a set of enhancements to the Universal Mobile Telecommunications System (UMTS) mobile standard released by the Third Generation Partnership Project (3GPP).

[0003] A wireless communication network may include several base stations (BS) that can support communications for several user equipments (UEs). User equipments (UEs) may communicate with base stations (BSs) via downlinks and uplinks. A downlink (or forward link) refers to a communication link from a BS to a UE, while an uplink (or reverse link) refers to a communication link from a UE to a BS. As will be described in more detail herein, a BS may be referred to as a Node B, gNB, access point (AP), radio head, transmit receive point (TRP), new radio (NR) BS, 5G Node B, etc.

[0004] The above multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different user equipment to communicate at the city, country, region, and even global level. New Radio (NR) (which may also be referred to as 5G) is an enhanced set of LTE mobile standards released by the Third Generation Partnership Project (3GPP). NR is designed to be better integrated with other open standards by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and using orthogonal frequency division multiplexing (OFDM) (CP-OFDM) with cyclic prefix (CP) on the downlink (DL), using CP-OFDM and / or SC-FDM (e.g., also referred to as discrete Fourier transform spread OFDM (DFT-s-OFDM)) on the uplink (UL), and supporting beamforming, multiple input multiple output (MIMO) antenna technology and carrier aggregation, so as to better support mobile broadband Internet access. However, as the demand for mobile broadband access continues to grow, there is a need for further improvements in LTE and NR technologies. Preferably, these improvements should be applicable to other multiple access technologies and telecommunication standards that adopt these technologies. Summary of the invention

[0005] In some aspects, a method of wireless communication performed by a wireless communication device may include: detecting a trigger for initiating a determination of a performance parameter for a Packet Data Convergence Protocol (PDCP) repetition process associated with a PDCP instance; receiving packets of the PDCP instance via multiple radio link control (RLC) entities according to the PDCP repetition process; and determining the performance parameter based at least in part on whether the packets of the PDCP instance are successfully received via one or more of the multiple RLC entities.

[0006] In some aspects, a wireless communication device for wireless communication may include a memory and one or more processors operatively coupled to the memory. The memory and the one or more processors may be configured to: detect a trigger for initiating a determination of a performance parameter for a PDCP repetition procedure associated with a PDCP instance; receive packets of the PDCP instance via multiple RLC entities in accordance with the PDCP repetition procedure; and determine the performance parameter based at least in part on whether the packets of the PDCP instance are successfully received via one or more of the multiple RLC entities.

[0007] In some aspects, a non-transitory computer-readable medium may store one or more instructions for wireless communication. The one or more instructions, when executed by one or more processors of a wireless communication device, may cause the one or more processors to perform the following operations: detecting a trigger for initiating a determination of a performance parameter for a PDCP repetition procedure associated with a PDCP instance; receiving a packet of the PDCP instance via a plurality of RLC entities in accordance with the PDCP repetition procedure; and determining the performance parameter based at least in part on whether the packet of the PDCP instance is successfully received via one or more of the plurality of RLC entities.

[0008] In some aspects, an apparatus for wireless communication may include: a unit for detecting a trigger for initiating a determination of a performance parameter for a PDCP repetition process associated with a PDCP instance; a unit for receiving packets of the PDCP instance via multiple RLC entities according to the PDCP repetition process; and a unit for determining the performance parameter based at least in part on whether the packets of the PDCP instance are successfully received via one or more RLC entities among the multiple RLC entities.

[0009] In summary, aspects include methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, wireless communication devices, and / or processing systems as fully described herein with reference to and as illustrated by the accompanying drawings and description.

[0010] The foregoing has been fairly broadly outlined according to the features and technical advantages of the examples of the present disclosure, so that the following detailed description may be better understood. Additional features and advantages will be described below. The disclosed concepts and specific examples may be easily used as the basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood according to the description below. Each of the figures in the accompanying drawings is provided for the purpose of illustration and description, and not as a definition of the limitations of the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to fully understand the above features of the present disclosure, a more specific description briefly summarized above can be obtained by referring to various aspects (some of which are shown in the accompanying drawings). However, it should be noted that the accompanying drawings only illustrate certain typical aspects of the present disclosure and are therefore not to be considered as limiting the scope of the present disclosure, because the description may allow for other equally effective aspects. The same reference numerals in different drawings may identify the same or similar elements.

[0012] Figure 1 is a diagram illustrating an example of a wireless communication network in accordance with various aspects of the present disclosure.

[0013] Figure 2 is a diagram illustrating an example of a base station communicating with a UE in a wireless communication network according to various aspects of the present disclosure.

[0014] Figure 3 is a diagram illustrating an example of PDCP repetition in accordance with various aspects of the present disclosure.

[0015] Figure 4-Figure 8 is a diagram illustrating an example of measuring performance of PDCP repetition according to various aspects of the present disclosure.

[0016] Fig. 9 is a diagram illustrating an example process, for example, performed by a wireless communication device, in accordance with various aspects of the present disclosure. DETAILED DESCRIPTION

[0017] The following is a more complete description of various aspects of the present disclosure with reference to the accompanying drawings. However, the present disclosure can be embodied in many different forms and should not be construed as being limited to any specific structure or function presented throughout the present disclosure. More specifically, these aspects are provided so that the present disclosure will be thorough and complete, and the scope of the present disclosure will be fully conveyed to those skilled in the art. Based on the teachings herein, it should be understood by those skilled in the art that the scope of the present disclosure is intended to cover any aspect of the present disclosure disclosed herein, whether the aspect is implemented independently of any other aspect of the present disclosure or implemented in combination with any other aspect. For example, using any number of aspects set forth herein, a device can be implemented or a method can be implemented. In addition, the scope of the present disclosure is intended to cover such a device or method implemented using other structures, functions, or structures and functions other than the various aspects of the present disclosure set forth herein or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein can be embodied by one or more elements of the claims.

[0018] Several aspects of telecommunication systems will now be presented with reference to various devices and techniques. These devices and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using hardware, software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0019] It should be noted that although various aspects may be described herein using terms commonly associated with 3G and / or 4G wireless technologies, various aspects of the present disclosure may be applied to communication systems based on other generations, such as 5G and beyond (including NR technologies).

[0020] Figure 1 1 is a diagram showing a wireless network 100 in which various aspects of the present disclosure may be implemented. The wireless network 100 may be an LTE network or some other wireless network (such as a 5G or NR network). The wireless network 100 may include several BSs 110 (shown as BS 110a, BS 110b, BS 110c, and BS 110d) and other network entities. A BS is an entity that communicates with a user equipment (UE) and may also be referred to as a base station, NR BS, Node B, gNB, 5G Node B (NB), access point, transmit receive point (TRP), etc. Each BS may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to a coverage area of ​​a BS and / or a BS subsystem serving the coverage area, depending on the context in which the term is used.

[0021] A BS may provide communication coverage for a macro cell, a pico cell, a femto cell, and / or another type of cell. A macro cell may cover a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscription. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG)). A BS for a macro cell may be referred to as a macro BS. A BS for a pico cell may be referred to as a pico BS. A BS for a femto cell may be referred to as a femto BS or a home BS. In Figure 1 In the example shown in , BS 110a may be a macro BS for macro cell 102a, BS 110b may be a pico BS for pico cell 102b, and BS 110c may be a femto BS for femto cell 102c. A BS may support one or more (e.g., three) cells. The terms "eNB", "base station", "NR BS", "gNB", "TRP", "AP", "Node B", "5G NB", and "cell" may be used interchangeably herein.

[0022] In some aspects, the cells may not necessarily be stationary, and the geographic area of ​​the cells may move depending on the location of the mobile BS. In some aspects, the BSs may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless network 100 through various types of backhaul interfaces (such as direct physical connections, virtual networks, etc.) using any suitable transport network.

[0023] The wireless network 100 may also include a relay station. A relay station is an entity that can receive data transmissions from an upstream station (e.g., a BS or a UE) and send data transmissions to a downstream station (e.g., a UE or a BS). A relay station may also be a UE that can relay transmissions for other UEs. Figure 1 In the example shown in FIG. 1 , a relay station 110 d may communicate with a macro BS 110 a and a UE 120 d to facilitate communication between the BS 110 a and the UE 120 d. A relay station may also be referred to as a relay BS, a relay base station, a relay, or the like.

[0024] The wireless network 100 may be a heterogeneous network including different types of BSs (e.g., macro BSs, pico BSs, femto BSs, relay BSs, etc.). These different types of BSs may have different transmit power levels, different coverage areas, and different effects on interference in the wireless network 100. For example, a macro BS may have a high transmit power level (e.g., 5 to 40 watts), while a pico BS, a femto BS, and a relay BS may have a lower transmit power level (e.g., 0.1 to 2 watts).

[0025] The network controller 130 may be coupled to a set of BSs and may provide coordination and control for these BSs. The network controller 130 may communicate with the BSs via a backhaul. The BSs may also communicate with each other, for example, directly or indirectly, via a wireless backhaul or a wired backhaul.

[0026] UE 120 (e.g., 120a, 120b, 120c) can be dispersed throughout the wireless network 100, and each UE can be stationary or mobile. UE can also be referred to as an access terminal, terminal, mobile station, subscriber unit, station, etc. UE can be a cellular phone (e.g., a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet device, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device or apparatus, a biometric sensor / device, a wearable device (smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.)), an entertainment device (e.g., a music or video device, or a satellite radio unit), a vehicle component or sensor, a smart meter / sensor, an industrial manufacturing device, a global positioning system device, or any other suitable device configured to communicate via a wireless medium or a wired medium.

[0027] Some UEs may be considered as machine type communication (MTC) or evolved or enhanced machine type communication (eMTC) UEs. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which may communicate with a base station, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, a connection to a network (e.g., a wide area network such as the Internet or a cellular network) or a connection to a network via a wired communication link or a wireless communication link. Some UEs may be considered as Internet of Things (IoT) devices, and / or may be implemented as NB-IoT (narrowband Internet of Things) devices. Some UEs may be considered as user premises equipment (CPE). UE 120 may be included inside a housing that houses components of UE 120 (such as a processor component, a memory component, etc.).

[0028] Generally, any number of wireless networks can be deployed in a given geographic area. Each wireless network can support a specific RAT and can operate on one or more frequencies. RAT can also be referred to as radio technology, air interface, etc. Frequency can also be referred to as carrier, frequency channel, etc. Each frequency can support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, NR or 5G RAT networks can be deployed.

[0029] In some aspects, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) may communicate directly using one or more sidelink channels (e.g., without using base station 110 as an intermediary for communicating with each other). For example, UE 120 may communicate using peer-to-peer (P2P) communication, device-to-device (D2D) communication, vehicle-to-everything (V2X) protocol (e.g., which may include vehicle-to-vehicle (V2V) protocol, vehicle-to-infrastructure (V2I) protocol, etc.), mesh network, etc. In this case, UE 120 may perform scheduling operations, resource selection operations, and / or other operations described elsewhere herein as being performed by base station 110.

[0030] As pointed out above, Figure 1 is provided as an example. Other examples may differ from those described above. Figure 1 Examples described.

[0031] Figure 2 A block diagram of a design 200 of a base station 110 and a UE 120 is shown, which may be Figure 1 Base station 110 may be equipped with T antennas 234a through 234t, and UE 120 may be equipped with R antennas 252a through 252r, where in general, T≥1 and R≥1.

[0032] At the base station 110, the transmit processor 220 may receive data for one or more UEs from the data source 212, select one or more modulation and coding schemes (MCS) for each UE based at least in part on a channel quality indicator (CQI) received from the UE, process (e.g., encode and modulate) the data for the UE based at least in part on the MCS selected for each UE, and provide data symbols for all UEs. The transmit processor 220 may also process system information (e.g., for semi-static resource partitioning information (SRPI), etc.) and control information (e.g., CQI requests, grants, upper layer signaling, etc.), and provide overhead symbols and control symbols. The transmit processor 220 may also generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS)) and synchronization signals (e.g., primary synchronization signals (PSS) and secondary synchronization signals (SSS)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, overhead symbols, and / or reference symbols, if applicable, and may provide T output symbol streams to T modulators (MOD) 232a to 232t. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. T downlink signals from modulators 232a to 232t may be sent via T antennas 234a to 234t, respectively. According to various aspects described in more detail below, a synchronization signal may be generated using position coding to convey additional information.

[0033] At UE 120, antennas 252a to 252r may receive downlink signals from base station 110 and / or other base stations, and may provide received signals to demodulators (DEMODs) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) the received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 256 may obtain received symbols from all R demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. Receive processor 258 may process (e.g., demodulate and decode) the detected symbols, provide decoded data for UE 120 to data sink 260, and provide decoded control information and system information to controller / processor 280. The channel processor may determine reference signal received power (RSRP), received signal strength indicator (RSSI), reference signal received quality (RSRQ), channel quality indicator (CQI), etc. In some aspects, one or more components of UE 120 may be included in a housing.

[0034] On the uplink, at the UE 120, a transmit processor 264 may receive and process data from a data source 262 and control information from a controller / processor 280 (e.g., for reports including RSRP, RSSI, RSRQ, CQI, etc.). The transmit processor 264 may also generate reference symbols for one or more reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for DFT-s-OFDM, CP-OFDM, etc.), and sent to the base station 110. At the base station 110, uplink signals from the UE 120 and other UEs may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120. The receive processor 238 may provide decoded data to a data sink 239 and provide decoded control information to a controller / processor 240. The base station 110 may include a communication unit 244 and communicate with the network controller 130 via the communication unit 244. The network controller 130 may include a communication unit 294, a controller / processor 290, and a memory 292.

[0035] The controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2Any other component in the controller / processor 240 of the base station 110, the controller / processor 280 of the UE 120, and / or Figure 2 Any other component in may perform or direct e.g. Fig. 9 The operations of process 900 and / or other processes as described herein. Memories 242 and 282 may store data and program codes for base station 110 and UE 120, respectively. In some aspects, memory 242 and / or memory 282 may include a non-transitory computer-readable medium storing one or more instructions for wireless communication. For example, one or more instructions, when executed by one or more processors of base station 110 and / or UE 120, may perform or direct, for example, Fig. 9 The process 900 and / or operations of other processes as described herein. The scheduler 246 can schedule UEs for data transmission on the downlink and / or uplink.

[0036] In some aspects, the UE 120 may include: means for detecting a trigger for initiating determination of a performance parameter for a PDCP repetition procedure associated with a PDCP instance; means for receiving a packet of the PDCP instance via a plurality of RLC entities according to the PDCP repetition procedure; means for determining the performance parameter based at least in part on whether the packet of the PDCP instance is successfully received via one or more of the plurality of RLC entities; etc. In some aspects, such means may include in conjunction with Figure 2 One or more components of UE 120 are depicted, such as controller / processor 280, transmit processor 264, TX MIMO processor 266, MOD 254, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, etc.

[0037] In some aspects, the base station 110 may include: a unit for detecting a trigger for initiating a determination of a performance parameter for a PDCP repetition procedure associated with a PDCP instance; a unit for receiving a packet of the PDCP instance via a plurality of RLC entities according to the PDCP repetition procedure; a unit for determining the performance parameter based at least in part on whether the packet of the PDCP instance is successfully received via one or more of the plurality of RLC entities; etc. In some aspects, such a unit may include a unit for initiating a determination of a performance parameter for a PDCP repetition procedure associated with a PDCP instance; a unit for receiving a packet of the PDCP instance via a plurality of RLC entities according to the PDCP repetition procedure; a unit for determining the performance parameter based at least in part on whether the packet of the PDCP instance is successfully received via one or more of the plurality of RLC entities; etc. Figure 2 One or more components of base station 110 are depicted, such as antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, transmit processor 220, TX MIMO processor 230, MOD 232, antenna 234, and the like.

[0038] As pointed out above, Figure 2 is provided as an example. Other examples may differ from those described above. Figure 2 Examples described.

[0039] Figure 3 300 is a diagram illustrating an example of PDCP repetition according to various aspects of the present disclosure. A wireless communication device, such as a base station, may communicate with another wireless communication device, such as a UE, using PDCP. PDCP occurs in a PDCP layer located above the RLC layer in the radio protocol stack, below the Internet Protocol (IP) layer in the user plane, and below the Radio Resource Control (RRC) layer in the control plane. A wireless communication device may use the PDCP layer to interface with the outside world, and the PDCP layer may implement integrity protection, ciphering, and header compression of packets received from upper layers (e.g., IP, RRC, etc.).

[0040] When using the PDCP layer, the wireless communication device can repeat the transmission path to improve reliability and reduce latency (for example, for ultra-reliable low latency communication or URLLC). When PDCP repetition is configured for a radio bearer via RRC signaling, the wireless communication device can add a second RLC entity for a second logical channel to the radio bearer to handle repeated packets. Packets are also referred to as packet data units or protocol data units (PDUs) in this article. That is, PDCP repetition involves sending the same PDCP PDU on two or more RLC entities. The PDCP repetition process can be associated with a PDCP instance for a radio bearer. Note that the transmission path through the RLC entity can also be referred to as an RLC branch. The wireless communication device can use, for example, a medium access control (MAC) command element (CE) to activate or deactivate PDCP repetition for a dedicated radio bearer (DRB).

[0041] In scenarios involving dual connectivity (DC) or carrier aggregation (CA), the wireless communication device may be configured for PDCP repetition. Figure 3 , and as indicated by reference numeral 305, the DC PDCP duplication may involve two further RLC entities associated with different MAC entities. For example, the primary RLC entity (e.g., user plane anchor) is associated with one MAC entity for component carriers CC1, CC2, and the secondary RLC entity is associated with a different MAC entity for component carriers CC3, CC4. On the other hand, as in Figure 3, and as shown by reference numeral 310, CA PDCP duplication may involve two or more RLC entities associated with the same MAC entity. For example, one RLC entity for CC1 and CC2 is associated with the same MAC entity as another RLC entity for CC3 and CC4.

[0042] Additionally or alternatively, during a scenario involving a handover process, PDCP repetition may be enabled. For example, a wireless communication device may use PDCP repetition as part of a make-before-break handover (MBB HO) process. During the MBB HO process, if the wireless communication device is being handed over, the wireless communication device establishes a source connection with a source base station and a target connection with a target base station. Once the establishment for the target connection is successful, the wireless communication device may send the same PDCP PDU for each connection on two or more RLC entities. This will provide additional reliability until the source connection is released.

[0043] In any of these scenarios, if the wireless communication device does not efficiently use the RLC entities during the PDCP repetition, this may result in wasted resources and increased latency. For example, if the wireless communication device underutilizes one of its RLC entities during the PDCP repetition, the wireless communication device does not send all necessary PDCP PDUs on the underutilized RLC entity to perform the PDCP repetition. This underutilization may be due to the PDCP PDUs being slowed down or dropped on the transmission path for that particular RLC entity. Unfortunately, this underutilization is not addressed because the wireless communication device does not measure the performance of the PDCP repetition.

[0044] As described herein, some aspects configure a wireless communication device to measure the performance of PDCP repetition. A wireless communication device (e.g., a base station, a UE, etc.) may measure the performance of PDCP repetition by determining a performance parameter of a PDCP repetition process (e.g., the number or percentage of PDUs received on an RLC entity). For example, the wireless communication device may detect a trigger for initiating a determination of a performance parameter for a PDCP repetition process associated with a PDCP instance. The wireless communication device may receive a PDU of a PDCP instance via multiple RLC entities according to the PDCP repetition process. The wireless communication device may determine the performance parameter based at least in part on whether the PDU of the PDCP instance is successfully received via one or more RLC entities of the multiple RLC entities.

[0045] In some aspects, the wireless communication device may modify the configuration of the RLC entity for PDCP repetition based at least in part on the determined performance parameters. For example, the wireless communication device may deactivate the use of RLC entities that are not fully used for PDCP repetition, add more RLC entities for the associated MAC entities for PDCP repetition, and / or reconfigure PDCP repetition for the MAC entity. In this way, the wireless communication device may not waste processing resources, power resources and / or channel resources by using RLC entities that are inefficient for PDCP repetition. In addition or alternatively, the configuration of the RLC entity for PDCP repetition can be optimized. Therefore, network reliability and latency can be improved compared to PDCP instances in which PDCP repetitions are not measured.

[0046] As pointed out above, Figure 3 is provided as an example. Other examples may differ from those described above. Figure 3 Examples described.

[0047] Figure 4 4 is a diagram illustrating an example 400 of measuring the performance of PDCP repetitions in accordance with various aspects of the present disclosure. Figure 4 As shown, a wireless communication device (eg, base station 110) may use PDCP to communicate with another wireless communication device (eg, UE 120), as described above in conjunction with Figure 3 Descriptive.

[0048] As indicated by reference numeral 405, in order to perform PDCP repetition, the base station 110 may transmit PDUs (PDCP PDUs) of a PDCP instance via a plurality of RLC entities (such as RLC1 and RLC2). Figure 4 1 shows that the base station 110 sends the PDU of the PDCP instance to the UE 120 via multiple RLC entities, but alternatively, the UE 120 can send the PDU of the PDCP instance to the base station 110. Figure 4 As depicted in FIG. 1 , certain operations are described with respect to base station 110 and UE 120, but base station 110 may perform the operations described herein with respect to UE 120, and vice versa.

[0049] As indicated by reference numeral 410, the UE 120 may detect a trigger for initiating a determination of a performance parameter for PDCP repetition. For example, the UE 120 may detect that the data rate of the PDU of the PDCP instance meets a threshold for one or more RLC entities in a plurality of RLC entities as a trigger. The UE 120 may measure the data rate based at least in part on the performance parameters determined in the PDCP layer or the MAC layer. In some aspects, if the UE 120 is to determine the performance parameters in the PDCP layer, the UE 120 may measure the data rate after discarding the duplicated PDUs in the PDCP layer. This allows the UE 120 to calculate the effective data rate for each RLC entity. If the UE 120 is to determine the performance parameters in the MAC layer, the UE 120 may measure the data rate of each duplicated logical channel or RLC entity.

[0050] Additionally or alternatively, the UE 120 may detect that the number or percentage of time slots in which the PDUs of the PDCP instance are received meets a threshold for one or more RLC entities in the plurality of RLC entities as a trigger. In some aspects, the UE 120 may attempt to utilize each RLC entity, and thus the number or percentage of the time slots identified above may be determined for each RLC entity. In some aspects, the UE 120 may be configured such that the UE 120 detects triggers for a particular RLC entity based at least in part on past utilization. Thus, the UE 120 may determine the number or percentage of the time slots identified above for a subset of RLC entities (such as those RLC entities that are already more efficient or have discarded fewer PDUs). In some aspects, the UE 120 may determine the number or percentage of the time slots identified above for different subsets of RLC entities (such as those RLC entities that are not more efficient or have regularly discarded PDUs).

[0051] Additionally or alternatively, the UE 120 may detect as a trigger the number or percentage of unsuccessfully received PDUs of the PDCP instance that meet a threshold for one or more of the multiple RLC entities. This may include, for example, the number or percentage of RLC PDUs with corresponding negative acknowledgement (NAK) messages indicating that the transmission of the PDU was unsuccessful or failed. The UE 120 may determine and report the number of NAK PDUs received within a specific time period. The UE 120 may report the number based at least in part on a comparison of the number of NAK PDUs with a threshold, an average, a maximum, and / or a minimum value of the NAK PDUs.

[0052] Additionally or alternatively, UE 120 may detect that the number or percentage of retransmissions of the PDU of the PDCP instance meets the threshold for one or more RLC entities in multiple RLC entities as a trigger. In some aspects, one or more thresholds may correspond to a histogram of the number or percentage of retransmissions for each RLC entity. In some aspects, UE 120 may determine a count of retransmissions for each RLC entity and record the count in a histogram. If an RLC entity has a number or percentage of retransmissions less than another RLC entity, less than all other RLC entities, less than a threshold number of RLC entities and / or falls into a specific histogram grouping, UE 120 may consider that the RLC entity is efficient relative to other RLC entities. In some aspects, UE 120 may consider the number or percentage of retransmissions specifically for uplink PDCP repetitions. The histogram may be used for other performance parameters, such as other performance parameters described herein.

[0053] As indicated by reference numeral 415, the UE 120 may determine a performance parameter (e.g., a key performance indicator or KPI) based at least in part on whether the PDUs of the PDCP instance are successfully received via one or more of the plurality of RLC entities. For example, the UE 120 may determine a performance parameter indicating a number or percentage of PDUs of the PDCP instance that are successfully received via all of the plurality of RLC entities. The performance parameter may correspond to a performance parameter index (e.g., a KPI index of 1) that indicates similar performance for all of the RLC entities.

[0054] Additionally or alternatively, UE 120 may determine a performance parameter indicating a number or percentage of PDUs of the PDCP instance that are successfully received via a particular RLC entity among the plurality of RLC entities, and / or indicating a number or percentage of PDUs of the PDCP instance that are successfully received via a first RLC entity (RLC 1) among the plurality of RLC entities and that are not successfully received via any other RLC entity among the plurality of RLC entities. From a reliability perspective, the performance parameter may correspond to a performance parameter index (e.g., a KPI index of 2) of outstanding performance of certain RLC entities (e.g., an RLC entity having a higher number of successful transmissions than most other RLC entities).

[0055] Additionally or alternatively, UE 120 may determine a performance parameter indicating the number or percentage of PDUs of the PDCP instance that are successfully received via a first RLC entity (RLC 1) among the plurality of RLC entities and unsuccessfully received via a second RLC entity (RLC2) among the plurality of RLC entities. From a reliability perspective, the performance parameter may correspond to another performance parameter index (e.g., a KPI of 3) of outstanding performance of certain RLC entities.

[0056] Additionally or alternatively, UE 120 may determine a performance parameter indicating a number or percentage of PDUs of a PDCP instance that are successfully received via a first RLC entity of the plurality of RLC entities at an earlier time than all other RLC entities of the plurality of RLC entities, and / or indicating a number or percentage of PDUs of a PDCP instance that are successfully received via a first RLC entity of the plurality of RLC entities at an earlier time than a second RLC entity of the plurality of RLC entities. The performance parameter may correspond to a performance parameter index (e.g., a KPI of 4) of outstanding performance of certain RLC entities from a latency perspective.

[0057] Additionally or alternatively, UE 120 may determine a performance parameter indicating the number or percentage of PDUs of the PDCP instance that were not successfully received via any of the plurality of RLC entities and / or indicating the number or percentage of PDUs of the PDCP instance that were not successfully received via a particular RLC entity of the plurality of RLC entities. The performance parameter may correspond to a performance parameter index (e.g., a KPI of 5) of "bad" performance for all RLC entities, or for an RLC entity that is less efficient and / or discards more PDUs than most other RLC entities.

[0058] Additionally or alternatively, UE 120 may determine a performance parameter indicating a number or percentage of PDUs of a PDCP instance that are cancelled or discarded for a particular RLC entity among the multiple RLC entities due to successful reception via another RLC entity among the multiple RLC entities. The performance parameter may correspond to a performance parameter index for PDCP duplicate cancellation (e.g., a KPI index of 6).

[0059] The above performance parameters are intended as examples of performance parameters that may be determined by UE 120, and in some aspects, UE 120 may determine other types of performance parameters. In some aspects, UE 120 may determine one or more performance parameters for each RLC entity. For example, UE 120 may determine multiple performance parameters for one or more RLC entities.

[0060] In some aspects, the PDCP repetition process may be performed in the uplink or downlink direction. In some aspects where the wireless communication device is a UE 120, the PDCP repetition process may be a downlink PDCP repetition process, and a plurality of RLC entities may be configured in an RLC confirmation mode or an RLC unconfirmed mode. In the RLC confirmation mode, if the UE 120 receives a PDU with any error, the base station 110 may retransmit the PDU. In the RLC unconfirmed mode, the base station 110 may not retransmit the PDU with error received by the UE 120. The RLC unconfirmed mode may be used for delay-sensitive PDUs, such as for audio and video streams. In some aspects where the wireless communication device is a UE 120, the PDCP repetition process may be an uplink PDCP repetition process, and a plurality of RLC entities may be configured in an RLC confirmation mode.

[0061] In some aspects where the wireless communication device is a base station 110, the PDCP repetition procedure may be an uplink PDCP repetition procedure, and the plurality of RLC entities may be configured in an RLC acknowledged mode or an RLC unacknowledged mode. In some aspects where the wireless communication device is a base station 110, the PDCP repetition procedure may be a downlink PDCP repetition procedure, and the plurality of RLC entities may be configured in an RLC acknowledged mode.

[0062] It should be noted that although reference numeral 405 is described before reference numerals 410 and 415, these operations may be performed in any order. For example, UE 120 may be configured by base station 110, for example, in an RRC message, to determine a performance parameter or measure performance, and then receive a PDU of a PDCP instance. As another example, UE 120 may start receiving PDUs of a PDCP instance, and only start determining a performance parameter or measuring performance when a certain trigger is detected.

[0063] As indicated by reference numeral 420, UE 120 may report a performance parameter. For example, if the performance parameter is a number or percentage of PDUs received on one or more RLC entities, UE 120 may send a message to base station 110 indicating the number or percentage. In some aspects, UE 120 may send a message with a value or performance parameter index corresponding to the number or percentage. This is merely an example, and reporting may apply to any or all of the above-described performance parameters. Reporting the performance parameter may provide an accurate indication of the quality of PDCP repetition for multiple RLC entity paths involved in the PDCP repetition.

[0064] As indicated by reference numeral 425, the base station 110 that receives the performance parameter reported by the UE 120 may modify the PDCP repetition process based at least in part on the performance parameter. For example, the base station 110 may deactivate or cancel the configuration of the PDCP repetition for one or more RLC entities associated with the MAC entity. Thus, the base station 110 and those devices with which the base station 110 communicates may save processing resources, power resources, and / or channel resources by avoiding sending PDCP PDUs on inefficient RLC entities during the PDCP repetition process. In another example, the base station 110 may activate PDCP repetition for a new RLC entity. Thus, by sending PDCP PDUs on the new RLC entity, communication between the base station 110 and the UE 120 may be more reliable, which is more efficient than the existing RLC entity used for the PDCP repetition process.

[0065] In some aspects, base station 110 may reconfigure UE 120 to use DC PDCP repetition or CA PDCP repetition in response to a report from UE 120 that one or more RLC entities are insufficient to process the amount of PDCP PDUs and / or a report that one or more RLC entities are unreliable. Base station 110 may reconfigure UE 120 by adding one or more RLC entities to the PDCP repetition process from other transmission paths or devices that become available through the use of DC PDCP or CA PDCP.

[0066] In some aspects, the base station 110 may reconfigure the PDCP repetition process for the UE 120 from CA PDCP repetition to DC PDCP repetition. An advantage of DC PDCP repetition is that the UE 120 can use performance parameters from multiple different types of base stations (e.g., LTE, enhanced LTE) and / or different radio access technologies (RATs), while CA PDCP repetition involves a single RAT. In addition, synchronization is not as strict for DC PDCP. In some aspects, if the PDCP repetition performance finds that one RLC entity is successfully receiving PDUs while very few PDUs are received on another RLC entity, the base station 110 may configure DC PDCP on the new RLC entity to improve the PDCP repetition performance.

[0067] In some aspects, the base station 110 may reconfigure the PDCP repetition procedure from DC PDCP repetition to CA PDCP repetition. Note that for CA PDCP repetition, one transmit / receive point (TRP) or multiple TRPs may be used with PDCP repetition. In addition, for CA PDCP, synchronization may be very strict so that the UE 120 may benefit from the higher capacity available by using additional carriers without compromising the quality of communications. The base station 110 may reconfigure the PDCP repetition procedure to or from CA PDCP repetition based at least in part on whether strict synchronization is being achieved or needs to be achieved for CA PDCP.

[0068] In some aspects, base station 110 may determine and use the above performance parameters in response to activation of DC PDCP repetition or CA PDCP repetition. That is, base station 110 may detect activation of DC PDCP repetition or CA PDCP repetition, and the activation may be a trigger for determining the PDCP repetition performance parameters.

[0069] Additionally or alternatively, base station 110 or UE 120 may determine and use the above performance parameters in response to initiation of handover (eg, MBB HO), such as Figure 8 Thus, the base station 110 or the UE 120 can help reduce delays and interruptions that occur during handover operations.

[0070] Although various scenarios and performance parameters are described, UE 120 and base station 110 may determine and use any combination of performance parameters in any reasonable combination of scenarios.

[0071] As pointed out above, Figure 4 is provided as an example. Other examples may differ from those described above. Figure 4 Examples described.

[0072] Figure 5 5 is a diagram illustrating an example 500 of measuring the performance of PDCP repetitions in accordance with various aspects of the present disclosure. Figure 5 As shown, a wireless communication device (eg, base station 110) may use PDCP to communicate with another wireless communication device (eg, UE 120), as described above in conjunction with Figure 3 and / or Figure 4 Descriptive.

[0073] As indicated by reference numeral 505, UE 120 may receive a configuration message from base station 110, wherein the configuration message indicates one or more configuration parameters for measuring the performance of the PDCP repetition procedure. In some cases, the configuration may be signaled using a radio resource control (RRC) reconfiguration. The one or more configuration parameters in the configuration message may identify one or more performance parameters (e.g., an index of the performance parameter) to be determined by UE 120, one or more RLC entities for which the performance parameter is to be determined, a trigger for initiating determination of the performance parameter, a condition for reporting the performance parameter, a period for reporting the performance parameter, an area in which the performance parameter is to be measured, a time during which the performance parameter is to be measured, and the like. In some aspects, UE 120 may receive and use multiple configuration parameters for one or more RLC entities.

[0074] As shown at reference numeral 510, UE 120 may detect a trigger based on a configuration including one or more configuration parameters. As shown at reference numeral 515, UE 120 may determine one or more PDCP repetition performance parameters for one or more RLC entities based on the configuration, such as in conjunction with Figure 4 As indicated by reference numeral 520, UE 120 may report one or more performance parameters to base station 110 based at least in part on one or more configuration parameters. For example, UE 120 may report one or more performance parameters based at least in part on a period for reporting a performance parameter, a determination that a performance parameter satisfies a condition for reporting a performance parameter, a determination that UE 120 has entered or left an area in which the performance parameter is to be measured, a determination that a time during which the performance parameter is to be measured is occurring (or has passed), and / or a combination thereof. In some aspects, UE 120 may report the performance parameter in a measurement report and / or in a PDCP PDU.

[0075] In some aspects, UE 120 may report performance parameters indicating identification information and / or indicating an uplink or downlink. For example, the performance parameter may be a DRB identifier and / or a list of DRB identifiers associated with a PDCP repetition procedure. The performance parameter may include a logical channel identifier or a cell identifier for certain RLC entities. The performance parameter may be specified for the uplink and / or downlink.

[0076] In some aspects, UE 120 may report performance parameters corresponding to other information. For example, the performance parameter may be a performance parameter type, a reporting type, and / or a performance parameter index that identifies a performance parameter, a trigger condition (e.g., a performance parameter index threshold). The performance parameter may be a time period or time interval for reporting, an RLC identifier indicating an RLC entity associated with the performance parameter, and / or an indication of whether the PDCP repetition procedure is for CA PDCP repetition or DC PDCP repetition. The performance parameter may indicate a cell identifier associated with the PDCP repetition procedure, a signal quality associated with the reception of a PDU (e.g., cell level or beam level), and / or an indication for modifying the PDCP repetition procedure. UE 120 may report one or more performance parameters individually or in any combination.

[0077] In some aspects, the UE 120 may report the performance parameters immediately (referred to as an immediate mode), or alternatively, the UE 120 may store or log the performance parameters during a logging period (referred to as a logging mode). The UE 120 may also report the performance parameters when the logging period expires or when the UE 120 moves out of a valid area. The configuration parameters may indicate a logging period, a valid area, and / or a valid time. The base station 110 may obtain the performance parameters using, for example, RRC signaling. In some aspects, the UE 120 may report the performance parameters following a radio resource management (RRM) procedure.

[0078] In some aspects regarding the logging mode, the UE 120 may store the performance parameters in a log file and suspend the determination of the performance parameters when the UE 120 enters the RRC_idle / inactive mode. Upon entering the RRC_connected mode, the UE 120 may report the performance parameters logged in the log file. In the case where PDCP repetition is activated, the UE 120 may also continue to determine the performance parameters when the UE 120 enters the RRC_connected mode. The UE 120 may update the log file in the RRC_connected mode to delete the logged performance parameters and / or add the performance parameters determined during the RRC_connected mode.

[0079] Each RLC entity may have one or more performance parameter indexes (e.g., KPI indexes 1-6) corresponding to the PDCP repetition performance of the corresponding RLC entity compared to other RLC entities. Each performance parameter index may have a value (referred to as a credit in this example) that changes favorably (e.g., increases by 1) or unfavorably (e.g., decreases by 1). Different PDCP repetition conditions may increase or decrease the credits of the performance parameter index for the RLC entity. The UE 120 may use the performance parameter index credits for the RLC entity to determine the PDCP repetition action to be performed. For example, the UE 120 may determine a percentage of the performance parameter index for the RLC entity and activate or deactivate the RLC entity based at least in part on a percentage or ratio of the corresponding credits of a certain RLC entity (or other RLC entities) relative to the total number of PDCP PDUs sent by the base station 110.

[0080] In one example, a first performance parameter index (e.g., KPI-1) may indicate the number or percentage of PDUs received across multiple RLC entities. In some aspects, if UE 120 successfully receives each PDCP PDU for each of the multiple RLC entities, UE 120 may increase (or otherwise advantageously change) the credit points for the first performance parameter index for the RLC entity (e.g., increase by 1). In some aspects, if the RLC entity is configured with an acknowledgement mode, and if base station 110 determines that UE 120 successfully received the PDCP PDU via the RLC entity, base station 110 as a transmitting device may increase the credit points for the first performance parameter index. In some aspects, for each PDCP PDU, the credit points for the performance parameter index (or any other performance parameter index) may be increased or decreased.

[0081] Additionally or alternatively, the second performance parameter index (e.g., KPI-2) indicates the number or percentage of PDUs received on a certain RLC entity. In some aspects, if the UE 120 successfully receives each PDCP PDU for the certain RLC entity, the UE 120 may increase the credit points of the second performance parameter index for the certain RLC entity. In some aspects, if the certain RLC entity is configured with an acknowledgement mode, and if the base station 110 determines that the UE 120 successfully receives each PDCP PDU for the certain RLC entity, the base station 110 as a transmitting device may increase the credit points of the second performance parameter index.

[0082] Additionally or alternatively, a third performance parameter index (e.g., KPI-3) may indicate the number or percentage of PDUs received on a certain RLC entity but not on any other RLC entity. In some aspects, if the UE 120 successfully receives each PDCP PDU for a certain RLC entity but not on any other RLC entity, the UE 120 may increase the credit points of the third performance parameter index for the certain RLC entity. In some aspects, if the certain RLC entity is configured with an acknowledgement mode, and if the base station 110 determines that the certain RLC entity but not any other RLC entity successfully performed a PDCP PDU transmission, the base station 110 as a transmitting device may increase the credit points of the third performance parameter index.

[0083] Additionally or alternatively, a fourth performance parameter index (e.g., KPI-4) may indicate the number or percentage of PDUs received by a certain RLC entity at an earlier time compared to another RLC entity or all other RLC entities. In some aspects, if the UE 120 successfully receives each PDCP PDU with a specific sequence number indicating the earliest time of the certain RLC entity, the UE 120 may increase the credit points of the fourth performance parameter index for the RLC entity. In some aspects, if the certain RLC entity is configured with an acknowledgement mode, and if the base station 110 determines that the certain RLC entity successfully receives the PDCP PDU at the earliest time compared to other RLC entities, the base station 110 as a transmitting device may increase the credit points of the fourth performance parameter index.

[0084] Additionally or alternatively, a fifth performance parameter index (e.g., KPI-5) may indicate the number or percentage of PDUs that were not received by any RLC entity. In some aspects, if the UE 120 does not receive each PDCP PDU from any RLC entity, the UE 120 may increase the credit points of the fifth performance parameter index. In some aspects, if the RLC entity is configured with an acknowledgement mode, and if the base station 110 determines that no RLC entity has successfully received each PDCP PDU, the base station 110 as a transmitting device may increase the credit points of the fifth performance parameter index.

[0085] Additionally or alternatively, a sixth performance parameter index (e.g., KPI-6) may indicate a PDCP duplicate cancellation. In some aspects, if a certain number or percentage of PDUs are cancelled on one or more RLC entities due to successful transmission on some other RLC entity, the UE 120 may increase the credit points of the sixth performance parameter index for the certain RLC entity. In some aspects, if the RLC entity is configured with an acknowledgement mode, and if the base station 110 determines that the RLC entity successfully received each PDCP PDU and the cancellation message was sent to the other RLC entity, the base station 110 as a transmitting device may increase the credit points of the sixth performance parameter index.

[0086] As pointed out above, Figure 5 is provided as an example. Other examples may differ from those described above. Figure 5 Examples described.

[0087] Figure 6 6 is a diagram illustrating an example 600 of measuring the performance of PDCP repetitions in accordance with various aspects of the present disclosure. Figure 6 As shown, a wireless communication device (eg, base station 110) may use PDCP to communicate with another wireless communication device (eg, UE 120), as described above in conjunction with Figure 3 , Figure 4 and / or Figure 5 Descriptive.

[0088] As indicated by reference numeral 605, the base station 110 may configure the UE 120 to provide a PDCP repetition performance measurement report. For example, as indicated by reference numeral 610, the base station 110 may send a configuration for a PDCP repetition performance measurement report to the UE 120. The configuration may include, for example, conditions for reporting, a period for reporting, etc. The configuration for PDCP repetition may be signaled via RRC signaling.

[0089] As indicated by reference numeral 615, UE 120 may send a PDCP repetition measurement report to base station 110. The PDCP repetition measurement report may include a DRB identifier associated with the PDCP repetition procedure, a cell identifier associated with the PDCP repetition procedure, and / or an indication of whether the PDCP repetition procedure is for CA PDCP repetition or DC PDCP repetition. The PDCP repetition measurement report may also or alternatively include a performance parameter index identifying a performance parameter type of the performance parameter and / or a corresponding RLC entity identifier indicating an RLC entity associated with the performance parameter. The PDCP repetition measurement report may also or alternatively include a signal quality indicator (channel quality indicator, or CQI) associated with reception of a PDU for a cell, beam, or channel. The PDCP repetition measurement report may also or alternatively include an indication for modifying the PDCP repetition procedure.

[0090] As shown in reference numeral 620, UE 120 may receive a request for performance parameters from base station 110 and send the performance parameters to base station 110 based at least in part on receiving the request. The request may be in response to UE 120 sending an indication to base station 110 that the performance parameters are available in an RRC message. For example, as shown in reference numeral 625, base station 110 may send a UE information request. This may include information about the availability of PDCP repetition performance parameters. UE 120 may have indicated the availability of the recorded performance parameters. The indication may have been in an RRC setup message, a recovery message, and / or a completion message. In some aspects, base station 110 may request UE 120 to send the collected performance parameters or a log of the collected performance parameters via RRC signaling. As shown in reference numeral 630, UE 120 may send a UE information response, which may include a PDCP repetition measurement report. The PDCP repetition measurement report may be signaled via a PDCP control PDU.

[0091] In some aspects, UE 120 may provide information including indications regarding: deconfiguring or deactivating underutilized RLC entities, reconfiguring or activating PDCP repetitions with more RLC entities for a MAC entity, and / or reconfiguring PDCP repetitions to DC PDCP repetitions or CA PDCP repetitions.

[0092] As pointed out above, Figure 6 is provided as an example. Other examples may differ from those described above. Figure 6 Examples described.

[0093] Figure 7 is a diagram illustrating an example 700 of measuring performance of PDCP repetitions in accordance with various aspects of the present disclosure.

[0094] It has been explained that although certain operations are described with respect to base station 110 and UE 120, base station 110 may perform operations described herein with respect to UE 120, and vice versa. Figure 4 The base station 110 is shown sending a PDCP PDU to the UE 120, but Figure 7 UE 120 is shown which may send PDCP PDUs to base station 110 . Figure 7 The base station 110 may perform a combined Figure 3 , Figure 4 , Figure 5 and / or Figure 6 The operations are described with respect to UE 120. Figure 7 The UE 120 in the Figure 3 , Figure 4 , Figure 5 and / or Figure 6 The operations are described with respect to base station 110 .

[0095] As indicated by reference numeral 705, the base station 110 may receive PDUs of a PDCP instance from the UE 120 via a plurality of RLC entities according to a PDCP repetition procedure. As indicated by reference numeral 710, the base station 110 may detect a trigger for initiating determination of a performance parameter for a PDCP repetition procedure associated with the PDCP instance. Figure 4 As described, the detecting and receiving may occur in any order and / or concurrently.As indicated by reference numeral 715, the base station 110 may determine a performance parameter based at least in part on whether the PDUs of the PDCP instance are successfully received via one or more of the plurality of RLC entities.

[0096] As pointed out above, Figure 7 is provided as an example. Other examples may differ from those described above. Figure 7 Examples described.

[0097] Figure 8 is a diagram illustrating an example 800 of measuring performance of PDCP repetitions in accordance with various aspects of the present disclosure.

[0098] As mentioned above, the MBB HO process is one of the example scenarios for measuring PDCP repetition performance. Base station 110 and / or UE 120 may measure the performance of PDCP repetition during and / or after the MBB HO process. Some further details of the MBB HO process will be provided as context.

[0099] like Figure 8As shown, the MBB HO process may involve UE 805, source base station 810, target base station 815, user plane function (UPF) device 820, and access and mobility management function (AMF) device 825. UE 805 may correspond to UE 120 described elsewhere herein. Source base station 810 and / or target base station 815 may correspond to base station 110 described elsewhere herein. UE 805 and source base station 810 may be connected via a serving cell or a source cell (e.g., may have an RRC connection), and UE 805 may experience a handover to target base station 815 via a target cell. UPF device 820 and / or AMF device 825 may be located within a core network. Source base station 810 and target base station 815 may communicate with the core network for mobility support and user plane functions. In some aspects, the MBB HO process may include an enhanced MBB (eMBB) HO process.

[0100] The MBB HO process may include several stages. As shown in the figure, the MBB HO process may include a handover preparation phase 830, a handover execution phase 835, and a handover completion phase 840. During the handover preparation phase 830, the UE 805 may report measurements that prepare the source base station 810 and / or the target base station 815 for handover and trigger the execution of the handover. During the handover execution phase 835, the UE 805 may perform the handover by performing a random access process with the target base station 815 and establishing an RRC connection with the target base station 815. During the handover completion phase 840, the source base station 810 may forward the stored communications associated with the UE 805 to the target base station 815, and may release the UE 805 from the connection with the source base station 805.

[0101] The signaling and operation of the MBB HO process will now be described. As indicated by reference numeral 845, the UE 805 may perform one or more signal measurements, and may send a signal measurement report to the source base station 810 based at least in part on performing one or more signal measurements (e.g., serving cell measurements, neighbor cell measurements, etc.). The signal measurement report may indicate, for example, a reference signal received power (RSRP) parameter, a reference signal received quality (RSRQ) parameter, a received signal strength indicator (RSSI) parameter, a signal to interference plus noise ratio (SINR) parameter, etc. (e.g., for a serving cell, one or more neighbor cells, etc.). The source base station 810 may use the signal measurement report to determine whether to trigger a handover to the target base station 815. For example, if one or more signal measurements meet a condition, the source base station 810 may trigger a handover of the UE 805 to the target base station 815.

[0102] As indicated by reference numeral 850, the source base station 810 and the target base station 815 may communicate with each other to prepare for the handover of the UE 805. As part of the handover preparation, the source base station 810 may send a handover request to the target base station 815 to indicate that the target base station 815 is ready for the handover. The source base station 810 may transmit RRC context information associated with the UE 805 and / or configuration information associated with the UE 805 to the target base station 815. The target base station 815 may prepare for the handover by reserving resources for the UE 805. After reserving resources, the target base station 815 may send an acknowledgment (ACK) to the source base station 810 in response to the handover request.

[0103] In some aspects, the source base station 810 and the target base station 815 may negotiate the PDCP repetition configuration and performance parameters during the HO preparation 850, and the negotiation will be described later. For now, the rest of the MBB HO process will be explained.

[0104] As indicated by reference numeral 855, the source base station 810 may send an RRC reconfiguration message to the UE 805. The RRC reconfiguration message may include a handover command instructing the UE 805 to perform a handover procedure from the source base station 810 to the target base station 815. The handover command may include information associated with the target base station 815, such as a random access channel (RACH) preamble assignment for accessing the target base station 815. The UE 805 receiving the RRC reconfiguration message including the handover command may trigger the start of the handover execution phase 835.

[0105] As indicated by reference numeral 860, during the handover execution phase 885 of the MBB HO procedure, the UE 805 may perform a handover by performing a random access procedure with the target base station 815 (e.g., including synchronization with the target base station 815) while continuing to communicate with the source base station 810. For example, while the UE 805 is performing the random access procedure with the target base station 815, the UE 805 may send uplink data, uplink control information, uplink reference signals (e.g., sounding reference signals), etc. to the source base station 810, and / or may receive downlink data, downlink control information, downlink reference signals, etc. from the source base station 810. As part of the MBB HO procedure, the UE 805 may maintain simultaneous connections with the source base station 810 and the target base station 815. In some aspects, the target base station 815, the source base station 810 and / or the UE 805 may detect a trigger for initiating determination of performance parameters for a PDCP repetition process associated with a PDCP instance during the MBB HO process, receive PDUs of the PDCP instance via multiple RLC entities according to the PDCP repetition process, and determine the performance parameters based at least in part on whether the PDUs of the PDCP instance are successfully received via one or more of the multiple RLC entities.

[0106] As indicated by reference numeral 865, after successfully establishing a connection with the target base station 815 (e.g., via a random access procedure), the UE 805 may send an RRC reconfiguration complete message to the target base station 815. Receipt of the RRC reconfiguration message by the target base station 815 may trigger the start of the handover completion phase 840.

[0107] As part of the handover completion phase 840 involving uplink PDCP duplication, the source base station 810 may forward the downlink PDU to the target base station 815 via the Xn interface. The source base station 810 may also send the decompressed uplink PDCP service data unit (SDU) to the target base station 815. The source base station 810 and / or the target base station may reorder the PDCP PDUs (and / or SDUs) and / or discard duplicate PDCP PDUs (and / or SDUs). The source base station 810 and / or the target base station 815 may use a robust header compression (ROHC) context associated with sending and / or receiving the PDCP PDUs (and / or SDUs).

[0108] As part of the handover completion phase 840 involving downlink PDCP repetition, the source base station 810 may forward the downlink PDU to the target base station 815 via the Xn interface. The source base station 810 may send the decompressed downlink PDCP SDU to the target base station 815. The source base station 810 may also send the downlink PDCP SDU with a sequence number for reordering. The source base station 810 and / or the target base station 815 may use the ROHC context associated with sending and / or receiving the PDCP PDU (and / or SDU).

[0109] As shown by reference numeral 870, the source base station 810 and the target base station 815 can communicate with each other to prepare to release the source connection between the base station 810 and the UE 805. In some aspects, the target base station 815 can determine that the connection between the source base station 810 and the UE 805 is to be released, such as after receiving an RRC reconfiguration message from the UE 805. In this case, the target base station 815 can send a handover connection setup complete message to the source base station 810. The handover connection setup complete message can cause the source base station 810 to stop sending data to the UE 805 and / or stop receiving data from the UE 805. Additionally or alternatively, the handover connection setup complete message can cause the source base station 810 to forward communications associated with the UE 805 to the target base station 815 and / or notify the target base station 815 of the status of one or more communications with the UE 805. For example, the source base station 810 may forward the buffered downlink communications (e.g., downlink data) for the UE 805 and / or the uplink communications (e.g., uplink data) received from the UE 805 to the target base station 815. Additionally or alternatively, the source base station 810 may inform the target base station 815 of the PDCP repetition status associated with the UE 805, the sequence number to be used for downlink communications with the UE 805, etc.

[0110] As indicated by reference numeral 875, the target base station 815 may send an RRC reconfiguration message to the UE 805 to instruct the UE 805 to release the connection with the source base station 810. Upon receiving the instruction to release the connection with the source base station 810, the UE 805 may stop communicating with the source base station 810. For example, the UE 805 may avoid sending uplink communications to the source base station 810, and / or may avoid monitoring downlink communications from the source base station 810.

[0111] As indicated by reference numeral 880, the UE 805 may send an RRC reconfiguration complete message to the target base station 815 to indicate that the connection between the source base station 810 and the UE 805 is being released or has been released.

[0112] As indicated by reference numeral 885, the target base station 815, the UPF device 820, and / or the AMF device 825 may communicate to switch the user plane path of the UE 805 from the source base station 810 to the target base station 815. Before switching the user plane path, downlink communications for the UE 805 may be routed to the source base station 810 through the core network. After switching the user plane path, downlink communications for the UE 805 may be routed to the target base station 815 through the core network. As indicated by reference numeral 890, the target base station 815 and the source base station 810 may communicate to release the source base station 810. In some aspects, the target base station 815, the source base station 810, and / or the UE 805 may determine performance parameters and / or other performance parameters after the MBB HO process.

[0113] Referring back to HO preparation 850, in some aspects, the source base station 810 and the target base station 815 may negotiate PDCP repetition performance parameters, PDCP configuration parameters, etc. during HO preparation 850. For example, the source base station 810 may send a handover request to the target base station 815 (e.g., via an Xn interface or an N2 message), wherein the handover request may include PDCP repetition configuration parameters and / or PDCP repetition performance parameters. The target base station 815 may receive the PDCP repetition configuration parameters and / or PDCP repetition performance parameters. In some aspects, the target base station 815 may accept and / or provide support for the PDCP repetition configuration parameters and / or PDCP repetition performance parameters. In response to determining that the target base station 815 will support the PDCP repetition configuration parameters and / or PDCP repetition performance parameters, the source base station 810 may notify the target base station 815 of credits, related information, etc. associated with one or more RLC entities, respectively. In some aspects, the target base station 815 may refuse or not provide support for the PDCP repetition configuration parameters and / or PDCP repetition performance parameters.

[0114] If uplink PDCP repetition is involved, the source base station 810 may forward an uplink PDCP SDU with information identifying which RLC entities the PDCP PDU is received on from the UE 805 to the target base station 815. If the performance parameter is not determined on the forwarded uplink PDCP SDU, the source base station 810 may forward the information. During the MBB HO process, the target base station 815 may determine the performance parameter index for one or more RLC entities based at least in part on the forwarded uplink PDCP SDU and / or the credit points sent by the source base station 810 for one or more RLC entities. The target base station 815 may also determine the PDCP repetition performance parameter based at least in part on the PDCP status report from the UE 805 and update the determined state. The target base station 815 may mark the PDCP repetition performance parameter with a DRB identifier, a logical channel identifier, and / or a cell identifier of the target cell.

[0115] If downlink PDCP repetition is involved, the UE 805 may determine a performance parameter index for one or more RLC entities during the MBB HO procedure. The UE 805 may mark the PDCP repetition performance parameter with a DRB identifier, a logical channel identifier, and / or a cell identifier of the target cell.

[0116] As pointed out above, Figure 8 is provided as an example. Other examples may differ from those described above. Figure 8 Examples described.

[0117] Fig. 9 900 is a diagram illustrating an example process 900 performed, for example, by a wireless communication device in accordance with various aspects of the present disclosure. Example process 900 is an example of operations in which a wireless communication device (e.g., base station 110, UE 120, UE 805, source base station 810, target base station 815, etc.) performs operations associated with measuring performance of PDCP duplication.

[0118] like Fig. 9 As shown, in some aspects, process 900 may include detecting a trigger to initiate determination of a performance parameter for a PDCP repetition procedure associated with a PDCP instance (block 910). For example, a wireless communication device (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may detect a trigger to initiate determination of a performance parameter for a PDCP repetition procedure associated with a PDCP instance, as described above.

[0119] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include receiving packets of a PDCP instance via multiple RLC entities in accordance with a PDCP repetition procedure (block 920). For example, a wireless communication device (e.g., using antenna 234, DEMOD 232, MIMO detector 236, receive processor 238, controller / processor 240, antenna 252, DEMOD 254, MIMO detector 256, receive processor 258, controller / processor 280, etc.) may receive packets of a PDCP instance via multiple RLC entities in accordance with a PDCP repetition procedure, as described above.

[0120] like Fig. 9 As further shown in FIG. 9 , in some aspects, process 900 may include determining a performance parameter based at least in part on whether packets for the PDCP instance are successfully received via one or more of the plurality of RLC entities (block 930). For example, a wireless communication device (e.g., using controller / processor 240, controller / processor 280, etc.) may determine a performance parameter based at least in part on whether packets for the PDCP instance are successfully received via one or more of the plurality of RLC entities.

[0121] Process 900 may include additional aspects, such as any single aspect or any combination of the aspects described below and / or in conjunction with one or more other processes described elsewhere herein.

[0122] In a first aspect, a performance parameter indicates a number or percentage of packets of a PDCP instance that are successfully received via all RLC entities of a plurality of RLC entities.

[0123] In a second aspect, alone or in combination with the first aspect, the performance parameter indicates a number or percentage of packets of the PDCP instance that are successfully received via a specific RLC entity of the plurality of RLC entities.

[0124] In a third aspect, alone or in combination with one or more of the first and second aspects, a performance parameter indicates the number or percentage of packets of a PDCP instance that are successfully received via a first RLC entity among multiple RLC entities and unsuccessfully received via any other RLC entity among the multiple RLC entities.

[0125] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, a performance parameter indicates the number or percentage of packets of a PDCP instance that are successfully received via a first RLC entity among multiple RLC entities and unsuccessfully received via a second RLC entity among multiple RLC entities.

[0126] In a fifth aspect, either alone or in combination with one or more of aspects 1 to 4, a performance parameter indicates the number or percentage of packets of a PDCP instance that are successfully received via a first RLC entity among multiple RLC entities at an earlier time compared to all other RLC entities among the multiple RLC entities.

[0127] In a sixth aspect, either alone or in combination with one or more of aspects 1 to 5, a performance parameter indicates the number or percentage of packets of a PDCP instance that are successfully received at an earlier time via a first RLC entity among multiple RLC entities compared to a second RLC entity among multiple RLC entities.

[0128] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, a performance parameter indicates a number or percentage of packets of a PDCP instance that were not successfully received via any RLC entity among a plurality of RLC entities.

[0129] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, a performance parameter indicates a number or percentage of packets of a PDCP instance that are not successfully received via a specific RLC entity among a plurality of RLC entities.

[0130] In a ninth aspect, either alone or in combination with one or more of aspects one to eight, a performance parameter indicates the number or percentage of packets of a PDCP instance that are canceled or discarded for a particular RLC entity among multiple RLC entities due to successful reception via another RLC entity among multiple RLC entities.

[0131] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, the detection trigger includes: detecting that a data rate of a packet of a PDCP instance satisfies a threshold for one or more RLC entities among a plurality of RLC entities.

[0132] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the detection trigger includes: detecting that the number or percentage of time slots in which packets of the PDCP instance are received meets a threshold for one or more RLC entities among the multiple RLC entities.

[0133] In the twelfth aspect, alone or in combination with one or more aspects from the first to the eleventh aspects, the detection trigger includes: detecting that the number or percentage of unsuccessfully received packets of the PDCP instance meets a threshold for one or more RLC entities among multiple RLC entities.

[0134] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, the detection trigger includes: detecting that the number or percentage of retransmissions of packets of the PDCP instance meets a threshold for one or more RLC entities among the multiple RLC entities.

[0135] In the fourteenth aspect, alone or in combination with one or more aspects from the first to the thirteenth aspects, the wireless communication device is a user equipment, the PDCP repetition process is a downlink PDCP repetition process, and multiple RLC entities are configured in an RLC confirmed mode or an RLC unconfirmed mode.

[0136] In the fifteenth aspect, alone or in combination with one or more aspects from the first to the thirteenth aspects, the wireless communication device is a base station, the PDCP repetition process is an uplink PDCP repetition process, and multiple RLC entities are configured in an RLC confirmed mode or an RLC unconfirmed mode.

[0137] In the sixteenth aspect, alone or in combination with one or more aspects from the first to the thirteenth aspects, the wireless communication device is a user equipment, the PDCP repetition process is an uplink PDCP repetition process, and multiple RLC entities are configured in an RLC confirmation mode.

[0138] In the seventeenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the wireless communication device is a base station, the PDCP repetition process is a downlink PDCP repetition process, and multiple RLC entities are configured in an RLC confirmation mode.

[0139] In the eighteenth aspect, alone or in combination with one or more of the first to seventeenth aspects, the process 900 further includes: receiving a configuration message indicating one or more configuration parameters for measuring the performance of the PDCP repetition process.

[0140] In the nineteenth aspect, alone or in combination with one or more of the first to eighteenth aspects, one or more configuration parameters indicate at least one of the following: a performance parameter to be determined by the wireless communication device, a plurality of RLC entities for which the performance parameter is to be determined, a trigger for initiating determination of the performance parameter, a condition for reporting the performance parameter, a period for reporting the performance parameter, an area in which the performance parameter is to be measured, a time during which the performance parameter is to be measured, or a combination thereof.

[0141] In the twentieth aspect, alone or in combination with one or more of aspects one to nineteen, process 900 further includes: reporting the performance parameters to the base station based at least in part on at least one of the following: a period for reporting the performance parameters, a determination that the performance parameters satisfy a condition for reporting the performance parameters, a determination that the wireless communication device has left an area in which the performance parameters are to be measured, a determination that a time during which the performance parameters are to be measured has passed, or a combination thereof.

[0142] In a twenty-first aspect, alone or in combination with one or more of the first to twentieth aspects, process 900 further comprises: reporting the performance parameters to a base station.

[0143] In a twenty-second aspect, alone or in combination with one or more of aspects one to twenty-first, the performance parameter is reported in a measurement report.

[0144] In a twenty-third aspect, alone or in combination with one or more of the first to twenty-second aspects, the performance parameters are reported in a PDCP packet data unit.

[0145] In aspect twenty-four, alone or in combination with one or more of aspects one to twenty-three, the performance parameter is reported in a report indicating at least one of: a dedicated radio bearer identifier associated with a PDCP repetition process, a performance parameter index identifying a performance parameter type of a performance parameter, an RLC identifier indicating an RLC entity associated with the performance parameter, an indication of whether the PDCP repetition process is for carrier aggregation PDCP repetition or for dual-connectivity PDCP repetition, a cell identifier associated with the PDCP repetition process, a signal quality associated with reception of a packet, an indication for modifying the PDCP repetition process, or a combination thereof.

[0146] In aspect twenty-fifth, alone or in combination with one or more of aspects one to twenty-fourth, process 900 further includes: sending an indication to a base station in a radio resource control message that performance parameters are available; receiving a request for performance parameters from the base station; and sending performance parameters to the base station based at least in part on receiving the request.

[0147] In aspect 26, alone or in combination with one or more of aspects 1 to 25, the wireless communication device is a source base station for a make-before-break handover procedure. In some aspects, process 900 further includes: as part of handover preparation, sending performance parameters to a target base station for the make-before-break handover procedure.

[0148] In the twenty-seventh aspect, alone or in combination with one or more of the first to twenty-sixth aspects, the process 900 further includes: sending one or more configuration parameters for measuring the performance of the PDCP repetition process to the target base station.

[0149] In aspect 28, alone or in combination with one or more of aspects 1 to 27, the wireless communication device is a target base station for a make-before-break handover procedure. In some aspects, process 900 further includes: receiving performance parameters from a source base station for the make-before-break handover procedure as part of handover preparation.

[0150] In the twenty-ninth aspect, alone or in combination with one or more of the first to twenty-eighth aspects, process 900 further includes: receiving one or more configuration parameters for measuring the performance of the PDCP repetition process from the source base station.

[0151] In a thirtieth aspect, either alone or in combination with one or more of aspects one to twenty-ninth, process 900 further comprises: modifying the PDCP repetition process based at least in part on a performance parameter.

[0152] In the thirty-first aspect, alone or in combination with one or more aspects from the first to the thirtieth aspects, modifying the PDCP repetition process includes at least one of the following: deactivating or reconfiguring PDCP repetition for an RLC entity among multiple RLC entities, activating PDCP repetition for an RLC entity, reconfiguring the PDCP repetition process from carrier aggregation PDCP repetition to dual-connection PDCP repetition, reconfiguring the PDCP repetition process from dual-connection PDCP repetition to carrier aggregation PDCP repetition, or a combination thereof.

[0153] although Fig. 9 Example blocks of process 900 are shown, but in some aspects process 900 may include Fig. 9 The blocks depicted in the process 900 may be additional blocks, fewer blocks, different blocks, or blocks arranged in a different manner. Additionally or alternatively, two or more blocks in the blocks of process 900 may be executed in parallel.

[0154] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the various aspects.

[0155] As used herein, the term "component" is intended to be broadly interpreted as hardware, firmware, and / or a combination of hardware and software. As used herein, a processor is implemented using hardware, firmware, and / or a combination of hardware and software.

[0156] As used herein, satisfying a threshold may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, etc., depending on the context.

[0157] It will be apparent that the systems and / or methods described herein may be implemented with various forms of hardware, firmware, and / or combinations of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limiting in any respect. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, it being understood that software and hardware may be designed to implement the systems and / or methods based, at least in part, on the description herein.

[0158] Even if a specific combination of features is recorded in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. In fact, many of these features can be combined in a manner that is not specifically recorded in the claims and / or specifically disclosed in the specification. Although each dependent claim listed below can only directly depend on one claim, the disclosure of various aspects includes each dependent claim and all other claim combinations in the claim set. The phrase "at least one of" referring to the list of items refers to any combination of those items (including single members). For example, "at least one of a, b or c" is intended to cover any combination of a, b, c, ab, ac, bc and abc, and with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc and ccc or any other ordering of a, b and c).

[0159] Unless explicitly described as such, none of the elements, actions or instructions used herein should be interpreted as key or necessary. In addition, as used herein, the articles "a" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the terms "set" and "group" are intended to include one or more projects (e.g., related projects, unrelated projects, combinations of related projects and unrelated projects, etc.), and can be used interchangeably with "one or more". In the case of only expecting one project, the phrase "only one" or similar language is used. In addition, as used herein, the terms "has", "have", "having" etc. are intended to be open terms. In addition, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part on".

Claims

1. A method of wireless communication performed by a wireless communication device, comprising: detecting a trigger to initiate determination of a performance parameter for a Packet Data Convergence Protocol (PDCP) repetition procedure comprising transmission of packets of a PDCP instance via a plurality of Radio Link Control (RLC) entities; receiving the packets of the PDCP instance via the plurality of RLC entities according to the PDCP repetition procedure; and The performance parameter is determined based at least in part on whether packets for the PDCP instance are successfully received via one or more RLC entities of the plurality of RLC entities.

2. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are successfully received via all RLC entities of the plurality of RLC entities.

3. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are successfully received via a specific RLC entity among the plurality of RLC entities.

4. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are successfully received via a first RLC entity of the plurality of RLC entities and unsuccessfully received via any other RLC entity of the plurality of RLC entities.

5. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are successfully received via a first RLC entity among the plurality of RLC entities and unsuccessfully received via a second RLC entity among the plurality of RLC entities.

6. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are successfully received via a first RLC entity of the plurality of RLC entities at an earlier time than all other RLC entities of the plurality of RLC entities.

7. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are successfully received via a first RLC entity of the plurality of RLC entities at an earlier time than via a second RLC entity of the plurality of RLC entities.

8. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are not successfully received via any RLC entity of the plurality of RLC entities.

9. The method according to claim 1, wherein: The performance parameter indicates a number or a percentage of packets of the PDCP instance that are not successfully received via a specific RLC entity among the plurality of RLC entities.

10. The method according to claim 1, wherein: The performance parameter indicates a number or percentage of packets of the PDCP instance that are canceled or discarded for a specific RLC entity among the plurality of RLC entities due to successful reception via another RLC entity among the plurality of RLC entities.

11. The method according to claim 1, wherein: Detecting the trigger includes detecting that a data rate of packets of the PDCP instance satisfies a threshold for one or more RLC entities of the plurality of RLC entities.

12. The method according to claim 1, wherein: Detecting the trigger includes detecting that a number or percentage of time slots in which packets of the PDCP instance are received satisfies a threshold for one or more of the plurality of RLC entities.

13. The method according to claim 1, wherein: Detecting the trigger includes detecting that a number or a percentage of unsuccessfully received packets of the PDCP instance satisfies a threshold for one or more of the plurality of RLC entities.

14. The method according to claim 1, wherein: Detecting the trigger includes detecting that a number or a percentage of retransmissions of packets of the PDCP instance satisfies a threshold for one or more of the plurality of RLC entities.

15. The method according to claim 1, wherein: The wireless communication device is a user equipment, the PDCP repetition procedure is a downlink PDCP repetition procedure, and the plurality of RLC entities are configured in an RLC acknowledged mode or an RLC unacknowledged mode.

16. The method according to claim 1, wherein: The wireless communication device is a network node, the PDCP repetition procedure is an uplink PDCP repetition procedure, and the plurality of RLC entities are configured in an RLC acknowledged mode or an RLC unacknowledged mode.

17. The method according to claim 1, wherein: The wireless communication device is a user equipment, the PDCP repetition procedure is an uplink PDCP repetition procedure, and the plurality of RLC entities are configured in an RLC acknowledgement mode.

18. The method according to claim 1, wherein: The wireless communication device is a network node, the PDCP repetition procedure is a downlink PDCP repetition procedure, and the plurality of RLC entities are configured in an RLC acknowledgement mode.

19. The method of claim 1, further comprising: A configuration message is received, the configuration message indicating one or more configuration parameters for measuring performance of the PDCP repetition procedure.

20. The method according to claim 19, wherein: The one or more configuration parameters indicate at least one of the following: said performance parameter to be determined by said wireless communication device, the plurality of RLC entities for which the performance parameter is to be determined, said trigger for initiating determination of said performance parameter, The conditions used to report the performance parameters, the period for reporting said performance parameter, the area in which the performance parameter is to be measured, or The time during which the performance parameter is to be measured.

21. The method of claim 20, further comprising reporting the performance parameter to a network node based at least in part on at least one of: said period for reporting said performance parameter, a determination that the performance parameter satisfies the condition for reporting the performance parameter, a determination that the wireless communication device has left the area in which the performance parameter is to be measured, or A determination is made that the time during which the performance parameter is to be measured has elapsed.

22. The method of claim 1, further comprising: The performance parameter is reported to a network node.

23. The method according to claim 22, wherein: The performance parameters are reported in a measurement report.

24. The method according to claim 22, wherein: The performance parameters are reported in PDCP packet data units.

25. The method according to claim 22, wherein: The performance parameter is reported in a report indicating at least one of the following: a dedicated radio bearer identifier associated with said PDCP repetition procedure, a performance parameter index identifying a performance parameter type of the performance parameter, an RLC identifier indicating the RLC entity associated with the performance parameter, an indication of whether the PDCP repetition procedure is for carrier aggregation PDCP repetition or for dual connectivity PDCP repetition, a cell identifier associated with the PDCP repetition procedure, a signal quality associated with reception of said packet, or An indication for modifying the PDCP repetition procedure.

26. The method of claim 1, further comprising: sending an indication to a network node in a radio resource control message that the performance parameter is available; receiving a request for the performance parameter from the network node; as well as The performance parameter is sent to the network node based at least in part on receiving the request.

27. The method of claim 1, wherein: The wireless communication device is a source network node of a make-before-break handover process, and wherein the method further comprises: As part of the handover preparation, the performance parameters are sent to a target network node of the make-before-break handover procedure.

28. The method according to claim 27, further comprising: One or more configuration parameters for measuring performance of the PDCP repetition procedure are sent to the target network node.

29. The method of claim 1, wherein: The wireless communication device is a target network node of a make-before-break handover process, and wherein the method further comprises: The performance parameters are received from a source network node of the make-before-break handover procedure as part of handover preparation.

30. The method of claim 29, further comprising: One or more configuration parameters for measuring performance of the PDCP repetition procedure are received from the source network node.

31. The method of claim 1, further comprising: The PDCP repetition procedure is modified based at least in part on the performance parameter.

32. The method according to claim 31, wherein: Modifying the PDCP repetition procedure includes at least one of the following: deactivating or reconfiguring PDCP repetition for an RLC entity among the multiple RLC entities, Activate PDCP repetition for the RLC entity, reconfiguring the PDCP repetition procedure from carrier aggregation PDCP repetition to dual connectivity PDCP repetition, or The PDCP repetition procedure is reconfigured from dual connectivity PDCP repetition to carrier aggregation PDCP repetition.

33. A wireless communication device for wireless communication, comprising: Memory; as well as one or more processors coupled to the memory, the one or more processors configured to: detecting a trigger to initiate determination of a performance parameter for a Packet Data Convergence Protocol (PDCP) repetition procedure comprising transmission of packets of a PDCP instance via a plurality of Radio Link Control (RLC) entities; receiving the packets of the PDCP instance via the plurality of RLC entities according to the PDCP repetition procedure; and The performance parameter is determined based at least in part on whether packets for the PDCP instance are successfully received via one or more RLC entities of the plurality of RLC entities.

34. A non-transitory computer readable medium storing one or more instructions for wireless communication, the one or more instructions comprising: One or more instructions that, when executed by one or more processors of a wireless communication device, cause the one or more processors to: detecting a trigger to initiate determination of a performance parameter for a Packet Data Convergence Protocol (PDCP) repetition procedure comprising transmission of packets of a PDCP instance via a plurality of Radio Link Control (RLC) entities; receiving the packets of the PDCP instance via the plurality of RLC entities according to the PDCP repetition procedure; and The performance parameter is determined based at least in part on whether packets for the PDCP instance are successfully received via one or more RLC entities of the plurality of RLC entities.

35. An apparatus for wireless communication, comprising: means for detecting a trigger for initiating determination of a performance parameter for a Packet Data Convergence Protocol (PDCP) repetition procedure comprising transmission of packets for a PDCP instance via a plurality of Radio Link Control (RLC) entities; means for receiving the grouping of the PDCP instances via the plurality of RLC entities according to the PDCP repetition procedure; as well as Means for determining the performance parameter based at least in part on whether packets for the PDCP instance are successfully received via one or more RLC entities of the plurality of RLC entities.

Images