Packet data convergence protocol replication in sidelink transmissions

Abstract

Aspects of the present disclosure relate to packet data convergence protocol (PDCP) replication in sidelink transmissions. In an aspect, a first UE includes a processor and a transceiver coupled to the processor. The processor is configured to transmit configuration information for PDCP replication to the second UE via the transceiver, the PDCP replication for sidelink transmission from the first UE to the second UE. The processor is configured to determine activation and deactivation of PDCP replication according to a capability of the second UE or an indication from the second UE.

Description

Technical Field

[0001] This disclosure relates to wireless communications, and more specifically, to methods, apparatus, and computer-readable media and systems for copying Packet Data Convergence Protocol (PDCP) in sidelink transmissions. Background Technology

[0002] A wireless communication system may include one or more network communication devices, such as base stations, which may also be referred to as eNodeB (eNB), next-generation node B (gNB), or other suitable terms. Each network communication device (e.g., base station) may support wireless communication with one or more user communication devices (which may also be referred to as user equipment (UE), or other suitable terms). The wireless communication system may support wireless communication with one or more user communication devices by utilizing the resources of the wireless communication system (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)). In addition, the wireless communication system may support wireless communication across a variety of wireless access technologies, including third-generation (3G), fourth-generation (4G), fifth-generation (5G), and other suitable wireless access technologies other than 5G (e.g., sixth-generation (6G)).

[0003] New technologies in 5G New Radio (NR) allow cellular devices to connect directly to each other using a technology called sidelink communication. Sidelink is a new communication paradigm in which cellular devices can communicate without relaying their data through the network. The sidelink interface is also known as the PC5 interface. Various applications can rely on communication over the sidelink interface, such as vehicle-to-owner (V2X) communication, public safety (PS) communication, direct file transfer between user equipment, and more. Summary of the Invention

[0004] This disclosure relates to supporting peer-to-peer UE control packet data convergence protocol (PDCP) replication, processing RLC entities for PDCP replication, and methods, apparatus, and systems for processing PDCP replication for carriers with faults. By performing the PDCP replication-related processes of this disclosure, PDCP replication in sidelinks can be supported.

[0005] Some implementations of the methods and apparatus described herein may further include: transmitting configuration information for a Packet Data Convergence Protocol (PDCP) replication process for sidelink transmission from the first UE to the second UE via a transceiver; and determining the activation and deactivation of PDCP replication based on the capabilities of the second UE or instructions from the second UE.

[0006] Some implementations of the methods and apparatus described herein may further include receiving a first indication from a second UE via a transceiver to instruct the second UE to determine a configuration for accepting PDCP replication.

[0007] Some implementations of the methods and apparatus described herein may further include receiving a second instruction via a transceiver and from a second UE to instruct the second UE to determine a configuration for rejecting PDCP replication and information on the reasons for the configuration for rejecting PDCP replication.

[0008] Some implementations of the methods and apparatus described herein may further include: in the case that a second UE rejects the configuration for PDCP replication of a first or more sidelink radio bearers (SLRBs) or logical channels (LCHs) and accepts the configuration for PDCP replication of a second or more SLRBs or LCHs, receiving, via a transceiver and from the second UE, a third indication indicating that the configuration for PDCP replication of the first or more SLRBs or LCHs is rejected, or a fourth indication indicating that the configuration for PDCP replication of the second or more SLRBs or LCHs is accepted.

[0009] Some implementations of the methods and apparatus described herein may further include determining whether to activate or deactivate PDCP replication based on capability information of the second UE indicating that the second UE supports PDCP replication or on the type of the second UE that is not suitable for enabling PDCP replication.

[0010] Some implementations of the methods and apparatus described herein may further include: receiving a fourth instruction to activate or deactivate PDCP replication via a transceiver and from a second UE after activating PDCP replication.

[0011] Some implementations of the methods and apparatus described herein may further include receiving deactivation reason information for PDCP replication via a transceiver and from a second UE.

[0012] In some implementations of the methods and apparatus described herein, the deactivation of PDCP replication is directed against one of the following: at least one SLRB; at least one LCH; or at least one Radio Link Control (RLC) entity.

[0013] Some implementations of the methods and apparatus described herein may further include transmitting, via a transceiver, at least one identifier of at least one RLC entity for PDCP replication to a second UE.

[0014] In some implementations of the methods and apparatus described herein, the configuration information is transmitted via one of the following: a sidelink radio resource control (RRC) message; a media access control (MAC) control element (CE); or physical layer signaling.

[0015] Some implementations of the methods and apparatus described herein may further include: detecting a fault on at least one carrier corresponding to at least one RLC entity associated with PDCP replication for side-link transmission from a first UE to a second UE; and performing activation or deactivation of PDCP replication based on fault detection.

[0016] Some implementations of the methods and apparatus described herein may further include: determining the number of RLC entities to be activated for PDCP replication based on the number of available carriers when PDCP replication is activated upon detection of a fault.

[0017] Some implementations of the methods and apparatus described herein may further include: determining the number of RLC entities to be activated for PDCP replication when PDCP replication is activated upon detection of a fault, regardless of the number of available carriers; and waiting for at least one RLC entity based on the number of available carriers.

[0018] Some implementations of the methods and apparatus described herein may further include: determining the number of RLC entities to be activated for PDCP replication when PDCP replication is activated upon fault detection, regardless of the number of available carriers; and suspending at least one RLC entity based on the number of available carriers.

[0019] Some implementations of the methods and apparatus described herein may further include: if PDCP replication is activated before a fault is detected, suspending at least one RLC entity based on determining that the number of available carriers is less than the number of active RLC entities used for PDCP replication, until the number of available carriers becomes equal to or greater than the number of active RLC entities.

[0020] Some implementations of the methods and apparatus described herein may further include: when a fault is detected, determining the number of RLC entities to be deactivated for the PDCP replication based on the number of available carriers.

[0021] In some implementations of the methods and apparatus described herein, the fault includes one of the following: sidelink radio link failure (RLF); beam failure; continuous listen-before-tell (LBT) failure; or carrier failure.

[0022] Some implementations of the methods and apparatus described herein may further include: receiving configuration information for Packet Data Convergence Protocol (PDCP) replication via the transceiver and from a first UE, the PDCP replication being used for sidelink transmission from the first UE to the second UE; and sending instructions via the transceiver to the first UE indicating activation and deactivation of PDCP replication.

[0023] Some implementations of the methods and apparatus described herein may further include sending a first indication to a first UE via a transceiver to instruct a second UE to determine a configuration for accepting PDCP replication.

