Method and terminal for configuring, activating or deactivating pdcp duplication

Abstract

The embodiment of the application discloses a PDCP repetition configuration, activation or deactivation method and a terminal, and can solve the problem that the PDCP repetition function cannot be supported in the related art, and thus the reliability of data packet transmission cannot be improved and the time delay of data packet repeated transmission cannot be reduced. The method comprises the following steps: a terminal receives a first message, and the first message is used for performing PDCP repetition configuration, activation or deactivation on a sidelink 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, and terminal.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to a method and terminal for configuring, activating or deactivating Packet Data Convergence Protocol (PDCP) duplication. Background Technology

[0002] Starting with release 12, the Long Term Evolution (LTE) system supports sidelinks, enabling direct data transmission between terminals without relying on network-side equipment. Both the Uu and sidelink in LTE support PDCP redundancy, while in New Radio (NR) systems, currently only Uu supports PDCP redundancy; NR sidelink PDCP redundancy is not yet supported.

[0003] In LTE systems, enabling PDCP repetition is determined based on the ProSe Per-Packet Reliability (PPPR) threshold for each sidelink data packet. However, in NR systems, each sidelink data packet no longer has an independent PPPR attribute; instead, QoS management is achieved through Quality of Service (QoS) streams. Therefore, in NR sidelinks, how to configure, activate, or deactivate PDCP repetition to improve data packet transmission reliability and reduce repetition latency is a pressing technical problem that needs to be solved in the current technology. Summary of the Invention

[0004] This application provides a method and terminal for configuring, activating, or deactivating PDCP repeat, which can solve the problem in related technologies that cannot support PDCP repeat function, thereby failing to improve the reliability of data packet transmission and reduce the latency of repeated data packet transmission.

[0005] In a first aspect, a method for configuring, activating, or deactivating PDCP repetition is provided, the method comprising: a terminal receiving a first message, the first message being used to configure, activate, or deactivate PDCP repetition on a 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, and terminal.

[0006] In a second aspect, a terminal is provided, comprising: a receiving module for receiving a first message, the first message being configured, activated, or deactivated by repeating PDCP on a 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, and terminal.

[0007] Thirdly, a terminal is provided, the terminal including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the method as described in the first aspect.

[0008] Fourthly, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the method as described in the first aspect.

[0009] Fifthly, a computer program product is provided, comprising a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the method as described in the first aspect.

[0010] In a sixth aspect, a chip is provided, the chip including a processor and a communication interface coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0011] In the embodiments of this application, the PDCP repetition of the terminal's SLRB can be configured, activated, or deactivated based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, terminal. This provides an effective solution for the PDCP repetition function in scenarios such as NR sidelink, which facilitates improving the reliability of data packet transmission and reducing the latency of repeated data packet transmission through the PDCP repetition function. Attached Figure Description

[0012] Figure 1 This is a block diagram of a wireless communication system according to an embodiment of this application;

[0013] Figure 2 This is a schematic flowchart of a method for repeatedly configuring, activating, or deactivating PDCP according to an embodiment of this application;

[0014] Figure 3 This is a schematic diagram of the repeated activation or deactivation of the PDCP of the SLRB by the MAC CE through bitmap indication in one embodiment of this application;

[0015] Figure 4This is a schematic diagram of the repeated activation or deactivation of the PDCP of the SLRB by the MAC CE through bitmap indication according to another embodiment of this application;

[0016] Figure 5 This is a schematic diagram illustrating the repeated activation or deactivation of the SLRB's PDCP by the MAC CE carrying the SLRB ID / index according to one embodiment of this application;

[0017] Figure 6 This is a schematic diagram illustrating the repeated activation or deactivation of the PDCP of the SLRB by the MAC CE carrying the destination address in one embodiment of this application.

[0018] Figure 7 This is a schematic diagram of the repeated activation or deactivation of the PDCP of the SLRB by the MAC CE carrying the link identifier in one embodiment of this application, indicated by a bitmap.

[0019] Figure 8 This is a schematic diagram illustrating the repeated activation or deactivation of the PDCP of the SLRB by the MAC CE carrying the link identifier according to another embodiment of this application;

[0020] Figure 9 This is a schematic diagram of the MAC CE carrying the destination address and indicating the repeated activation or deactivation of the PDCP of the SLRB by means of a bitmap indication, according to one embodiment of this application.

