Method and terminal for configuring, activating or deactivating PDCP overlap

Abstract

The embodiments of the present application disclose a method and a terminal for configuring, activating, or deactivating PDCP overlap, which can solve problems in the related art that the PDCP overlap function cannot be supported, and further the reliability of data packet transmission cannot be improved and the delay of data packet overlap transmission cannot be reduced. The method includes receiving a first message by a terminal, the first message being used to configure, activate, or deactivate PDCP overlap for a sidelink radio bearer (SLRB) of the terminal based on at least one granularity of the SLRB, the destination, the link, the radio link control (RLC) bearer or entity, and the terminal.

Description

[Technical field]

[0001] (CROSS REFERENCE TO RELATED APPLICATIONS) This application claims priority to a Chinese patent application filed in China on October 28, 2020, bearing application number 202011177351.1 and entitled "Method and terminal for configuring, activating or deactivating PDCP overlap", the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the field of communications technology, and in particular to a method and terminal for configuring, activating or deactivating Packet Data Convergence Protocol (PDCP) duplication. [Background technology]

[0003] The Long Term Evolution (LTE) system supports sidelink for direct data transmission between terminals without network equipment from the 12th release version. Both Uu and sidelink in the LTE system support PDCP overlap function, but the New Radio (NR) system currently supports only Uu PDCP overlap function, and does not yet support NR sidelink PDCP overlap function.

[0004] In the LTE system, it can be determined whether to turn on the PDCP duplication function based on the ProSe Per-Packet Reliability (PPPR) threshold of each sidelink data packet, while in the NR system, each sidelink data packet no longer has an independent PPPR attribute, and QoS management is performed according to Quality of Service (QoS) flows. Therefore, in the NR sidelink, how to realize the configuration, activation or deactivation of PDCP duplication, and further how to improve the reliability of data packet transmission and reduce the delay of duplication transmission through the PDCP duplication function are technical problems that need to be solved urgently in the prior art. Summary of the Invention [Problem to be solved by the invention]

[0005] The embodiments of the present application provide a method and terminal for configuring, activating or deactivating PDCP duplication, which can solve the problems in the related art of not being able to support the PDCP duplication function, and further not being able to improve the reliability of data packet transmission and not being able to reduce the delay of data packet duplication transmission. [Means for solving the problem]

[0006] According to a first aspect, there is provided a method for configuring, activating or deactivating PDCP overlap, the method including receiving a first message by a terminal, the first message being used to configure, activate or deactivate PDCP overlap for an SLRB of the terminal based on granularity of at least one of an SLRB, a destination, a link, a radio link control (RLC) bearer or entity, and a terminal.

[0007] According to a second aspect, a terminal is provided, the terminal including: a receiving module for receiving a first message, the first message being used to configure, activate or deactivate PDCP overlap for an SLRB of the terminal based on a granularity of at least one of an SLRB, a destination, a link, a radio link control (RLC) bearer or entity, and a terminal.

[0008] According to a third aspect, there is provided a terminal including a processor, a memory, and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, implementing a method according to the first aspect.

[0009] According to a fourth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, realises the method of the first aspect.

[0010] According to a fifth aspect there is provided a computer program product comprising a processor, a memory and a program or instructions stored in the memory and operable to run on the processor, the program or instructions, when executed by the processor, implementing a method according to the first aspect.

[0011] According to a sixth aspect, there is provided a chip, the chip including a processor and a communication interface, the communication interface coupled to the processor, the processor running a program or instructions and adapted to implement the method of the first aspect. Effect of the Invention

[0012] In an embodiment of the present application, PDCP duplication can be configured, activated or deactivated for an SLRB of a terminal based on the granularity of at least one of the SLRB, the destination, the link, the RLC bearer or entity, and the terminal, providing an effective solution to the PDCP duplication function in scenarios such as NR sidelink, and facilitating the improvement of reliability of data packet transmission through the PDCP duplication function and the reduction of delay in data packet duplication transmission. [Brief description of the drawings]