[0024] Some implementations of the methods and apparatus described herein may further include: sending a second instruction to a first UE via a transceiver to instruct the second UE to determine the configuration for rejecting PDCP replication and the reason information for the configuration for rejecting PDCP replication.

[0025] Some implementations of the methods and apparatus described herein may further include: determining a configuration to reject PDCP replication for a first or more sidelink radio bearers (SLRBs) or logical channels (LCHs), and a configuration to accept PDCP replication for a second or more SLRBs or LCHs; and transmitting a third indication or a fourth indication to the first UE via a transceiver, the third indication indicating a configuration to reject the PDCP replication for the first or more SLRBs or LCHs, and the fourth indication indicating a configuration to accept the PDCP replication for the second or more SLRBs or LCHs.

[0026] Some implementations of the methods and apparatus described herein may further include: after activating PDCP replication, sending a fourth indication to the first UE via a transceiver to activate or deactivate PDCP replication.

[0027] Some implementations of the methods and apparatus described herein may further include: after activating PDCP replication, sending a fourth indication to the first UE via a transceiver to activate or deactivate PDCP replication.

[0028] Some implementations of the methods and apparatus described herein may further include sending deactivation reason information for PDCP replication to a first UE via a transceiver.

[0029] In some implementations of the methods and apparatus described herein, the deactivation of PDCP replication is directed against one of the following: at least one SLRB; at least one LCH; or at least one Radio Link Control (RLC) entity.

[0030] Some implementations of the methods and apparatus described herein may further include establishing at least one RLC entity for PDCP replication based on received configuration information.

[0031] In some implementations of the methods and apparatus described herein, the establishment of at least one RLC entity is performed based on one of the following: accepting the configuration of PDCP replication; establishing at least one SLRB with PDCP replication enabled in the configuration or pre-configuration; or activating PDCP replication for at least one SLRB or at least one LCH.

[0032] In some implementations of the methods and apparatus described herein, the number of at least one RLC entity established for PDCP replication is determined based on configuration information.

[0033] Some implementations of the methods and apparatus described herein may further include receiving, via a transceiver and from a first UE, at least one identifier of at least one RLC entity for PDCP replication.

[0034] In some implementations of the methods and apparatus described herein, the first indication, the second indication, the third indication, or the fourth indication is transmitted via one of the following: a sidelink radio resource control (RRC) message; a media access control (MAC) control element (CE); or physical layer signaling. Attached Figure Description

[0035] Figure 1 An example of a wireless communication system supporting a sidelink according to various aspects of this disclosure is shown.

[0036] Figure 2 An example of a signaling flow replicated by PDCP in a support side link according to various aspects of this disclosure is shown.

[0037] Figure 3 An example of a device supporting PDCP replication in a side link according to various aspects of this disclosure is shown.

[0038] Figure 4 An example of a processor supporting PDCP replication in a side link according to various aspects of this disclosure is shown.

[0039] Figure 5 A flowchart is shown of a method for PDCP replication in a support side link according to various aspects of this disclosure.

[0040] Figure 6 A flowchart is shown of a method for supporting PDCP in a side link according to various aspects of this disclosure.

[0041] Figure 7 A flowchart is shown of a method for PDCP replication in a support side link according to various aspects of this disclosure. Detailed Implementation

[0042] The principles of this disclosure will now be described with reference to some embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The disclosure described herein can be implemented in various ways other than those described below.

[0043] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0044] In this disclosure, references to "an embodiment," "example embodiment," "embodiment," "some embodiments," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but it is not necessary for every embodiment to include that particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments (whether explicitly described or not) to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.

[0045] It should be understood that although the terms “first” and “second”, etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. For example, a first element may also be referred to as a second element without departing from the scope of the embodiments, and similarly, a second element may also be referred to as a first element. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0046] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. It will also be understood that the terms “comprising,” “including,” “having,” “containing,” and / or “comprising” as used herein specify the presence of the stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0047] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as 5G NR, LTE, LTE-A Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G) communication protocols, and / or any other currently known or to be developed in the future. Embodiments of this disclosure can be applied to a variety of communication systems. Given the rapid development of communications, there will also be future types of communication technologies and systems in which this disclosure can be implemented. This should not be construed as limiting the scope of the invention to the aforementioned systems.

[0048] As used herein, the term "network device" generally refers to a node in a communication network through which terminal devices can access the communication network and receive services. Depending on the terminology and technology applied, network devices can refer to base stations (BS) or access points (APs), such as Node B (Node B or NB), Radio Access Network (RAN) nodes, Evolved Node B (eNodeB or eNB), NRNB (also known as gNB), Remote Radio Unit (RRU), Radio Head (RH), infrastructure equipment for V2X (Vehicle to Everything) communication, Transmit and Receive Point (TRP), Receive Point (RP), Remote Radio Head (RRH), relay, Integrated Access and Backhaul (IAB) nodes, and low-power nodes such as femtoBS, picoBS, etc.

[0049] As used herein, the term "terminal device" generally refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), end user equipment, subscriber station (SS), unmanned aerial vehicle (UAV), portable subscriber station, mobile station (MS), or access terminal (AT). The terminal device may include, but is not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), USB dongles, smart devices, wireless client devices (CPEs), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, targets, medical devices (e.g., remote surgical equipment), industrial equipment (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments, consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc.). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.

[0050] In NR carrier aggregation (CA) / dual connectivity (DC), replication for data radio bearers (DRBs) can be activated / deactivated via radio resource control (RRC) signaling or MAC control elements (MACCEs). The MACCEs include replication activation / deactivation MACCEs and replication radio link control (RLC) activation / deactivation MACCEs. In NR, if PDCP replication is configured, replication of signaling radio bearers (SRBs) is always active.

[0051] In Long Term Evolution (LTE) Sidelink Carrier Aggregation (SLCA), replication activation is based on a (pre)configured reliability threshold threshSL-Reliability-r15, meaning that PDCP replication is activated when the ProSe per Packet Reliability (PPPR) is greater than this threshold. SL-SRB is not present.

[0052] For NR SLCA, each sidelink radio bearer (SLRB) is configured with PDCP replication, which differs from LTE SL replication but is similar to NR replication. The SLRB is configured to use either PDCP replication. Furthermore, SLCA / PDCP replication is applied to the PC5-RRC after the sidelink is established. However, other details regarding the sidelink are not defined.