[0021] Figure 10 This is a schematic diagram illustrating the activation or deactivation of a secondary RLC entity using a bitmap method according to one embodiment of this application;

[0022] Figure 11 This is a schematic diagram of the structure of a terminal according to an embodiment of this application;

[0023] Figure 12 This is a schematic diagram of the structure of a communication device according to an embodiment of this application;

[0024] Figure 13 This is a schematic diagram of the structure of a terminal according to an embodiment of this application. Detailed Implementation

[0025] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0026] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0027] It is worth noting that the technologies described in this application are not limited to Long Term Evolution (LTE) / LTE-Advanced (LTE-A) systems, but can also be used in 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 this application are often used interchangeably, and the described technologies can be used with the systems and radio technologies mentioned above, as well as with other systems and radio technologies. The following description describes New Radio (NR) systems for illustrative purposes, and the term NR is used in most of the following description; however, these technologies can also be applied to applications other than NR systems, such as 6th generation (6G) radio systems. th Generation 6G communication system.

[0028] Figure 1This diagram illustrates a block diagram of a wireless communication system applicable to embodiments of this application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can also be referred to as a terminal device or user equipment (UE). The terminal 11 can be a mobile phone, tablet computer, laptop computer, personal digital assistant (PDA), handheld computer, netbook, ultra-mobile personal computer (UMPC), mobile internet device (MID), wearable device, vehicle-mounted device (VUE), pedestrian terminal (PUE), etc. Wearable devices include wristbands, headphones, glasses, etc. It should be noted that this application does not limit the specific type of terminal 11. Network-side device 12 can be a base station or a core network. The base station can be referred to as a node B, evolved node B, access point, base transceiver station (BTS), radio base station, radio transceiver, basic service set (BSS), extended service set (ESS), B node, evolved B node (eNB), next-generation node B (gNB), home B node, home evolved B node, WLAN access point, WiFi node, transmitting and receiving point (TRP), or any other suitable term in the field, as long as the same technical effect is achieved. The base station is not limited to specific technical terms. It should be noted that in this application embodiment, only the base station in the NR system is used as an example, but the specific type of base station is not limited.

[0029] The following, in conjunction with the accompanying drawings, provides a detailed description of the configuration, activation, or deactivation methods and terminals for the Packet Data Convergence Protocol (PDCP) duplication provided in this application, through specific embodiments and application scenarios.

[0030] like Figure 2 As shown, one embodiment of this application provides a method 200 for repeatedly configuring, activating, or deactivating PDCP. This method can be executed by a terminal; in other words, it can be executed by software or hardware installed on the terminal. The method includes the following steps.

[0031] S202: The terminal receives a first message, which is used to configure, activate or deactivate the terminal's SideLink Radio Bearer (SLRB) repeatedly based on at least one of the following granularities: SLRB, destination address, link, Radio Link Control (RLC) bearer or entity, and terminal.

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

[0033] The first message in this embodiment may also be a Media Access Control-Control Element (MAC CE) or Downlink Control Information (DCI), and the MAC CE or DCI message may perform PDCP repeated activation or deactivation of the terminal's SLRB based on at least one of the above granularities.

[0034] In this embodiment, the first message may come from the network-side device, so that the network-side device can repeatedly configure, activate, or deactivate the SLRB of the terminal using PDCP.

[0035] In this embodiment, the first message can also come from the peer terminal. In this case, the peer terminal can repeatedly configure, activate, or deactivate the SLRB of the local terminal (i.e., the terminal mentioned in S202) using PDCP. In this example, the peer terminal can be a sending terminal (TX UE), and the local terminal can be a receiving terminal (RX UE); or, the peer terminal can be a receiving terminal (RX UE), and the local terminal can be a sending terminal (TX UE).

[0036] The PDCP repetition configuration, activation, or deactivation method provided in this application embodiment can configure, activate, or deactivate PDCP repetition for the terminal's SLRB based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, and terminal. This provides an effective solution for PDCP repetition functionality in scenarios such as NR sidelink, facilitating the improvement of data packet transmission reliability and reduction of data packet repetition latency through PDCP repetition functionality.