[0013] [Figure 1] 1 is a block diagram of a wireless communication system according to one embodiment of the present application. [Diagram 2] 1 is a schematic flowchart of a method for configuring, activating or deactivating a PDCP overlap according to one embodiment of the present application. [Diagram 3] FIG. 2 is a schematic diagram of a MAC CE instructing activation or deactivation of PDCP duplication of an SLRB in a manner indicated by a bitmap according to one embodiment of the present application; [Figure 4] A schematic diagram of a MAC CE instructing activation or deactivation of PDCP duplication of an SLRB in a manner indicated by a bitmap according to another embodiment of the present application. [Diagram 5] A schematic diagram of a MAC CE instructing activation or deactivation of PDCP duplication of an SLRB in a manner carrying an SLRB ID / index according to one embodiment of the present application. [Figure 6] A schematic diagram of a MAC CE instructing activation or deactivation of PDCP duplication of an SLRB in a manner carrying a destination according to one embodiment of the present application. [Figure 7] 1 is a schematic diagram of a MAC CE carrying a link identifier and indicating activation or deactivation of PDCP duplication of an SLRB in a manner indicated by a bitmap according to one embodiment of the present application; [Figure 8]A schematic diagram of a MAC CE instructing activation or deactivation of PDCP duplication of an SLRB in a manner carrying a link identifier according to another embodiment of the present application. [Figure 9] A schematic diagram of a MAC CE carrying a destination and indicating activation or deactivation of PDCP duplication of an SLRB in a manner indicated by a bitmap according to one embodiment of the present application. [Figure 10] FIG. 2 is a schematic diagram of activating or deactivating a secondary RLC entity in a bitmap manner according to one embodiment of the present application; [Figure 11] FIG. 2 is a structural schematic diagram of a terminal according to one embodiment of the present application; [Figure 12] FIG. 2 is a structural schematic diagram of a communication device according to one embodiment of the present application; [Figure 13] FIG. 2 is a structural schematic diagram of a terminal according to one embodiment of the present application; DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] The following clearly describes the technical solutions in the embodiments of the present application in conjunction with the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only some of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present application are all within the scope of protection of the present application.

[0015] The terms "first," "second," etc. in the specification and claims of the present application are intended to distinguish between similar objects and are not intended to describe a particular order or sequence. It is to be understood that data so used are interchangeable where appropriate, such that the embodiments of the present application may be performed in an order other than that shown or described herein, and that the objects distinguished by "first" and "second" are generally of the same type and do not limit the number of objects, e.g., the first object may be one or more. Note that "and / or" in the specification and claims represents at least one of the objects connected, and the character " / " generally represents an "or" relationship between the related objects.

[0016] It should be noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be applied to other wireless communication systems, such as 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), and other systems. The terms "system" and "network" in the embodiments of the present application are always used interchangeably, and the techniques described may be used in the above-mentioned systems and radio technologies, or in other systems and radio technologies. Although the following description describes a New Radio (NR) system for illustrative purposes and uses NR terminology in most of the following description, these technologies may also be used in applications other than NR system applications, such as sixth generation (6G) systems.th This may be applied to a 6G (6th Generation) communication system.

[0017] FIG. 1 shows a block diagram of a wireless communication system to which the embodiment of the present application can be applied. The wireless communication system includes a terminal 11 and a network side device 12. Here, the terminal 11 may be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a terminal side device such as a mobile phone, a tablet personal computer, a laptop computer (or called a notebook computer), a personal digital assistant (PDA), a palmtop computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile Internet device (MID), a wearable device, a vehicle-mounted device (VUE), a pedestrian terminal (PUE), etc., and the wearable device includes a bracelet, an earphone, glasses, etc. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network side equipment 12 may be a base station or a core network, where the base station may be called 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 (BSS), an extended service set (ESS), a B node, an evolved B node (eNB), a next generation Node B (gNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting receiving point (TRP), or any other suitable term in the art, and as long as the same technical effect is achieved, the base station is not limited to a specific technical term, and it should be explained that in the embodiments of this application, only a base station in an NR system is taken as an example, but the specific type of the base station is not limited.

[0018] In the following, a method and terminal for configuring, activating or deactivating duplication of a Packet Data Convergence Protocol (PDCP) according to an embodiment of the present application will be described in detail with reference to the drawings, in accordance with specific embodiments and application scenarios thereof.

[0019] As shown in FIG. 2, one embodiment of the present application provides a method 200 for configuring, activating or deactivating PDCP overlap, which may be performed by a terminal, in other words, the method may be performed by software or hardware installed in the terminal, and the method includes the following steps:

[0020] S202, the terminal receives a first message, the first message being used to configure, activate or deactivate PDCP overlap for a SideLink Radio Bearer (SLRB) of the terminal based on at least one granularity of the SLRB, the destination, the link, the Radio Link Control (RLC) bearer or entity, and the terminal.

[0021] The first message in this embodiment may be a Radio Resource Control (RRC) message, which may configure, activate or deactivate PDCP overlap for an SLRB of the terminal based on at least one of the above granularities.

[0022] The first message in this embodiment may be a Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI), and the MAC CE or DCI message may activate or deactivate PDCP duplication for the SLRB of the terminal based on at least one of the above granularities.

[0023] The first message in this embodiment may be from the network side device, and thus the network side device may configure, activate or deactivate PDCP overlap for the SLRB of the terminal.

[0024] The first message in this embodiment may be from the opposite terminal, and thus the opposite terminal may configure, activate or deactivate PDCP overlap for the SLRB of its own terminal (i.e. the terminal referred to in S202). In this example, the opposite terminal may be a transmitting terminal (TX UE) and the own terminal may be a receiving terminal (RX UE), or the opposite terminal may be a receiving terminal (RX UE) and the own terminal may be a transmitting terminal (TX UE).