[0053] This application provides a solution for PDCP replication. In this solution, a sending UE in a sidelink sends configuration information to a receiving UE in the same sidelink. This configuration information is used for PDCP replication for sidelink transmission from the sending UE to the receiving UE. The sending UE determines the activation and deactivation (or in other words, the start of PDCP replication) of the replication based on the capabilities of the receiving UE or instructions from the receiving UE. This solution allows for the activation and deactivation of PDCP replication based on the capabilities or instructions of the receiving UE.

[0054] The aspects of this disclosure are described in the context of wireless communication systems.

[0055] Figure 1 An example of a wireless communication system 100 supporting PDCP replication in a sidelink according to various aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 102 (also referred to as network devices (NEs)), one or more UEs 104, a core network 106, and a packet data network 108. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an Advanced LTE (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as an NR network. In other implementations, the wireless communication system 100 may be a combination of 4G and 5G networks, or other suitable radio access technologies including IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20. The wireless communication system 100 may support radio access technologies other than 5G. Additionally, the wireless communication system 100 may support technologies such as Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), or Code Division Multiple Access (CDMA).

[0056] One or more network entities 102 may be distributed throughout a geographic area to form a wireless communication system 100. The one or more network entities 102 described herein may be, include, or may be referred to as network nodes, base stations, network elements, radio access networks (RANs), base transceivers, access points, Node Bs, eNodeBs (eNBs), next-generation Node Bs (gNBs), or other suitable terms. Network entities 102 and UE 104 may communicate via a communication link 110, which may be a wireless or wired connection. For example, network entities 102 and UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) via a Uu interface.

[0057] Network entity 102 can provide a geographic coverage area 112, and network entity 102 can support services (e.g., voice, video, packet data, messaging, broadcasting, etc.) for one or more UEs 104 within that geographic coverage area 112. For example, network entity 102 and UE 104 can support wireless communication of signals associated with services (e.g., voice, video, packet data, messaging, broadcasting, etc.) based on one or more radio access technologies. In some implementations, network entity 102 can be mobile, such as a satellite associated with a non-terrestrial network. In some implementations, different geographic coverage areas 112 associated with the same or different radio access technologies can overlap, but different geographic coverage areas 112 can be associated with different network entities 102. The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the specification can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0058] One or more UEs 104 may be distributed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or be referred to as a mobile device, wireless device, remote device, remote unit, handheld device, or subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, station, terminal, or client, etc. Alternatively or optionally, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Things (IOE) device, or a Machine-Type Communication (MTC) device, etc. In some implementations, UE 104 may be fixed within the wireless communication system 100. In some other implementations, UE 104 may be mobile within the wireless communication system 100.

[0059] One or more UE104s can be devices of different forms or with different capabilities. Figure 1Examples of UE104 are shown. UE104 is capable of communicating with various types of devices, such as network entity 102, other UE104s, or network devices (e.g., core network 106, packet data network 108, relay devices, integrated access and backhaul (IAB) nodes, or another network device). Figure 1 As shown. Additionally or alternatively, UE104 may support communication with other network entities 102 or UE104, which may act as relays in the wireless communication system 100.

[0060] UE104 can also support direct wireless communication with other UE104s via communication link 114. For example, UE104 can support direct wireless communication with another UE104 via a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-owner (V2X) deployments, or cellular V2X deployments, communication link 114 may be referred to as a side link. For example, UE104 can support direct wireless communication with another UE104 via a PC5 interface.

[0061] Network entity 102 may support communication with core network 106, or with another network entity 102, or both. For example, network entity 102 may interface with core network 106 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Network entities 102 may communicate with each other via backhaul links 116 (e.g., via X2, Xn, or another network interface). In some implementations, network entities 102 may communicate directly with each other (e.g., between network entities 102). In some other implementations, network entities 102 may communicate with each other or indirectly (e.g., via core network 106). In some implementations, one or more network entities 102 may include sub-components, such as access network entities, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transport entities, which may be referred to as radio headends, smart radio headends, or transmit-receive points (TRPs).

[0062] In some implementations, network entity 102 can be configured in a decomposed architecture that utilizes protocol stacks physically or logically distributed across two or more network entities 102, such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 102 may include one or more of a Central Unit (CU), a Distributed Unit (DU), a Radio Unit (RU), a RAN Intelligent Controller (RIC) (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) system, or any combination thereof.

[0063] An RU can also be referred to as a radio head, intelligent radio head, remote radio head (RRH), remote radio unit (RRU), or transmit-receive point (TRP). One or more components of network entity 102 in a de-aggregated RAN architecture can be located in the same location, or one or more components of network entity 102 can be located in distributed locations (e.g., separate physical locations). In some implementations, one or more network entities 102 in a de-aggregated RAN architecture can be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0064] The functional partitioning among CU, DU, and RU can be flexible and can support different functions depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combination thereof) are performed at the CU, DU, or RU. For example, a protocol stack functional partitioning can be used between the CU and DU, such that the CU can support one or more layers of the protocol stack and the DU can support one or more different layers of the protocol stack. In some implementations, the CU can host upper-layer protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functions and signaling (e.g., Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU can connect to one or more DUs or RUs, and said one or more DUs or RUs can host lower-layer protocol layer functions, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Media Access Control (MAC) layer) functions and signaling, and each can be at least partially controlled by the CU160.

[0065] Alternatively or alternatively, a functional partitioning of the protocol stack can be employed between the DU and RU, allowing the DU to support one or more layers of the protocol stack, and the RU to support one or more different layers of the protocol stack. The DU can support one or more different cells (e.g., via one or more RUs). In some implementations, the functional partitioning between the CU and DU, or between the DU and RU, can be within the protocol layer (e.g., some functions of the protocol layer can be performed by one of the CU, DU, or RU, while other functions of the protocol layer are performed by a different one of the CU, DU, or RU).

[0066] The CU can be further functionally divided into CU control plane (CU-CP) and CU user plane (CU-UP) functions. The CU can be connected to one or more DUs via mid-range communication links (e.g., F1, F1c, F1u), and the DUs can be connected to one or more RUs via forward communication links (e.g., open forward (FH) interfaces). In some implementations, the mid-range or forward communication links can be implemented based on the interfaces (e.g., channels) between layers of the protocol stack supported by the various network entities 102 communicating via such communication links.

[0067] Core network 10 can support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. Core network 106 can be an evolved packet core (EPC) or a 5G core (5GC), which can include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), access and mobility management functions (AMF)) and user plane entities that route packets or interconnects to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities can manage one or more non-access stratum (NAS) functions of UE 104 served by one or more network entities 102 associated with core network 106, such as mobility, authentication, and bearer management (e.g., data bearers, signaling bearers, etc.).

