WO2022089349A1 - Pdcp重复的配置、激活或去激活方法和终端 - Google Patents

Pdcp重复的配置、激活或去激活方法和终端 Download PDF

Info

Publication number
WO2022089349A1
WO2022089349A1 PCT/CN2021/126026 CN2021126026W WO2022089349A1 WO 2022089349 A1 WO2022089349 A1 WO 2022089349A1 CN 2021126026 W CN2021126026 W CN 2021126026W WO 2022089349 A1 WO2022089349 A1 WO 2022089349A1
Authority
WO
WIPO (PCT)
Prior art keywords
mac
slrb
terminal
deactivation
activation
Prior art date
Application number
PCT/CN2021/126026
Other languages
English (en)
French (fr)
Inventor
梁敬
郑倩
Original Assignee
维沃移动通信有限公司
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 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to EP21885076.6A priority Critical patent/EP4239928A4/en
Priority to JP2023526447A priority patent/JP2023547257A/ja
Publication of WO2022089349A1 publication Critical patent/WO2022089349A1/zh
Priority to US18/302,988 priority patent/US20230262517A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • 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/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/1829—Arrangements specially adapted for the receiver end
    • H04L1/1864—ARQ related signaling
    • 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/1896—ARQ related signaling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0273—Traffic management, e.g. flow control or congestion control adapting protocols for flow control or congestion control to wireless environment, e.g. adapting transmission control protocol [TCP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/54—Allocation or scheduling criteria for wireless resources based on quality criteria
    • H04W72/542—Allocation or scheduling criteria for wireless resources based on quality criteria using measured or perceived quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to a method and terminal for configuring, activating or deactivating duplication of a Packet Data Convergence Protocol (PDCP).
  • PDCP Packet Data Convergence Protocol
  • the Long Term Evolution (Long Term Evolution, LTE) system supports a side link (sidelink) since the 12th release, which is used for direct data transmission between terminals without going through a network side device.
  • Both the Uu and the sidelink of the LTE system support the PDCP repetition function, while in the New Radio (NR) system, only the PDCP repetition function of the Uu is currently supported, and the PDCP repetition function of the NR sidelink is not yet supported.
  • NR New Radio
  • whether to enable the PDCP repetition function can be determined based on the ProSe Per-Packet Reliability (PPPR) threshold of each sidelink data packet, while each sidelink data packet in the NR system no longer has an independent PPPR Attributes, but QoS management is performed through Quality of Service (QoS) flows. Therefore, in the NR sidelink, how to realize the configuration, activation or deactivation of PDCP repetition, and then use the PDCP repetition function to improve the reliability of data packet transmission and reduce the delay of repeated transmission, is an urgent need to solve in the prior art technical problem.
  • PPPR ProSe Per-Packet Reliability
  • the embodiments of the present application provide a method and a terminal for configuring, activating or deactivating PDCP repetition, which can solve the problem that the PDCP repetition function cannot be supported in the related art, thus the reliability of data packet transmission cannot be improved, and the delay of data packet repetition transmission cannot be reduced. The problem.
  • a method for configuring, activating or deactivating PDCP repetition comprising: a terminal receiving a first message, the first message being used to, based on at least one of the following granularities, perform a
  • the SLRB performs the repeated configuration, activation or deactivation of PDCP: SLRB, destination address, link, radio link control RLC bearer or entity, terminal.
  • a terminal including: a receiving module configured to receive a first message, where the first message is used to perform PDCP repetition configuration and activation on an SLRB of the terminal based on at least one of the following granularities Or deactivated: SLRB, destination address, link, radio link control RLC bearer or entity, terminal.
  • a terminal in a third aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor A method as described in the first aspect is implemented.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the method according to the first aspect is implemented.
  • a computer program product comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the When executed by the processor, the method as described in the first aspect is implemented.
  • a chip in a sixth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the method according to the first aspect .
  • the SLRB of the terminal may be configured, activated or deactivated for PDCP repetition based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, terminal, NR sidelink, etc.
  • the PDCP repetition function in the scenario provides an effective solution, which is convenient to improve the reliability of data packet transmission and reduce the delay of data packet repetition transmission through the PDCP repetition function.
  • FIG. 1 is a block diagram of a wireless communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for configuring, activating or deactivating PDCP repetition according to an embodiment of the present application
  • FIG. 3 is a schematic diagram showing the repeated activation or deactivation of the PDCP of the SLRB indicated by the MAC CE by means of a bitmap indication according to an embodiment of the present application;
  • FIG. 4 is a schematic diagram showing the repeated activation or deactivation of the PDCP of the SLRB indicated by the MAC CE by means of a bitmap indication according to another embodiment of the present application;
  • FIG. 5 is a schematic diagram illustrating the activation or deactivation of the PDCP repetition of the SLRB in the manner in which the MAC CE carries the SLRB ID/index according to an embodiment of the present application;
  • FIG. 6 is a schematic diagram illustrating the repeated activation or deactivation of the PDCP of the SLRB in the manner in which the MAC CE carries the destination address according to an embodiment of the present application;
  • FIG. 7 is a schematic diagram showing the repeated activation or deactivation of the PDCP of the SLRB by means of a bitmap indicating that the MAC CE carries a link identifier according to an embodiment of the present application;
  • FIG. 8 is a schematic diagram illustrating the repeated activation or deactivation of PDCP of SLRB in a manner in which a MAC CE carries a link identifier according to another embodiment of the present application;
  • FIG. 9 is a schematic diagram of the repeated activation or deactivation of the PDCP of the SLRB by means of a bitmap indicating that the MAC CE carries the destination address according to an embodiment of the present application;
  • FIG. 10 is a schematic diagram of activating or deactivating a secondary RLC entity by means of a bitmap according to an embodiment of the present application
  • FIG. 11 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the description below, but these techniques can also be applied to applications other than NR system applications, such as 6th Generation , 6G) communication system.
  • NR New Radio
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • PDA Personal Digital Assistant
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Next Generation Node B (gNB), Home Node B, Home Evolved Node B, WLAN Access point, WiFi node, Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. In the application embodiments, only the base station in the NR system is used as an example, but the specific type of the base station is not limited.
  • an embodiment of the present application provides a method 200 for configuring, activating or deactivating PDCP repetition.
  • the method can be executed by a terminal.
  • the method can be executed by software or hardware installed in the terminal.
  • the method includes the following steps.
  • S202 The terminal receives a first message, where the first message is used to perform PDCP repeated configuration, activation or deactivation on a secondary link radio bearer (SideLink Radio Bearer, SLRB) of the terminal based on at least one of the following granularities: SLRB, purpose Address, link, radio link layer control (Radio Link Control, RLC) bearer or entity, terminal.
  • SLRB Secondary Link Radio Bearer
  • RLC Radio Link Control
  • the first message in this embodiment may be a radio resource control (Radio Resource Control, RRC) message, and the RRC message may perform PDCP repetition configuration, activation or deactivation on the SLRB of the terminal based on at least one of the foregoing granularities.
  • RRC Radio Resource Control
  • the first message in this embodiment may also be a media access control-control element (Media Access Control-Control Element, MAC CE) or downlink control information (Downlink Control Information, DCI), and the MAC CE or DCI message may be based on the above granularity At least one of the PDCP repetition activation or deactivation is performed on the SLRB of the terminal.
  • Media Access Control-Control Element Media Access Control-Control Element, MAC CE
  • DCI Downlink Control Information
  • the first message in this embodiment may come from a network-side device, so that the network-side device may perform PDCP repetition configuration, activation or deactivation on the SLRB of the terminal.
  • the first message in this embodiment may also come from the opposite terminal, so that the opposite terminal can perform PDCP repetition configuration, activation or deactivation on the SLRB of the local terminal (ie, the terminal mentioned in S202).
  • the opposite terminal may be a transmitting terminal (TX UE), and the local terminal may be a receiving terminal (RX UE); or, the opposite terminal may be a receiving terminal (RX UE), and the local terminal may be a transmitting terminal ( TX UE).
  • the method for configuring, activating, or deactivating PDCP repetition may perform PDCP repetition configuration, activation, or deactivation on the SLRB of the terminal based on at least one of the following granularities: SLRB, destination address, link, RLC
  • the bearer or entity, terminal provides an effective solution for the PDCP repetition function in scenarios such as NR sidelink, which is convenient to improve the reliability of data packet transmission and reduce the delay of data packet repetition transmission through the PDCP repetition function.
  • the first message in this embodiment includes a MAC CE, and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB of the terminal based on the granularity of the SLRB. That is, in this embodiment, based on the granularity of the SLRB, the SLRB configured by the terminal can be repeatedly activated or deactivated by PDCP (per-SLRB activation and deactivation) through the MAC CE (that is, the first message).
  • PDCP per-SLRB activation and deactivation
  • the MAC CE in this embodiment satisfies at least one of the following 1) to 8):
  • the MAC CE includes an SLRB identifier (ID), an index value or a ranking value, and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB corresponding to the SLRB ID, index value or ranking value.
  • ID an SLRB identifier
  • index value an index value or a ranking value
  • the ID, index value (such as slrb-Uu-ConfigIndex) or order value corresponding to the SLRB may be carried in the MAC CE, so as to activate or deactivate the corresponding SLRB.
  • the MAC CE includes the sorting value, and the MAC CE performs PDCP repetition on the SLRB corresponding to the sorting value in a manner indicated by a bitmap (bitmap). activation or deactivation, wherein the multiple SLRBs configured by the terminal are sorted in target order.
  • bitmap bitmap
  • the MAC CE includes the SLRBID or the index value, and the MAC CE directly indicates the SLRB ID or the index value. Or the SLRB corresponding to the index value performs PDCP repetition activation or deactivation.
  • Mode 1 can sort all the SLRBs configured with duplication according to the ID or index value of the SLRB, and then use the bitmap to indicate whether the i-th SLRB is activated or deactivated (with PDCP repetition).
  • FIG. 3 is a schematic diagram of one byte in the MAC CE
  • Figure 4 is a schematic diagram of two bytes in the MAC CE.
  • the example shown in FIG. 3 sorts the 8 SLRBs configured with PDCP repetition by the terminal in descending order according to the ID or index value of the SLRBs.
  • S i in FIG. 3 indicates that i can be 0-7.
  • the example shown in FIG. 4 sorts the 16 SLRBs configured with PDCP repetition by the terminal in descending order according to the ID or index value of the SLRBs.
  • S i in FIG. 4 indicates that i can be 0-15.
  • Mode 2 may directly indicate the ID or index value corresponding to the SLRB to activate or deactivate the SLRB.
  • the MAC CE includes a transmission range or a transmission range threshold, and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB that satisfies the transmission range or the transmission range threshold.
  • the transmission range or transmission range threshold corresponding to the SLRB is carried in the MAC CE, and the SLRB whose transmission range is equal to the transmission range indicated in the MAC CE or the SLRB whose transmission range meets the transmission range threshold indicated in the MAC CE is subjected to PDCP repetition activation or go activate.
  • the MAC CE is used to activate or deactivate the PDCP repetition for the default SLRB.
  • the MAC CE indicates that the default SLRB is activated or deactivated for PDCP repetition; of course, in other examples, it is also possible to instruct the MAC CE to perform PDCP repetition activation or deactivation for the non-default SLRB.
  • the MAC CE includes a secondary link interface quality of service flow ID (PC5Qos Flow ID, referred to as PFI or PQFI), and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB corresponding to the PFI.
  • PC5Qos Flow ID PC5Qos Flow ID
  • the PFI is carried in the MAC CE, and the SLRB to which the PFI is mapped (or referred to as the corresponding) is used to activate or deactivate the PDCP repetition.
  • the MAC CE includes a communication type (cast type), and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB that satisfies the communication type.
  • the communication type is carried in the MAC CE, and the SLRB whose communication type is configured to be equal to the communication type indicated in the MAC CE performs the repeated activation or deactivation of PDCP, and the above-mentioned communication type includes unicast, multicast or broadcast.
  • the MAC CE includes a discard timer (discard timer) or a discard timer threshold, and the MAC CE is used to perform PDCP repeated activation or deactivation on the SLRB that satisfies the discard timer or the discard timer threshold.
  • the SLRB whose drop timer configuration is equal to the drop timer indicated in the MAC CE is used to activate or deactivate PDCP repetition; or, the SLRB whose drop timer configuration meets the drop timer threshold indicated in the MAC CE is used for PDCP repetition. activate or deactivate.
  • the above-mentioned meeting the discard timer threshold may mean greater than or equal to the threshold; or less than or equal to the threshold.
  • the MAC CE includes a PDCP sequence number size (PDCP SN size), and the MAC CE is used to perform PDCP repetition activation or deactivation for the SLRB that satisfies the PDCP sequence number size.
  • PDCP SN size PDCP sequence number size
  • This example carries the PDCP sequence number size in the MAC CE, and configures the SLRB with the PDCP sequence number size equal to the PDCP sequence number size indicated in the MAC CE to perform PDCP repeated activation or deactivation.
  • the PDCP serial number size mentioned in this example includes 12bit, 18bit or other newly defined serial number size.
  • the MAC CE is used to activate or deactivate the PDCP repetition for the SLRB that supports out-of-order delivery (Out Of Order Delivery).
  • This example indicates in the MAC CE that out-of-sequence delivery of SLRBs will be supported for PDCP repetition activation or deactivation.
  • any two or more factors in the above 1)-8) may also be combined with instructions to perform PDCP repetition activation or deactivation on the SLRB whose configuration meets the requirements.
  • SLRB ID x
  • PDCP repetition activation or deactivation may be performed for the default SLRB, that is, the combination of 1) and 3).
  • This embodiment performs PDCP repeated activation or deactivation (per-destination or per link activation deactivation) on the SLRB of the terminal based on the granularity of the destination address or link.
  • the first message in this embodiment includes a MAC CE, and the MAC CE includes a destination address (destination) or a link ID (link ID); wherein, when the MAC CE includes a destination address, the MAC CE is used for Perform PDCP repetition activation or deactivation on the SLRB corresponding to the destination address; or when the MAC CE includes a link identifier, the MAC CE is used to perform PDCP repetition activation on the SLRB corresponding to the link identifier or deactivate.
  • the destination address is indicated in the MAC CE, and all SLRBs that establish connections with the destination address are repeatedly activated or deactivated for PDCP.
  • the link identifier is indicated in the MAC CE, and all SLRBs belonging to the link identifier are repeatedly activated or deactivated by PDCP.
  • the example shown in this embodiment is shown in FIG. 7 or FIG. 8 .
  • Figures 7 and 8 show a schematic diagram of a byte in the MAC CE.
  • the third embodiment is a combined embodiment of the second embodiment and the first embodiment.
  • the destination address/link identifier is determined first, and then for all SLRBs belonging to the destination address/link identifier, per-SLRB is performed based on one or more of 1)-8) in Embodiment 1.
  • Repeated activation or deactivation of PDCP For example, the destination address is determined first, and then the PDCP repetition activation or deactivation is indicated based on the SLRB ranking value.
  • FIG. 9 is a schematic diagram of two bytes in the MAC CE.
  • the R field in FIG. 9 represents the reserved field.
  • the example shown in FIG. 9 sorts the 8 SLRBs configured with PDCP repetition by the terminal in descending order according to the ID or index value of the SLRB.
  • the SLRB of the terminal is repeatedly activated or deactivated for PDCP (activation and deactivation of per RLC bearer/entity).
  • the first message in this embodiment is used to activate or deactivate at least one secondary RLC entity of the SLRB of the terminal.
  • the activation or deactivation of the secondary RLC entity may be directly indicated through the first message.
  • the secondary RLC entities may be sorted (in ascending or descending order) based on logical channel IDs, where RLC i represents the ith (ascending or descending) secondary RLC entity.
  • the first message in this embodiment is used to perform PDCP repetition activation or deactivation (per UE activation deactivation) on the SLRB of the terminal based on the granularity of the terminal.
  • the network vehicle device can send 1 bit to the terminal through DCI or MAC CE to instruct the terminal to activate or deactivate all SLRBs configured with PDCP repetition.
  • the network side device may configure PDCP repetition based on the report of the terminal, or activate/deactivate the PDCP repetition of SLRB.
  • the method further includes: the terminal sends a second message, where the second message is used to request the SLRB of the terminal to perform PDCP repetition configuration, and activate the or deactivate.
  • the second message includes terminal assistance information (UEAssistanceInformation) or secondary link terminal information (SidelinkUEInformation).
  • UEAssistanceInformation terminal assistance information
  • SidelinkUEInformation secondary link terminal information
  • the second message may include corresponding information under each granularity, such as the SLRBID, index value or sorting value under the per-SLRB granularity.
  • the network side device can be requested to specify which SLRB to perform. Repeated configuration, activation or deactivation of PDCP.
  • the format of the second message may refer to the methods described in the foregoing Embodiments 1 to 5, and then request the network side device to specifically configure, activate or deactivate the PDCP repetition for which SLRB.
  • the terminal carries the information in the first embodiment to the fifth embodiment in the SidelinkUEInformation or UEAssistanceInformation to indicate to the network side device that the terminal wishes to be configured with PDCP repetition, or wishes to activate or deactivate the attribute corresponding to the SLRB of PDCP repetition.
  • the network side device After receiving the report information of the terminal, the network side device performs PDCP repeated configuration or activation or deactivation on the SLRB corresponding to the terminal by using the methods in Embodiment 1 to Embodiment 5.
  • the network side device can perform PDCP repetition configuration on the SLRB through RRC, which can be configured to activate or deactivate (initial state), etc., and the configuration granularity can also be the granularity in Embodiment 1 to Embodiment 5. Subsequently, the above-mentioned SLRB may also be deactivated or activated with PDCP repetition through MAC CE or DCI.
  • the execution subject may be a terminal, or the control in the terminal for performing the method for configuring, activating, or deactivating PDCP repetition. module.
  • the terminal provided by the embodiment of the present application is described by taking the method for the terminal to perform the repeated configuration, activation or deactivation of PDCP as an example.
  • FIG. 11 is a schematic structural diagram of a terminal according to an embodiment of the present application. As shown in FIG. 11 , the terminal 1100 includes the following modules.
  • the receiving module 1102 may be configured to receive a first message, where the first message is used to perform PDCP repetition configuration, activation or deactivation on the SLRB of the terminal based on at least one of the following granularities: SLRB, destination address, chain Road, RLC bearer or entity, terminal.
  • the SLRB of the terminal may be configured, activated or deactivated for PDCP repetition based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, terminal, NR sidelink, etc.
  • the PDCP repetition function in the scenario provides an effective solution, which is convenient to improve the reliability of data packet transmission and reduce the delay of data packet repetition transmission through the PDCP repetition function.
  • the terminal 1100 further includes a sending module configured to send a second message, where the second message is used to request to perform PDCP repetition configuration, activation or deactivation on the SLRB of the terminal.
  • a sending module configured to send a second message, where the second message is used to request to perform PDCP repetition configuration, activation or deactivation on the SLRB of the terminal.
  • the second message includes terminal assistance information or secondary link terminal information.
  • the first message includes a MAC CE
  • the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB of the terminal based on the granularity of the SLRB.
  • the MAC CE satisfies at least one of the following 1) to 8):
  • the MAC CE includes an SLRB identification ID, an index value or a ranking value, and the MAC CE is used to activate or deactivate the PDCP repetition for the SLRB corresponding to the SLRB ID, the index value or the ranking value.
  • the MAC CE includes a transmission range or a transmission range threshold, and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB that satisfies the transmission range or the transmission range threshold.
  • the MAC CE is used to activate or deactivate the PDCP repetition for the default SLRB.
  • the MAC CE includes a secondary link interface quality of service flow identifier PFI, and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB corresponding to the PFI.
  • the MAC CE includes a communication type, and the MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB that satisfies the communication type.
  • the MAC CE includes a drop timer or a drop timer threshold, and the MAC CE is used to perform PDCP repeated activation or deactivation on the SLRB that satisfies the drop timer or the drop timer threshold.
  • the MAC CE includes a PDCP sequence number size, and the MAC CE is used to activate or deactivate PDCP repetition for the SLRB that satisfies the PDCP sequence number size.
  • the MAC CE is used to activate or deactivate PDCP repetition for the SLRB that supports out-of-sequence delivery.
  • the MAC CE includes the sorting value, and the MAC CE performs PDCP repetition activation or deactivation on the SLRB corresponding to the sorting value by means of a bitmap indication, wherein the The multiple SLRBs configured by the terminal are sorted according to the target order; or, the MAC CE includes the SLRB ID or the index value, and the MAC CE directly indicates the SLRB ID or the index value.
  • the SLRB corresponding to the value performs PDCP repetition activation or deactivation.
  • the MAC CE includes a destination address or a link identifier; wherein, the MAC CE is used to perform PDCP repeated activation or deactivation on the SLRB corresponding to the destination address; or, all The MAC CE is used to perform PDCP repetition activation or deactivation on the SLRB corresponding to the link identifier.
  • the first message is used to activate or deactivate at least one secondary RLC entity of the SLRB of the terminal.
  • the first message includes a radio resource control RRC message, and the RRC message is used to perform PDCP repetition configuration on the SLRB of the terminal, and/or the first message includes a MAC CE or downlink control information DCI, the MAC CE or DCI is used to perform PDCP repetition activation or deactivation on the SLRB of the terminal.
  • RRC message is used to perform PDCP repetition configuration on the SLRB of the terminal
  • DCI downlink control information
  • the MAC CE or DCI is used to perform PDCP repetition activation or deactivation on the SLRB of the terminal.
  • the terminal 1100 may refer to the process of the method 200 corresponding to the embodiment of the present application, and each unit/module and the above-mentioned other operations and/or functions in the terminal 1100 are respectively in order to implement the corresponding process in the method 200, And can achieve the same or equivalent technical effects, for the sake of brevity, details are not repeated here.
  • the terminal in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in the terminal.
  • the terminal may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the terminal in this embodiment of the present application may be a device having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the terminal provided in this embodiment of the present application can implement each process implemented by the method embodiments in FIG. 2 to FIG. 10 , and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 1200, including a processor 1201, a memory 1202, a program or instruction stored in the memory 1202 and executable on the processor 1201,
  • a communication device 1200 including a processor 1201, a memory 1202, a program or instruction stored in the memory 1202 and executable on the processor 1201,
  • the communication device 1200 is a terminal
  • the program or instruction is executed by the processor 1201
  • each process of the above-mentioned PDCP repeated configuration, activation or deactivation method embodiment can be achieved, and the same technical effect can be achieved. In order to avoid repetition, I won't go into details here.
  • FIG. 13 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 1300 includes but is not limited to: a radio frequency unit 1301, a network module 1302, an audio output unit 1303, an input unit 1304, a sensor 1305, a display unit 1306, a user input unit 1307, an interface unit 1308, a memory 1309, a processor 1310 and other components .
  • the terminal 1300 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 1310 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 13 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 1304 may include a graphics processor (Graphics Processing Unit, GPU) 13041 and a microphone 13042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 1306 may include a display panel 13061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 1307 includes a touch panel 13071 and other input devices 13072 .
  • the touch panel 13071 is also called a touch screen.
  • the touch panel 13071 may include two parts, a touch detection device and a touch controller.
  • Other input devices 13072 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described herein again.
  • the radio frequency unit 1301 receives the downlink data from the network side device, and then processes it to the processor 1310; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 1301 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 1309 may be used to store software programs or instructions as well as various data.
  • the memory 1309 may mainly include a stored program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 1309 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM) ), erasable programmable read-only memory (ErasablePROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • ErasablePROM ErasablePROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 1310 may include one or more processing units; optionally, the processor 1310 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1310.
  • the radio frequency unit 1301 is configured to receive a first message, and the first message is used to configure, activate or deactivate the PDCP repetition on the secondary link radio bearer SLRB of the terminal based on at least one of the following granularities: SLRB, destination address, link, radio link control RLC bearer or entity, terminal.
  • the SLRB of the terminal may be configured, activated or deactivated for PDCP repetition based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, terminal, NR sidelink, etc.
  • the PDCP repetition function in the scenario provides an effective solution, which is convenient to improve the reliability of data packet transmission and reduce the delay of data packet repetition transmission through the PDCP repetition function.
  • the terminal 1300 provided in this embodiment of the present application can also implement the various processes of the foregoing PDCP repeated configuration, activation, or deactivation method embodiments, and can achieve the same technical effect. To avoid repetition, details are not described here.
  • the embodiments of the present application further provide a readable storage medium, the readable storage medium may be volatile or non-volatile, and a program or an instruction is stored on the readable storage medium, the program or When the instruction is executed by the processor, each process of the above-mentioned PDCP repeated configuration, activation or deactivation method embodiment can be achieved, and the same technical effect can be achieved. To avoid repetition, details are not repeated here.
  • the processor may be the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used for running a program or an instruction to implement the above-mentioned repeated configuration and activation of PDCP or deactivating each process of the method embodiment, and can achieve the same technical effect, in order to avoid repetition, it will not be repeated here.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • the embodiment of the present application further provides a computer program product, the computer program product is stored in a non-transitory memory, and the computer program product is executed by at least one processor to implement the above-mentioned PDCP repeated configuration, activation or deactivation method
  • the embodiment can achieve the same technical effect, and to avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a communication device, which is configured to perform each process of the above-mentioned PDCP repeated configuration, activation or deactivation method embodiments, and can achieve the same technical effect. Repeat.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

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

Abstract

本申请实施例公开了一种PDCP重复的配置、激活或去激活方法和终端，能够解决相关技术中无法支持PDCP重复功能，进而无法提高数据包传输的可靠性及无法降低数据包重复传输的时延的问题。该方法包括：终端接收第一消息，所述第一消息用于基于如下粒度的至少之一，对所述终端的副链路无线承载SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，无线链路控制RLC承载或实体，终端。

Description

PDCP重复的配置、激活或去激活方法和终端
交叉引用
本申请要求在2020年10月28日在中国提交的申请号为202011177351.1、发明名称为“PDCP重复的配置、激活或去激活方法和终端”的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请属于通信技术领域，具体涉及一种分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)重复(duplication)的配置、激活或去激活方法和终端。
背景技术
长期演进(Long Term Evolution，LTE)系统从第12个发布版本开始支持副链路(sidelink)，用于终端之间不通过网络侧设备进行直接数据传输。LTE系统的Uu和sidelink都支持PDCP重复功能，而在新空口(NewRadio，NR)系统中，目前仅支持Uu的PDCP重复功能，对于NR sidelink的PDCP重复功能尚未支持。
在LTE系统中，可以基于每个sidelink数据包的单包可靠性(ProSe Per-Packet Reliability，PPPR)阈值来决定是否开启PDCP重复功能，而NR系统中每个sidelink数据包不再具有独立的PPPR属性，而是通过服务质量(Quality of Service，QoS)流来进行QoS管理。因此，在NR sidelink中，如何实现PDCP重复的配置、激活或去激活，进而通过PDCP重复功能来提高数据包传输的可靠性，同时降低重复传输的时延，是现有技术中亟需解决的技术问题。
发明内容
本申请实施例提供一种PDCP重复的配置、激活或去激活方法和终端，能够解决相关技术中无法支持PDCP重复功能，进而无法提高数据包传输的可靠性及无法降低数据包重复传输的时延的问题。
第一方面，提供了一种PDCP重复的配置、激活或去激活方法，所述方法包括：终端接收第一消息，所述第一消息用于基于如下粒度的至少之一，对所述终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，无线链路控制RLC承载或实体，终端。
第二方面，提供了一种终端，包括：接收模块，用于接收第一消息，所述第一消息用于基于如下粒度的至少之一，对所述终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，无线链路控制RLC承载或实体，终端。
第三方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法。
第四方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法。
第五方面，提供了一种计算机程序产品，该计算机程序产品包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时，实现如第一方面所述的方法。
第六方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法。
在本申请实施例中，可以基于如下粒度的至少之一，对终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，RLC承载或实体，终端，为NR sidelink等场景下的PDCP重复功能提供了一种有效解决方案，便于通过PDCP重复功能提高数据包传输的可靠性及降低数据包重复传输的时延。
附图说明
图1是根据本申请的一个实施例的无线通信系统的框图；
图2是根据本申请的一个实施例的PDCP重复的配置、激活或去激活方法的示意性流程图；
图3是根据本申请的一个实施例中MAC CE通过位图指示的方式指示SLRB的PDCP重复的激活或去激活示意图；
图4是根据本申请的另一个实施例中MAC CE通过位图指示的方式指示SLRB的PDCP重复的激活或去激活示意图；
图5是根据本申请的一个实施例中MAC CE携带SLRB ID/索引的方式指示SLRB的PDCP重复的激活或去激活示意图；
图6是根据本申请的一个实施例中MAC CE携带目的地址的方式指示SLRB的PDCP重复的激活或去激活示意图；
图7是根据本申请的一个实施例中MAC CE携带链路标识，通过位图指示的方式指示SLRB的PDCP重复的激活或去激活示意图；
图8是根据本申请的另一个实施例中MAC CE携带链路标识的方式指示SLRB的PDCP重复的激活或去激活示意图；
图9是根据本申请的一个实施例中MAC CE携带目的地址，通过位图指示的方式指示SLRB的PDCP重复的激活或去激活示意图；
图10是根据本申请的一个实施例中通过位图的方式对辅RLC实体进行激活或去激活示意图；
图11是根据本申请的一个实施例的终端的结构示意图；
图12是根据本申请的一个实施例的通信设备的结构示意图；
图13是根据本申请的一个实施例的终端的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行 清楚地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。以下描述出于示例目的描述了新空口(NewRadio，NR)系统，并且在以下大部分描述中使用NR术语，但是这些技术也可应用于NR系统应用以外的应用，如第6代(6 thGeneration，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计 算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、下一代节点B(gNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(TransmittingReceivingPoint，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的分组数据汇聚协议(Packet Data Convergence Protocol，PDCP，或称作包数据汇聚协议)重复(duplication)的配置、激活或去激活方法和终端进行详细地说明。
如图2所示，本申请的一个实施例提供一种PDCP重复的配置、激活或去激活方法200，该方法可以由终端执行，换言之，该方法可以由安装在终端的软件或硬件来执行，该方法包括如下步骤。
S202：终端接收第一消息，第一消息用于基于如下粒度的至少之一，对终端的副链路无线承载(SideLink Radio Bearer，SLRB)进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，无线链路层控制(Radio Link Control，RLC)承载或实体，终端。
该实施例中的第一消息可以是无线资源控制(Radio Resource Control，RRC)消息，该RRC消息可以基于上述粒度的至少之一对终端的SLRB进行PDCP重复的配置、激活或去激活。
该实施例中的第一消息还可以是媒体接入控制控制单元(Media Access  Control-Control Element，MAC CE)或下行控制信息(Downlink Control Information，DCI)，该MAC CE或DCI消息可以基于上述粒度的至少之一对终端的SLRB进行PDCP重复的激活或去激活。
该实施例中的第一消息可以来自于网络侧设备，这样，网络侧设备可以对终端的SLRB进行PDCP重复的配置、激活或去激活。
该实施例中的第一消息还可以来自于对端终端，这样，对端终端可以对本端终端(即S202中提到的终端)的SLRB进行PDCP重复的配置、激活或去激活。该例子中，对端终端可以是发送终端(TX UE)，本端终端可以是接收终端(RX UE)；或者，对端终端可以是接收终端(RX UE)，本端终端可以是发送终端(TX UE)。
本申请实施例提供的PDCP重复的配置、激活或去激活方法，可以基于如下粒度的至少之一，对终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，RLC承载或实体，终端，为NR sidelink等场景下的PDCP重复功能提供了一种有效解决方案，便于通过PDCP重复功能提高数据包传输的可靠性及降低数据包重复传输的时延。
为详细说明本申请上述实施例提供的PDCP重复的配置、激活或去激活方法，以下将结合几个具体的实施例进行说明。
实施例一
该实施例中的第一消息包括MAC CE，该MAC CE用于基于SLRB的粒度对终端的SLRB进行PDCP重复的激活或去激活。也即，该实施例可以基于SLRB的粒度，通过MAC CE(即第一消息)对终端配置的SLRB进行PDCP重复的激活或去激活(per-SLRB的激活去激活)。
该实施例中的MAC CE满足如下1)至8)中的至少之一：
1)该MAC CE包括有SLRB标识(ID)、索引值或排序值，所述MAC CE用于对所述SLRB ID、索引值或排序值对应的SLRB进行PDCP重复的激活或去激活。
该例子可以在MAC CE中携带SLRB对应的ID、索引值(如 slrb-Uu-ConfigIndex)或排序值，从而将对应的SLRB进行激活或去激活。
在一种具体的实施方式(后续简称方式1)中，所述MAC CE包括所述排序值，所述MAC CE通过位图(bitmap)指示的方式，对所述排序值对应的SLRB进行PDCP重复的激活或去激活，其中，所述终端配置的多个SLRB按照目标顺序排序。
在另一种具体的实施方式中(后续简称方式2)，所述MAC CE包括所述SLRBID或索引值，所述MAC CE通过直接指示所述SLRB ID或索引值的方式，对所述SLRB ID或索引值对应的SLRB进行PDCP重复的激活或去激活。
方式1可以把所有配置了duplication的SLRB根据SLRB的ID或索引值进行排序，然后用bitmap来指示第i个SLRB是(PDCP重复的)激活还是去激活。
方式1所示的例子如图3和图4所示，图3所示的是MAC CE中的一个字节的示意图，图4所示的是MAC CE中的两个字节的示意图。
图3所示的例子将终端配置了PDCP重复的8个SLRB根据SLRB的ID或索引值进行降序排序，图3中S i表示，i可以是0-7。
图4所示的例子将终端配置了PDCP重复的16个SLRB根据SLRB的ID或索引值进行降序排序，图4中S i表示，i可以是0-15。
图3和图4所示的例子中，S i＝1表示激活，S i＝0表示去激活；或者S i＝0表示激活，S i＝1表示去激活。
方式2可以直接指示SLRB对应的ID或索引值来对SLRB进行激活或去激活。方式2所示的例子如图5所示，图5所示的是MAC CE中的一个字节的示意图，直接在MAC CE中携带SLRB的ID或索引(index)，并在最前面用1bit来指示是激活还是去激活，例如，图5所示的A＝1表示激活，A＝0表示去激活；或者A＝0表示激活，A＝1表示去激活。
2)所述MAC CE包括有传输范围(transmission range)或传输范围阈值，所述MAC CE用于对满足所述传输范围或传输范围阈值的SLRB进行PDCP重复的激活或去激活。
该例子在MAC CE中携带SLRB对应的传输范围或传输范围阈值，将传输范围等于MAC CE中指示的传输范围的SLRB或传输范围满足MAC CE中指示的传输范围阈值的SLRB进行PDCP重复的激活或去激活。
3)所述MAC CE用于对默认SLRB进行PDCP重复的激活或去激活。
该例子在MAC CE中指示将默认SLRB进行PDCP重复的激活或去激活；当然，在其他的例子中，还可以在MAC CE中指示将非默认SLRB进行PDCP重复的激活或去激活。
4)所述MAC CE包括有副链路接口服务质量流标识(PC5Qos Flow ID，简称PFI或PQFI)，所述MAC CE用于对所述PFI对应的SLRB进行PDCP重复的激活或去激活。
该例子在MAC CE中携带PFI，将PFI映射到的(或称对应的)SLRB进行PDCP重复的激活或去激活。
5)所述MAC CE包括有通信类型(cast type)，所述MAC CE用于对满足所述通信类型的SLRB进行PDCP重复的激活或去激活。
该例子在MAC CE中携带通信类型，将通信类型配置等于MAC CE中指示的通信类型的SLRB进行PDCP重复的激活或去激活，上述通信类型包括单播、组播或广播。
6)所述MAC CE包括有丢弃定时器(discard timer)或丢弃定时器阈值，所述MAC CE用于对满足所述丢弃定时器或丢弃定时器阈值的SLRB进行PDCP重复的激活或去激活。
该例子将丢弃定时器配置等于MAC CE中指示的丢弃定时器的SLRB进行PDCP重复的激活或去激活；或者，将丢弃定时器配置满足MAC CE中指示的丢弃定时器阈值的SLRB进行PDCP重复的激活或去激活。
上述提到的满足丢弃定时器阈值可以指大于或等于阈值；或者小于或等于阈值。
7)所述MAC CE包括有PDCP序列号尺寸(PDCP SN size)，所述MAC CE用于对满足所述PDCP序列号尺寸的SLRB进行PDCP重复的激活或去激 活。
该例子在MAC CE中携带PDCP序列号尺寸，将PDCP序列号尺寸配置等于MAC CE中指示的PDCP序列号尺寸的SLRB进行PDCP重复的激活或去激活。
该例子中提到的PDCP序列号尺寸包括12bit，18bit或其他新定义的序列号尺寸大小。
8)所述MAC CE用于对支持不按序递交(Out Of Order Delivery)的SLRB进行PDCP重复的激活或去激活。
该例子在MAC CE中指示将支持不按序递交的SLRB进行PDCP重复的激活或去激活。当然，在其他的例子中，还可以在MAC CE中指示将不支持不按序递交的SLRB进行PDCP重复的激活或去激活。
需要说明的是，上述1)-8)中任意两个或多个因素还可以结合指示，将配置满足要求的SLRB进行PDCP重复的激活或去激活。例如，可以将SLRB ID＝x，且为默认的SLRB进行PDCP重复的激活或去激活，即1)和3)的结合。又例如，可以将SLRB排序值i＝x，且传输范围小于阈值y的SLRB进行PDCP重复的激活去激活，即1)和2)的结合。
实施例二
该实施例基于目的地址或链路的粒度对终端的SLRB进行PDCP重复的激活或去激活(per-destination或per link的激活去激活)。
该实施例中的第一消息包括MAC CE，该MAC CE包括有目的地址(destination)或链路标识(link ID)；其中，在该MAC CE包括有目的地址的情况下，该MAC CE用于对所述目的地址对应的SLRB进行PDCP重复的激活或去激活；或在该MAC CE包括有链路标识的情况下，该MAC CE用于对所述链路标识对应的SLRB进行PDCP重复的激活或去激活。
在一种实施方式中，在MAC CE中指示目的地址，将所有与该目的地址建立连接的SLRB进行PDCP重复的激活或去激活。该实施方式所示的例子如图6所示，图6所示的是MAC CE中的一个字节的示意图，图6中的R域 表示预留域，A＝1表示激活，A＝0表示去激活；或者A＝0表示激活，A＝1表示去激活。
在另一种实施方式中，在MAC CE中指示链路标识，将所有属于该链路标识的SLRB进行PDCP重复的激活或去激活，该实施方式所示的例子如图7或图8所示，图7和8所示的是MAC CE中的一个字节的示意图。
图7中的其中Li代表Link ID＝i，i＝0-7，其中，Li＝1表示激活，Li＝0表示去激活；或者Li＝0表示激活，Li＝1表示去激活。
图8中的R域表示预留域，A＝1表示激活，A＝0表示去激活；或者A＝0表示激活，A＝1表示去激活。
实施例三
该实施例三为实施例二+实施例一的组合实施例。
该实施例先确定目的地址/链路标识，然后对于所有属于该目的地址/链路标识的SLRB中，基于实施例一中的1)-8)中的一种或多种方式进行per-SLRB的PDCP重复的激活或去激活。例如，先确定目的地址，再基于SLRB的排序值指示PDCP重复的激活或去激活。
该实施方式所示的例子如图9所示，图9所示的是MAC CE中的两个字节的示意图。图9中的R域表示预留域，图9所示的例子将终端配置了PDCP重复的8个SLRB根据SLRB的ID或索引值进行降序排序，图9中S i表示，i可以是0-7。图9所示的例子中，S i＝1表示激活，S i＝0表示去激活；或者S i＝0表示激活，S i＝1表示去激活。
实施例四
该实施例基于RLC承载(bearer)或实体(entity)的粒度对终端的SLRB进行PDCP重复的激活或去激活(per RLC bearer/entity的激活去激活)。
该实施例中的第一消息用于对所述终端的SLRB的至少一个辅RLC实体进行激活或去激活。
具体地，对于每个SLRB，可以通过第一消息直接指示辅RLC实体的激活或去激活。该实施例可以将辅RLC实体基于逻辑信道ID进行排序(升序 或降序)，其中RLC i就代表第i个(升序或降序)辅RLC实体。RLC i＝1表示激活，RLC i＝0表示去激活；或者RLCi＝0表示激活，RLCi＝1表示去激活。
如图10所示，图10所示的是MAC CE中的一个字节的示意图，图10所示的例子将辅RLC实体进行降序排序，见图10中的RLC 2、RLC 1、RLC 0，RLC i＝1表示激活，RLC i＝0表示去激活；或者RLCi＝0表示激活，RLCi＝1表示去激活。
实施例五
该实施例中的第一消息用于基于终端的粒度，对终端的SLRB进行PDCP重复的激活或去激活(per UE的激活去激活)。
该实施例中，网络车设备可以通过DCI或MAC CE发送1bit给终端，来指示终端所有配置了PDCP重复的SLRB都进行激活或去激活。
可选的，在上面的实施例一至实施例五中，网络侧设备可能基于终端的上报来配置PDCP重复，或激活/去激活SLRB的PDCP重复.
这样，前文各个实施例所述终端接收第一消息之前，所述方法还包括：所述终端发送第二消息，所述第二消息用于请求对所述终端的SLRB进行PDCP重复的配置，激活或去激活。
可选地，第二消息包括终端辅助信息(UEAssistanceInformation)或副链路终端信息(SidelinkUEInformation)。
可选地，第二消息中可以包括了各个粒度下的相应信息，如per-SLRB粒度下的SLRBID、索引值或排序值，这样，通过第二消息可以向网络侧设备请求具体对哪个SLRB进行PDCP重复的配置、激活或去激活。具体地，第二消息的格式可以参照前文实施例一至实施例五介绍的方式，进而向网络侧设备请求具体对哪个SLRB进行PDCP重复的配置、激活或去激活。
该实施例例如，终端在SidelinkUEInformation或UEAssistanceInformation中携带以上实施例一至实施例五中的信息，来向网络侧设备表示终端希望被配置PDCP重复，或希望激活或去激活PDCP重复的SLRB对应的属性。网络侧设备收到终端的上报信息后，通过实施例一至实施例五中的方法将终端 对应的SLRB进行PDCP重复的配置或激活或去激活。
前文各个实施例中，网络侧设备可以通过RRC对SLRB进行PDCP重复的配置，可以配置为激活或去激活(初始状态)等，其中配置的粒度也可以是实施例一至实施例五中的粒度。后续还可以通过MAC CE或DCI对上述SLRB进行PDCP重复的去激活或激活等。
需要说明的是，本申请实施例提供的PDCP重复的配置、激活或去激活方法方法，执行主体可以为终端，或者，该终端中的用于执行PDCP重复的配置、激活或去激活方法的控制模块。本申请实施例中以终端执行PDCP重复的配置、激活或去激活方法为例，说明本申请实施例提供的终端。
图11是根据本申请实施例的终端的结构示意图，如图11所示，终端1100包括如下模块。
接收模块1102，可以用于接收第一消息，所述第一消息用于基于如下粒度的至少之一，对所述终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，RLC承载或实体，终端。
在本申请实施例中，可以基于如下粒度的至少之一，对终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，RLC承载或实体，终端，为NR sidelink等场景下的PDCP重复功能提供了一种有效解决方案，便于通过PDCP重复功能提高数据包传输的可靠性及降低数据包重复传输的时延。
可选地，作为一个实施例，所述终端1100还包括发送模块，用于发送第二消息，所述第二消息用于请求对所述终端的SLRB进行PDCP重复的配置，激活或去激活。
可选地，作为一个实施例，所述第二消息包括终端辅助信息或副链路终端信息。
可选地，作为一个实施例，所述第一消息包括MAC CE，所述MAC CE用于基于SLRB的粒度对所述终端的SLRB进行PDCP重复的激活或去激活。
可选地，作为一个实施例，所述MAC CE满足如下1)至8)中的至少 之一：
1)所述MAC CE包括有SLRB标识ID、索引值或排序值，所述MAC CE用于对所述SLRB ID、索引值或排序值对应的SLRB进行PDCP重复的激活或去激活。
2)所述MAC CE包括有传输范围或传输范围阈值，所述MAC CE用于对满足所述传输范围或传输范围阈值的SLRB进行PDCP重复的激活或去激活。
3)所述MAC CE用于对默认SLRB进行PDCP重复的激活或去激活。
4)所述MAC CE包括有副链路接口服务质量流标识PFI，所述MAC CE用于对所述PFI对应的SLRB进行PDCP重复的激活或去激活。
5)所述MAC CE包括有通信类型，所述MAC CE用于对满足所述通信类型的SLRB进行PDCP重复的激活或去激活。
6)所述MAC CE包括有丢弃定时器或丢弃定时器阈值，所述MAC CE用于对满足所述丢弃定时器或丢弃定时器阈值的SLRB进行PDCP重复的激活或去激活。
7)所述MAC CE包括有PDCP序列号尺寸，所述MAC CE用于对满足所述PDCP序列号尺寸的SLRB进行PDCP重复的激活或去激活。
8)所述MAC CE用于对支持不按序递交的SLRB进行PDCP重复的激活或去激活。
可选地，作为一个实施例，所述MAC CE包括所述排序值，所述MAC CE通过位图指示的方式，对所述排序值对应的SLRB进行PDCP重复的激活或去激活，其中，所述终端配置的多个SLRB按照目标顺序排序；或，所述MAC CE包括所述SLRBID或索引值，所述MAC CE通过直接指示所述SLRB ID或索引值的方式，对所述SLRB ID或索引值对应的SLRB进行PDCP重复的激活或去激活。
可选地，作为一个实施例，所述MAC CE包括有目的地址或链路标识；其中，所述MAC CE用于对所述目的地址对应的SLRB进行PDCP重复的激 活或去激活；或，所述MAC CE用于对所述链路标识对应的SLRB进行PDCP重复的激活或去激活。
可选地，作为一个实施例，所述第一消息用于对所述终端的SLRB的至少一个辅RLC实体进行激活或去激活。
可选地，作为一个实施例，所述第一消息包括无线资源控制RRC消息，所述RRC消息用于对所述终端的SLRB进行PDCP重复的配置，和/或，所述第一消息包括MAC CE或下行控制信息DCI，所述MAC CE或DCI用于对所述终端的SLRB进行PDCP重复的激活或去激活。
根据本申请实施例的终端1100可以参照对应本申请实施例的方法200的流程，并且，该终端1100中的各个单元/模块和上述其他操作和/或功能分别为了实现方法200中的相应流程，并且能够达到相同或等同的技术效果，为了简洁，在此不再赘述。
本申请实施例中的终端可以是装置，也可以是终端中的部件、集成电路、或芯片。该终端可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的终端可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的终端能够实现图2至图10的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图12所示，本申请实施例还提供一种通信设备1200，包括处理器1201，存储器1202，存储在存储器1202上并可在所述处理器1201上运行的程序或指令，例如，该通信设备1200为终端时，该程序或指令被处理器1201执行时实现上述PDCP重复的配置、激活或去激活方法实施例的各 个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图13为实现本申请实施例的一种终端的硬件结构示意图。
该终端1300包括但不限于：射频单元1301、网络模块1302、音频输出单元1303、输入单元1304、传感器1305、显示单元1306、用户输入单元1307、接口单元1308、存储器1309、以及处理器1310等部件。
本领域技术人员可以理解，终端1300还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1310逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图13中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1304可以包括图形处理器(Graphics Processing Unit，GPU)13041和麦克风13042，图形处理器13041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1306可包括显示面板13061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板13061。用户输入单元1307包括触控面板13071以及其他输入设备13072。触控面板13071，也称为触摸屏。触控面板13071可包括触摸检测装置和触摸控制器两个部分。其他输入设备13072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1301将来自网络侧设备的下行数据接收后，给处理器1310处理；另外，将上行的数据发送给网络侧设备。通常，射频单元1301包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1309可用于存储软件程序或指令以及各种数据。存储器1309可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1309可以包括高速随机存取存储器，还可以 包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-OnlyMemory，ROM)、可编程只读存储器(ProgrammableROM，PROM)、可擦除可编程只读存储器(ErasablePROM，EPROM)、电可擦除可编程只读存储器(ElectricallyEPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器1310可包括一个或多个处理单元；可选的，处理器1310可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1310中。
其中，射频单元1301，用于接收第一消息，所述第一消息用于基于如下粒度的至少之一，对所述终端的副链路无线承载SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，无线链路控制RLC承载或实体，终端。
在本申请实施例中，可以基于如下粒度的至少之一，对终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，RLC承载或实体，终端，为NR sidelink等场景下的PDCP重复功能提供了一种有效解决方案，便于通过PDCP重复功能提高数据包传输的可靠性及降低数据包重复传输的时延。
本申请实施例提供的终端1300还可以实现上述PDCP重复的配置、激活或去激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质可以是易失性的，也可以是非易失性的，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述PDCP重复的配置、激活或去激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器可以为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only  Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述PDCP重复的配置、激活或去激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序产品，所述计算机程序产品存储于非瞬态的存储器，所述计算机程序产品被至少一个处理器执行以实现上述PDCP重复的配置、激活或去激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供了一种通信设备，被配置成用于执行上述PDCP重复的配置、激活或去激活方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述 实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (22)

  1. 一种分组数据汇聚协议PDCP重复的配置、激活或去激活方法，所述方法包括：
    终端接收第一消息，所述第一消息用于基于如下粒度的至少之一，对所述终端的副链路无线承载SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，无线链路控制RLC承载或实体，终端。
  2. 根据权利要求1所述的方法，其中，所述终端接收第一消息之前，所述方法还包括：
    所述终端发送第二消息，所述第二消息用于请求对所述终端的SLRB进行PDCP重复的配置，激活或去激活。
  3. 根据权利要求2所述的方法，其中，所述第二消息包括终端辅助信息或副链路终端信息。
  4. 根据权利要求1所述的方法，其中，所述第一消息包括媒体接入控制控制单元MAC CE，所述MAC CE用于基于SLRB的粒度对所述终端的SLRB进行PDCP重复的激活或去激活。
  5. 根据权利要求4所述的方法，其中，所述MAC CE满足如下至少之一：
    所述MAC CE包括有SLRB标识ID、索引值或排序值，所述MAC CE用于对所述SLRB ID、索引值或排序值对应的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有传输范围或传输范围阈值，所述MAC CE用于对满足所述传输范围或传输范围阈值的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE用于对默认SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有副链路接口服务质量流标识PFI，所述MAC CE用于对所述PFI对应的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有通信类型，所述MAC CE用于对满足所述通信类型的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有丢弃定时器或丢弃定时器阈值，所述MAC CE用于对满足所述丢弃定时器或丢弃定时器阈值的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有PDCP序列号尺寸，所述MAC CE用于对满足所述PDCP序列号尺寸的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE用于对支持不按序递交的SLRB进行PDCP重复的激活或去激活。
  6. 根据权利要求5所述的方法，其中，
    所述MAC CE包括所述排序值，所述MAC CE通过位图指示的方式，对所述排序值对应的SLRB进行PDCP重复的激活或去激活，其中，所述终端配置的多个SLRB按照目标顺序排序；或
    所述MAC CE包括所述SLRBID或索引值，所述MAC CE通过直接指示所述SLRB ID或索引值的方式，对所述SLRB ID或索引值对应的SLRB进行PDCP重复的激活或去激活。
  7. 根据权利要求1或5所述的方法，其中，所述第一消息包括MAC CE，所述MAC CE包括有目的地址或链路标识；其中，
    所述MAC CE用于对所述目的地址对应的SLRB进行PDCP重复的激活或去激活；或
    所述MAC CE用于对所述链路标识对应的SLRB进行PDCP重复的激活或去激活。
  8. 根据权利要求1所述的方法，其中，所述第一消息用于对所述终端的SLRB的至少一个辅RLC实体进行激活或去激活。
  9. 根据权利要求1所述的方法，其中，
    所述第一消息包括无线资源控制RRC消息，所述RRC消息用于对所述终端的SLRB进行PDCP重复的配置；和/或
    所述第一消息包括MAC CE或下行控制信息DCI，所述MAC CE或DCI用于对所述终端的SLRB进行PDCP重复的激活或去激活。
  10. 一种终端，包括：
    接收模块，用于接收第一消息，所述第一消息用于基于如下粒度的至少之一，对所述终端的SLRB进行PDCP重复的配置、激活或去激活：SLRB，目的地址，链路，RLC承载或实体，终端。
  11. 根据权利要求10所述的终端，其中，所述终端还包括发送模块，用于发送第二消息，所述第二消息用于请求对所述终端的SLRB进行PDCP重复的配置，激活或去激活。
  12. 根据权利要求11所述的终端，其中，所述第二消息包括终端辅助信息或副链路终端信息。
  13. 根据权利要求10所述的终端，其中，所述第一消息包括媒体接入控制控制单元MAC CE，所述MAC CE用于基于SLRB的粒度对所述终端的SLRB进行PDCP重复的激活或去激活。
  14. 根据权利要求13所述的终端，其中，所述MAC CE满足如下至少之一：
    所述MAC CE包括有SLRB标识ID、索引值或排序值，所述MAC CE用于对所述SLRB ID、索引值或排序值对应的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有传输范围或传输范围阈值，所述MAC CE用于对满足所述传输范围或传输范围阈值的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE用于对默认SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有副链路接口服务质量流标识PFI，所述MAC CE用于对所述PFI对应的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有通信类型，所述MAC CE用于对满足所述通信类型的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有丢弃定时器或丢弃定时器阈值，所述MAC CE用于对满足所述丢弃定时器或丢弃定时器阈值的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE包括有PDCP序列号尺寸，所述MAC CE用于对满足所述PDCP序列号尺寸的SLRB进行PDCP重复的激活或去激活；
    所述MAC CE用于对支持不按序递交的SLRB进行PDCP重复的激活或去激活。
  15. 根据权利要求14所述的终端，其中，
    所述MAC CE包括所述排序值，所述MAC CE通过位图指示的方式，对所述排序值对应的SLRB进行PDCP重复的激活或去激活，其中，所述终端配置的多个SLRB按照目标顺序排序；或
    所述MAC CE包括所述SLRBID或索引值，所述MAC CE通过直接指示所述SLRB ID或索引值的方式，对所述SLRB ID或索引值对应的SLRB进行PDCP重复的激活或去激活。
  16. 根据权利要求10或14所述的终端，其中，所述第一消息包括MAC CE，所述MAC CE包括有目的地址或链路标识；其中，
    所述MAC CE用于对所述目的地址对应的SLRB进行PDCP重复的激活或去激活；或
    所述MAC CE用于对所述链路标识对应的SLRB进行PDCP重复的激活或去激活。
  17. 根据权利要求10所述的终端，其中，所述第一消息用于对所述终端的SLRB的至少一个辅RLC实体进行激活或去激活。
  18. 根据权利要求10所述的终端，其中，
    所述第一消息包括无线资源控制RRC消息，所述RRC消息用于对所述终端的SLRB进行PDCP重复的配置；和/或
    所述第一消息包括MAC CE或下行控制信息DCI，所述MAC CE或DCI用于对所述终端的SLRB进行PDCP重复的激活或去激活。
  19. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至9任一项所述的PDCP重复的配置、激活或去激活方法。
  20. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至9任一项所述的PDCP重复的配置、激活或去激活方法。
  21. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至9任一项所述的PDCP重复的配置、激活或去激活方法。
  22. 一种计算机程序产品，所述计算机程序产品存储于非瞬态的存储器，所述计算机程序产品被至少一个处理器执行以实现如权利要求1至9任一项所述的PDCP重复的配置、激活或去激活方法。
PCT/CN2021/126026 2020-10-28 2021-10-25 Pdcp重复的配置、激活或去激活方法和终端 WO2022089349A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21885076.6A EP4239928A4 (en) 2020-10-28 2021-10-25 PROCEDURE FOR CONFIGURING, ACTIVATING OR DEACTIVATING PDCP DUPLICATION AND TERMINAL DEVICE
JP2023526447A JP2023547257A (ja) 2020-10-28 2021-10-25 Ｐｄｃｐ重複の配置、アクティブ化又は非アクティブ化方法と端末
US18/302,988 US20230262517A1 (en) 2020-10-28 2023-04-19 Pdcp duplication configuring, activating, or deactivating method and terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011177351.1A CN114422094A (zh) 2020-10-28 2020-10-28 Pdcp重复的配置、激活或去激活方法和终端
CN202011177351.1 2020-10-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/302,988 Continuation US20230262517A1 (en) 2020-10-28 2023-04-19 Pdcp duplication configuring, activating, or deactivating method and terminal

Publications (1)

Publication Number Publication Date
WO2022089349A1 true WO2022089349A1 (zh) 2022-05-05

Family

ID=81260524

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/126026 WO2022089349A1 (zh) 2020-10-28 2021-10-25 Pdcp重复的配置、激活或去激活方法和终端

Country Status (5)

Country Link
US (1) US20230262517A1 (zh)
EP (1) EP4239928A4 (zh)
JP (1) JP2023547257A (zh)
CN (1) CN114422094A (zh)
WO (1) WO2022089349A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117460067A (zh) * 2022-07-13 2024-01-26 大唐移动通信设备有限公司 直接通信接口重复传输控制方法、终端及网络设备
CN115398958A (zh) * 2022-07-14 2022-11-25 北京小米移动软件有限公司 数据传输方法和装置
WO2024036519A1 (zh) * 2022-08-17 2024-02-22 北京小米移动软件有限公司 一种侧行链路pdcp复用的激活方法及装置
WO2024082572A1 (en) * 2023-04-06 2024-04-25 Lenovo (Beijing) Limited Methods and apparatuses for a discard timer
WO2024093397A1 (en) * 2023-07-28 2024-05-10 Lenovo (Beijing) Limited Pdcp duplication for slrb

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020198687A1 (en) * 2019-03-27 2020-10-01 Apple Inc. Pdcp duplication enhancements
WO2020197259A1 (ko) * 2019-03-25 2020-10-01 삼성전자 주식회사 무선 통신 시스템에서 복수 개의 rlc 계층 장치의 활성화를 제어하는 방법 및 장치
WO2020192672A1 (zh) * 2019-03-27 2020-10-01 维沃移动通信有限公司 信息发送方法及终端
WO2020198336A1 (en) * 2019-03-28 2020-10-01 Apple Inc. Data duplication over radio link control channels
KR20200114968A (ko) * 2019-03-25 2020-10-07 삼성전자주식회사 무선 통신 시스템에서 복수 개의 rlc 계층 장치의 활성화를 제어하는 방법 및 장치

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10827380B2 (en) * 2018-01-30 2020-11-03 Huawei Technologies Co., Ltd. System and method for supporting URLLC in advanced V2X communications
CN110139322A (zh) * 2018-02-08 2019-08-16 电信科学技术研究院有限公司 一种数据传输方法及终端
CN111130722B (zh) * 2018-10-31 2022-02-22 维沃移动通信有限公司 一种承载的控制方法、终端及网络侧设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020197259A1 (ko) * 2019-03-25 2020-10-01 삼성전자 주식회사 무선 통신 시스템에서 복수 개의 rlc 계층 장치의 활성화를 제어하는 방법 및 장치
KR20200114968A (ko) * 2019-03-25 2020-10-07 삼성전자주식회사 무선 통신 시스템에서 복수 개의 rlc 계층 장치의 활성화를 제어하는 방법 및 장치
WO2020198687A1 (en) * 2019-03-27 2020-10-01 Apple Inc. Pdcp duplication enhancements
WO2020192672A1 (zh) * 2019-03-27 2020-10-01 维沃移动通信有限公司 信息发送方法及终端
WO2020198336A1 (en) * 2019-03-28 2020-10-01 Apple Inc. Data duplication over radio link control channels

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4239928A4 *

Also Published As

Publication number Publication date
EP4239928A1 (en) 2023-09-06
US20230262517A1 (en) 2023-08-17
JP2023547257A (ja) 2023-11-09
EP4239928A4 (en) 2024-03-27
CN114422094A (zh) 2022-04-29

Similar Documents

Publication Publication Date Title
WO2022089349A1 (zh) Pdcp重复的配置、激活或去激活方法和终端
WO2022007930A1 (zh) 一种载波切换处理方法、装置及终端
WO2022022636A1 (zh) 初始接入方法及装置、终端及网络侧设备
EP3937565A1 (en) Communication method and apparatus
WO2022148313A1 (zh) 直流位置处理方法及相关设备
WO2022033560A1 (zh) 上报能力的方法、终端设备和网络设备
WO2022012525A1 (zh) 数据传输方法、数据传输装置、网络侧设备及第一终端
WO2021087996A1 (zh) 通信方法和通信装置
US20230109276A1 (en) Access procedure processing method, apparatus and communications device
WO2022188737A1 (zh) 上行传输方法、装置及终端
WO2022228341A1 (zh) 上行信道的传输参数方法、终端及网络侧设备
WO2022028524A1 (zh) 物理下行控制信道的监听方法、装置和设备
WO2022135439A1 (zh) 资源分配方法和设备
WO2023066106A1 (zh) 数据丢弃方法、装置、终端及网络侧设备
WO2022017480A1 (zh) 管理目标业务的方法、装置和通信设备
WO2022237619A1 (zh) Rrc消息的传输方法及装置、终端及可读存储介质
WO2022012583A1 (zh) 数据处理方法、数据处理装置及第一终端
WO2024017244A1 (zh) 信息发送方法、信息接收方法、装置及相关设备
WO2022033540A1 (zh) 数据传输处理方法、装置及设备
WO2022206664A1 (zh) 信息传输方法、装置及通信设备
WO2023001172A1 (zh) 推荐比特率确定方法、装置及相关设备
CN113950007B (zh) 业务传输的方法、装置和通信设备
WO2022237650A1 (zh) Dci大小对齐方法和设备
WO2021249438A1 (zh) 模式切换方法、终端及网络侧设备
WO2024114642A2 (zh) 数据包的处理方法及通信设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21885076

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2023526447

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021885076

Country of ref document: EP

Effective date: 20230530