[0025] The method for configuring, activating, or deactivating PDCP overlap according to an embodiment of the present application can configure, activate, or deactivate PDCP overlap for an SLRB of a terminal based on the granularity of at least one of the SLRB, the destination, the link, the RLC bearer or entity, and the terminal, providing an effective solution to the PDCP overlap function in scenarios such as NR sidelink, and facilitating the improvement of reliability of data packet transmission through the PDCP overlap function and the reduction of delay in data packet overlap transmission.

[0026] In order to describe in detail the method for configuring, activating or deactivating PDCP redundancy according to the above embodiments of the present application, the following will be described in conjunction with several specific embodiments.

[0027] Example 1 In this embodiment, the first message includes a MAC CE, and the MAC CE is used to activate or deactivate PDCP duplication for an SLRB of a terminal based on the granularity of the SLRB. That is, in this embodiment, PDCP duplication can be activated or deactivated (per-SLRB activation / deactivation) for an SLRB allocated to a terminal via the MAC CE (i.e., the first message) based on the granularity of the SLRB.

[0028] The MAC CE in this embodiment satisfies at least one of the following 1) to 8).

[0029] 1) The MAC CE includes an SLRB identifier (ID), an index value, or a sort value, and the MAC CE is used to activate or deactivate PDCP duplication for the SLRB corresponding to the SLRB ID, index value, or sort value.

[0030] In this example, the activation or deactivation of a corresponding SLRB can be performed by carrying an ID, an index value (eg, slrb-Uu-ConfigIndex) or a sort value corresponding to the SLRB in the MAC CE.

[0031] In one specific embodiment (hereinafter referred to as embodiment 1), the MAC CE includes the sort value, and the MAC CE activates or deactivates PDCP duplication for an SLRB corresponding to the sort value in a manner indicated by a bitmap, where multiple SLRBs located in the terminal are sorted according to a target order.

[0032] In another specific embodiment (hereinafter referred to as embodiment 2), the MAC CE includes the SLRB ID or index value, and the MAC CE activates or deactivates PDCP duplication for the SLRB corresponding to the SLRB ID or index value in a manner of directly indicating the SLRB ID or index value.

[0033] In form 1, all SLRBs in which duplication is arranged may be sorted by the SLRB ID or index value, and a bitmap may indicate whether the i-th SLRB is activated or deactivated (of PDCP duplication).

[0034] Examples shown in form 1 are as shown in FIG. 3 and FIG. 4, where FIG. 3 shows a schematic diagram of one byte in the MAC CE, and FIG. 4 shows a schematic diagram of two bytes in the MAC CE.

[0035] In the example shown in FIG. 3, the eight SLRBs in which PDCP duplication is placed in the terminal are sorted in descending order by the SLRB ID or index value. i where i may be 0 to 7.

[0036] In the example shown in FIG. 4, 16 SLRBs in which PDCP duplication is placed in the terminal are sorted in descending order by the SLRB ID or index value. i where i may be 0 to 15.

[0037] In the examples shown in Figs. 3 and 4, S i =1 indicates activation, S i =0 indicates deactivation, or S i =0 indicates activation, S i =1 indicates deactivation.

[0038] In form 2, the SLRB may be activated or deactivated by directly indicating an ID or index value corresponding to the SLRB. An example of form 2 is as shown in Fig. 5, which shows a schematic diagram of one byte in the MAC CE, which directly carries the ID or index of the SLRB in the MAC CE, and indicates activation or deactivation with 1 bit at the beginning, for example, A=1 in Fig. 5 indicates activation and A=0 indicates deactivation, or A=0 indicates activation and A=1 indicates deactivation.

[0039] 2) The MAC CE includes a transmission range or a transmission range threshold, and the MAC CE is used to activate or deactivate PDCP overlap for SLRBs that satisfy the transmission range or transmission range threshold.

[0040] In this example, the MAC CE carries a transmission range or a transmission range threshold corresponding to the SLRB, and activates or deactivates PDCP overlap for SLRBs whose transmission range is equal to the transmission range indicated in the MAC CE or whose transmission range meets the transmission range threshold indicated in the MAC CE.

[0041] 3) The MAC CE is used to activate or deactivate PDCP duplication for the default SLRB.

[0042] In this example, the MAC CE is instructed to activate or deactivate PDCP overlap for a default SLRB, and of course, in other examples, the MAC CE may be instructed to activate or deactivate PDCP overlap for a non-default SLRB.

[0043] 4) The MAC CE includes a sidelink interface Quality of Service Flow Identifier (PC5 Qos Flow ID, abbreviated as PFI or PQFI), and the MAC CE is used to activate or deactivate PDCP duplication for the SLRB corresponding to the PFI.

[0044] In this example, the MAC CE carries the PFI and activates or deactivates PDCP duplication for the SLRB to which the PFI maps (or is said to correspond).

[0045] 5) The MAC CE includes a cast type, and the MAC CE is used to activate or deactivate PDCP duplication for an SLRB that satisfies the cast type.