[0037] To explain in detail the PDCP repetitive configuration, activation, or deactivation methods provided in the above embodiments of this application, the following will describe them in conjunction with several specific embodiments.

[0038] Example 1

[0039] The first message in this embodiment includes a MAC CE, which is used to perform PDCP repeated activation or deactivation of the terminal's SLRB based on the granularity of the SLRB. That is, this embodiment can perform PDCP repeated activation or deactivation (per-SLRB activation / deactivation) of the SLRB configured on the terminal based on the granularity of the SLRB through the MAC CE (i.e., the first message).

[0040] The MAC CE in this embodiment satisfies at least one of the following:

[0041] 1) The MAC CE includes an SLRB identifier (ID), an index value, or a sort value. The MAC CE is used to activate or deactivate the SLRB corresponding to the SLRBID, index value, or sort value by repeating PDCP.

[0042] This example allows you to carry the ID, index value (such as slrb-Uu-ConfigIndex), or sort value corresponding to the SLRB in the MAC CE, thereby activating or deactivating the corresponding SLRB.

[0043] In one specific implementation (hereinafter referred to as Method 1), the MAC CE includes the sorting value. The MAC CE activates or deactivates the SLRB corresponding to the sorting value by repeating PDCP through bitmap indication. The multiple SLRBs configured in the terminal are sorted according to the target order.

[0044] In another specific implementation (hereinafter referred to as Method 2), the MAC CE includes the SLRB ID or index value, and the MAC CE activates or deactivates the SLRB corresponding to the SLRB ID or index value by directly instructing the SLRB ID or index value.

[0045] Method 1 can sort all SLRBs configured with duplication according to their ID or index value, and then use a bitmap to indicate whether the i-th SLRB is activated or deactivated (PDCP duplicate).

[0046] The example shown in Method 1 is as follows: Figure 3 and Figure 4 As shown, Figure 3 The diagram shown is a schematic of a single byte in a MAC CE. Figure 4The diagram shown is a representation of two bytes in a MAC CE.

[0047] Figure 3 The example shown sorts the 8 SLRBs configured with PDCP in descending order based on their ID or index value. Figure 3 S i This means that i can be 0-7.

[0048] Figure 4 The example shown configures the terminal with 16 repeating SLRBs (Search Server Repositories) sorted in descending order based on the SLRB's ID or index value. Figure 4 S i This means that i can be 0-15.

[0049] Figure 3 and Figure 4 In the example shown, S i =1 indicates activation, S i =0 indicates deactivation; or S i =0 indicates activation, S i =1 indicates deactivation.

[0050] Method 2 allows you to directly specify the ID or index value corresponding to the SLRB to activate or deactivate it. An example of Method 2 is shown below. Figure 5 As shown, Figure 5 The diagram shows a single byte in a MAC CE. The MAC CE directly carries the SLRB's ID or index, and uses a leading bit to indicate whether it's active or deactivated. For example, Figure 5 As shown, A=1 indicates activation, and A=0 indicates deactivation; or A=0 indicates activation, and A=1 indicates deactivation.

[0051] 2) The MAC CE includes a transmission range or a transmission range threshold. The MAC CE is used to activate or deactivate SLRBs that satisfy the transmission range or transmission range threshold by repeating PDCP.

[0052] This example carries the transmission range or transmission range threshold corresponding to the SLRB in the MAC CE, and performs PDCP repeated activation or deactivation on the SLRB whose transmission range is equal to the transmission range indicated in the MAC CE or whose transmission range satisfies the transmission range threshold indicated in the MAC CE.

[0053] 3) The MAC CE is used to reactivate or deactivate the default SLRB by repeating PDCP.

[0054] This example in MAC CE instructs the default SLRB to be activated or deactivated by PDCP repetition; of course, in other examples, it is also possible to instruct non-default SLRBs to be activated or deactivated by PDCP repetition in MAC CE.

[0055] 4) The MAC CE includes a secondary link interface service quality flow identifier (PC5 Qos Flow ID, abbreviated as PFI or PQFI), and the MAC CE is used to activate or deactivate the SLRB corresponding to the PFI by repeating PDCP.

[0056] This example carries a PFI in MAC CE and performs PDCP repeated activation or deactivation on the SLRB mapped to (or corresponding to) the PFI.

