WO2024093397A1 - Duplication de pdcp pour slrb - Google Patents

Duplication de pdcp pour slrb Download PDF

Info

Publication number
WO2024093397A1
WO2024093397A1 PCT/CN2023/110041 CN2023110041W WO2024093397A1 WO 2024093397 A1 WO2024093397 A1 WO 2024093397A1 CN 2023110041 W CN2023110041 W CN 2023110041W WO 2024093397 A1 WO2024093397 A1 WO 2024093397A1
Authority
WO
WIPO (PCT)
Prior art keywords
slrb
pdcp duplication
processor
sidelink
base station
Prior art date
Application number
PCT/CN2023/110041
Other languages
English (en)
Inventor
Jing HAN
Min Xu
Jie Hu
Haiming Wang
Original Assignee
Lenovo (Beijing) Limited
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Beijing) Limited filed Critical Lenovo (Beijing) Limited
Priority to PCT/CN2023/110041 priority Critical patent/WO2024093397A1/fr
Publication of WO2024093397A1 publication Critical patent/WO2024093397A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/08—Arrangements for detecting or preventing errors in the information received by repeating transmission, e.g. Verdan system
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0023—Systems modifying transmission characteristics according to link quality, e.g. power backoff characterised by the signalling
    • H04L1/0026—Transmission of channel quality indication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1825—Adaptation of specific ARQ protocol parameters according to transmission conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/188—Time-out mechanisms