[0068] Core network 106 can communicate with packet data network 108 via one or more backhaul links 116 (e.g., via S1, N2, N2, or another network interface). Packet data network 108 may include application server 118. In some implementations, one or more UEs 104 may communicate with application server 118. UE 104 may establish a session (e.g., Protocol Data Unit (PDU) session, etc.) with core network 106 via network entity 102. Core network 106 can use the established session (e.g., an established PDU session) to route traffic (e.g., control information, data, etc.) between UE 104 and application server 118. A PDU session may be an example of a logical connection between UE 104 and core network 106 (e.g., one or more network functions of core network 106).

[0069] In the wireless communication system 100, network entity 102 and UE 104 can use the resources of the wireless communication system 100 (e.g., time resources (e.g., symbols, time slots, subframes, frames, etc.) or frequency resources (e.g., subcarriers, carriers)) to perform various operations (e.g., wireless communication). In some implementations, network entity 102 and UE 104 can support different resource structures. For example, network entity 102 and UE 104 can support different frame structures. In some implementations, such as in 4G, network entity 102 and UE 104 can support a single frame structure. In some other implementations, such as in 5G and in other suitable radio access technologies, network entity 102 and UE 104 can support various frame structures (i.e., multiple frame structures). Network entity 102 and UE 104 can support various frame structures based on one or more numerical configurations.

[0070] One or more numerical configurations may be supported in the wireless communication system 100, and these numerical configurations may include subcarrier spacing and a cyclic prefix. A first numerical configuration (e.g., μ=0) may be associated with a first subcarrier spacing (e.g., 15kHz) and a normal cyclic prefix. In some implementations, the first numerical configuration (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15kHz) may utilize one time slot per subframe. A second numerical configuration (e.g., μ=1) may be associated with a second subcarrier spacing (e.g., 30kHz) and a normal cyclic prefix. A third numerical configuration (e.g., μ=2) may be associated with a third subcarrier spacing (e.g., 60kHz) and a normal cyclic prefix or an extended cyclic prefix. A fourth numerical configuration (e.g., μ=3) may be associated with a fourth subcarrier spacing (e.g., 120kHz) and a normal cyclic prefix. A fifth numerical configuration (e.g., μ=4) may be associated with a fifth subcarrier spacing (e.g., 240kHz) and a normal cyclic prefix.

[0071] The time intervals of resources (e.g., communication resources) can be organized according to frames (also called radio frames). Each frame can have a duration, such as 10 milliseconds (ms). In some implementations, each frame can include multiple subframes. For example, each frame can include 10 subframes, and each subframe can have a duration of, for example, 1 ms. In some implementations, each frame can have the same duration. In some implementations, each subframe of a frame can have the same duration.

[0072] Additionally or alternatively, the time intervals of resources (e.g., communication resources) can be organized according to time slots. For example, a subframe may include multiple (e.g., a number of) time slots. The number of time slots in each subframe may also depend on one or more digital schemes supported in the wireless communication system 100. For example, the first, second, third, fourth, and fifth digital schemes (i.e., μ=0, μ=1, μ=2, μ=3, μ=4) associated with corresponding subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, and 240 kHz may utilize a single time slot per subframe, two time slots per subframe, four time slots per subframe, eight time slots per subframe, and 16 time slots per subframe, respectively. Each time slot may include multiple (e.g., a number of) symbols (e.g., OFDM symbols). In some implementations, the number of time slots in a subframe may depend on a numerical configuration. For a normal cyclic prefix, a time slot may include 14 symbols. For an extended cyclic prefix (e.g., applicable to a 60 kHz subcarrier interval), a time slot may include 12 symbols. The relationship between the number of symbols per slot for the normal cyclic prefix and the extended cyclic prefix, the number of slots per subframe, and the number of slots per frame can depend on the numerical configuration. It should be understood that references to the first numerical configuration (e.g., μ=0) associated with the first subcarrier spacing (e.g., 15 kHz) can be used interchangeably between subframes and slots.

[0073] In the wireless communication system 100, the electromagnetic (EM) spectrum can be divided into various categories, frequency bands, frequency channels, etc., based on frequency or wavelength. As an example, the wireless communication system 100 can support one or more operating frequency bands, such as frequency range names FR1 (410MHz-7.125GHz), FR2 (24.25GHz-52.6GHz), FR3 (7.125GHz-24.25GHz), FR4 (52.6GHz-114.25GHz), FR4a or FR4-1 (52.6GHz-71GHz), and FR5 (114.25GHz-300GHz). In some implementations, network entity 102 and UE 104 can perform wireless communication on one or more operating frequency bands. In some implementations, FR1 can be used by network entity 102 and UE 104, as well as other devices or apparatuses, for cellular communication services (e.g., control information, data). In some implementations, FR2 can be used by network entity 102 and UE 104, as well as other devices or apparatuses for short-range, high data rate capabilities.

[0074] FR1 can be associated with one or more digital schemes (e.g., at least three digital schemes). For example, FR1 can be associated with a first numerical configuration (e.g., μ=0) including a 15 kHz subcarrier spacing; a second numerical configuration (e.g., μ=1) including a 30 kHz subcarrier spacing; and a third numerical configuration (e.g., μ=2) including a 60 kHz subcarrier spacing. FR2 can be associated with one or more digital schemes (e.g., at least two digital schemes). For example, FR2 can be associated with a third numerical configuration (e.g., μ=2) including a 60 kHz subcarrier spacing; and a fourth numerical configuration (e.g., μ=3) including a 120 kHz subcarrier spacing.

[0075] Figure 2 An example of a signaling flow supporting PDCP replication in a side link according to various aspects of this disclosure is shown. In some embodiments, UE104-1 sends 201 configuration information 202 for PDCP replication to UE104-2, which is used for side link transmission from UE104-1 to UE104-2. UE104-1 may also send 204 indication 205 to UE104-2 to indicate the activation and deactivation of PDCP replication. UE104-1 determines 206 the activation and deactivation of PDCP replication based on the capabilities of UE104-2 or the indication from UE104-2.

[0076] For example, UE104-1 establishes a PC5 unicast link 110 and a corresponding PC5-RRC connection with UE104-2. Multiple carriers exist between the UEs for SLRB transmission, associated with either the PC5 unicast link or the PC5-RRC connection. PDCP replication is supported by both UE104-1 and UE104-2, and the network can be (pre-)configured to implement PDCP replication for specific SLRBs (SL-SRB or SL-DRB).