[0046] In this example, it carries a communication type in the MAC CE and activates or deactivates PDCP overlap for SLRBs whose communication type configuration is equal to the communication type indicated in the MAC CE, where the communication type includes unicast, groupcast or broadcast.

[0047] 6) The MAC CE includes a discard timer or a discard timer threshold, and the MAC CE is used to activate or deactivate PDCP duplication for SLRBs that satisfy the discard timer or the discard timer threshold.

[0048] In this example, an SLRB whose discard timer configuration is equal to the discard timer indicated in the MAC CE is activated or deactivated for PDCP duplication, or an SLRB whose discard timer configuration meets the discard timer threshold indicated in the MAC CE is activated or deactivated for PDCP duplication.

[0049] As referred to above, meeting the discard timer threshold may refer to being above the threshold or below the threshold.

[0050] 7) The MAC CE includes a PDCP sequence number size (PDCP SN size), and the MAC CE is used to activate or deactivate PDCP duplication for an SLRB that satisfies the PDCP sequence number size.

[0051] In this example, the SLRB carrying the PDCP sequence number size in the MAC CE and having a PDCP sequence number size alignment equal to the PDCP sequence number size indicated in the MAC CE is used to activate or deactivate PDCP duplication.

[0052] The PDCP sequence number sizes mentioned in this example include 12 bits, 18 bits, or other newly defined sequence number sizes.

[0053] 8) The MAC CE is used to activate or deactivate PDCP duplication for SLRBs that support Out Of Order Delivery.

[0054] In this example, the MAC CE instructs the SLRB that supports out-of-order delivery to activate or deactivate PDCP overlap. Of course, in other examples, the MAC CE may instruct the SLRB that does not support out-of-order delivery to activate or deactivate PDCP overlap.

[0055] It should be noted that any two or more of the elements 1) to 8) above may be combined to instruct the SLRB whose configuration satisfies the requirements to activate or deactivate PDCP duplication. For example, the SLRB whose SLRB ID=x and is the default may be activated or deactivated for PDCP duplication, i.e., 1) and 3) may be combined. Also, for example, the SLRB whose SLRB sort value i=x and whose transmission range is smaller than a threshold y may be activated or deactivated for PDCP duplication, i.e., 1) and 2) may be combined.

[0056] Example 2 In this embodiment, PDCP duplication is activated or deactivated for the SLRB of the terminal based on destination or link granularity (per-destination or per link activation or deactivation).

[0057] In this embodiment, the first message includes a MAC CE, which includes a destination or a link identifier (link ID), where if the MAC CE includes a destination, the MAC CE is used to activate or deactivate PDCP duplication for an SLRB corresponding to the destination, or if the MAC CE includes a link identifier, the MAC CE is used to activate or deactivate PDCP duplication for an SLRB corresponding to the link identifier.

[0058] In one embodiment, the MAC CE indicates a destination and activates or deactivates PDCP duplication for all SLRBs that have established a connection with this destination. An example of this embodiment is shown in Figure 6, which shows a schematic diagram of one byte in the MAC CE, where the R field in Figure 6 represents a reserved field, and A=1 represents activation and A=0 represents deactivation, or A=0 represents activation and A=1 represents deactivation.

[0059] In another embodiment, a link identifier is indicated in the MAC CE, and PDCP duplication is activated or deactivated for all SLRBs belonging to this link identifier, and an example of this embodiment is shown in Figure 7 or Figure 8, where a schematic diagram of one byte in the MAC CE is shown.

[0060] Li in FIG. 7 represents Link ID=i, where i=0 to 7, where Li=1 represents activation and Li=0 represents deactivation, or Li=0 represents activation and Li=1 represents deactivation.

[0061] The R field in FIG. 8 represents a reserved field, where A=1 represents activation and A=0 represents deactivation, or A=0 represents activation and A=1 represents deactivation.

[0062] Example 3 This Example 3 is a combination example of Example 2+Example 1.

[0063] In this embodiment, a destination / link identifier is first determined, and then, for all SLRBs belonging to this destination / link identifier, activation or deactivation of PDCP duplication of per-SLRB is performed based on one or more of the forms 1) to 8) in embodiment 1. For example, a destination is first determined, and then activation or deactivation of PDCP duplication is instructed based on the sort value of the SLRB.

[0064] An example of this embodiment is shown in Figure 9, which shows a schematic diagram of two bytes in MAC CE. The R field in Figure 9 represents a reserved field. In the example shown in Figure 9, the eight SLRBs in which PDCP duplication is arranged in the terminal are sorted in descending order according to the ID or index value of the SLRB. In Figure 9, S i where i may be 0 to 7. In the example shown in FIG. i =1 indicates activation, S i =0 indicates deactivation, or S i =0 indicates activation, S i =1 indicates deactivation.

[0065] Example 4 In this embodiment, PDCP duplication is activated or deactivated for the SLRB of the terminal based on the granularity of the RLC bearer or entity (activation or deactivation per RLC bearer / entity).

[0066] The first message in this embodiment is used to activate or deactivate at least one secondary RLC entity of an SLRB of the terminal.