[0057] 5) The MAC CE includes a communication type (cast type), and the MAC CE is used to activate or deactivate the SLRB that satisfies the communication type by repeating the PDCP.

[0058] This example carries a communication type in the MAC CE, and activates or deactivates the SLRB with the communication type configured equal to the communication type indicated in the MAC CE for repeated PDCP. The communication type includes unicast, multicast, or broadcast.

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

[0060] This example activates or deactivates the PDCP repeat for the SLRB configured to be equal to the discard timer indicated in the MAC CE; or, activates or deactivates the PDCP repeat for the SLRB configured to satisfy the discard timer threshold indicated in the MAC CE.

[0061] The threshold mentioned above for satisfying the discard timer can be greater than or equal to the threshold; or less than or equal to the threshold.

[0062] 7) The MAC CE includes a PDCP serial number size (PDCP SN size), and the MAC CE is used to activate or deactivate PDCP repeating for SLRBs that meet the PDCP serial number size.

[0063] This example carries the PDCP serial number size in the MAC CE and configures the SLRB with the PDCP serial number size equal to the PDCP serial number size indicated in the MAC CE for PDCP repetition activation or deactivation.

[0064] The PDCP serial number size mentioned in this example includes 12-bit, 18-bit, or other newly defined serial number sizes.

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

[0066] This example in MAC CE indicates that PDCP re-activation or deactivation will be performed on SLRBs that are not submitted out of order. Of course, in other examples, MAC CE can also indicate that PDCP re-activation or deactivation will be performed on SLRBs that are not submitted out of order.

[0067] It should be noted that any two or more factors in 1)-8) above can be combined with the indication to activate or deactivate PDCP repetition for SLRBs that meet the configuration requirements. For example, SLRBs with SLRB ID = x and which are the default can be activated or deactivated for PDCP repetition, i.e., a combination of 1) and 3). Another example is SLRBs with SLRB sorting value i = x and transmission range less than the threshold y, which can be activated or deactivated for PDCP repetition, i.e., a combination of 1) and 2).

[0068] Example 2

[0069] This embodiment performs PDCP repeated activation or deactivation of the terminal's SLRB based on the granularity of the destination address or link (per-destination or per-link activation / deactivation).

[0070] The first message in this embodiment includes a MAC CE, which includes a destination address or a link ID; wherein,

[0071] When the MAC CE includes a destination address, the MAC CE is used to activate or deactivate the PDCP repeating function of the SLRB corresponding to the destination address; or

[0072] When the MAC CE includes a link identifier, the MAC CE is used to activate or deactivate the SLRB corresponding to the link identifier through PDCP repetition.

[0073] In one implementation, the destination address is indicated in the MAC CE, and all SLRBs connected to that destination address are repeatedly activated or deactivated using PDCP. An example of this implementation is shown below. Figure 6 As shown, Figure 6The diagram shown is a schematic of a single byte in MACCE. Figure 6 In this context, the R field represents the reserved field, A=1 indicates activation, A=0 indicates deactivation; or A=0 indicates activation, A=1 indicates deactivation.

[0074] In another implementation, the MAC CE indicates the link identifier, and all SLRBs belonging to that link identifier are repeatedly activated or deactivated using PDCP. An example of this implementation is shown below. Figure 7 or Figure 8 As shown, Figure 7 and 8 The diagram shown is a schematic of a single byte in a MAC CE.

[0075] Figure 7 In this context, Li represents Link ID = i, where i = 0-7. Li = 1 indicates activation and Li = 0 indicates deactivation; or Li = 0 indicates activation and Li = 1 indicates deactivation.

[0076] Figure 8 In this context, the R field represents the reserved field, A=1 indicates activation, A=0 indicates deactivation; or A=0 indicates activation, A=1 indicates deactivation.

[0077] Example 3

[0078] This third embodiment is a combination of the second and first embodiments.

[0079] This embodiment first determines the destination address / link identifier, and then, for all SLRBs belonging to that destination address / link identifier, performs per-SLRB PDCP repetition activation or deactivation based on one or more of the methods in 1)-8) of Embodiment 1. For example, the destination address is determined first, and then the PDCP repetition activation or deactivation is indicated based on the SLRB's sort value.