[0077] Furthermore, after establishing the unicast link, UE104-1 sends a 201 PC5-RRC message (e.g., RRCReconfigurationSidelink) or other signaling (e.g., MACCE, etc.) which includes PDCP replication configuration or activation parameters for PDCP replication of a specific SLRB or LCH. UE104-2 can accept or reject the PDCP replication configuration or activation after receiving the 203 PC5RRC message or other signaling. Then, UE104-2 sends a 204 Indication 205 to UE104-1.

[0078] Alternatively, if UE104-2 does not explicitly respond regarding whether it supports PDCP replication, UE104-1 can implicitly determine whether to activate PDCP replication based on UE104-2's capabilities. For example, if UE104-2's capabilities indicate that it is a low-power UE, a redcap UE, an IoT UE, etc., it implicitly indicates that UE104-2 does not wish to or does not support activating PDCP replication. In this case, UE104-1 does not activate PDCP replication for the SLRB of that unicast link.

[0079] In some embodiments, UE104-2 sends a 204 First Instruction to UE104-1 to instruct UE104-2 to determine whether to accept the PDCP replication configuration. For example, if UE104-2 accepts the relevant configuration and activation of PDCP replication, UE104-2 responds to UE104-1 with a 204 acceptance of the PDCP replication configuration or activation, for example, in a PC5-RRC reconfiguration complete message or other signaling.

[0080] In some embodiments, UE104-2 sends a 204 second indication to UE104-1, which instructs UE104-2 to determine the configuration for rejecting PDCP replication and results in information for the configuration for rejecting PDCP replication. For example, if UE104-2 cannot accept the relevant configuration and activation of PDCP replication, UE104-2 responds to UE104-1 with a NACK, such as a PC5-RRC reconfiguration complete message including PDCP replication rejection parameters. If UE104-2 is a low-power UE or is in low-power mode, or if UE104-2 is overheating and UE104-2 does not want to enable PDCP replication, UE104-2 can indicate the reason for rejection, such as overheating, low power, etc., in the response message to UE104-1.

[0081] In some embodiments, if UE104-2 determines that it rejects the PDCP duplication configuration for one or more sidelink radio bearers (SLRBs) or logical channels (LCHs) and accepts the PDCP duplication configuration for one or more other SLRBs or LCHs, UE104-2 sends a third indication to UE104-1. The third indication indicates rejection of the PDCP duplication configuration for one or more SLRBs or LCHs. Alternatively, a fourth indication indicates acceptance of the PDCP duplication configuration for one or more other SLRBs or LCHs. For example, UE104-2 can respond to the rejection with finer granularity. UE104-2 can reject the PDCP duplication configuration or activation for a specific SLRB or LCH while accepting the PDCP duplication configuration or activation for other SLRBs or LCHs. In this case, UE104-1 activates PDCP duplication only for the specific SLRB or LCH based on the peer UE response message.

[0082] In some embodiments, after activating PDCP replication, UE104-2 sends an indication to UE104-1 to activate or deactivate PDCP replication. UE104-2 also sends UE104-1 information regarding the reason for deactivation of PDCP replication. For example, after activating PDCP replication, UE104-2 may send a message to UE104-1 to stop or deactivate PDCP replication during unicast transmission based on UE104-2's condition or a problem with UE104-2. For example, if UE104-2 is overheating, UE104-2 may send a PC5-RRC message or other signaling (e.g., MACCE or PHY signaling) to disable or deactivate PDCP replication. Furthermore, UE104-2 may indicate the reason for deactivation, such as overheating.

[0083] In some embodiments, PDCP replication deactivation is targeted at at least one SLRB, at least one LCH, or at least one Radio Link Control (RLC) entity. For example, UE104-2 can deactivate PDCP replication for a specific SLRB or LCH without deactivating it for other SLRBs or LCHs where PDCP replication is active. Furthermore, UE104-2 can deactivate PDCP replication for a specific RLC entity. If four RLC entities are already active and established, UE104-2 can deactivate one of them, such as RLC entity #2.

[0084] In some embodiments, UE104-2 establishes at least one RLC entity for PDCP replication based on the received configuration information. For example, UE104-2 needs to set up multiple RLC entities according to the PDCP replication configuration. After receiving and accepting the PDCP replication configuration from UE104-1, UE104-2 establishes additional RLC entities for PDCP replication.

[0085] In some embodiments, the establishment of at least one RLC entity is performed based on a configuration that accepts PDCP replication, or by establishing at least one SLRB with PDCP replication enabled in the configuration or pre-configuration, or by activating PDCP replication for at least one SLRB or at least one LCH. For example, UE104-2 establishes additional RLC entities for a specific SLRB or LCH activation after PDCP replication. If PDCP replication activation is indicated from UE104-1 to UE104-2, UE104-1 indicates the RLC entity ID for PDCP activation. After the corresponding SLRB is established, UE104-2 establishes additional RLC entities for PDCP replication and enables PDCP replication for these SLRBs in the (pre)configuration.

[0086] In some embodiments, UE104-1 sends at least one identifier for at least one RLC entity for PDCP to UE104-2. For example, for a particular SLRBLCH, four RLC entities are configured, and UE104-1 determines to activate an additional RLC entity, then UE104-1 may indicate the RLC entity ID to UE104-2.

[0087] In some embodiments, if UE104-1 detects a fault on at least one carrier corresponding to at least one RLC entity associated with PDCP replication for sidelink transmission from UE104-1 to UE104-2, UE104-1 performs activation or deactivation of PDCP replication based on the fault detection. Furthermore, in the case of activating PDCP replication upon detecting a fault, UE104-1 determines the number of RLC entities for activating PDCP replication based on the number of available carriers.

[0088] For example, one or more carriers may be in a fault condition, such as a sidelink radio link failure, beam failure, consistent LBT failure, carrier failure, etc. In this case, the problematic carrier cannot be used for data transmission temporarily. If a carrier is in a fault condition and PDCP replication is not activated but is to be activated, the UE104-1 or gNB determines the activated RLC entity number by considering the available carrier numbers. For example, if there are four carriers and one of them is faulty, up to three RLC entities can be activated. For another example, if there are two carriers and one of them is faulty, PDCP replication cannot be activated.

[0089] In some embodiments, when PDCP replication is activated upon detecting a fault, UE104-1 determines the number of RLC entities to activate PDCP replication, regardless of the number of available carriers. At least one RLC entity is suspended based on the number of available carriers. For example, UE104-1 or gNB may determine activation without considering the available carrier number and wait for additional RLC entities based on the available carrier number. After activation, if one or more carriers fail and the number of remaining carriers is less than the number of activated RLC entities, one or more RLC entities wait until the number of available carriers is equal to or greater than the number of activated RLC entities.