[0067] Specifically, for each SLRB, the first message may directly instruct the activation or deactivation of the secondary RLC entity. In this embodiment, the secondary RLC entities may be sorted (ascending or descending) based on the logical channel ID, where RLC i represents the i-th (ascending or descending) secondary RLC entity. i =1 indicates activation, RLC i =0 represents deactivation, or RLCi=0 represents activation and RLCi=1 represents deactivation.

[0068] As shown in FIG. 10, FIG. 10 shows a schematic diagram of one byte in MAC CE. In the example shown in FIG. 10, the secondary RLC entities are sorted in descending order, as shown in FIG. 10 as RLC2, RLC1, and RLC0. i =1 indicates activation, RLC i =0 represents deactivation, or RLCi=0 represents activation and RLCi=1 represents deactivation.

[0069] Example 5 The first message in this embodiment is used to activate or deactivate PDCP duplication for the SLRB of the terminal based on the granularity of the terminal (per UE activation / deactivation).

[0070] In this embodiment, the network side device may instruct the terminal to activate or deactivate all SLRBs in which PDCP overlap is configured by sending 1 bit to the terminal via DCI or MAC CE.

[0071] Optionally, in the above embodiments 1 to 5, the network side device may configure PDCP duplication or activate / deactivate PDCP duplication in the SLRB based on a report from the terminal.

[0072] Thus, in each of the above-mentioned embodiments, before the terminal receives the first message, the method further includes the terminal sending a second message, the second message being used to request configuration, activation or deactivation of PDCP overlap for an SLRB of the terminal.

[0073] Optionally, the second message includes terminal assistance information (UE Assistance Information) or sidelink terminal information (Sidelink UE Information).

[0074] Alternatively, the second message may include corresponding information at each granularity, for example, an SLRB ID, an index value, or a sort value at per-SLRB granularity, and thus the second message may request the network side device to specifically configure, activate, or deactivate PDCP duplication for which SLRB. Specifically, the format of the second message may refer to the forms introduced in the above-mentioned embodiments 1 to 5, and more specifically, the second message requests the network side device to specifically configure, activate, or deactivate PDCP duplication for which SLRB.

[0075] In this embodiment, for example, the terminal conveys the information in any one of the above embodiments 1 to 5 in SidelinkUEInformation or UEAssistanceInformation to indicate to the network side device that the terminal expects to configure PDCP overlap or expects to activate or deactivate an attribute corresponding to the SLRB of PDCP overlap. After receiving the report information of the terminal, the network side device configures, activates, or deactivates PDCP overlap for the corresponding SLRB of the terminal in the manner in any one of the embodiments 1 to 5.

[0076] In each of the above embodiments, the network side device may configure PDCP duplication for the SLRB by RRC, and may configure it to be activated or deactivated (initial state), etc., where the granularity of the configuration may be the granularity in embodiments 1 to 5. Then, the MAC CE or DCI may deactivate or activate PDCP duplication for the SLRB.

[0077] It should be mentioned that in the method for configuring, activating or deactivating PDCP overlap according to the embodiment of the present application, the execution body may be a terminal or a control module for executing the method for configuring, activating or deactivating PDCP overlap in the terminal. In the embodiment of the present application, the terminal according to the embodiment of the present application will be described by taking the terminal performing the method for configuring, activating or deactivating PDCP overlap as an example.

[0078] FIG. 11 is a structural schematic diagram of a terminal according to an embodiment of the present application. As shown in FIG. 11, a terminal 1100 includes the following modules:

[0079] The receiving module 1102 may be used to receive a first message, which is used to configure, activate, or deactivate PDCP overlap for an SLRB of the terminal based on granularity of at least one of an SLRB, a destination, a link, an RLC bearer or entity, and a terminal.

[0080] In an embodiment of the present application, PDCP duplication can be configured, activated or deactivated for an SLRB of a terminal based on the granularity of at least one of the SLRB, the destination, the link, the RLC bearer or entity, and the terminal, providing an effective solution to the PDCP duplication function in scenarios such as NR sidelink, and facilitating the improvement of reliability of data packet transmission through the PDCP duplication function and the reduction of delay in data packet duplication transmission.

[0081] Optionally, as one embodiment, the terminal 1100 further includes a transmitting module for transmitting a second message, the second message being used to request the configuration, activation or deactivation of PDCP overlap for the SLRB of the terminal.

[0082] Optionally, in one embodiment, the second message includes terminal auxiliary information or sidelink terminal information.

[0083] Optionally, in one embodiment, the first message includes a MAC CE, and the MAC CE is used to activate or deactivate PDCP duplication for an SLRB of the terminal based on the granularity of the SLRB.

[0084] Optionally, in one embodiment, the MAC CE satisfies at least one of the following 1) to 8).

[0085] 1) The MAC CE includes an SLRB identifier ID, an index value, or a sort value, and the MAC CE is used to activate or deactivate PDCP duplication for the SLRB corresponding to the SLRB ID, index value, or sort value.