[0080] The example shown in this implementation is as follows: Figure 9 As shown, Figure 9 The diagram shown is a representation of two bytes in a MAC CE. Figure 9 In this context, the R field represents a reserved field. Figure 9 The example shown sorts the 8 SLRBs configured with PDCP in descending order based on their ID or index value. Figure 9 S i This means that i can be 0-7. Figure 9 In the example shown, S i =1 indicates activation, S i =0 indicates deactivation; or S i =0 indicates activation, S i =1 indicates deactivation.

[0081] Example 4

[0082] This embodiment performs PDCP repeated activation or deactivation of the terminal's SLRB at the RLC bearer or entity granularity (per RLC bearer / entity activation / deactivation).

[0083] In this embodiment, the first message is used to activate or deactivate at least one secondary RLC entity of the terminal's SLRB.

[0084] Specifically, for each SLRB, the activation or deactivation of the secondary RLC entity can be directly indicated via the first message. This embodiment can sort the secondary RLC entities based on logical channel IDs (ascending or descending order), where RLC... i This represents the i-th (ascending or descending) secondary RLC entity. RLC i =1 indicates activation, RLC i =0 indicates deactivation; or RLCi=0 indicates activation, and RLCi=1 indicates deactivation.

[0085] like Figure 10 As shown, Figure 10 The diagram shown is a schematic of a single byte in a MAC CE. Figure 10 The example shown sorts the secondary RLC entities in descending order. See Figure 10 RLC2, RLC1, RLC0, RLC i =1 indicates activation, RLC i =0 indicates deactivation; or RLCi=0 indicates activation, and RLCi=1 indicates deactivation.

[0086] Example 5

[0087] In this embodiment, the first message is used to perform PDCP repeated activation or deactivation on the SLRB of the terminal based on the granularity of the terminal (per UE activation / deactivation).

[0088] In this embodiment, the network vehicle device can send 1 bit to the terminal via DCI or MAC CE to instruct the terminal to activate or deactivate all SLRBs configured with PDCP repetition.

[0089] Optionally, in Embodiments 1 to 5 above, the network-side device may configure PDCP repetition or activate / deactivate PDCP repetition of SLRB based on the terminal's report.

[0090] Thus, before the terminal receives the first message as described in the preceding embodiments, the method further includes: the terminal sending a second message, the second message being used to request the SLRB of the terminal to be configured for PDCP repetition, activated or deactivated.

[0091] Optionally, the second message includes UE Assistance Information or Sidelink UE Information.

[0092] Optionally, the second message may include corresponding information at various granularities, such as the SLRB ID, index value, or sorting value at the per-SLRB granularity. Thus, the second message can be used to request the network-side device to configure, activate, or deactivate a specific SLRB for PDCP repetition. Specifically, the format of the second message can refer to the methods described in Embodiments 1 to 5 above, thereby requesting the network-side device to configure, activate, or deactivate a specific SLRB for PDCP repetition.

[0093] In this embodiment, for example, the terminal carries the information from Embodiments 1 to 5 above in its SidelinkUEInformation or UEAssistanceInformation to indicate to the network-side device that the terminal wishes to be configured for PDCP repetition, or wishes to activate or deactivate the attribute corresponding to the SLRB for PDCP repetition. After receiving the reported information from the terminal, the network-side device configures, activates, or deactivates the PDCP repetition of the SLRB corresponding to the terminal using the methods described in Embodiments 1 to 5.

[0094] In the preceding embodiments, the network-side device can configure the SLRB to repeat PDCP via RRC, which can be configured to activate or deactivate (initial state), etc., and the granularity of the configuration can also be the granularity of embodiments one to five. Subsequently, the SLRB can also be deactivated or activated via MAC CE or DCI.

[0095] It should be noted that the PDCP repetition configuration, activation, or deactivation method provided in this application embodiment can be executed by a terminal, or by a control module in the terminal for executing the PDCP repetition configuration, activation, or deactivation method. This application embodiment uses the terminal executing the PDCP repetition configuration, activation, or deactivation method as an example to illustrate the terminal provided in this application embodiment.

[0096] Figure 11 This is a schematic diagram of the terminal structure according to an embodiment of this application, such as... Figure 11 As shown, terminal 1100 includes:

[0097] The receiving module 1102 can be used to receive a first message, which is used to configure, activate or deactivate the SLRB of the terminal based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, and terminal.

[0098] In the embodiments of this application, the PDCP repetition of the terminal's SLRB can be configured, activated, or deactivated based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, terminal. This provides an effective solution for the PDCP repetition function in scenarios such as NR sidelink, which facilitates improving the reliability of data packet transmission and reducing the latency of repeated data packet transmission through the PDCP repetition function.

[0099] Optionally, as an embodiment, the terminal 1100 further includes a sending module for sending a second message, the second message being used to request the PDCP repetition configuration, activation or deactivation of the SLRB of the terminal.

[0100] Optionally, as an embodiment, the second message includes terminal assistance information or secondary link terminal information.

[0101] Optionally, as an embodiment, the first message includes a MAC CE, which is used to perform PDCP re-activation or deactivation of the SLRB of the terminal based on the granularity of the SLRB.

[0102] Optionally, as an embodiment, the MAC CE satisfies at least one of the following:

[0103] The MAC CE includes an SLRB identifier ID, an index value, or a sorting value. The MAC CE is used to activate or deactivate the SLRB corresponding to the SLRB ID, index value, or sorting value by repeating the PDCP.

[0104] The MAC CE includes a transmission range or a transmission range threshold, and the MAC CE is used to activate or deactivate PDCP repeats for SLRBs that meet the transmission range or transmission range threshold.

[0105] The MAC CE is used to reactivate or deactivate the default SLRB using PDCP repetition.

[0106] The MAC CE includes a secondary link interface service quality flow identifier (PFI), and the MAC CE is used to activate or deactivate the PDCP of the SLRB corresponding to the PFI.

[0107] The MAC CE includes a communication type, and the MAC CE is used to activate or deactivate the SLRB that satisfies the communication type by repeating the PDCP.

[0108] The MAC CE includes a drop timer or a drop timer threshold, and the MAC CE is used to activate or deactivate SLRBs that satisfy the drop timer or drop timer threshold by repeating PDCP.

[0109] The MAC CE includes a PDCP sequence number size, and the MAC CE is used to activate or deactivate PDCP repeats for SLRBs that meet the PDCP sequence number size.

[0110] The MAC CE is used to activate or deactivate SLRBs that support out-of-order submissions by repeating PDCP.

[0111] Alternatively, as an example,

[0112] The MAC CE includes the sorting value. The MAC CE activates or deactivates the SLRB corresponding to the sorting value using a bitmap-based method, wherein the multiple SLRBs configured in the terminal are sorted according to a target order; or

[0113] The MAC CE includes the SLRB ID or index value. The MAC CE activates or deactivates the SLRB corresponding to the SLRB ID or index value by directly instructing the SLRB ID or index value.

[0114] Optionally, as an embodiment, the MAC CE includes a destination address or link identifier; wherein,

[0115] The MAC CE is used to activate or deactivate the PDCP repeat of the SLRB corresponding to the destination address; or

[0116] The MAC CE is used to activate or deactivate the SLRB corresponding to the link identifier by repeating PDCP.

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

[0118] Alternatively, as an example,

[0119] The first message includes a Radio Resource Control (RRC) message, which is used to configure PDCP repetition for the SLRB of the terminal; and / or

[0120] The first message includes a MAC CE or downlink control information (DCI), which is used to reactivate or deactivate the SLRB of the terminal by repeating the PDCP.

[0121] The terminal 1100 according to the embodiments of this application can refer to the process of the method 200 corresponding to the embodiments of this application. Furthermore, each unit / module in the terminal 1100 and the other operations and / or functions mentioned above are respectively implemented to achieve the corresponding process in the method 200 and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be described in detail here.

[0122] The terminal in this application embodiment can be a device, or a component, integrated circuit, or chip within the terminal. The terminal can be a mobile terminal or a non-mobile terminal. For example, a mobile terminal can include, but is not limited to, the types of terminal 11 listed above, while a non-mobile terminal can be a server, network attached storage (NAS), personal computer (PC), television set (TV), ATM, or self-service machine, etc. This application embodiment does not impose specific limitations.

[0123] The terminal in this application embodiment can be a device with an operating system. The operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system.