[0090] In some embodiments, if PDCP replication is activated before a fault is detected, at least one RLC entity is suspended until the number of available carriers becomes equal to or greater than the number of active RLC entities, based on the determination that the number of available carriers is less than the number of active RLC entities used for PDCP replication.

[0091] If a fault occurs on a carrier and PDCP replication is already activated, and if one or more carriers are faulty and the number of remaining carriers is less than the number of active RLC entities, then one or more RLC entities are suspended until the number of available carriers is equal to or greater than the number of active RLC entities. Furthermore, after the problematic carrier is restored and one or more RLC entities are reactivated, the UE104-1 can recheck the PDCP replication activation conditions to determine whether to reactivate one or more RLC entities.

[0092] Figure 3An example of a device 300 supporting PDCP replication in a side link according to various aspects of this disclosure is shown. Device 300 may be an example of UE104-1 or UE104-2 as described herein. Device 300 may support wireless communication with one or more network entities 102, UE104, or any combination thereof. Device 300 may include components for bidirectional communication, including components for transmitting and receiving communications, such as processor 302, memory 304, transceiver 306, and optionally, I / O controller 308. These components may be electronically communicative or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0093] Processor 302, memory 304, transceiver 306, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure as described herein. For example, processor 302, memory 304, transceiver 306, or various combinations thereof, or components thereof, may support methods for performing one or more of the operations described herein.

[0094] In some implementations, processor 302, memory 304, transceiver 306, or various combinations or components thereof, may be implemented in hardware (e.g., in communication management circuitry). This hardware may include processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination of elements configured or otherwise supporting the performance of the functions described herein. In some embodiments, processor 302 and memory 304 coupled to processor 302 may be configured to perform one or more of the functions described herein (e.g., processor 302 executing instructions stored in memory 304).

[0095] For example, according to the examples disclosed herein, processor 302 may support wireless communication at device 300. Processor 302 may be configured to operablely support means for transmitting configuration information for Packet Data Convergence Protocol (PDCP) replication for sidelink transmission from first UE to second UE via transceiver, and for determining activation and deactivation of PDCP replication based on the capabilities of the second UE or instructions from the second UE. Furthermore, processor 302 may be configured to operablely support means for detecting faults on at least one carrier corresponding to at least one RLC entity associated with PDCP replication for sidelink transmission from first UE to second UE, and for performing activation or deactivation of PDCP replication based on the detection of the fault. Furthermore, processor 302 may be configured to operablely support means for receiving configuration information for Packet Data Convergence Protocol (PDCP) replication for sidelink transmission from first UE to second UE via transceiver, and for transmitting instructions indicating activation and deactivation of PDCP replication to first UE via transceiver.

[0096] Processor 302 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some embodiments, processor 302 may be configured to operate a memory array using a memory controller. In some other embodiments, the memory controller may be integrated into processor 302. Processor 302 may be configured to execute computer-readable instructions stored in memory (e.g., memory 304) to cause device 300 to perform various functions of this disclosure.

[0097] Memory 304 may include random access memory (RAM) and read-only memory (ROM). Memory 304 may store computer-readable, computer-executable code including instructions that, when executed by processor 302, cause device 300 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some implementations, the code may not be directly executed by processor 302, but may instead cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, memory 304 may include a basic I / O system (BIOS) or similar system that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0098] I / O controller 308 can manage the input and output signals of device 300. I / O controller 308 can also manage peripheral devices not integrated into device M02. In some implementations, I / O controller 308 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 308 can utilize an operating system, such as iOS. ® ANDROID ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Or other known operating systems. In some implementations, the I / O controller 308 may be implemented as part of the processor (e.g., processor 306). In some implementations, the user can interact with the device 300 via the I / O controller 308 or via hardware components controlled by the I / O controller 308.

[0099] In some implementations, device 300 may include a single antenna 310. However, in other implementations, device 300 may have more than one antenna 310 (i.e., multiple antennas), including multiple antenna panels or antenna arrays capable of simultaneously transmitting or receiving multiple wireless transmissions. Transceiver 306 may communicate bidirectionally via one or more antennas 310, wired or wireless links as described herein. For example, transceiver 306 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 306 may also include a modem for modulating packets, providing modulated packets to one or more antennas 310 for transmission, and demodulating packets received from one or more antennas 310. Transceiver 306 may include one or more transmit chains, one or more receive chains, or combinations thereof.

[0100] The transmission chain can be configured to generate and transmit signals (e.g., control information, data, packets). The transmission chain may include at least one modulator for modulating data onto a carrier signal, preparing a signal for transmission over a wireless medium. The at least one modulator may be configured to support one or more techniques, such as amplitude modulation (AM), frequency modulation (FM), or digital modulation schemes like phase shift keying (PSK) or quadrature amplitude modulation (QAM). The transmission chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over a wireless medium. The transmission chain may also include one or more antennas 310 for transmitting the amplified signal into the air or wireless medium.

[0101] A receiver chain can be configured to receive signals (e.g., control information, data, packets) over a wireless medium. For example, the receiver chain may include one or more antennas 310 for receiving signals over the air or a wireless medium. The receiver chain may include at least one amplifier (e.g., a low-noise amplifier (LNA)) configured to amplify the received signal. The receiver chain may include at least one demodulator configured to demodulate the received signal and obtain the transmitted data by reversing the modulation technique applied during signal transmission. The receiver chain may include at least one decoder for decoding the processed demodulated signal to receive the transmitted data.

[0102] Figure 4 An example of a processor 400 supporting PDCP replication in a side link according to various aspects of this disclosure is shown. Processor 400 may be an example of a processor configured to perform various operations according to the examples described herein. Processor 400 may include a controller 402 configured to perform various operations according to the examples described herein. Processor 400 may optionally include at least one memory 404. Additionally or alternatively, processor 400 may optionally include one or more arithmetic logic units (ALUs) 400. One or more of these components may be electronically communicateable or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0103] Processor 400 may be a processor chipset and includes a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receive, acquire, retrieve, send, output, forward, store, determine, identify, access, write, read) according to the examples described herein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to the processor chipset (e.g., processor 400) or included in the processor chipset (e.g., processor 400)) or other memory (e.g., random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase-change memory (PCM), etc.).

[0104] Controller 402 can be configured to manage and coordinate various operations of processor 400 (e.g., signaling, receiving, acquiring, retrieving, sending, outputting, forwarding, storing, determining, identifying, accessing, writing, and reading) to enable processor 400 to support various operations according to the examples described herein. For example, controller 402 can operate as a control unit of processor 400, generating control signals that manage the operation of various components of processor 400. These control signals include enabling or disabling functional units, selecting data paths, initiating memory accesses, and coordinating the timing of operations.