[0086] 2) The MAC CE includes a transmission range or a transmission range threshold, and the MAC CE is used to activate or deactivate PDCP overlap for SLRBs that satisfy the transmission range or the transmission range threshold.

[0087] 3) The MAC CE is used to activate or deactivate PDCP duplication for the default SLRB.

[0088] 4) The MAC CE includes a sidelink interface quality of service flow identifier PFI, and the MAC CE is used to activate or deactivate PDCP duplication for the SLRB corresponding to the PFI.

[0089] 5) The MAC CE includes a communication type, and the MAC CE is used to activate or deactivate PDCP overlap for an SLRB that satisfies the communication type.

[0090] 6) The MAC CE includes a discard timer or a discard timer threshold, and the MAC CE is used to activate or deactivate PDCP duplication for SLRBs that satisfy the discard timer or the discard timer threshold.

[0091] 7) The MAC CE includes a PDCP sequence number size, and the MAC CE is used to activate or deactivate PDCP duplication for an SLRB that satisfies the PDCP sequence number size.

[0092] 8) The MAC CE is used to activate or deactivate PDCP duplication for SLRBs that support out-of-order delivery.

[0093] Alternatively, as one embodiment, the MAC CE includes the sort value, and the MAC CE activates or deactivates PDCP duplication for an SLRB corresponding to the sort value in a manner indicated by a bitmap, where a plurality of SLRBs arranged in the terminal are sorted according to a target order, or the MAC CE includes the SLRB ID or index value, and the MAC CE activates or deactivates PDCP duplication for an SLRB corresponding to the SLRB ID or index value in a manner directly indicating the SLRB ID or index value.

[0094] Optionally, as one embodiment, the MAC CE includes a destination or a link identifier, where the MAC CE is used to activate or deactivate PDCP duplication for an SLRB corresponding to the destination, or the MAC CE is used to activate or deactivate PDCP duplication for an SLRB corresponding to the link identifier.

[0095] Optionally, in one embodiment, the first message is used to activate or deactivate at least one secondary RLC entity of an SLRB of the terminal.

[0096] Optionally, as one embodiment, the first message includes a radio resource control (RRC) message, which is used to configure PDCP overlap for an SLRB of the terminal, and / or the first message includes a MAC CE or downlink control information (DCI), which is used to activate or deactivate PDCP overlap for an SLRB of the terminal.

[0097] The terminal 1100 according to an embodiment of the present application may refer to the flow of the method 200 corresponding to the embodiment of the present application, and each unit / module and other operations and / or functions in the terminal 1100 mentioned above can be respectively used to realize the corresponding flow in the method 200 and achieve the same or equivalent technical effects, and will not be further described here for the sake of brevity.

[0098] The terminal in the 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. Exemplarily, the mobile terminal may include, but is not limited to, the types of terminal 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (PC), a television (TV), a deposit payment machine or a self-service machine, etc., and the embodiment of the present application is not specifically limited.

[0099] The terminal in the embodiment of the present application may be a device having an operating system, which may be the Android operating system, the ios operating system, or other possible operating systems, and the embodiment of the present application is not specifically limited.

[0100] The terminal according to the embodiments of the present application can realize each process realized by the method embodiments of Figures 2 to 10 and achieve the same technical effects, and will not be further described here to avoid repetition of description.

[0101] Optionally, as shown in Fig. 12, an embodiment of the present application further provides a communication device 1200, including a processor 1201, a memory 1202, and a program or instruction stored in the memory 1202 and operable on the processor 1201, for example, when the communication device 1200 is a terminal, when the program or instruction is executed by the processor 1201, each process of the embodiment of the PDCP overlap configuration, activation or deactivation method can be realized and the same technical effect can be achieved. In order to avoid repetition, no further description will be given here.

[0102] FIG. 13 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0103] The terminal 1300 includes components such as, but 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, and a processor 1310.

[0104] As can be understood by those skilled in the art, the terminal 1300 may further include a power source (e.g., a battery) for powering each component, and the power source may be logically connected to the processor 1310 by a power management system, so that the power management system can realize functions such as charge / discharge management and power consumption management. 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 the number of components shown, or a combination of some components, or a different arrangement of components, and will not be further described here.

[0105] It should be understood that in the embodiment of the present application, the input unit 1304 may include a graphics processor (Graphics Processing Unit, GPU) 13041 and a microphone 13042, and the graphics processor 13041 processes image data of still or video images obtained by an image capture device (e.g., a camera) in a video capture mode or an image capture mode. The display unit 1306 may include a display panel 13061, and the display panel 13061 may be arranged 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. The other input devices 13072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control buttons, switch buttons, etc.), a trackball, a mouse, and an operation lever, which will not be described further herein.

[0106] In the embodiment of the present application, the radio frequency unit 1301 receives downlink data from the network side device, and then causes the processor 1310 to process the data, and transmits uplink data to the network side device. In general, 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, etc.