Definitions

  • the present disclosure relates to wireless communications, and more specifically to devices, methods, apparatuses, and computer readable medium for packet data convergence protocol (PDCP) duplication for a sidelink radio bearer (SLRB) .
  • PDCP packet data convergence protocol
  • SLRB sidelink radio bearer
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • a PDCP duplication may be configured per SLRB in new radio (NR) sidelink carrier aggregation (CA) .
  • NR new radio
  • CA sidelink carrier aggregation
  • SLRB may configure whether a PDCP duplication is used or not.
  • some more details for PDCP duplication need to be further studied.
  • the present disclosure relates to devices, methods, apparatuses, and computer readable medium for PDCP duplication for SLRB.
  • a first UE comprises at least one memory; and at least one processor coupled with the at least one memory and configured to cause the first UE to: obtain a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; determine a start time for the PDCP duplication of the at least one SLRB; and activate or enable the PDCP duplication for the at least one SLRB from the start time.
  • a base station comprising at least one memory; and at least one processor coupled with the at least one memory and configured to cause the base station to: transmit, to a first UE, a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; receive, from the first UE, information about the first UE and the second UE; and transmit, to the first UE, an indication indicating to the first UE to activate or enable the PDCP duplication for the at least one SLRB.
  • a method performed by the first UE comprises: obtaining a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; determining a start time for the PDCP duplication of the at least one SLRB; and activating or enabling the PDCP duplication for the at least one SLRB from the start time.
  • a method performed by the base station comprises: transmitting, to a first UE, a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; receiving, from the first UE, information about the first UE and the second UE; and transmitting, to the first UE, an indication indicating to the first UE to activate or enable the PDCP duplication for the at least one SLRB.
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: obtain a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; determine a start time for the PDCP duplication of the at least one SLRB; and activate or enable the PDCP duplication for the at least one SLRB from the start time.
  • a processor for wireless communication comprises at least one controller coupled with at least one memory and configured to cause the processor to: transmit, to a first UE, a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; receive, from the first UE, information about the first UE and the second UE; and transmit, to the first UE, an indication indicating to the first UE to activate or enable the PDCP duplication for the at least one SLRB.
  • the first UE determines the start time based on: a first time when a carrier coordination between the first UE and the second UE is finished, and a second time when receiving a capability message from the second UE, wherein the capability message indicates that the second UE supports a PDCP duplication.
  • the first UE determines the start time based on a transmission time of an earliest PC5 message between the first UE and the second UE.
  • the earliest PC5 message is associated with the at least one SLRB.
  • the start time is determined based on a determination that a service associated with a unicast link between the first UE and the second UE indicates that a carrier aggregation (CA) or a PDCP duplication is supported.
  • CA carrier aggregation
  • the at least one SLRB comprises at least one sidelink signalling radio bearer (SL-SRB) , and in accordance with a determination that the PDCP duplication is activated or enabled for at least one sidelink data radio bearer (SL-DRB) , the first UE activates or enables the PDCP duplication for the at least one SL-SRB.
  • SRB sidelink signalling radio bearer
  • the first UE activates or enables the PDCP duplication for partial or all messages associated with the at least one SLRB.
  • the partial or all messages are on a same sidelink control channel (SCCH) or on a same SL-SRB.
  • SCCH sidelink control channel
  • the first UE determines the start time based on a time when one of following conditions fulfills: a timer T400 is still running and a remaining time length of the timer T400 is shorter than a time length threshold, a first index of a channel quality indication (CQI) is lower than a CQI threshold being indicated in a sidelink channel state information (SL-CSI) report, a first reference signal received power (RSRP) of the sidelink determined by the second UE is lower than a power threshold, a consecutive discontinuous transmission (DTX) number is larger than a DTX threshold, a received negative acknowledgement (NACK) number is larger than a NACK threshold, or a sum of a DTX number and a received NACK number is larger than a number threshold.
  • CQI channel quality indication
  • SL-CSI sidelink channel state information
  • RSRP reference signal received power
  • DTX consecutive discontinuous transmission
  • NACK received negative acknowledgement
  • the first UE determines an end time based on a time when one of following conditions fulfills: a second index of a CQI is not lower than the CQI threshold in the SL-CSI report, a second RSRP of the sidelink is not lower than the power threshold, a measured channel busy rate (CBR) is not lower than a CBR threshold, or all SL RBs associated with the sidelink have deactivated the PDCP duplication; and deactivates or disables the PDCP duplication for the at least one SLRB from the end time.
  • CBR channel busy rate
  • the first UE determines the start time based on a reception of an indication from the base station, wherein the indication indicates activating or enabling the PDCP duplication for the at least one SLRB.
  • the first UE receives, from the second UE, capability information of the second UE, wherein the capability information of the second UE indicates that the second UE supports PDCP duplication; transmits, to the base station, the capability information of the second UE; and receives, from the base station, the indication.
  • the first UE transmits, to the base station, information indicating one of: an index of a CQI, an RSRP of the sidelink, a consecutive DTX number, or a received NACK number; and receives, from the base station, the indication, wherein the indication is determined by the base station based on the information.
  • the first UE determines the start time based on a time when one of the following conditions fulfills: one or more indications of listen before talk (LBT) failure for the at least one SLRB are received, a consecutive LBT failure occurs for a resource block (RB) set the at least one SLRB transmits, a number of RB sets for which a consecutive LBT failure occurs is larger than a threshold, a resource reselection is triggered by a consecutive LBT failure, or a number of conditional primary secondary cell (PSCell) addition or change (CPAC) of the at least one SLRB is larger than a further threshold.
  • LBT listen before talk
  • RB resource block
  • PSCell conditional primary secondary cell
  • CPAC conditional primary secondary cell
  • the first UE determines the start time based on a time when one of the following conditions fulfills: a number of received beam failure indications is larger than a threshold value, or a beam failure associated with the at least one SLRB is detected.
  • the first UE transmits, to a base station, capability information of the first UE indicating one of: whether the first UE supports PDCP duplication, at least one band or carrier supporting the PDCP duplication, or a number of carriers supporting the PDCP duplication.
  • the at least one SLRB comprises at least one SL SRB being used for a transmission of a RC5 radio resource control (RRC) message or for a transmission of a PC5-Smessage.
  • RRC radio resource control
  • the first UE setups two or more radio link control (RLC) entities for a same PDCP entity associated with the at least one SLRB; and duplicates a plurality of PDCP packet data units (PDUs) for the two or more RLC entities.
  • RLC radio link control
  • the information comprises capability information of the second UE, wherein the capability information of the second UE indicates that the second UE supports PDCP duplication.
  • the information comprises capability information of the first UE indicating one of: whether the first UE supports PDCP duplication, at least one band or carrier supporting the PDCP duplication, or a number of carriers supporting the PDCP duplication.
  • the information indicates one of: an index of a CQI, an RSRP of the sidelink determined by the second UE, a consecutive DTX number, or a received NACK number.
  • the base station schedules a sidelink resource between the first UE and the second UE.
  • FIG. 1 illustrates an example of a wireless communications system in which some embodiments of the present disclosure can be implemented
  • FIG. 2A illustrates a schematic diagram of a Duplication Activation/Deactivation MAC CE
  • FIG. 2B illustrates a schematic diagram of a Duplication RLC Activation/Deactivation MAC CE
  • FIG. 3 illustrates a schematic diagram of an example communication network in which some embodiments of the present disclosure can be implemented
  • FIG. 4A illustrates an example RRC reconfiguration sidelink procedure
  • FIG. 4B illustrates another example RRC reconfiguration sidelink procedure
  • FIG. 4C illustrates an example sidelink UE capability transfer procedure
  • FIG. 5 illustrates a signalling chart illustrating communication process in accordance with some example embodiments of the present disclosure
  • FIG. 6 illustrates an example of a device that is suitable for implementing embodiments of the present disclosure
  • FIG. 7 illustrates an example of a processor that is suitable for implementing some embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of an example method implemented at a UE in accordance with aspects of the present disclosure.
  • FIG. 9 illustrates a flowchart of an example method implemented at a base station in accordance with some embodiments of the present disclosure.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms. In some examples, values, procedures, or apparatuses are referred to as “best, ” “lowest, ” “highest, ” “minimum, ” “maximum, ” or the like. It will be appreciated that such descriptions are intended to indicate that a selection among many used functional alternatives can be made, and such selections need not be better, smaller, higher, or otherwise preferable to other selections.
  • the term “includes” and its variants are to be read as open terms that mean “includes, but is not limited to. ”
  • the term “based on” is to be read as “based at least in part on. ”
  • the term “one embodiment” and “an embodiment” are to be read as “at least one embodiment. ”
  • the term “another embodiment” is to be read as “at least one other embodiment. ”
  • the use of an expression such as “A and/or B” can mean either “only A” or “only B” or “both A and B. ”
  • Other definitions, explicit and implicit, may be included below.
  • FIG. 1 illustrates an example of a wireless communications system 100 in which some embodiments of the present disclosure can be implemented.
  • the wireless communications system 100 may include one or more network entities 102 (also referred to as network equipment (NE) ) , one or more UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as a long term evolution (LTE) network or an LTE-Advanced (LTE-A) network.
  • LTE long term evolution
  • LTE-A LTE-Advanced
  • the wireless communications system 100 may be a 5G network, such as a new radio (NR) network.
  • NR new radio
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE Institute of Electrical and Electronics Engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the one or more network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station, a network element, a radio access network (RAN) , a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, message, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, message, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an Internet-of-Things (IoT) device, an Internet-of-Everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT Internet-of-Things
  • IoE Internet-of-Everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in FIG. 1.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink (SL) .
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among 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) ) .
  • IAB integrated access backhaul
  • O-RAN open RAN
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a 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 (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC) ) , a Service Management and Orchestration (SMO) system, or any combination thereof.
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • RIC RAN Intelligent Controller
  • RIC e.g., a Near-Real Time RIC (Near-RT RIC) , a Non-Real Time RIC (Non-RT RIC)
  • SMO Service Management and Orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., a layer 3 (L3) , a layer 2 (L2) ) functionality and signaling (e.g., Radio Resource Control (RRC) , service data adaption protocol (SDAP) , Packet Data Convergence Protocol (PDCP) ) .
  • RRC Radio Resource Control
  • SDAP service data adaption protocol
  • PDCP Packet Data Convergence Protocol
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as a layer 1 (L1) (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-C, F1-U)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes 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) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway Packet Data Network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N3, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • proximity communication 5 (PC5) link may be used interchangeably with PC5 interface, sidelink (SL) , unicast link, PC5 unicast link, SL unicast link, device-to-device (D2D) link, user-to-user link, UE-to-UE (U2U) link, or the like.
  • a wireless communications system may include one or more devices, such as one or more base stations and/or one or more UEs.
  • two different UEs may communicate with each other via a PC5 link
  • two different base stations may communicate with each other via an Xn link (Xn interface)
  • Xn interface Xn link
  • Uu link Uu interface
  • a UE may be in a dual connectivity (DC) or may be configured in a carrier aggregation (CA) , in this case, a duplication for data radio bearer (DRB) may be activated or deactivated, e.g., by a radio resource control (RRC) signalling, a medium access control (MAC) control element (CE) , or retransmission scheduling.
  • RRC radio resource control
  • MAC medium access control
  • CE medium access control
  • a duplication for signalling radio bearer (SRB) in NR is always activated if configured with pdcp-Duplication.
  • FIG. 2A illustrates a schematic diagram 210 of a Duplication Activation/Deactivation MAC CE.
  • the Duplication Activation/Deactivation MAC CE of one octet is identified by an MAC subheader with a logical channel identify (LCID) . It has a fixed size and consists of a single octet containing eight D-fields.
  • FIG. 2B illustrates a schematic diagram 220 of a Duplication RLC Activation/Deactivation MAC CE.
  • the Duplication RLC Activation/Deactivation MAC CE is identified by an MAC subheader with eLCID. It has a fixed size and consists of a single octet.
  • a network device may activate or deactivate the PDCP duplication for one or more RLC entities.
  • two different UEs may communicate with each other via a PC5 link.
  • how a PDCP duplication is activated or deactivated should be further studied.
  • Embodiments of the present disclosure provide a solution of PDCP duplication for SLRB.
  • a first UE may obtain a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication.
  • the first UE may determine a start time for the PDCP duplication of the at least one SLRB; and activate or enable the PDCP duplication for the at least one SLRB from the start time.
  • when to activate the PDCP duplication for SLRB may be determined.
  • FIG. 3 illustrates a schematic diagram of an example communication network 300 in which some embodiments of the present disclosure can be implemented.
  • the communication network 300 may include a UE 310, a UE 320, and a base station 330.
  • the base station 330 may be a serving network device (such as a serving gNB) of the UE 310.
  • the base station 330 may communicate with the UE 310 via a Uu link, and the UE 310 may communicate with the UE 320 via a PC5 link.
  • the UE 310 and the UE 320 may communicate with each other via a sidelink channel, such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , a physical sidelink feedback channel (PSFCH) , a physical sidelink broadcast channel (PSBCH) or the like.
  • a sidelink channel such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , a physical sidelink feedback channel (PSFCH) , a physical sidelink broadcast channel (PSBCH) or the like.
  • a PC5 link or PC5 RRC connection may be established between the UE 310 and the UE 320.
  • the UE 320 may locate within the coverage of the base station 330, or may locate outside of the coverage of the base station 330, the present disclosure does not limit this aspect.
  • the base station 330 may communicate with the UE 320 via a Uu link.
  • FIG. 4A illustrates an example RRC reconfiguration sidelink procedure 410
  • FIG. 4B illustrates another example RRC reconfiguration sidelink procedure 420
  • a UE 401 may transmit an RRCReconfigurationSidelink message to a UE 402
  • the UE 402 may transmit an RRCReconfigurationCompleteSidelink message back to the UE 401
  • a UE 401 may transmit an RRCReconfigurationSidelink message to a UE 402
  • the UE 402 may transmit an RRCReconfigurationFailureSidelink message back to the UE 401.
  • the purpose of the RRC reconfiguration sidelink procedure 410/420 is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink data radio bearers (DRBs) , to configure NR sidelink measurement and reporting, to configure sidelink channel state indicator (CSI) reference signal resources.
  • DRBs sidelink data radio bearers
  • the UE (such as the UE 401) may initiate the sidelink RRC reconfiguration procedure and perform an operation on the corresponding PC5-RRC connection in following cases:
  • the UE 401 may be one of UE 310 and UE 320 in FIG. 3, while the UE 402 is the other one of UE 310 and UE 320 in FIG. 3.
  • FIG. 4C illustrates an example sidelink UE capability transfer procedure 430.
  • a UE 401 may transmit a UECapabilityEnquirySidelink message to a UE 402, and the UE 402 may transmit a UECapabilityInforamtionSidelink message back to the UE 401.
  • the UE 401 may transmit a UECapabilityInforamtionSidelink message to the UE 402.
  • a sidelink UE In a sidelink communication, a sidelink UE established a PC5 unicast link and corresponding PC5-RRC connection with a peer UE.
  • SL-SRB0 is used to transmit the PC5-Smessage (s) before the PC5-Ssecurity has been established.
  • SL-SRB1 is used to transmit the PC5-Smessages to establish the PC5-Ssecurity.
  • SL-SRB2 is used to transmit the PC5-Smessages after the PC5-Ssecurity has been established, which is protected.
  • SL-SRB3 is used to transmit the PC5-RRC signalling, which is protected and only sent after the PC5-Ssecurity has been established.
  • SL-SRB4 is used to transmit/receive the NR sidelink discovery messages.
  • ⁇ SL-SRB4 NR sidelink discovery messages
  • FIG. 5 illustrates a signalling chart illustrating communication process 500 in accordance with some example embodiments of the present disclosure.
  • the process 500 may involve the UE 310, the UE 320, and the base station 330 as shown in FIG. 3. It would be appreciated that the process 500 may be applied to other communication scenarios, which will not be described in detail.
  • the UE 310 is a transmitter (Tx UE) and the UE 320 is a receiver (Rx UE) .
  • the UE 310 may be called as a first UE, and the UE 320 may be called as a second UE.
  • the UE 310 obtains 520 a configuration message, where the configuration message indicates that at least one SLRB is configured a PDCP duplication.
  • the configuration message may indicate that one or more SLRBs enable PDCP duplication.
  • the configuration message may be pre-configured.
  • a base station which may be the base station 330 or may be a previously serving network device different from the base station 330, may transmit the configuration message.
  • one or more pre-configured parameters may be pre-stored (or pre-defined) in the UE 310 from the beginning.
  • the base station 330 may transmit 510 the configuration message 515 to the UE 310. And on the other side of communication, the UE 310 obtains the configuration message 515 by receiving.
  • the configuration message 515 may be implemented as an RRC message or RRS signalling.
  • the UE 310 may transmit capability information of the UE 310 to the base station.
  • the capability information of the UE 310 may indicate one or more of: whether the UE 310 supports PDCP duplication, at least one band or carrier supporting the PDCP duplication, or a number of carriers supporting the PDCP duplication. In the present disclosure, it is assumed that the UE 310 supports the PDCP duplication.
  • the UE 310 determines 540 a start time for PDCP duplication. In addition, the UE 310 activate (or enable) 560 the PDCP duplication for the at least one SLRB from the start time.
  • the UE 310 may determine when to activate (or enable) the PDCP duplication based on a resource allocation mode used by the communication between the UE 310 and the UE 320 (i.e., sidelink communication) via a unicast link.
  • a resource allocation mode used by the communication between the UE 310 and the UE 320 (i.e., sidelink communication) via a unicast link.
  • the sidelink communication between the UE 310 and the UE 320 may use a resource allocation mode 2.
  • UE decides the SL transmission resources in the resource pool based on sensing result.
  • the UE 310 may determine the start time based on at least one of: a first time when a carrier coordination between the first UE and the second UE is finished e.g. there are multiple carriers for sidelink transmission and reception between the first UE and the second UE, or a second time when receiving a capability message from the second UE 320, wherein the capability message indicates that the second UE supports a PDCP duplication, or both above conditions have fulfilled.
  • the UE 310 may receive a capability message from the UE 320 at a second time, where the capability message includes capability information of the UE 320, which may indicate that the UE 320 supports a PDCP duplication.
  • multiple carrier coordination between the UE 310 and the UE 320 may be finished (done) at a first time.
  • the start time may be or be after a later one of the first time and the second time.
  • the UE 310 may determine the start time based on a transmission time of an earliest PC5 message between the UE 310 and the UE 320.
  • the earliest PC5 message may be the first one of PC5 messages that are associated with the at least one SLRB.
  • the at least one SLRB may include SL-SRB3 for PC5-RRC message, the earliest PC5 message may be the first PC5-RRC message.
  • the start time may be determined based on a determination that a service associated with the unicast link indicates that a CA or a PDCP duplication is supported. In some examples, if a profile (of the UE 310) of corresponding services associated with the unicast link indicates that CA or PDCP duplication is supported, then the PDCP duplication may be activated or enabled from the first PC5-RRC message. In some examples, if a service associated with the unicast link is a new service which implicitly indicates that the PDCP duplication is supported, then the PDCP duplication may be activated or enabled from the first PC5-RRC message.
  • the at least one SLRB may include one of SL-SRB0, SL-SRB1, or SL-SRB2 for a PC5-Smessage.
  • the at least one SLRB may include SL-SRB4 for an NR SL discovery message.
  • the UE 310 may determine the start time based on a transmission time of an intermediate PC5 message between the UE 310 and the UE 320. In some embodiments, if a PDCP duplication has been activated or enabled for at least one SL-DRB, then the UE 310 may determine to activate (or enable) the PDCP duplication for at least one SL-SRB.
  • the PDCP duplication for at least one SL-SRB (such as SL-SRB3) is activated or enabled when one of SL-DRBs associated with the unicast link or the PC5-RRC connection has activated PDCP duplication.
  • the PDCP duplication for at least one SL-SRB (such as SL-SRB3) is deactivated or disabled when all of SL-DRBs associated with the unicast link or the PC5-RRC connection have deactivated PDCP duplication.
  • the UE 310 may activate or enable the PDCP duplication for partial or all messages associated with the at least one SLRB.
  • the partial or all messages are on a same SCCH or on a same SL-SRB.
  • the at least one SLRB may include SL-SRB3 for PC5-RRC message.
  • the base station 330 may transmit a configuration to the UE 310, where the configuration may be the configuration message 515 above or may be a different message.
  • the configuration may indicate a first group of messages using the SL-SRB3 for which the PDCP duplication can be activated (or enabled) and a second group of messages using the SL-SRB3 for which the PDCP duplication cannot be activated (or enabled) .
  • the UE 310 may activate (or enable) the PDCP duplication for the first group of messages using the SL-SRB3, but not activate (or enable) the PDCP duplication for the second group of messages using the SL-SRB3.
  • the first group of messages may include one or more important PC5-RRC messages using the SL-SRB3.
  • the first group of message may include one or more of: UuMessageTransferSidelink, NotificationMessageSidelink, or the like.
  • the sidelink communication between the UE 310 and the UE 320 may use resource allocation mode 2.
  • the start time of the PDCP duplication may be determined dynamically.
  • the UE 310 may determine that start time based on a time when one of following conditions fulfills: a timer T400 is still running and a remaining time length of the timer T400 is shorter than a time length threshold, a first index of a CQI is lower than a CQI threshold being indicated in an SL-CSI report, a first RSRP of the sidelink determined by the second UE is lower than a power threshold, a consecutive DTX number is larger than a DTX threshold, a received NACK number is larger than a NACK threshold, or a sum of a DTX number and a received NACK number is larger than a number threshold.
  • the at least one SLRB may include SL-SRB3 for PC5-RRC message.
  • a condition may include: a first index of a CQI (i.e., CQI index) is lower than a CQI threshold, where the CQI threshold is indicated in the SL-CSI report.
  • the UE 310 may determine the CQI index of at least one carrier that transmit the PC5-RRC message, or determine the CQI index of all carriers that may be used for transmitting PC5-RRC messages. In some examples, if only one carrier (such as a primary carrier) is allowed to transmit the PC5-PRC message, the CQI index of the primary carrier is considered. In some other examples, if some or all carriers are allowed to transmit the PC5-PRC message, the CQI indexes of the some or all carriers are considered.
  • carrier #1 there are 4 carriers between the UE 310 and the UE 320: carrier #1, carrier #2, carrier #3, and carrier #4.
  • carrier #1 if only carrier #1 is used for transmitting the PC5-RRC message, then the CQI indexes of carrier #1 is considered. For example, if the CQI index of carrier #1 is lower than the CQI threshold, then the condition is fulfilled. In another embodiment, the CQI indexes of carrier #1 to carrier #4 are all considered. For example, if the CQI index of carrier #1, the CQI index of carrier #2, the CQI index of carrier #3, and the CQI index of carrier #4 are all is lower than the CQI threshold, then the condition is fulfilled.
  • a condition may include: a first RSRP of the sidelink (i.e., SL-RSRP) determined by the second UE 320 is lower than a power threshold.
  • the second UE 320 may determine the SL-RSRP and report it to the UE 310 through a measurement report.
  • the UE 310 may determine the SL-RSRP of at least one carrier that transmit the PC5-RRC message, or determine the SL-RSRP of all carriers that may be used for transmitting PC5-RRC messages.
  • the SL-RSRP of the primary carrier is considered if only one carrier (such as a primary carrier) is allowed to transmit the PC5-PRC message.
  • the SL-RSRPs of the some or all carriers are considered.
  • the SL-RSRPs of carrier #1 is considered. For example, if the SL-RSRP of carrier #1 is lower than the power threshold, then the condition is fulfilled. In another embodiment, the SL-RSRPs of carrier #1 to carrier #4 are all considered. For example, if the SL-RSRP of carrier #1, the SL-RSRP of carrier #2, the SL-RSRP of carrier #3, and the SL-RSRP of carrier #4 are all is lower than the power threshold, then the condition is fulfilled.
  • a condition may include: a consecutive DTX number is larger than a DTX threshold.
  • the UE 310 may determine the consecutive DTX number of at least one carrier that transmit the PC5-RRC message, or determine the consecutive DTX number of all carriers that may be used for transmitting PC5-RRC messages. In some examples, if only one carrier (such as a primary carrier) is allowed to transmit the PC5-PRC message, the consecutive DTX number of the primary carrier is considered. In some other examples, if some or all carriers are allowed to transmit the PC5-PRC message, the consecutive DTX numbers of the some or all carriers are considered.
  • the consecutive DTX numbers of carrier #1 is considered. For example, if the consecutive DTX number of carrier #1 exceeds the DTX threshold, then the condition is fulfilled. In another embodiment, the consecutive DTX numbers of carrier #1 to carrier #4 are all considered. For example, if the consecutive DTX number of carrier #1, the consecutive DTX number of carrier #2, the consecutive DTX number of carrier #3, and the consecutive DTX number of carrier #4 all exceed the DTX threshold, then the condition is fulfilled.
  • a condition may include: a received NACK number is larger than a NACK threshold.
  • the received NACK number may be a quantity of received NACK messages within a specific time period.
  • the at least one SLRB may include one or more SL-DRBs.
  • the UE 310 may further determine an end time based on a time when one of following conditions fulfills: a second index of a CQI is not lower than the CQI threshold in the SL-CSI report, a second RSRP of the sidelink is not lower than the power threshold, a measured CBR) is not lower than a CBR threshold, or all SL RBs associated with the sidelink have deactivated the PDCP duplication.
  • the UE 310 may deactivate (or disable) the PDCP duplication for the at least one SLRB from the end time.
  • the second index of a CQI may be a CQI index of a carrier or some carriers or all carriers
  • the second RSRP of the sidelink may be an SL-RSRP of a carrier or some carriers or all carriers, the present disclosure does not limit this aspect.
  • a power saving and a small overhead may be guaranteed if the UE 310 active (or enable) the PDCP duplication dynamically and deactivate (or disable) the PDCP duplication in some cases.
  • the sidelink communication between the UE 310 and the UE 320 may use a resource allocation mode 1.
  • mode 1 the sidelink resource is scheduled by the base station 330.
  • the base station 330 may transmit a resource indication of the sidelink resource to the UE 310, and the sidelink resource is scheduled by the base station 330 and may be used for a sidelink transmission between the UE 310 and the UE 320.
  • the UE 310 may determine the start time based on a reception of an indication from the base station 330, where the indication may indicate activating or enabling the PDCP duplication for the at least one SLRB.
  • the PDCP duplication may be activated or enabled by the base station 330.
  • the indication may be carried in one of: an RRC message, an MAC CE, or a DCI (L1 signalling) .
  • the UE 320 may transmit capability information of the UE 320 to the UE 310.
  • the UE 310 may transmit, to the base station 330, the capability information of the UE 320.
  • the capability information of the UE 320 indicates that the UE 320 supports PDCP duplication.
  • the UE 310 may transmit, to the base station 330, capability information of the UE 310.
  • the capability information of the UE 310 indicates that the UE 310 supports PDCP duplication.
  • the base station 330 may determine when to activate or enable the PDCP duplication for the at least one SLRB based on the capability information of the UE 310 and the UE 320.
  • the UE 310 may determine information associated with the unicast link, and may further transmit the information to the base station 330.
  • the base station 330 may determine when to activate or enable the PDCP duplication for the at least one SLRB based on the information from the UE 310.
  • the information may indicate one of: an index of a CQI, an RSRP of the sidelink, a consecutive DTX number, or a received NACK number.
  • the information may include an index of a CQI, i.e., a CQI index, of a carrier or some carriers or all carriers.
  • the information may include an RSRP of the sidelink, i.e., an SL-RSRP, of a carrier or some carriers or all carriers.
  • the information may include a consecutive DTX number. of a carrier or some carriers or all carriers.
  • the information may include a received NACK number within a specific time period.
  • the sidelink communication between the UE 310 and the UE 320 may use unlicensed band carriers.
  • the UE 310 may determine the start time based on a time when one of the following conditions fulfills: one or more indications of LBT failure for the at least one SLRB are received, a consecutive LBT failure occurs for a RB set the at least one SLRB transmits, a number of RB sets for which a consecutive LBT failure occurs is larger than a threshold, a resource reselection is triggered by a consecutive LBT failure, or a number of CPACs of the at least one SLRB is larger than a further threshold.
  • the configuration message may indicate that one or more SL-SRBs or SL-DRBs are configured with PDCP duplication, e.g., SL-SRB3 (which is for PC5-RRS message) .
  • the UE 310 may activate or enable the PDCP duplication for the SL-SRB3 (or the PC5-RRS message) or for the SL-DRBs dynamically. For example, if the PC5-RRC message or the SL-DRBs are to be transmitted on unlicensed band carrier, the UE 310 may activate (or enable) the PDCP duplication if one or more following conditions fulfilled:
  • the UE 310 may deactivate (or disable) the PDCP duplication.
  • the sidelink communication between the UE 310 and the UE 320 may use one or more carriers with FR2.
  • the UE 310 may determine the start time based on a time when one of the following conditions fulfills: a number of received beam failure indications is larger than a threshold value, or a beam failure associated with the at least one SLRB is detected.
  • the configuration message may indicate that one or more SL-SRBs or SL-DRBs are configured with PDCP duplication, e.g., SL-SRB3 (which is for PC5-RRS message) .
  • the UE 310 may activate or enable the PDCP duplication for the SL-SRB3 (or the PC5-RRS message) or for the SL-DRBs dynamically. For example, if the PC5-RRC message or the SL-DRBs are to be transmitted on carriers with FR2, the UE 310 may activate (or enable) the PDCP duplication if one or more following conditions fulfilled:
  • the UE 310 may further perform a transmission with the UE 320.
  • at least one PC5-RRC message may be transmitted from the UE 310 to the UE 320 via the unicast link.
  • the UE 310 may setup two or more RLC entities for a same PDCP entity associated with the at least one SLRB; and duplicate multiple PDCP PDUs for the two or more RLC entities.
  • the UE 320 may setup two or more RLC entities for the same PDCP entity associated with the at least one SLRB; and receive duplicated multiple PDCP PDUs.
  • the UE 310 may setup two or more RLC entities for the same PDCP entity and duplicate PDCP PDUs from the first PC5-RRC message of the associated PC5-RRC connection, and the UE 320 may setup two or more RLC entities for the same PDCP entity to receive duplicated PDCP PDUs from the first PC5-RRC message of the associated PC5-RRC connection.
  • a start time for a PDCP duplication for at least one SLRB may be determined by a Tx UE, and accordingly an issue that when to activate or enable the PDCP duplication in the NR SL scenario may be solved.
  • FIG. 6 illustrates an example of a device 600 that is suitable for implementing embodiments of the present disclosure.
  • the device 600 may be an example of a UE or a base station as described herein.
  • the device 600 may support wireless communication with the UE 310, the base station 330, or any combination thereof.
  • the device 600 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 602, a memory 604, a transceiver 606, and, optionally, an I/O controller 608. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • interfaces e.g., buses
  • the processor 602, the memory 604, the transceiver 606, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 602, the memory 604, the transceiver 606, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 602 and the memory 604 coupled with the processor 602 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 602, instructions stored in the memory 604) .
  • the processor 602 may support wireless communication at the device 600 in accordance with examples as disclosed herein.
  • the processor 602 may be configured to operable to support a means for obtaining a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; means for determining a start time for the PDCP duplication of the at least one SLRB; and means for activating or enabling the PDCP duplication for the at least one SLRB from the start time.
  • the processor 602 may be configured to operable to support a means for transmitting, to a first UE, a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication; means for receiving, from the first UE, information about the first UE and the second UE; and means for transmitting, to the first UE, an indication indicating to the first UE to activate or enable the PDCP duplication for the at least one SLRB.
  • the processor 602 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 602 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 602.
  • the processor 602 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 604) to cause the device 600 to perform various functions of the present disclosure.
  • the memory 604 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 604 may store computer-readable, computer-executable code including instructions that, when executed by the processor 602 cause the device 600 to perform 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.
  • the code may not be directly executable by the processor 602 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 604 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 608 may manage input and output signals for the device 600.
  • the I/O controller 608 may also manage peripherals not integrated into the device M02.
  • the I/O controller 608 may represent a physical connection or port to an external peripheral.
  • the I/O controller 608 may utilize an operating system such as or another known operating system.
  • the I/O controller 608 may be implemented as part of a processor, such as the processor 606.
  • a user may interact with the device 600 via the I/O controller 608 or via hardware components controlled by the I/O controller 608.
  • the device 600 may include a single antenna 610. However, in some other implementations, the device 600 may have more than one antenna 610 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 606 may communicate bi-directionally, via the one or more antennas 610, wired, or wireless links as described herein.
  • the transceiver 606 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver.
  • the transceiver 606 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 610 for transmission, and to demodulate packets received from the one or more antennas 610.
  • the transceiver 606 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the 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 transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 610 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 610 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • FIG. 7 illustrates an example of a processor 700 that is suitable for implementing some embodiments of the present disclosure.
  • the processor 700 may be an example of a processor configured to perform various operations in accordance with examples as described herein.
  • the processor 700 may include a controller 702 configured to perform various operations in accordance with examples as described herein.
  • the processor 700 may optionally include at least one memory 704, such as L1/L2/L3 cache. Additionally, or alternatively, the processor 700 may optionally include one or more arithmetic-logic units (ALUs) 700.
  • ALUs arithmetic-logic units
  • One or more of these components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 700 may be a processor chipset and include a protocol stack (e.g., a software stack) executed by the processor chipset to perform various operations (e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) in accordance with examples as described herein.
  • a protocol stack e.g., a software stack
  • operations e.g., receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading
  • the processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in the processor chipset (e.g., the processor 700) 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) , and others) .
  • RAM random access memory
  • ROM read-only memory
  • DRAM dynamic RAM
  • SDRAM synchronous dynamic RAM
  • SRAM static RAM
  • FeRAM ferroelectric RAM
  • MRAM magnetic RAM
  • RRAM resistive RAM
  • PCM phase change memory
  • the controller 702 may be configured to manage and coordinate various operations (e.g., signaling, receiving, obtaining, retrieving, transmitting, outputting, forwarding, storing, determining, identifying, accessing, writing, reading) of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may operate as a control unit of the processor 700, generating control signals that manage the operation of various components of the processor 700. These control signals include enabling or disabling functional units, selecting data paths, initiating memory access, and coordinating timing of operations.
  • the controller 702 may be configured to fetch (e.g., obtain, retrieve, receive) instructions from the memory 704 and determine subsequent instruction (s) to be executed to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may be configured to track memory address of instructions associated with the memory 704.
  • the controller 702 may be configured to decode instructions to determine the operation to be performed and the operands involved.
  • the controller 702 may be configured to interpret the instruction and determine control signals to be output to other components of the processor 700 to cause the processor 700 to support various operations in accordance with examples as described herein.
  • the controller 702 may be configured to manage flow of data within the processor 700.
  • the controller 702 may be configured to control transfer of data between registers, arithmetic logic units (ALUs) , and other functional units of the processor 700.
  • ALUs arithmetic logic units
  • the memory 704 may include one or more caches (e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc. In some implementations, the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .
  • caches e.g., memory local to or included in the processor 700 or other memory, such RAM, ROM, DRAM, SDRAM, SRAM, MRAM, flash memory, etc.
  • the memory 704 may reside within or on a processor chipset (e.g., local to the processor 700) . In some other implementations, the memory 704 may reside external to the processor chipset (e.g., remote to the processor 700) .
  • the memory 704 may store computer-readable, computer-executable code including instructions that, when executed by the processor 700, cause the processor 700 to perform 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.
  • the controller 702 and/or the processor 700 may be configured to execute computer-readable instructions stored in the memory 704 to cause the processor 700 to perform various functions.
  • the processor 700 and/or the controller 702 may be coupled with or to the memory 704, the processor 700, the controller 702, and the memory 704 may be configured to perform various functions described herein.
  • the processor 700 may include multiple processors and the memory 704 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein.
  • the one or more ALUs 700 may be configured to support various operations in accordance with examples as described herein.
  • the one or more ALUs 700 may reside within or on a processor chipset (e.g., the processor 700) .
  • the one or more ALUs 700 may reside external to the processor chipset (e.g., the processor 700) .
  • One or more ALUs 700 may perform one or more computations such as addition, subtraction, multiplication, and division on data.
  • one or more ALUs 700 may receive input operands and an operation code, which determines an operation to be executed.
  • One or more ALUs 700 be configured with a variety of logical and arithmetic circuits, including adders, subtractors, shifters, and logic gates, to process and manipulate the data according to the operation. Additionally, or alternatively, the one or more ALUs 700 may support logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 700 to handle conditional operations, comparisons, and bitwise operations.
  • logical operations such as AND, OR, exclusive-OR (XOR) , not-OR (NOR) , and not-AND (NAND) , enabling the one or more ALUs 700 to handle conditional operations, comparisons, and bitwise operations.
  • the processor 700 may support wireless communication in accordance with examples as disclosed herein.
  • the processor 700 may be configured to or operable to support a means for operations described in some embodiments of the present disclosure.
  • FIG. 8 illustrates a flowchart of a method 800 performed by a UE in accordance with aspects of the present disclosure.
  • the operations of the method 800 may be implemented by a device or its components as described herein.
  • the operations of the method 800 may be performed by a UE 310 in FIG. 3.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include obtaining a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication.
  • the operations of 810 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 810 may be performed by the UE 310 as described with reference to FIG. 3.
  • the method may include determining a start time for the PDCP duplication of the at least one SLRB.
  • the operations of 820 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 820 may be performed by the UE 310 as described with reference to FIG. 3.
  • the method may include activating or enabling the PDCP duplication for the at least one SLRB from the start time.
  • the operations of 830 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 830 may be performed by the UE 310 as described with reference to FIG. 3.
  • FIG. 9 illustrates a flowchart of a method 900 performed by a base station in accordance with aspects of the present disclosure.
  • the operations of the method 900 may be implemented by a device or its components as described herein.
  • the operations of the method 900 may be performed by the base station 330 in FIG. 3.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include transmitting, to a first UE, a configuration message indicating that at least one SLRB associated with a second UE is configured with a PDCP duplication.
  • the operations of 910 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 910 may be performed by the base station 330 as described with reference to FIG. 3.
  • the method may include receiving, from the first UE, information about the first UE and the second UE.
  • the operations of 920 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 920 may be performed by the base station 330 as described with reference to FIG. 3.
  • the method may include transmitting, to the first UE, an indication indicating to the first UE to activate or enable the PDCP duplication for the at least one SLRB.
  • the operations of 930 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 930 may be performed by the base station 330 as described with reference to FIG. 3.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a 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 in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Quality & Reliability (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des modes de réalisation de la présente divulgation cités à titre d'exemple concernent un UE, une station de base, des procédés et un support de stockage informatique pour une duplication de PDCP pour SLRB. Dans certains modes de réalisation, un premier UE peut obtenir un message de configuration indiquant qu'au moins un SLRB associé à un second UE est configuré avec une duplication de PDCP. Le premier UE peut déterminer un temps de début pour la duplication de PDCP du/des SLRB ; et activer ou permettre la duplication de PDCP pour le(s) SLRB à partir du temps de début. De telle sorte, le moment d'activation de la duplication de PDCP pour SLRB peut être déterminé.
PCT/CN2023/110041 2023-07-28 2023-07-28 Duplication de pdcp pour slrb WO2024093397A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/110041 WO2024093397A1 (fr) 2023-07-28 2023-07-28 Duplication de pdcp pour slrb

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2023/110041 WO2024093397A1 (fr) 2023-07-28 2023-07-28 Duplication de pdcp pour slrb

Publications (1)

Publication Number Publication Date
WO2024093397A1 true WO2024093397A1 (fr) 2024-05-10

Family

ID=90929630

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/110041 WO2024093397A1 (fr) 2023-07-28 2023-07-28 Duplication de pdcp pour slrb

Country Status (1)

Country Link
WO (1) WO2024093397A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110139322A (zh) * 2018-02-08 2019-08-16 电信科学技术研究院有限公司 一种数据传输方法及终端
CN113785661A (zh) * 2019-05-01 2021-12-10 苹果公司 基于用户装备的分组数据汇聚协议(pdcp)重复激活和去激活
CN114422094A (zh) * 2020-10-28 2022-04-29 维沃移动通信有限公司 Pdcp重复的配置、激活或去激活方法和终端
WO2023000275A1 (fr) * 2021-07-22 2023-01-26 Nec Corporation Procédé, dispositif et support lisible par ordinateur pour des communications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110139322A (zh) * 2018-02-08 2019-08-16 电信科学技术研究院有限公司 一种数据传输方法及终端
CN113785661A (zh) * 2019-05-01 2021-12-10 苹果公司 基于用户装备的分组数据汇聚协议(pdcp)重复激活和去激活
CN114422094A (zh) * 2020-10-28 2022-04-29 维沃移动通信有限公司 Pdcp重复的配置、激活或去激活方法和终端
WO2023000275A1 (fr) * 2021-07-22 2023-01-26 Nec Corporation Procédé, dispositif et support lisible par ordinateur pour des communications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "UE based PDCP duplication activation/deactivation", 3GPP TSG-RAN WG2 MEETING #106, R2-1906365, 3 May 2019 (2019-05-03), XP051710682 *

Similar Documents

Publication Publication Date Title
WO2024093397A1 (fr) Duplication de pdcp pour slrb
WO2024087755A1 (fr) Transmissions de psfch multiples sur un spectre sans licence
WO2024093655A1 (fr) Division de données de liaison montante déclenchée par état de retard
WO2024113888A1 (fr) Sélection de ressources pour une transmission de liaison latérale
WO2024093338A1 (fr) Dispositifs et procédés de communication
WO2024093439A1 (fr) Ajout ou libération de trajet dans un trajet multiple inter-gnb
WO2024082725A1 (fr) Dispositifs et procédés de communication
WO2024109154A1 (fr) Émission de signal de réveil en liaison latérale
WO2024093383A1 (fr) Rapport d'état de mémoire tampon
WO2024109166A1 (fr) Changement de trajet indirect dans un trajet multiple
WO2024109144A1 (fr) Duplication de protocole de convergence de données par paquets dans une transmission par liaison latérale
WO2024093337A1 (fr) Dispositifs et procédés de communication
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024087750A1 (fr) Transmission de signalisation de réveil de liaison latérale
WO2024093358A1 (fr) Dispositifs et procédés de communication
WO2024093344A1 (fr) Mécanisme de détermination d'id court
WO2024098839A1 (fr) Ajout de trajet indirect pour communication u2n
WO2024103852A1 (fr) Mécanisme cho spécifique de nes
WO2024093428A1 (fr) Mécanisme pour cho avec des scg candidats
WO2024119859A1 (fr) Communication de rapports de mesures de faisceau
WO2024093394A1 (fr) Récupération d'informations système
WO2024088019A1 (fr) Signalisation de rapport d'état de retard
WO2024093349A1 (fr) Retransmission autonome pour mcst sl
WO2024093262A1 (fr) Mécanisme d'indication de ressource pusch
WO2024119868A1 (fr) Transmission de données dans un réseau prenant en charge une détection sans fil