[0105] Controller 402 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from memory 404 and determine subsequent instructions to be executed to enable processor 400 to support various operations according to the examples described herein. Controller 402 may be configured to track the memory addresses of instructions associated with memory 404. Controller 402 may be configured to decode instructions to determine the operation to be performed and the operands involved. For example, controller 402 may be configured to interpret instructions and determine control signals to be output to other components of processor 400, such that processor 400 supports various operations according to the examples described herein. Additionally or alternatively, controller 402 may be configured to manage data flow within processor 400. Controller 402 may be configured to control data transfer between registers, arithmetic logic unit (ALU), and other functional units of processor 400.

[0106] Memory 404 may include one or more caches (e.g., memory native to processor 400 or included in processor 400, or other memory such as RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.). In some implementations, memory 404 may reside within or on the processor chipset (e.g., native to processor 400). In some other implementations, memory 404 may reside outside the processor chipset (e.g., remote from processor 400).

[0107] Memory 404 may store computer-readable, computer-executable code including instructions that, when executed by processor 400, cause processor 400 to perform the various functions described herein. The code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. Controller 402 and / or processor 400 may be configured to execute the computer-readable instructions stored in memory 404, causing processor 400 to perform various functions (e.g., functions or tasks supporting transmission power prioritization). For example, processor 400 and / or controller 402 may be coupled to or coupled to memory 404, and processor 400, controller 402, and memory 404 may be configured to perform the various functions described herein. In some examples, processor 400 may include multiple processors, and memory 404 may include multiple memories. One or more of the multiple processors may be coupled to one or more of the multiple memories, and the multiple memories may be configured individually or collectively to perform the various functions described herein.

[0108] One or more ALU 400s may be configured to support various operations according to the examples described herein. In some embodiments, one or more ALU 400s may reside within or on a processor chipset (e.g., processor 400). In some other embodiments, one or more ALU 400s may reside outside the processor chipset (e.g., processor 400). One or more ALU 400s may perform one or more computations on data, such as addition, subtraction, multiplication, and division. For example, one or more ALU 400s may receive input operands and opcodes, the opcodes determining the operation to be performed. One or more ALU 400s may be configured with various logic and arithmetic circuitry, including adders, subtractors, shifters, and logic gates, to process and manipulate data according to the operation. Alternatively, one or more ALU400s may support logical operations such as AND, OR, XOR, NOR, and NAND, thereby enabling one or more ALU400s to handle conditional operations, comparisons, and bitwise operations.

[0109] Processor 400 may support wireless communication according to the examples disclosed herein. Processor 402 may be configured or operable to support means for transmitting, via a transceiver, to a second UE, configuration information for Packet Data Convergence Protocol (PDCP) replication for sidelink transmission from the first UE to the second UE, and for determining activation and deactivation of PDCP replication based on the capabilities of the second UE or indications from the second UE. Processor 402 may also be configured or operable to support means for detecting faults on at least one carrier corresponding to at least one RLC entity associated with PDCP replication for sidelink transmission from the first UE to the second UE, and for performing activation or deactivation of PDCP replication based on the detection of the fault. Furthermore, processor 402 may be configured or operable to support means for receiving, via a transceiver, configuration information for Packet Data Convergence Protocol (PDCP) replication for sidelink transmission from the first UE to the second UE, and for transmitting via a transceiver, indications for activation and deactivation of PDCP replication to the first UE.

[0110] Figure 5 A flowchart of a method 500 supporting PDCP replication in SDELink according to various aspects of this disclosure is shown. Operation of method 500 may be implemented by means of apparatus or components thereof as described herein. For example, operation of method 500 may be performed by UE104-1, as described herein. In some implementations, the apparatus may execute a set of instructions to control functional elements of the apparatus to perform the described functions. Alternatively or optionally, the apparatus may use dedicated hardware to perform aspects of the described functions.

[0111] In step 505, the method may include sending configuration information for Packet Data Convergence Protocol (PDCP) replication to a second UE via a transceiver for sidelink transmission from the first UE to the second UE. Operation of step 505 can be performed according to the examples described herein. In some implementations, aspects of operation of step 505 may be derived from references... Figure 1 The device described is used to perform this action.

[0112] In 510, the method may include determining the activation and deactivation of PDCP replication based on the capabilities of the second UE or instructions from the second UE. The operation of 510 may be performed according to the examples described herein. In some implementations, aspects of the operation of 510 may be derived from, as referenced... Figure 1 The device described is used to perform this action.

[0113] Figure 6A flowchart of a method 600 supporting PDCP replication in SDELink according to various aspects of this disclosure is shown. Operation of method 600 may be implemented by means of apparatus or components thereof as described herein. For example, operation of method 600 may be performed by UE104-1, as described herein. In some implementations, the apparatus may execute a set of instructions to control functional elements of the apparatus to perform the described functions. Alternatively or optionally, the apparatus may use dedicated hardware to perform aspects of the described functions.

[0114] In 605, the method may include detecting a fault on at least one carrier corresponding to at least one RLC entity associated with a PDCP replication for sidelink transmission from the first UE to the second UE. Operation of 605 may be performed according to the examples described herein. In some implementations, aspects of operation of 605 may be derived from references... Figure 1 The device described is used to perform this action.

[0115] At 610, the method may include performing activation or deactivation of PDCP replication based on fault detection. The operation of 610 may be performed according to the examples described herein. In some implementations, aspects of the operation of 610 may be derived from, as referenced... Figure 1 The device described is used to perform this action.

[0116] Figure 7 A flowchart of a method 700 for PDCP replication in a supporting sidelink according to various aspects of this disclosure is shown. Operation of method 700 can be implemented by means or components thereof as described herein. For example, operation of method 700 can be performed by UE 104-2, as described herein. In some implementations, the device can execute a set of instructions to control functional elements of the device to perform the described functions. Alternatively or optionally, the device can use dedicated hardware to perform aspects of the described functions.

[0117] At 705, the method may include receiving, via a transceiver and from a first UE, configuration information for Packet Data Convergence Protocol (PDCP) replication used for sidelink transmission from the first UE to the second UE. Operation of 705 can be performed according to the examples described herein. In some implementations, aspects of operation of 705 may be derived from references... Figure 1 The device described is used to perform this action.