[0107] The memory 1309 may be used to store software programs or instructions and various data. The memory 1309 may mainly include a program or instruction storage area and a data storage area, where the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (e.g., a sound playback function, an image playback function, etc.), etc. The memory 1309 may include a high-speed random access memory or a non-volatile memory, where the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. For example, the memory 1309 may be at least one magnetic disk memory device, a flash memory device, or other non-volatile solid-state memory device.

[0108] The processor 1310 may include one or more processing units. Optionally, the processor 1310 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, and application programs or instructions, and the modem processor mainly processes wireless communication, such as a baseband processor. As can be understood, the modem processor does not have to be integrated into the processor 1310.

[0109] Here, the radio frequency unit 1301 is used to receive a first message, and the first message is used to configure, activate or deactivate PDCP overlap for a sidelink radio bearer SLRB of the terminal based on at least one granularity of the SLRB, the destination, the link, the radio link control RLC bearer or entity, and the terminal.

[0110] In an embodiment of the present application, PDCP duplication can be configured, activated or deactivated for an SLRB of a terminal based on the granularity of at least one of the SLRB, the destination, the link, the RLC bearer or entity, and the terminal, providing an effective solution to the PDCP duplication function in scenarios such as NR sidelink, and facilitating the improvement of reliability of data packet transmission through the PDCP duplication function and the reduction of delay in data packet duplication transmission.

[0111] The terminal 1300 according to the embodiment of the present application can further realize each process of the embodiment of the PDCP overlap configuration, activation or deactivation method described above, and can achieve the same technical effect. In order to avoid repetition, it will not be described further here.

[0112] The embodiments of the present application further provide a readable storage medium, which may be volatile or non-volatile, and a program or instruction is stored on the readable storage medium, which, when executed by a processor, can realize each process of the above-mentioned PDCP redundancy configuration, activation or deactivation method embodiment and achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0113] Here, the processor may be the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

[0114] The embodiments of the present application further provide a chip, the chip including a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction to realize each process of the embodiments of the PDCP redundancy configuration, activation or deactivation method, and can achieve the same technical effect. In order to avoid repetition, no further description will be given here.

[0115] It should be understood that the chips referred to in the embodiments of the present application may be referred to as system level chips, system chips, chip systems, or systems on chips.

[0116] An embodiment of the present application further provides a computer program product, which is stored in a non-transitory memory, and which can be executed by at least one processor to realize each process of the embodiment of the PDCP redundancy configuration, activation or deactivation method and achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0117] The embodiments of the present application further provide a communication device, which is configured to perform each process of the above-mentioned PDCP overlap configuration, activation or deactivation method embodiments, and can achieve the same technical effects. In order to avoid repetition, no further description will be given here.

[0118] It should be explained that in this specification, the terms "comprise", "include", or any other variants thereof are intended to cover the non-exclusive "comprise", whereby a process, method, article, or apparatus that includes a set of elements includes not only those elements, but also other elements not expressly listed or inherent to such process, method, article, or apparatus. In the absence of further limitations, an element limited by the phrase "comprises a" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes this element. It should be pointed out that the scope of the method and apparatus in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may include performing functions in an essentially simultaneous manner or in reverse order based on the functions involved, for example, the described method can be performed in a different order than described, and various steps can be added, omitted, or combined. Also, features described with reference to some examples can be combined in other examples.

[0119] From the above description of the embodiments, it is clear to those skilled in the art that the methods of the above embodiments can be realized in the form of software and a necessary general-purpose hardware platform. Of course, they can also be realized in hardware, but in many cases the former is a more preferred embodiment. Based on this understanding, the technical solution of the present application may be substantially or in part embodied in the form of a software product. The computer software product is stored in a storage medium (e.g., ROM / RAM, magnetic disk, optical disk) and includes some instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0120] The above describes the embodiments of the present application in conjunction with the drawings, but the present application is not limited to the above specific embodiments. The above specific embodiments are merely illustrative and not limiting. Those skilled in the art can take many forms suggested by the present application without departing from the spirit and scope of the claims of the present application, and all of them belong to the protection scope of the present application.

Claims

1. A method for configuring, activating or deactivating a Packet Data Convergence Protocol (PDCP) overlap, comprising: receiving a first message by a terminal, the first message being used to configure, activate or deactivate PDCP duplication for a sidelink radio bearer (SLRB) of the terminal based on a granularity of at least one of a SLRB, a destination, a link, a radio link control (RLC) bearer or entity, and a terminal; The first message includes a media access control unit (MAC CE), and the MAC CE is used to activate or deactivate PDCP duplication for an SLRB of the terminal based on a granularity of the SLRB.

2. Before the terminal receives a first message, the method further comprises: The method further includes the terminal sending a second message, the second message being used to request configuration, activation, or deactivation of PDCP duplication for an SLRB of the terminal; The method of claim 1 , wherein the second message includes terminal auxiliary information or sidelink terminal information.