[0124] The terminal provided in this application embodiment can achieve... Figures 2 to 10 The various processes implemented in the method embodiments achieve the same technical effect, and will not be described again here to avoid repetition.

[0125] Optional, such as Figure 12 As shown, this application embodiment also provides a communication device 1200, including a processor 1201, a memory 1202, and a program or instruction stored in the memory 1202 that can be executed 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, it implements the various processes of the above-mentioned PDCP repeated configuration, activation or deactivation method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0126] Figure 13 A schematic diagram of the hardware structure of a terminal to implement an embodiment of this application.

[0127] The terminal 1300 includes, but is not limited to, the following components: radio frequency unit 1301, network module 1302, audio output unit 1303, input unit 1304, sensor 1305, display unit 1306, user input unit 1307, interface unit 1308, memory 1309, and processor 1310.

[0128] Those skilled in the art will understand that the terminal 1300 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 1310 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 13 The terminal structure shown does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0129] It should be understood that, in this embodiment, the input unit 1304 may include a graphics processing unit (GPU) 13041 and a microphone 13042. The GPU 13041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. 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 a touch detection device and a touch controller. Other input devices 13072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, power buttons, etc.), a trackball, a mouse, and a joystick, which will not be described in detail here.

[0130] In this embodiment, the radio frequency unit 1301 receives downlink data from the network-side device and processes it for the processor 1310; additionally, it sends uplink data to the network-side device. Typically, 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.

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

[0132] Processor 1310 may include one or more processing units; optionally, processor 1310 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications or instructions, and the modem processor mainly handles wireless communication, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 1310.

[0133] The radio frequency unit 1301 is used to receive a first message, which is used to configure, activate or deactivate 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, and terminal.

[0134] In the embodiments of this application, the PDCP repetition of the terminal's SLRB can be configured, activated, or deactivated based on at least one of the following granularities: SLRB, destination address, link, RLC bearer or entity, terminal. This provides an effective solution for the PDCP repetition function in scenarios such as NR sidelink, which facilitates improving the reliability of data packet transmission and reducing the latency of repeated data packet transmission through the PDCP repetition function.

[0135] The terminal 1300 provided in this application embodiment can also implement the various processes of the above-described PDCP repeated configuration, activation or deactivation method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0136] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described PDCP repetitive configuration, activation, or deactivation method embodiments and achieve the same technical effect. To avoid repetition, they will not be described again here.

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

[0138] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described PDCP repeated configuration, activation or deactivation method embodiments, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0139] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0140] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0141] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0142] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for configuring, activating, or deactivating repeated Packet Data Convergence Protocol (PDCP) calls, characterized in that, The method applied to the NR sidelink, the method comprises: A terminal receives a first message, the first message is used for configuring, activating or deactivating PDCP repetition of a sidelink radio bearer (SLRB) of the terminal based on SLRB granularity; The first message comprises a medium access control control element (MAC CE); the MAC CE comprises a sidelink interface quality of service flow identifier (PFI), and the MAC CE is used for activating or deactivating PDCP repetition of an SLRB corresponding to the PFI; The MAC CE satisfies at least one of the following conditions: The MAC CE comprises a destination address or a link identifier, and the MAC CE is used for activating or deactivating PDCP repetition of an SLRB corresponding to the destination address or the link identifier; The MAC CE comprises an SLRB identifier (ID), an index value or an order value, and the MAC CE is used for activating or deactivating PDCP repetition of an SLRB corresponding to the SLRB ID, the index value or the order value; The MAC CE comprises a transmission range or a transmission range threshold, and the MAC CE is used for activating or deactivating PDCP repetition of an SLRB satisfying the transmission range or the transmission range threshold; The MAC CE is used for activating or deactivating PDCP repetition of a default SLRB; The MAC CE comprises a communication type, and the MAC CE is used for activating or deactivating PDCP repetition of an SLRB satisfying the communication type; The MAC CE comprises a discard timer or a discard timer threshold, and the MAC CE is used for activating or deactivating PDCP repetition of an SLRB satisfying the discard timer or the discard timer threshold; The MAC CE comprises a PDCP sequence number size, and the MAC CE is used for activating or deactivating PDCP repetition of an SLRB satisfying the PDCP sequence number size; The MAC CE is used for activating or deactivating PDCP repetition of an SLRB supporting out-of-sequence delivery.