[0118] In 710, the method may include sending, via a transceiver, an indication of activation and deactivation of PDCP replication to a first UE. The operation of 710 may be performed according to the examples described herein. In some implementations, aspects of the operation of 710 may be derived from, as referenced... Figure 1 The device described is used to perform this action.

[0119] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0120] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors incorporating a DSP core, or any other such configuration).

[0121] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted on a computer-readable medium as one or more instructions or code on that medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0122] Computer-readable media include non-transitory computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. As examples, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store the required program code in the form of instructions or data structures and is accessible by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

[0123] As used herein, including in the claims, the article “a” preceding an element is non-limiting and should be understood to mean “at least one” or “one or more” of those elements. The terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. As used herein, including in the claims, the word “or” used in a list of items (e.g., a list of items beginning with phrases such as “at least one of,” “one or more of,” or “one or both”) indicates an inclusive list, such that a list of at least one of A, B, or C represents A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase “based on” should not be construed as a reference to a closed set of conditions. For example, an example step described as “based on condition A” could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase “based on” should be interpreted in the same manner as the phrase “at least partially based on.” Additionally, as used herein, including in the claims, “group” can include one or more elements.

[0124] The description herein is provided to enable those skilled in the art to make or use the invention. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of this disclosure. Therefore, the invention is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first user equipment (UE), comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: send, via the transceiver, configuration information for packet data convergence protocol (PDCP) duplication for a sidelink transmission from the first UE to a second UE to the second UE; determine activation and deactivation of the PDCP duplication according to a capability of the second UE or an indication from the second UE. the indication comprises a first indication, the processor is further configured to:

2. The first UE of claim 1, wherein, receive, via the transceiver and from the second UE, the first indication to indicate that the second UE decides to accept the PDCP duplication configuration. the indication comprises a second indication, the processor is further configured to:

3. The first UE of claim 1, wherein, receive, via the transceiver and from the second UE, the second indication to indicate that the second UE determines to reject the PDCP duplication configuration and cause information for the rejection of the PDCP duplication configuration. the indication comprises a third indication and a fourth indication, the processor is further configured to:

4. The first UE of claim 1, wherein, in a case that the second UE rejects the PDCP duplication configuration for a first one or more sidelink radio bearers (SLRBs) or logical channels (LCHs) and accepts the PDCP duplication configuration for a second one or more SLRBs or LCHs, receive, via the transceiver and from the second UE, the third indication indicating that the PDCP duplication configuration for the first one or more SLRBs or LCHs is rejected or the fourth indication indicating that the PDCP duplication configuration for the second one or more SLRBs or LCHs is accepted.

5. The first UE of claim 1, wherein the processor is further configured to: determine whether to activate the PDCP duplication based on capability information of the second UE indicating that the second UE supports the PDCP duplication or a type of the second UE indicating that the PDCP duplication is not suitable to be enabled. the indication comprises a fifth indication, the processor is further configured to:

6. The first UE of claim 1, wherein, receive, via the transceiver and from the second UE, the fifth indication to activate or deactivate the PDCP duplication after the PDCP duplication is activated.

7. The first UE of claim 6, wherein the processor is further configured to: receive, via the transceiver and from the second UE, cause information for deactivation of the PDCP duplication.

8. The first UE of claim 6, wherein the deactivation of the PDCP duplication is for one of: at least one SLRB; at least one LCH; or at least one radio link control (RLC) entity.

9. The first UE of claim 1, wherein the processor is further configured to: send, via the transceiver and to the second UE, at least one identifier for at least one RLC entity for the PDCP duplication. the configuration information is sent via one of:

10. The first UE of any one of claims 1-9, wherein, a sidelink radio resource control (RRC) message; a medium access control (MAC) control element (CE); or a radio resource control (RRC) message. Physical layer signaling.

11. A processor for wireless communication, comprising: at least one memory; and a controller coupled with the at least one memory and configured to cause the controller to: transmit, via the transceiver, configuration information for packet data convergence protocol (PDCP) duplication for sidelink transmissions from a first UE to a second UE to the second UE; determine activation and deactivation of the PDCP duplication in accordance with a capability of the second UE or an indication from the second UE.

12. A method performed by a first user equipment, the method comprising: transmitting, via the transceiver, configuration information for packet data convergence protocol (PDCP) duplication for sidelink transmissions from a first UE to a second UE to the second UE; determining activation and deactivation of the PDCP duplication in accordance with a capability of the second UE or an indication from the second UE.

13. A first user equipment (UE), comprising: a processor; and a transceiver coupled to the processor, wherein the processor is configured to: detect a failure on at least one carrier corresponding to at least one RLC entity associated with PDCP duplication for sidelink transmissions from the first UE to a second UE; and perform activation or deactivation of the PDCP duplication based on the failure detection.

14. The first UE of claim 13, wherein, performing activation of the PDCP duplication based on the failure detection comprises: in a case that the PDCP duplication is activated upon detecting the failure, determining a number of RLC entities for the PDCP duplication to be activated based on a number of available carriers.

15. The first UE of claim 13, wherein, performing activation of the PDCP duplication based on the failure detection comprises: in a case that the PDCP duplication is activated upon detecting the failure, determining a number of RLC entities for the PDCP duplication to be activated regardless of a number of available carriers; and suspending at least one RLC entity based on the number of available carriers.

16. The first UE of claim 13, wherein, performing activation of the PDCP duplication based on the failure detection comprises: in a case that the PDCP duplication is activated prior to detecting the failure, suspending at least one RLC entity based on a determination that a number of available carriers is less than a number of RLC entities for activation of the PDCP duplication until the number of available carriers becomes equal to or greater than the number of activated RLC entities.

17. The first UE of claim 13, wherein, performing deactivation of the PDCP duplication based on the failure detection comprises: when detecting the failure, determining a number of RLC entities for the PDCP duplication to be deactivated based on a number of available carriers.

18. The first UE of claim 13, wherein the failure comprises one of: a sidelink radio link failure (RLF); a beam failure; a persistent listen-before-talk (LBT) failure; or a carrier failure.

19. A processor for wireless communication, comprising: at least one memory; and a controller coupled with the at least one memory and configured to cause the controller to: detecting a failure on at least one carrier corresponding to at least one RLC entity associated with PDCP duplication for sidelink transmission from a first UE to a second UE; and performing activation or deactivation of the PDCP duplication based on the failure detection.

20. A method performed by a first user equipment, the method comprising: detecting a failure on at least one carrier corresponding to at least one RLC entity associated with PDCP duplication for sidelink transmission from a first UE to a second UE; and performing activation or deactivation of the PDCP duplication based on the failure detection. ​

Images