3. The MAC CE is The MAC CE includes a SLRB identifier ID, an index value, or a sort value, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB corresponding to the SLRB ID, the index value, or the sort value; The MAC CE includes a transmission range or a transmission range threshold, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the transmission range or the transmission range threshold; The MAC CE is used to activate or deactivate PDCP duplication for a default SLRB; The MAC CE includes a sidelink interface quality of service flow identifier (PFI), and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB corresponding to the PFI; The MAC CE includes a communication type, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the communication type; The MAC CE includes a discard timer or a discard timer threshold, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the discard timer or the discard timer threshold; The MAC CE includes a PDCP sequence number size, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the PDCP sequence number size; and wherein the MAC CE is used to activate or deactivate PDCP duplication for a SLRB supporting out-of-order delivery.

4. The MAC CE includes the sorting value, and the MAC CE activates or deactivates PDCP duplication for a SLRB corresponding to the sorting value in a manner indicated by a bitmap, where a plurality of SLRBs arranged in the terminal are sorted according to a target order, or The method of claim 3, wherein the MAC CE includes the SLRB ID or index value, and the MAC CE activates or deactivates PDCP duplication for the SLRB corresponding to the SLRB ID or index value in a manner of directly indicating the SLRB ID or index value.

5. The first message includes a MAC CE, the MAC CE including a destination or link identifier, where: The MAC CE is used to activate or deactivate PDCP duplication for the SLRB corresponding to the destination; or The method according to claim 1 or 3, wherein the MAC CE is used to activate or deactivate PDCP duplication for a SLRB corresponding to the link identifier.

6. The method of claim 1 , wherein the first message is used to activate or deactivate at least one secondary RLC entity of a SLRB of the terminal.

7. The first message includes a radio resource control (RRC) message, and the RRC message is used to configure PDCP duplication for a SLRB of the terminal; and / or The method of claim 1 , wherein the first message includes a MAC CE or a downlink control information (DCI), and the MAC CE or DCI is used to activate or deactivate PDCP duplication for a SLRB of the terminal.

8. A terminal, A receiving module for receiving a first message, the first message being used to configure, activate or deactivate PDCP duplication for a SLRB of the terminal based on at least one granularity of a SLRB, a destination, a link, an RLC bearer or entity, and a terminal; The terminal, wherein the first message includes a media access control unit (MAC CE), the MAC CE being used to activate or deactivate PDCP duplication for a SLRB of the terminal based on a granularity of the SLRB.

9. The terminal further includes a transmitting module for transmitting a second message, the second message being used to request configuration, activation, or deactivation of PDCP duplication for an SLRB of the terminal; The terminal of claim 8 , wherein the second message includes terminal auxiliary information or sidelink terminal information.

10. The MAC CE is The MAC CE includes a SLRB identifier ID, an index value, or a sort value, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB corresponding to the SLRB ID, the index value, or the sort value; The MAC CE includes a transmission range or a transmission range threshold, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the transmission range or the transmission range threshold; The MAC CE is used to activate or deactivate PDCP duplication for a default SLRB; The MAC CE includes a sidelink interface quality of service flow identifier (PFI), and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB corresponding to the PFI; The MAC CE includes a communication type, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the communication type; The MAC CE includes a discard timer or a discard timer threshold, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the discard timer or the discard timer threshold; The MAC CE includes a PDCP sequence number size, and the MAC CE is used to activate or deactivate PDCP duplication for a SLRB that satisfies the PDCP sequence number size; and wherein the MAC CE is used to activate or deactivate PDCP duplication for a SLRB supporting out-of-order delivery.

11. The MAC CE includes the sorting value, and the MAC CE activates or deactivates PDCP duplication for a SLRB corresponding to the sorting value in a manner indicated by a bitmap, where a plurality of SLRBs arranged in the terminal are sorted according to a target order, or The terminal of claim 10, wherein the MAC CE includes the SLRB ID or index value, and the MAC CE activates or deactivates PDCP duplication for a SLRB corresponding to the SLRB ID or index value in a manner of directly indicating the SLRB ID or index value.

12. The first message includes a MAC CE, the MAC CE including a destination or link identifier, where: The MAC CE is used to activate or deactivate PDCP duplication for the SLRB corresponding to the destination; or The terminal according to claim 8 or 10, wherein the MAC CE is used to activate or deactivate PDCP duplication for a SLRB corresponding to the link identifier.

13. The first message is used to activate or deactivate at least one secondary RLC entity of a SLRB of the terminal; Or, The first message includes a radio resource control (RRC) message, and the RRC message is used to configure PDCP duplication for a SLRB of the terminal; and / or The terminal of claim 8 , wherein the first message includes a MAC CE or a downlink control information (DCI), and the MAC CE or DCI is used to activate or deactivate PDCP duplication for a SLRB of the terminal.

14. A readable storage medium having a program or instructions stored thereon, the program or instructions implementing the method for PDCP redundancy configuration, activation or deactivation according to any one of claims 1 to 7, when the program or instructions are executed by a processor.

Images