2. The method of claim 1, wherein, Before the terminal receives the first message, the method further comprises: The terminal sends a second message, and the second message is used for requesting configuration, activation or deactivation of PDCP repetition of an SLRB of the terminal.

3. The method of claim 2, wherein, The second message comprises terminal assistance information or sidelink terminal information.

4. The method of claim 1, wherein: The MAC CE comprises the order value, and the MAC CE activates or deactivates PDCP repetition of an SLRB corresponding to the order value by means of bitmap indication, wherein a plurality of SLRBs configured by the terminal are sorted in a target order; or The MAC CE comprises the SLRB ID or the index value, and the MAC CE activates or deactivates PDCP repetition of an SLRB corresponding to the SLRB ID or the index value by directly indicating the SLRB ID or the index value.

5. The method of claim 1, wherein, The first message is used for activating or deactivating at least one secondary RLC entity of the SLRB of the terminal.

6. The method of claim 1, wherein, The first message comprises a radio resource control (RRC) message used for configuring PDCP duplication of the SLRB of the terminal; and / or The first message comprises a MAC CE or a downlink control information (DCI) used for activating or deactivating PDCP duplication of the SLRB of the terminal.

7. A terminal, characterized by comprising: Applicable to NR sidelink, comprising: A receiving module is configured to receive a first message used for configuring, activating, or deactivating PDCP duplication of a SLRB of the terminal based on a SLRB granularity. The first message comprises a media access control control element (MAC CE), and the MAC CE comprises a sidelink interface flow identity (PFI), and the MAC CE is used for activating or deactivating PDCP duplication of a SLRB corresponding to the PFI. The MAC CE satisfies at least one of the following conditions: The MAC CE comprises a destination address or a link identity, and the MAC CE is used for activating or deactivating PDCP duplication of a SLRB corresponding to the destination address or the link identity. The MAC CE comprises a SLRB identity (ID), an index value, or an order value, and the MAC CE is used for activating or deactivating PDCP duplication of a SLRB corresponding to the SLRB ID, the index value, or the order value. The MAC CE comprises a transmission range or a transmission range threshold, and the MAC CE is used for activating or deactivating PDCP duplication of a SLRB satisfying the transmission range or the transmission range threshold. The MAC CE is used for activating or deactivating PDCP duplication of a default SLRB. The MAC CE comprises a communication type, and the MAC CE is used for activating or deactivating PDCP duplication of a SLRB satisfying the communication type. The MAC CE comprises a discard timer or a discard timer threshold, and the MAC CE is used for activating or deactivating PDCP duplication of a SLRB satisfying the discard timer or the discard timer threshold. The MAC CE comprises a PDCP sequence number size, and the MAC CE is used for activating or deactivating PDCP duplication of a SLRB satisfying the PDCP sequence number size. The MAC CE is used for activating or deactivating PDCP duplication of a SLRB supporting out-of-sequence delivery.

8. The terminal according to claim 7, characterized by The terminal further comprises a sending module configured to send a second message used for requesting configuration, activation, or deactivation of PDCP duplication of a SLRB of the terminal.

9. The terminal according to claim 8, characterized by The second message comprises terminal assistance information or sidelink terminal information.

10. The terminal of claim 7, wherein, The MAC CE includes the sequence value, and the MAC CE activates or deactivates the SLRB corresponding to the sequence value in a bitmap indication manner, wherein the multiple SLRBs configured by the terminal are sequenced according to a target sequence; or The MAC CE includes the SLRB ID or index value, and the MAC CE activates or deactivates the SLRB corresponding to the SLRB ID or index value in a direct indication manner.

11. The terminal according to claim 7, characterized by The first message is used to activate or deactivate at least one secondary RLC entity of the SLRB of the terminal.

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

13. A terminal, characterized by The processor, the memory, and a program or instructions stored in the memory and executable on the processor are included, and the program or instructions are executed by the processor to implement the PDCP duplication configuration, activation, or deactivation method according to any one of claims 1 to 6.

14. A readable storage medium, characterized by, A program or instructions are stored in the readable storage medium, and the program or instructions are executed by the processor to implement the PDCP duplication configuration, activation, or deactivation method according to any one of claims 1 to 6.

Images