Method and apparatus used in communication node for wireless communication

Abstract

The present application discloses a method and apparatus used in a communication node for wireless communication. The method comprises: a communication node receiving a first message, wherein the first message is used for configuring a first PDCP entity and a plurality of RLC entities, and the first PDCP entity is associated with the plurality of RLC entities; and operating a first PDCP PDU, the behavior of operating the first PDCP PDU comprising copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset, wherein the target RLC entity subset is an RLC subset among a plurality of RLC entity subsets, each RLC entity subset among the plurality of RLC entity subsets comprises at least one RLC entity among the plurality of RLC entities, the plurality of RLC entity subsets depend on at least the first message, and the behavior of copying the first PDCP PDU depends on the target RLC entity subset comprising at least two RLC entities. The PDCP PDU operation method provided in the present application can reduce latency while improving the transmission reliability, thereby reducing the probability of a PDCP PDU being discarded.

Description

A method and apparatus for use in a communication node for wireless communication Technical Field

[0001] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to an operation method and apparatus for PDCP PDU. Background Art

[0002] The application scenarios of future wireless communication systems are becoming increasingly diverse, and each scenario places high-speed and low-latency performance requirements on the system. For example, to meet the diverse performance requirements of various application scenarios, the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #98 plenary meeting approved the "XR (Extended Reality) Enhancements for NR (New Radio)" WI (Work Item).

[0003] Summary of the Invention

[0004] In existing protocols, when delivering a PDCP (Packet Data Convergence Protocol) PDU (Protocol Data Unit) to an RLC (Radio Link Control) entity, the transmitting PDCP entity determines whether to perform PDCP duplication or PDCP splitting based on the current configuration, and does not support simultaneous PDCP duplication and PDCP splitting. For data-intensive, latency-sensitive services, especially but not limited to dependent PDCP PDUs, using the existing mechanism can easily trigger PDCP PDU discard.

[0005] In response to the above problems, the present application provides a solution. In the description of the above problems, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) systems, achieving technical effects similar to those of the NR system. Furthermore, although the present application provides a specific implementation method for the sending PDCP entity of the first node, the present application can also be used in scenarios such as the sending PDCP entity of the second node, achieving technical effects similar to those of the sending PDCP entity of the first node. Furthermore, adopting a unified design solution for different scenarios can also help reduce hardware complexity and cost. Furthermore, although the present application provides a specific implementation method for the XR scenario, the present application can also be used in other high-speed, low-latency scenarios, achieving technical effects similar to those of the XR system. Furthermore, although the original intention of the present application is for the Uu air interface, the present application can also be used for the PC5 port, achieving technical effects similar to those of the Uu air interface. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the V2X (Vehicle-to-Everything, Internet of Vehicles) scenario, the communication scenario between the terminal and the relay, and the relay and the base station, to achieve similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the IAB (Integrated Access and Backhaul, integrated access and backhaul) communication scenario, to achieve similar technical effects in the terminal and base station scenario. Furthermore, although the original intention of this application is for the terrestrial network (TN) scenario, this application is also applicable to the non-terrestrial network (NTN) communication scenario, to achieve similar technical effects in the TN scenario. In addition, the use of a unified solution for different scenarios can also help reduce hardware complexity and cost.

[0006] As an embodiment, the interpretation of the terms in this application refers to the definition of the 3GPP specification protocol TS38 series.

[0007] As an embodiment, the interpretation of the terms in this application refers to the definitions of the 3GPP specification protocol TS37 series.

[0008] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

[0009] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0010] receiving a first message, the first message configuring a first PDCP entity and a plurality of RLC entities, the first PDCP entity being associated with the plurality of RLC entities;

[0011] operating a first PDCP PDU;

[0012] Among them, the behavior operation of the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to the RLC entity in the target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

[0013] As an embodiment, the problem to be solved by the present application includes: how to avoid discarding PDCP PDU.

[0014] As an embodiment, the characteristics of the above method include: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets.

[0015] As an embodiment, the characteristics of the above method include: the first PDCP PDU and the copy of the first PDCP PDU are flexibly delivered to an RLC entity in a target RLC entity subset among multiple RLC entity subsets.

[0016] The above method improves the processing efficiency of PDCP PDU.

[0017] The above method reduces delay and improves reliability at the same time.

[0018] The above method reduces the probability of PDCP PDU being discarded.

[0019] The above method is particularly suitable for processing PDCP PDUs with dependency relationships.

[0020] According to one aspect of the present application, it is characterized in that the behavior operation of the first PDCP PDU includes: determining the target RLC entity subset among the multiple RLC entity subsets.

[0021] According to one aspect of the present application, it is characterized in that first signaling is received, where the first signaling is signaling of a protocol layer below the RRC sublayer;

[0022] The first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set; the first candidate RLC entity set includes the multiple RLC entities; the first message configures each RLC entity in the first candidate RLC entity set, and the first PDCP entity is associated with each RLC entity in the candidate RLC entity set.

[0023] The above method realizes flexible configuration of RLC entity subsets.

[0024] The above method realizes flexible configuration of the RLC entities in the RLC entity subset.

[0025] The above method realizes flexible configuration of the target RLC entity subset.

[0026] The above method realizes flexible configuration of the multiple RLC entity subsets.

[0027] According to one aspect of the present application, it is characterized in that the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0028] The above method is simple to implement.

[0029] The above method reduces the impact of the protocol.

[0030] The above method is more flexible.

[0031] According to one aspect of the present application, it is characterized in that determining the target RLC entity subset among the multiple RLC entity subsets depends on a first threshold; and the first message configures the first threshold.

[0032] The above method reduces unnecessary PDCP splitting through the first threshold.

[0033] The above method reduces unnecessary PDCP duplication through the first threshold.

[0034] The above method reduces the complexity of the protocol implementation through the first threshold.

[0035] According to one aspect of the present application, it is characterized in that, accompanied by the behavioral operation of the first PDCP PDU, the sum of the first PDCP data volume and the first RLC data volume is not less than the first threshold, and the first PDCP data volume and the first RLC data volume are associated with the first PDCP entity.

[0036] The above method avoids PDCP splitting when the amount of data is small.

[0037] The above method avoids PDCP duplication when the amount of data is small.

[0038] The above method reduces the complexity of protocol implementation when the amount of data is small.

[0039] According to one aspect of the present application, it is characterized in that the first message is configured with multiple thresholds, and the first threshold is one of the multiple thresholds.

[0040] The above method determines the target RLC entity subset from the multiple RLC entity subsets by using multiple thresholds.

[0041] The above method further reduces unnecessary PDCP splitting.

[0042] The above method further reduces unnecessary PDCP duplication.

[0043] The above method makes the protocol architecture more flexible.

[0044] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0045] Sending a first message, wherein the first message configures a first PDCP entity and a plurality of RLC entities, wherein the first PDCP entity is associated with the plurality of RLC entities;

[0046] Decoding a first PDCP PDU;

[0047] Among them, the first PDCP PDU is operated by the receiver of the first message; the operation of the first PDCP PDU by the receiver of the first message includes: the first PDCP PDU is copied and the first PDCP PDU is delivered to the RLC entity in the target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the first PDCP PDU is copied and depends on the target RLC entity subset including at least two RLC entities.

[0048] According to one aspect of the present application, it is characterized in that the first PDCP PDU is operated by the receiver of the first message, including: the target RLC entity subset is determined among the multiple RLC entity subsets.

[0049] According to one aspect of the present application, it is characterized by comprising:

[0050] Sending first signaling, where the first signaling is signaling of a protocol layer below the RRC sublayer;

[0051] The first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set; the first candidate RLC entity set includes the multiple RLC entities; the first message configures each RLC entity in the first candidate RLC entity set, and the first PDCP entity is associated with each RLC entity in the candidate RLC entity set.

[0052] According to one aspect of the present application, it is characterized in that the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0053] According to one aspect of the present application, it is characterized in that determining the target RLC entity subset among the multiple RLC entity subsets depends on a first threshold; and the first message configures the first threshold.

[0054] According to one aspect of the present application, it is characterized in that, as the first PDCP PDU is operated by the recipient of the first message, the sum of the first PDCP data volume and the first RLC data volume is not less than the first threshold, and the first PDCP data volume and the first RLC data volume are associated with the first PDCP entity.

[0055] According to one aspect of the present application, it is characterized in that the first message is configured with multiple thresholds, and the first threshold is one of the multiple thresholds.

[0056] The present application discloses a first node used for wireless communication, characterized by comprising:

[0057] A first receiver receives a first message, wherein the first message configures a first PDCP entity and a plurality of RLC entities, wherein the first PDCP entity is associated with the plurality of RLC entities;

[0058] A first transmitter operates a first PDCP PDU;

[0059] Among them, the behavior operation of the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to the RLC entity in the target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

[0060] The present application discloses a second node used for wireless communication, characterized by comprising:

[0061] A second transmitter sends a first message, wherein the first message configures a first PDCP entity and multiple RLC entities, wherein the first PDCP entity is associated with the multiple RLC entities;

[0062] a second receiver, configured to decode the first PDCP PDU;

[0063] Among them, the first PDCP PDU is operated by the receiver of the first message; the operation of the first PDCP PDU by the receiver of the first message includes: the first PDCP PDU is copied and the first PDCP PDU is delivered to the RLC entity in the target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the first PDCP PDU is copied and depends on the target RLC entity subset including at least two RLC entities.

[0064] As an embodiment, compared with the traditional solution, the present application has at least one of the following advantages:

[0065] -.Improved PDCP PDU processing efficiency;

[0066] -. Shorten latency while improving transmission reliability;

[0067] -.Reducing the probability of PDCP PDU being discarded;

[0068] -. Simple implementation;

[0069] -. Reduce the impact of the agreement;

[0070] -. Make the protocol architecture more flexible. BRIEF DESCRIPTION OF THE DRAWINGS

[0071] Other features, objects and advantages of the present application will become more apparent upon reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0072] FIG1 shows a flow chart according to an embodiment of the present application;

[0073] FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0074] FIG3 is a schematic diagram showing an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0075] FIG4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0076] FIG5 shows a wireless signal transmission flow chart according to an embodiment of the present application;

[0077] FIG6 shows a schematic diagram of a case where the target RLC entity subset is any one of multiple RLC entity subsets according to an embodiment of the present application;

[0078] FIG7 is a schematic diagram showing a method of determining a target RLC entity subset from a plurality of RLC entity subsets depending on a first threshold according to an embodiment of the present application;

[0079] FIG8 is a schematic diagram showing that the sum of the first PDCP data amount and the first RLC data amount is not less than a first threshold according to an embodiment of the present application;

[0080] FIG9 shows a schematic diagram of configuring multiple thresholds for a first message according to an embodiment of the present application;

[0081] FIG10 is a schematic diagram showing a relationship between a first PDCP entity and multiple RLC entities according to an embodiment of the present application;

[0082] FIG11 shows a structural block diagram of a processing device used in a first node according to an embodiment of the present application;

[0083] FIG12 shows a structural block diagram of a processing device used in a second node according to an embodiment of the present application;

[0084] FIG. 13 is a schematic diagram showing that multiple thresholds are used to determine multiple RLC subsets according to an embodiment of the present application. DETAILED DESCRIPTION

[0085] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of the present application can be combined with each other in any way.

[0086] Example 1

[0087] Example 1 illustrates a flowchart according to an embodiment of the present application, as shown in Figure 1. In Figure 1, each box represents a step, and it should be emphasized that the order of the boxes in the figure does not represent the temporal sequence between the steps represented.

[0088] In Example 1, the first node in the present application receives a first message in step 101, wherein the first message configures a first PDCP entity and multiple RLC entities, and the first PDCP entity is associated with the multiple RLC entities; in step 102, operates a first PDCP PDU; wherein the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity in the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

[0089] As an embodiment, the first PDCP entity is used for DRB (Data Radio Bearer), and the first RB identity is indicated by a DRB-Identity.

[0090] As an embodiment, the first PDCP entity is used for MRB (MBS Radio Bearer), and the first RB identity is indicated by an MRB-Identity.

[0091] As an embodiment, the first PDCP entity is used for SL (Sidelink)-DRB.

[0092] As an embodiment, the first PDCP entity is a transmitting PDCP entity.

[0093] As an embodiment, the first PDCP entity is located at the first node.

[0094] As an embodiment, the first PDCP entity is a sending PDCP entity of the first node.

[0095] As an embodiment, the first PDCP entity is used for a first radio bearer, and the first radio bearer is a radio bearer (Radio Bearer, RB) mapped to a control logical channel.

[0096] As a sub-embodiment of this embodiment, the control logic channel is a DCCH (Dedicated Control Channel).

[0097] As a sub-embodiment of this embodiment, the control logic channel is SCCH (Sidelink Control Channel).

[0098] As a sub-embodiment of this embodiment, the control logic channel is MCCH (MBS Control Channel).

[0099] As a sub-embodiment of this embodiment, the above method is beneficial to the transmission of control signaling.

[0100] As an embodiment, the first PDCP entity is used for a first radio bearer, and the first radio bearer is mapped to an RB of a data logical channel.

[0101] As a sub-embodiment of this embodiment, the data logical channel is a DTCH (Dedicated Traffic Channel).

[0102] As a sub-embodiment of this embodiment, the data logical channel is STCH (Sidelink Traffic Channel).

[0103] As a sub-embodiment of this embodiment, the data logical channel is MTCH (MBS Traffic Channel).

[0104] As a sub-embodiment of this embodiment, the above method is conducive to data transmission.

[0105] As an embodiment, along with the behavior operation of the first PDCP PDU, the PDCP copy of the first radio bearer is activated.

[0106] As an embodiment, along with the behavior operation of the first PDCP PDU, the PDCP copy of the first radio bearer is not deactivated.

[0107] As an embodiment, along with the behavior operation of the first PDCP PDU, the PDCP splitting of the first radio bearer is activated.

[0108] As an embodiment, along with the behavior operation of the first PDCP PDU, the PDCP splitting of the first radio bearer is not deactivated.

[0109] As an embodiment, the multiple RLC entities are associated with only one MAC entity.

[0110] As an embodiment, the multiple RLC entities are not associated with multiple MAC entities.

[0111] As an embodiment, the multiple RLC entities are associated with multiple MAC entities.

[0112] As an embodiment, the multiple RLC entities are associated with two MAC entities.

[0113] As an embodiment, the multiple RLC entities are associated with a MAC entity of an MCG (Master Cell Group) and a MAC entity of an SCG (Secondary Cell Group).

[0114] As an embodiment, any one of the multiple RLC entities is an active RLC entity.

[0115] As an embodiment, any RLC entity among the multiple RLC entities is not deactivated.

[0116] As an embodiment, the multiple RLC entities are all RLC entities associated with the first PDCP entity.

[0117] As an embodiment, the multiple RLC entities are some RLC entities associated with the first PDCP entity.

[0118] As an embodiment, the multiple RLC entities include at least one split secondary RLC entity.

[0119] As an embodiment, the multiple RLC entities do not include any split secondary RLC entity.

[0120] As an embodiment, the multiple RLC entities include at least one primary RLC entity.

[0121] As an embodiment, the multiple RLC entities do not include any primary RLC entity.

[0122] As an embodiment, the multiple RLC entities are a positive integer number of RLC entities.

[0123] As an embodiment, the multiple RLC entities are 2 RLC entities.

[0124] As an embodiment, the multiple RLC entities are 3 RLC entities.

[0125] As an embodiment, the multiple RLC entities are 4 RLC entities.

[0126] As an embodiment, the multiple RLC entities are 5 RLC entities.

[0127] As an embodiment, the multiple RLC entities are 6 RLC entities.

[0128] As an embodiment, the multiple RLC entities are 7 RLC entities.

[0129] As an embodiment, the multiple RLC entities are 8 RLC entities.

[0130] As an embodiment, the plurality of RLC entities is greater than 8 RLC entities.

[0131] As an embodiment, the above method is conducive to supporting transmission with higher rate and / or higher reliability.

[0132] As an embodiment, the above method is conducive to system expansion.

[0133] As an embodiment, any RLC entity among the multiple RLC entities is a UM (Unacknowledged Mode) RLC entity.

[0134] As an embodiment, any RLC entity among the multiple RLC entities is an AM (Acknowledged Mode) RLC entity.

[0135] As an embodiment, any RLC entity among the multiple RLC entities is an AM RLC entity or a UM RLC entity.

[0136] As an embodiment, the phrase “the first PDCP entity is associated with the multiple RLC entities” means that the first PDCP entity and the multiple RLC entities are configured to the same RB.

[0137] As an embodiment, the phrase "the first PDCP entity is associated with the multiple RLC entities" means that the multiple RLC entities are configured to the first PDCP entity.

[0138] As an embodiment, the phrase “the first PDCP entity is associated with the plurality of RLC entities” means that each of the plurality of RLC entities is linked to the first PDCP entity.

[0139] As an embodiment, the first message is an RRC message.

[0140] As an embodiment, the first message is a DCCH message.

[0141] As an embodiment, the first message is an SCCH message.

[0142] As an embodiment, a field in the first message indicates that the plurality of RLC entity subsets are activated.

[0143] As an embodiment, the first message indicates the status of each RLC entity subset among the multiple RLC entity subsets.

[0144] As an embodiment, the first message includes at least one RRCReconfiguration message.

[0145] As an embodiment, the first message includes at least one RadioBearerConfig IE, and at least one DRB-ToAddMod field in the at least one RadioBearerConfig IE configures the first PDCP entity; each DRB-ToAddMod field in the at least one DRB-ToAddMod field includes the identity of the first radio bearer.

[0146] As an embodiment, the first message includes at least one PDCP-Config IE, and the at least one PDCP-Config IE configures the first PDCP entity.

[0147] As an embodiment, the first message includes at least one RLC-Config IE, and one RLC-Config IE in the at least one RLC-Config IE configures one RLC entity among the multiple RLC entities.

[0148] As an embodiment, the first message includes at least one RLC-BearerConfig IE, and the at least one RLC-BearerConfig IE configures the first PDCP entity to be associated with the multiple RLC entities.

[0149] As an embodiment, the first message includes at least one RLC-BearerConfig IE, and each RLC-BearerConfig IE in the at least one RLC-BearerConfig IE is used to link one RLC entity among the multiple RLC entities to the first PDCP entity.

[0150] As an embodiment, the first message includes at least one RLC-BearerConfig IE, and each RLC-BearerConfig IE in the at least one RLC-BearerConfig IE includes the identity of the first radio bearer and an RLC-Config IE.

[0151] As an embodiment, each RLC-BearerConfig IE in the first message includes the identity of the first radio bearer and an RLC-Config IE for one RLC entity among the multiple RLC entities.

[0152] As an embodiment, the first message includes at least one RadioBearerConfig IE, and each RadioBearerConfig IE in the at least one RadioBearerConfig IE configures the identity of the first radio bearer and the PDCP configuration of the first radio bearer.

[0153] As an embodiment, the first message configures the multiple RLC entity subsets.

[0154] As an embodiment, the first message configures the RLC entity subset to which each RLC entity belongs.

[0155] As an embodiment, the first message configures an index of an RLC entity subset for each RLC entity among the multiple RLC entities.

[0156] As an embodiment, the first PDCP PDU is operated in the first PDCP entity.

[0157] As an embodiment, the first PDCP entity operates the first PDCP PDU.

[0158] As an embodiment, the first PDCP PDU is a PDCP Data PDU.

[0159] As an embodiment, the first PDCP PDU is a PDCP Data PDU.

[0160] As an embodiment, the first PDCP PDU is a resulting PDCP Data PDU.

[0161] As an embodiment, the first PDCP PDU is a PDCP Data PDU; the first PDCP entity is used to map to an RB of a control logical channel.

[0162] As an embodiment, the first PDCP PDU is a PDCP Control PDU.

[0163] As an embodiment, the first PDCP PDU is a PDCP Control PDU; the first PDCP entity is used to map to an RB of a data logical channel.

[0164] As an embodiment, the behavior of operating the first PDCP PDU includes: generating the first PDCP PDU.

[0165] As an embodiment, the first PDCP PDU is operated after the first PDCP PDU is generated.

[0166] As an embodiment, the first PDCP PDU is operated after TX_NEXT for the first PDCP entity is increased by 1.

[0167] As an embodiment, the behavior of operating the first PDCP PDU includes: delivering the first PDCP PDU to a lower layer.

[0168] As an embodiment, the behavior of operating the first PDCP PDU includes: delivering the first PDCP PDU to a lower layer protocol entity.

[0169] As an embodiment, the lower layer is a protocol layer below the PDCP sublayer of the first node.

[0170] As an embodiment, the lower layer includes an RLC sublayer.

[0171] As an embodiment, the lower layer is the RLC sublayer.

[0172] As an embodiment, the behavior of operating the first PDCP PDU includes: sending the first PDCP PDU.

[0173] As an embodiment, the behavior of operating the first PDCP PDU refers to: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in the target RLC entity subset.

[0174] As an embodiment, the behavior of copying the first PDCP PDU includes: generating a copy of the first PDCP PDU.

[0175] As an embodiment, the behavior of copying the first PDCP PDU includes: copying the first PDCP PDU according to the number of RLC entities in the first RLC entity subset.

[0176] As an embodiment, the behavior of copying the first PDCP PDU includes: copying N first PDCP PDUs; the N is the number of RLC entities in the first RLC entity subset.

[0177] As an embodiment, the behavior of copying the first PDCP PDU includes: copying N-1 of the first PDCP PDUs; the N is the number of RLC entities in the first RLC entity subset.

[0178] As an embodiment, the behavior of delivering the first PDCP PDU to an RLC entity in the target RLC entity subset refers to: delivering the first PDCP PDU to at least one RLC entity in the target RLC entity subset.

[0179] As an embodiment, the behavior of delivering the first PDCP PDU to an RLC entity in the target RLC entity subset refers to: delivering the first PDCP PDU to any RLC entity in the target RLC entity subset.

[0180] As an embodiment, the behavior of delivering the first PDCP PDU to an RLC entity in the target RLC entity subset refers to: delivering the first PDCP PDU to each RLC entity in the target RLC entity subset.

[0181] As an embodiment, any two RLC entity subsets among the multiple RLC entity subsets do not include the same RLC entity.

[0182] As an embodiment, the number of RLC entities in at least one RLC entity subset among the multiple RLC entity subsets is not less than 2.

[0183] As an embodiment, the number of RLC entities in any RLC entity subset among the multiple RLC entity subsets is not less than 2.

[0184] As an embodiment, the number of RLC entities in one of the multiple RLC entity subsets is 1.

[0185] As an embodiment, the number of RLC entity subsets in the multiple RLC entity subsets is configurable.

[0186] As an embodiment, the number of RLC entity subsets in the multiple RLC entity subsets is default.

[0187] As an embodiment, the multiple RLC entity subsets are 2 RLC entity subsets.

[0188] As an embodiment, the multiple RLC entity subsets are greater than 2 RLC entity subsets.

[0189] As an embodiment, the multiple RLC entity subsets are no less than 2 RLC entity subsets.

[0190] As an embodiment, the multiple RLC entity subsets include at most 8 RLC entity subsets.

[0191] As an embodiment, the multiple RLC entity subsets include at most 4 RLC entity subsets.

[0192] As an embodiment, the multiple RLC entity subsets include at most 2 RLC entity subsets.

[0193] As an embodiment, multiple RLC entities belonging to the same RLC entity subset are used for PDCP duplication.

[0194] As an embodiment, PDCP replication is activated for multiple RLC entities belonging to the same RLC entity subset.

[0195] As an embodiment, multiple RLC entities belonging to the same RLC entity subset are allowed PDCP duplication.

[0196] As an embodiment, multiple RLC entities belonging to the same RLC entity subset are enabled with PDCP duplication.

[0197] As an embodiment, any RLC entity in each of the multiple RLC entity subsets is an RLC entity activated for PDCP duplication.

[0198] As an embodiment, one RLC entity subset among the multiple RLC entity subsets includes more than one RLC entity, and any one of the more than one RLC entities is an RLC entity activated for PDCP duplication.

[0199] As an embodiment, one RLC entity subset among the multiple RLC entity subsets includes more than one RLC entity, and any RLC entity among the more than one RLC entities does not deactivate PDCP duplication.

[0200] As an embodiment, one RLC entity subset among the multiple RLC entity subsets includes more than one RLC entity, and any one of the more than one RLC entities is used for PDCP duplication.

[0201] As an embodiment, one RLC entity subset among the multiple RLC entity subsets includes a primary RLC entity, and another RLC entity subset among the multiple RLC entity subsets includes a split secondary RLC entity.

[0202] As an embodiment, one RLC entity subset among the multiple RLC entity subsets includes a split secondary RLC entity, and another RLC entity subset among the multiple RLC entity subsets includes another split secondary RLC entity; the one split secondary RLC entity and the another split secondary RLC entity are different.

[0203] As an embodiment, the first message configures the multiple RLC entity subsets.

[0204] As an embodiment, the first message configures and activates the multiple RLC entity subsets.

[0205] As an embodiment, the first message configures the RLC entities included in each RLC entity subset of the multiple RLC entity subsets.

[0206] As an embodiment, the first message configures each of the multiple RLC entities to an RLC entity subset among the multiple RLC entity subsets.

[0207] As an embodiment, each RLC entity subset among the multiple RLC entity subsets is associated with an index of an RLC entity subset.

[0208] As a sub-embodiment of the above embodiment, an index of an RLC entity subset is used to indicate an RLC entity subset among the multiple RLC entity subsets.

[0209] As a sub-embodiment of the above embodiment, any two RLC entity subsets among the multiple RLC entity subsets are configured with different RLC entity subset indexes.

[0210] As a sub-embodiment of the above embodiment, if an RLC entity is configured with an index of an RLC entity subset, the RLC entity belongs to the RLC entity subset identified by the index of the RLC entity subset; the first message configures an index of an RLC entity subset for each of the multiple RLC entities.

[0211] As a sub-embodiment of the above embodiment, if an item in a list for an RLC entity subset includes an index of an RLC entity, the RLC entity belongs to the RLC entity subset; the first message configures a list for each RLC entity subset in the multiple RLC entity subsets.

[0212] As a sub-embodiment of the above embodiment, the list of each RLC entity subset in the plurality of RLC entity subsets includes an index of the RLC entity subset.

[0213] As an embodiment, if an RLC entity is associated with a primary RLC entity, the RLC entity belongs to the RLC entity subset including the primary RLC entity; if an RLC entity is associated with a split secondary RLC entity, the RLC entity belongs to the RLC entity subset including the split secondary RLC entity.

[0214] As an embodiment, when the target RLC entity subset includes at least two RLC entities, the behavior of copying the first PDCP PDU is performed.

[0215] As an embodiment, the target RLC entity subset includes at least two RLC entities that trigger the behavior of copying the first PDCP PDU.

[0216] As an embodiment, under the premise that the target RLC entity subset includes only one RLC entity, the behavior of copying the first PDCP PDU is not performed.

[0217] Example 2

[0218] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in FIG2 . FIG2 illustrates a network architecture 200 of a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system. The 5G NR / LTE / LTE-A network architecture 200 may be referred to as a 5G System (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5G Core Network (5G Core Network) / EPC (Evolved Packet Core) 210, a Home Subscriber Server (HSS) / UDM (Unified Data Management) 220, and an Internet service 230. 5GS / EPS can interconnect with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, but those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmitter / receiver node), or some other appropriate terminology. Node 203 provides an access point to the 5GC / EPC 210 for UE 201. Examples of UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device.Those skilled in the art may also refer to UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate term. Node 203 is connected to 5GC / EPC 210 via an S1 / NG interface. 5GC / EPC 210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF 213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​Generally, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocol) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet services 230. Internet services 230 include operator-specific Internet protocol services, which may specifically include the Internet, intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0219] As an embodiment, the UE201 corresponds to the first node in this application.

[0220] As an embodiment, the UE 201 is a user equipment (UE).

[0221] As an embodiment, the UE 201 is a base station (BS).

[0222] As an embodiment, the UE 201 is a relay device.

[0223] As an embodiment, the UE 201 is a gateway device.

[0224] As an embodiment, the node 203 corresponds to the second node in this application.

[0225] As an embodiment, the node 203 is a base station device.

[0226] As an embodiment, the node 203 is a user equipment.

[0227] As an embodiment, the node 203 is a relay device.

[0228] As an embodiment, the node 203 is a gateway device.

[0229] Typically, the UE 201 is a user equipment, and the node 203 is a base station device.

[0230] Typically, the UE 201 is a user equipment, and the node 203 is a user equipment.

[0231] Typically, the UE 201 is a base station device, and the node 203 is a base station device.

[0232] As an embodiment, the user equipment supports transmission of large amounts of data.

[0233] As an embodiment, the user equipment supports XR.

[0234] As an embodiment, the user equipment supports VR.

[0235] As an embodiment, the user equipment supports AR.

[0236] As an embodiment, the user equipment supports PDCP duplication.

[0237] As an embodiment, the user equipment supports PDCP splitting.

[0238] As an embodiment, the user equipment supports PDCP duplication and splitting.

[0239] As an embodiment, the user equipment supports transmission of a non-terrestrial network (NTN).

[0240] As an embodiment, the user equipment supports transmission via a terrestrial network (Terrestrial Network).

[0241] As an embodiment, the user equipment supports dual connection (DC) transmission.

[0242] As an embodiment, the user equipment includes an aircraft.

[0243] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0244] As an embodiment, the user equipment includes a vessel.

[0245] As an embodiment, the user equipment includes an Internet of Things terminal.

[0246] As an embodiment, the user equipment includes a terminal of the Industrial Internet of Things.

[0247] As an embodiment, the user equipment includes a device that supports low-latency and high-reliability transmission.

[0248] As an embodiment, the user equipment includes a test device.

[0249] As an embodiment, the user equipment includes a signaling tester.

[0250] As an embodiment, the user equipment includes an IAB (Integrated Access and Backhaul)-MT.

[0251] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0252] As an embodiment, the base station device supports transmission of a terrestrial network.

[0253] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0254] As an embodiment, the base station device includes a Node B (NB).

[0255] As an embodiment, the base station device includes a gNB.

[0256] As an embodiment, the base station device includes an eNB.

[0257] As an embodiment, the base station device includes ng-eNB.

[0258] As an embodiment, the base station device includes an en-gNB.

[0259] As an embodiment, the base station device includes a CU (Centralized Unit).

[0260] As an embodiment, the base station device includes a DU (Distributed Unit).

[0261] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

[0262] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.

[0263] As an embodiment, the base station device includes a micro cell base station.

[0264] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0265] As an embodiment, the base station device includes a home base station (Femtocell).

[0266] As an embodiment, the base station device includes a flying platform device.

[0267] As an embodiment, the base station device includes a satellite device.

[0268] As an embodiment, the base station device includes a testing device.

[0269] As an embodiment, the base station equipment includes a signaling tester.

[0270] As an embodiment, the base station device includes a gateway device.

[0271] As an embodiment, the base station device includes an IAB-node.

[0272] As an embodiment, the base station device includes an IAB-donor.

[0273] As an embodiment, the base station device includes an IAB-donor-CU.

[0274] As an embodiment, the base station device includes an IAB-donor-DU.

[0275] As an embodiment, the base station device includes an IAB-DU.

[0276] As an embodiment, the base station device includes an IAB-MT.

[0277] As an embodiment, the relay device includes a relay.

[0278] As an embodiment, the relay device includes an L3 relay.

[0279] As an embodiment, the relay device includes an L2 relay.

[0280] As an embodiment, the relay device includes a router.

[0281] As an embodiment, the relay device includes a switch.

[0282] As an embodiment, the relay device includes a gateway device.

[0283] As an embodiment, the relay device includes user equipment.

[0284] As an embodiment, the relay device includes a base station device.

[0285] Example 3

[0286] Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in FIG3 . FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 illustrates the radio protocol architecture for the control plane 300 using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. Layer 2 (L2 layer) 305 is above PHY 301 and includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets and supports inter-zone mobility. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) within a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling. The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture in the user plane 350 is generally identical to the corresponding layers and sublayers in the control plane 300, including the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355. However, the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping QoS flows to data radio bearers (DRBs) to support service diversity.

[0287] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the first node in this application.

[0288] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the second node in this application.

[0289] As an embodiment, the first message in this application is generated in the RRC306.

[0290] As an embodiment, the first message in the present application is generated by the MAC302 or MAC352.

[0291] As an embodiment, the first message in this application is generated by the PHY301 or PHY351.

[0292] As an embodiment, the first PDCP PDU in the present application is generated in the RRC306.

[0293] As an embodiment, the first PDCP PDU in this application is generated in the SDAP356.

[0294] As an embodiment, the first PDCP PDU in the present application is generated by the PDCP354.

[0295] As an embodiment, the first PDCP PDU in the present application is generated by the MAC302 or MAC352.

[0296] As an embodiment, the first PDCP PDU in the present application is generated by the PHY301 or PHY351.

[0297] Example 4

[0298] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in Figure 4. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0299] The first communication device 450 includes a controller / processor 459 , a memory 460 , a data source 467 , a transmit processor 468 , a receive processor 456 , a multi-antenna transmit processor 457 , a multi-antenna receive processor 458 , a transmitter / receiver 454 and an antenna 452 .

[0300] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 , and an antenna 420 .

[0301] During transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to the controller / processor 475 at the second communication device 410. The controller / processor 475 implements L2 layer functionality. During transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0302] During transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal via its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a fast Fourier transform (FFT). In the frequency domain, the receive processor 456 demultiplexes the physical layer data signal and reference signal, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to the L3 layer for L3 processing.

[0303] During transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission functionality at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 457, the stream is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a RF symbol stream before providing it to the antenna 452.

[0304] During transmission from the first communications device 450 to the second communications device 410, the functionality at the second communications device 410 is similar to the reception functionality at the first communications device 450 described for transmission from the second communications device 410 to the first communications device 450. Each receiver 418 receives RF signals via its corresponding antenna 420, converts the received RF signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement L1 layer functionality. A controller / processor 475 implements L2 layer functionality. The controller / processor 475 may be associated with a memory 476 storing program codes and data. The memory 476 may be referred to as a computer-readable medium. During transmission from the first communications device 450 to the second communications device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0305] As an embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 at least: receives a first message, the first message configures a first PDCP entity and multiple RLC entities, the first PDCP entity is associated with the multiple RLC entities; operates a first PDCP PDU; wherein the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity in the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

[0306] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receiving a first message, the first message configuring a first PDCP entity and multiple RLC entities, the first PDCP entity being associated with the multiple RLC entities; operating a first PDCP PDU; wherein the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity in the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

[0307] As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 410 at least: sends a first message, the first message configures a first PDCP entity and multiple RLC entities, the first PDCP entity is associated with the multiple RLC entities; de-operates a first PDCP PDU; the first PDCP PDU is operated by the receiver of the first message; the first PDCP PDU is operated by the receiver of the first message including: the first PDCP PDU is copied and the first PDCP PDU is delivered to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity in the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the first PDCP PDU is copied and depends on the target RLC entity subset including at least two RLC entities.

[0308] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: sending a first message, the first message configuring a first PDCP entity and multiple RLC entities, the first PDCP entity being associated with the multiple RLC entities; de-operating a first PDCP PDU; the first PDCP PDU being operated by the receiver of the first message; the first PDCP PDU being operated by the receiver of the first message including: the first PDCP PDU being copied and the first PDCP PDU being delivered to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity in the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the first PDCP PDU is copied and depends on the target RLC entity subset including at least two RLC entities.

[0309] As an embodiment, at least one of the antenna 452 , the receiver 454 , the reception processor 456 , and the controller / processor 459 is used to receive a first message.

[0310] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first message.

[0311] As an embodiment, at least one of the antenna 452 , the receiver 454 , the receiving processor 456 , and the controller / processor 459 is used to receive first signaling.

[0312] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send the first signaling.

[0313] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to operate the first PDCP PDU.

[0314] As an embodiment, at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller / processor 475 is used to decompress the first PDCP PDU.

[0315] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0316] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0317] As an embodiment, the first communication device 450 is a user equipment.

[0318] As an embodiment, the first communication device 450 is a base station device.

[0319] As an embodiment, the first communication device 450 is a relay device.

[0320] As an embodiment, the second communication device 410 is a user equipment.

[0321] As an embodiment, the second communication device 410 is a base station device.

[0322] As an embodiment, the second communication device 410 is a relay device.

[0323] Example 5

[0324] Example 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in FIG5. It should be noted that the order in this example does not limit the signal transmission order and implementation order in the present application.

[0325] For the first node U01, in step S5101, a first message is received, wherein the first message configures a first PDCP entity and multiple RLC entities, and the first PDCP entity is associated with the multiple RLC entities; in step S5102, a first signaling is received, wherein the first signaling is a signaling of a protocol layer below the RRC sublayer; in step S5103, the target RLC entity subset is determined among the multiple RLC entity subsets; in step S5104, the first PDCP PDU is copied; in step S5105, the first PDCP PDU is delivered to the RLC entity in the target RLC entity subset; in step S5106, a first data block is sent, wherein the first data block carries at least part of the first PDCP PDU.

[0326] For the second node N02, in step S5201, the first message is sent; in step S5202, the first signaling is sent; in step S5203, the first data block is received; in step S5204, the first PDCP PDU is decoded.

[0327] In Example 5, the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

[0328] As an embodiment, the first node U01 and the second node N02 are connected wirelessly.

[0329] As an embodiment, the first node U01 and the second node N02 are connected via a wired connection.

[0330] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0331] As an embodiment, the first node U01 and the second node N02 are connected via an IAB port.

[0332] As an embodiment, the first node U01 and the second node N02 are connected via a PC5 interface.

[0333] As an embodiment, step S5103 is optional.

[0334] As an embodiment, step S5103 exists.

[0335] As an embodiment, the behavior operation of the first PDCP PDU includes: determining the target RLC entity subset among the multiple RLC entity subsets.

[0336] As an embodiment, step S5103 does not exist.

[0337] As an embodiment, step S5204 is optional.

[0338] As an embodiment, step S5204 exists.

[0339] As an embodiment, when step S5204 exists, step S5203 exists.

[0340] As an embodiment, step S5204 does not exist.

[0341] As an embodiment, the dotted box F5.1 is optional.

[0342] As an embodiment, the dotted box F5.1 exists.

[0343] As an embodiment, the dotted box F5.1 does not exist.

[0344] As an embodiment, the dotted box F5.2 is optional.

[0345] As an embodiment, the dotted box F5.2 exists.

[0346] As an embodiment, the dotted box F5.2 does not exist.

[0347] As an embodiment, the first message configures the first candidate RLC entity set.

[0348] As an embodiment, the first message configures a subset of RLC entities in the first candidate RLC entity set.

[0349] As an embodiment, the first message configures an RLC entity in each RLC entity subset in the first set of candidate RLC entities.

[0350] As an embodiment, the first candidate RLC entity set only includes activated RLC entities.

[0351] As an embodiment, the first candidate RLC entity set includes any one of an activated RLC entity and an unactivated RLC entity.

[0352] As an embodiment, the first candidate RLC entity set includes at least one split secondary RLC entity.

[0353] As an embodiment, the first candidate RLC entity set does not include any split secondary RLC entity.

[0354] As an embodiment, the first candidate RLC entity set includes at least one primary RLC entity.

[0355] As an embodiment, the first candidate RLC entity set does not include any primary RLC entity.

[0356] As an embodiment, the first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in a first candidate RLC entity set; the first candidate RLC entity set includes the multiple RLC entities; the first message configures each RLC entity in the first candidate RLC entity set, and the first PDCP entity is associated with each RLC entity in the candidate RLC entity set.

[0357] As an embodiment, the first signaling is used to activate or deactivate each RLC entity subset among the multiple RLC entity subsets.

[0358] As an embodiment, the first signaling is used to activate or deactivate each RLC entity subset in the first candidate RLC entity set.

[0359] As an embodiment, the first signaling is used to indicate the activation or deactivation status of each RLC entity subset among the multiple RLC entity subsets.

[0360] As an embodiment, the reception of the first signaling triggers activation of at least one RLC entity subset among the multiple RLC entity subsets.

[0361] As an embodiment, the first signaling is used to activate the at least one RLC entity subset among the multiple RLC entity subsets.

[0362] As an embodiment, the first signaling is used to indicate the at least one RLC entity subset among the multiple RLC entity subsets.

[0363] As an embodiment, the reception of the first signaling triggers activation of the plurality of RLC entity subsets in the first candidate RLC entity set.

[0364] As an embodiment, the first signaling is used to activate the plurality of RLC entity subsets in the first candidate RLC entity set.

[0365] As an embodiment, the first signaling is used to indicate the multiple RLC entity subsets in the first candidate RLC entity set.

[0366] As an embodiment, the first signaling indicates a subset of RLC entities used for PDCP splitting.

[0367] As an embodiment, the first signaling indicates a subset of RLC entities used for PDCP replication.

[0368] As an embodiment, the first signaling indicates a subset of RLC entities that are used for PDCP replication and splitting.

[0369] As an embodiment, the first signaling is a MAC subPDU.

[0370] As an embodiment, the first signaling is a MAC CE (Control Element).

[0371] As an embodiment, the first signaling is a Duplication RLC Activation / Deactivation MAC CE.

[0372] As an embodiment, the first signaling is not Duplication RLC Activation / Deactivation MAC CE.

[0373] As an embodiment, the first signaling is a MAC subheader.

[0374] As an embodiment, the first signaling includes a MAC subheader.

[0375] As an embodiment, the LCID (Logical Channel ID) field in the MAC subheader in the first signaling indicates that the first signaling is used to activate at least one RLC entity subset among the multiple RLC entity subsets.

[0376] As an embodiment, the eLCID (extended LCID) field in the MAC subheader in the first signaling indicates that the first signaling is used to activate at least one RLC entity subset among the multiple RLC entity subsets.

[0377] As an embodiment, the first signaling is a DCI.

[0378] As an embodiment, a DCI field in the first signaling indicates that the first signaling is used to activate at least one RLC entity subset among the multiple RLC entity subsets.

[0379] As an embodiment, a DCI field in the first signaling indicates that the first signaling is used to activate at least one RLC entity subset among the multiple RLC entity subsets.

[0380] As an embodiment, the first signaling is a DCI payload.

[0381] As an embodiment, the first signaling is a DCI format.

[0382] As an embodiment, the first signaling indicates each RLC entity subset in the multiple RLC entity subsets in the first candidate RLC entity set.

[0383] As an embodiment, the first signaling indicates the index of each RLC entity subset in the multiple RLC entity subsets in the first candidate RLC entity set.

[0384] As an embodiment, the first signaling indicates, in the first candidate RLC entity set, an index of the RLC entity included in each RLC entity subset of the multiple RLC entity subsets.

[0385] As an embodiment, the first signaling indicates each RLC entity subset in the multiple RLC entity subsets included in the first candidate RLC entity set; the first candidate RLC entity set includes multiple candidate RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets is a candidate RLC entity subset in the first candidate RLC entity set.

[0386] As an embodiment, a field in the first signaling indicates the identity of the first radio bearer.

[0387] As an embodiment, at least one field in the first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set.

[0388] As a sub-embodiment of the above embodiment, each field in the at least one field is set to an index of an RLC entity subset in the at least one RLC entity subset.

[0389] As an embodiment, a bitmap in the first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set.

[0390] As a sub-embodiment of the above embodiment, the bits in the one bitmap correspond one-to-one to a subset of RLC entities in the first candidate RLC entity set.

[0391] As a sub-embodiment of the above embodiment, one bit in the one bitmap indicates a subset of RLC entities in the first candidate RLC entity set.

[0392] As a sub-embodiment of the above embodiment, the bits corresponding to the at least one RLC entity subset among the multiple RLC entity subsets in the one bit map are set to 1; the bits corresponding to the RLC entity subsets other than the at least one RLC entity subset among the multiple RLC entity subsets in the one bit map are set to 0.

[0393] As a sub-embodiment of the above embodiment, if a bit in the bit map is set to 1, it indicates that the RLC entity subset corresponding to the bit is activated; if a bit in the bit map is set to 0, it does not indicate that the RLC entity subset corresponding to the bit is activated.

[0394] As a sub-embodiment of the above embodiment, the number of the bitmap is not less than the number of RLC entity subsets in the first candidate RLC entity set.

[0395] As a sub-embodiment of the above embodiment, the number of the bitmap is the maximum number of configurable RLC entity subsets in the first candidate RLC entity set.

[0396] As an embodiment, a bitmap in the first signaling indicates each RLC entity of the multiple RLC entities in the first candidate RLC entity set.

[0397] As a sub-embodiment of the above embodiment, the bits in the one bitmap correspond one-to-one to the RLC entities in the first candidate RLC entity set.

[0398] As a sub-embodiment of the above embodiment, one bit in the one bitmap indicates one RLC entity in the first candidate RLC entity set.

[0399] As a sub-embodiment of the above embodiment, the bit corresponding to each of the multiple RLC entities in the one bit map is set to 1; the bit corresponding to the RLC entity other than the multiple RLC entities in the one bit map is set to 0.

[0400] As a sub-embodiment of the above embodiment, if a bit in the bit map is set to 1, it indicates that the RLC entity corresponding to the bit is activated; if a bit in the bit map is set to 0, it does not indicate that the RLC entity corresponding to the bit is activated.

[0401] As a sub-embodiment of the above embodiment, the number of the bitmap is not less than the number of RLC entities in the first candidate RLC entity set.

[0402] As a sub-embodiment of the above embodiment, the number of the bitmap is the maximum number of configurable RLC entities in the first candidate RLC entity set.

[0403] As an embodiment, a field in the first signaling indicates one of PDCP duplication, PDCP splitting, and PDCP duplication and splitting.

[0404] As a sub-embodiment of the above embodiment, the one field occupies 2 bits.

[0405] As a sub-embodiment of the above embodiment, the one field includes four bit states, wherein three bit states respectively indicate PDCP duplication, PDCP splitting, and PDCP duplication and splitting, and one bit state is reserved.

[0406] As an embodiment, a field in the first signaling indicates the identity of the first radio bearer; a bit map in the first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set.

[0407] As an embodiment, a field in the first signaling indicates the identity of the first radio bearer; and a bit map in the first signaling indicates each RLC entity in the multiple RLC entities in the first candidate RLC entity set.

[0408] As an embodiment, the first candidate RLC entity set is the multiple RLC entities.

[0409] As an embodiment, the first candidate RLC entity set includes the multiple RLC entities and at least one RLC entity other than the multiple RLC entities.

[0410] As an embodiment, the first candidate RLC entity set is all RLC entities associated with the first PDCP entity.

[0411] As an embodiment, the first candidate RLC entity set is all RLC entities associated with multiple PDCP entities, and the multiple PDCP entities include at least the first PDCP entity.

[0412] As an embodiment, the behavior operation of the first PDCP PDU includes: determining the target RLC entity subset among the multiple RLC entity subsets.

[0413] As an embodiment, an RLC entity subset is selected from the multiple RLC entity subsets, and the one RLC entity subset is the target RLC entity subset; the phrase determining the target RLC entity subset from the multiple RLC entity subsets means: selecting the target RLC entity subset from the multiple RLC entity subsets.

[0414] As a sub-embodiment of the above embodiment, the selection refers to: random selection.

[0415] As a sub-embodiment of the above embodiment, the selection refers to: selecting according to Poisson distribution.

[0416] As a sub-embodiment of the above embodiment, the selection refers to: selecting according to measurement results.

[0417] As a subsidiary embodiment of the above sub-embodiment, the measurement result is RSRP (Reference Signal Received Power).

[0418] As a subsidiary embodiment of the above sub-embodiment, the measurement result is RSRQ (Reference Signal Received Quality).

[0419] As a subsidiary embodiment of the above sub-embodiment, the measurement result is an L1 (Layer 1) measurement result.

[0420] As a subsidiary embodiment of the above sub-embodiment, the measurement result is an L3 (Layer 3) measurement result.

[0421] As a sub-embodiment of the above embodiment, the selection refers to: selecting according to the amount of data.

[0422] As a subsidiary embodiment of the above sub-embodiment, the data amount is the PDCP data amount.

[0423] As a subsidiary embodiment of the above sub-embodiment, the data amount is the RLC data amount.

[0424] As a subsidiary embodiment of the above sub-embodiment, the data amount is the data amount of PDCP and the data amount of RLC.

[0425] As a sub-embodiment of the above embodiment, the selecting refers to: selecting according to the number of RLC entities included in each RLC entity subset among the multiple RLC entity subsets.

[0426] As a sub-embodiment of the above embodiment, the selection refers to: selecting according to the data volume and the measurement result.

[0427] As a sub-embodiment of the above embodiment, the selection refers to: selecting according to the amount of data and the number of RLC entities included in the RLC entity subset.

[0428] As an embodiment, the target RLC entity subset is activated among the multiple RLC entity subsets; the phrase determining the target RLC entity subset among the multiple RLC entity subsets means: activating the target RLC entity subset among the multiple RLC entity subsets.

[0429] As a sub-embodiment of the above embodiment, when a signaling is received, the target RLC entity subset is activated among the multiple RLC entity subsets.

[0430] As a subsidiary embodiment of the above sub-embodiment, the signaling is signaling of a protocol layer below the RRC sublayer.

[0431] As a subsidiary embodiment of the above sub-embodiment, the one signaling includes the first signaling.

[0432] As a sub-embodiment of the above embodiment, when at least one condition is met, the target RLC entity subset is activated among the multiple RLC entity subsets; and the first message configures the at least one condition.

[0433] As a subsidiary embodiment of the above sub-embodiment, one of the at least one condition is related to the amount of data.

[0434] As a subsidiary embodiment of the above sub-embodiment, one of the at least one condition is related to a measurement result.

[0435] As a subsidiary embodiment of the above sub-embodiment, one of the at least one condition is related to the number of RLC entities included in each of the multiple RLC entity subsets.

[0436] As an embodiment, the first data block is used to carry the first PDCP PDU.

[0437] As an embodiment, the first data block includes the first PDCP PDU.

[0438] As an embodiment, the first data block is used to carry at least the portion of the first PDCP PDU.

[0439] As an embodiment, the first data block includes at least the portion of the first PDCP PDU.

[0440] As an embodiment, the first data block is transmitted at the physical layer.

[0441] As an embodiment, the first data block is a TB (Transport Block).

[0442] As an embodiment, the first data block is multiple TBs.

[0443] As an embodiment, the first data block is transmitted through a PUSCH (Physical Uplink Shared Channel) resource.

[0444] As an embodiment, the first data block is transmitted through multiple PUSCH resources.

[0445] As an embodiment, the first data block is transmitted through a PSSCH (Physical Sidelink Shared Channel) resource.

[0446] As an embodiment, the first data block is transmitted through multiple PSSCH resources.

[0447] As an embodiment, the first data block is transmitted through at least one PSSCH resource and at least one PUSCH resource.

[0448] As an embodiment, the behavior of decomposing the first PDCP PDU includes: receiving the first PDCP PDU.

[0449] As an embodiment, the behavior of operating the first PDCP PDU includes: determining a COUNT value of the first PDCP PDU.

[0450] As an embodiment, the behavior of operating the first PDCP PDU includes: determining an RCVD_COUNT of the first PDCP PDU.

[0451] As an embodiment, the behavior of deciphering the first PDCP PDU includes: performing deciphering and integrity verification of the first PDCP PDU.

[0452] As an embodiment, the behavior of decomposing the first PDCP PDU includes: receiving the first PDCP PDU from a lower layer.

[0453] As an embodiment, the behavior of operating the first PDCP PDU includes: delivering the first PDCP PDU to a higher layer.

[0454] Example 6

[0455] Embodiment 6 illustrates a schematic diagram in which the target RLC entity subset is any RLC entity subset among multiple RLC entity subsets according to an embodiment of the present application, as shown in FIG6 .

[0456] In embodiment 6, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0457] As an embodiment, when the multiple RLC entity subsets are configured, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0458] As an embodiment, when the multiple RLC entity subsets are indicated, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0459] As an embodiment, when the multiple RLC entity subsets are activated, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0460] As an embodiment, accompanying the behavior operation of the first PDCP PDU, when the sum of the first PDCP data amount and the first RLC data amount is not less than the first threshold, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0461] As an embodiment, accompanying the behavior operation of the first PDCP PDU, when the sum of the first PDCP data amount and the first RLC data amount is not less than the first threshold and the multiple RLC entity subsets are configured, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0462] As an embodiment, the behavior operates a first PDCP PDU, when the sum of the first PDCP data amount and the first RLC data amount is not less than the first threshold and the multiple RLC entity subsets are indicated, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0463] As an embodiment, accompanying the behavior operation of the first PDCP PDU, when the sum of the first PDCP data amount and the first RLC data amount is not less than the first threshold and the multiple RLC entity subsets are activated, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0464] Example 7

[0465] Embodiment 7 illustrates a schematic diagram of determining a target RLC entity subset depending on a first threshold value among multiple RLC entity subsets according to an embodiment of the present application, as shown in FIG7 .

[0466] In embodiment 7, determining the target RLC entity subset among the multiple RLC entity subsets depends on a first threshold; and the first message configures the first threshold.

[0467] As an embodiment, the first threshold is a data volume threshold.

[0468] As a sub-embodiment of the above embodiment, the data volume threshold is configured by a ul-DataSplitThreshold field.

[0469] As a sub-embodiment of the above embodiment, the data volume threshold is configured by a ul-DataSplitThreshold-r19 field.

[0470] As a sub-embodiment of the above embodiment, the data volume threshold is configured by a ul-DataSplitThreshold-r20 field.

[0471] As a sub-embodiment of the above embodiment, the unit of the data volume threshold is bit.

[0472] As a sub-embodiment of the above embodiment, the unit of the data volume threshold is byte.

[0473] As an embodiment, the first threshold is a measurement result threshold.

[0474] As a sub-embodiment of the above embodiment, the measurement result threshold is an RSRP threshold.

[0475] As a sub-embodiment of the above embodiment, the measurement result threshold is an RSRQ threshold.

[0476] As a sub-embodiment of the above embodiment, the measurement result threshold is an SINR threshold.

[0477] As a sub-embodiment of the above embodiment, the measurement result threshold is a BLER threshold.

[0478] As a sub-embodiment of the above embodiment, the unit of the measurement result threshold is dB.

[0479] As a sub-embodiment of the above embodiment, the unit of the measurement result threshold is dBm.

[0480] As an embodiment, the first threshold is a quantity threshold.

[0481] As a sub-embodiment of the above embodiment, the quantity threshold is a constant.

[0482] As a sub-embodiment of the above embodiment, the quantity threshold is a positive integer.

[0483] As an embodiment, the target RLC entity subset is determined from the multiple RLC entity subsets according to the first threshold.

[0484] As an embodiment, the target RLC entity subset is determined from the multiple RLC entity subsets only when the first threshold is satisfied.

[0485] As an embodiment, when the first threshold is met, the target RLC entity subset is determined from the multiple RLC entity subsets; when the first threshold is not met, the target RLC entity subset is a default RLC entity subset.

[0486] As an embodiment, when the first threshold is met, the target RLC entity subset is determined in the multiple RLC entity subsets; when the first threshold is not met, the target RLC entity subset is determined in the RLC entity subsets outside the multiple RLC entity subsets.

[0487] As an embodiment, the target RLC entity subset depends on the data amount and the first threshold value in the multiple RLC entity subsets.

[0488] As an embodiment, the first threshold being satisfied means that the amount of data is not less than the first threshold.

[0489] As a sub-embodiment of the above embodiment, when the amount of data is less than the first threshold, the first threshold is not met.

[0490] As a sub-embodiment of the above embodiment, when the data amount is not less than the first threshold, the target RLC entity subset is determined from the multiple RLC entity subsets.

[0491] As a sub-embodiment of the above embodiment, the first PDCP PDU is operated along with the behavior, the data volume is not less than the first threshold, and the data volume is associated with the first PDCP entity.

[0492] As a sub-embodiment of the above embodiment, the data volume includes at least PDCP data volume.

[0493] As a sub-embodiment of the above embodiment, the data volume includes the RLC data volume.

[0494] As a sub-embodiment of the above embodiment, the data volume is the PDCP data volume associated with the first PDCP entity and the RLC data volume associated with the first PDCP entity.

[0495] As a sub-embodiment of the above embodiment, the data volume is the PDCP data volume associated with the first PDCP entity and the RLC data volume associated with the multiple RLC entity subsets.

[0496] As an embodiment, determining the target RLC entity subset among the multiple RLC entity subsets depends on the measurement result and the first threshold.

[0497] As an embodiment, the first threshold being met means that a measurement result of at least one cell associated with the multiple RLC entities is not better than the first threshold.

[0498] As a sub-embodiment of the above embodiment, the at least one cell refers to a cell associated with a default RLC entity subset.

[0499] As a sub-embodiment of the above embodiment, when a measurement result of at least one cell associated with the multiple RLC entities is worse than the first threshold, the first threshold is met.

[0500] As a subsidiary embodiment of the above sub-embodiment, along with the behavior operation of the first PDCP PDU, a measurement result of at least one cell associated with the multiple RLC entities is not better than the first threshold.

[0501] As a subsidiary embodiment of the above sub-embodiment, when the measurement result of any cell associated with the multiple RLC entities is better than the first threshold, the first threshold is not met.

[0502] As a sub-embodiment of the above embodiment, when the measurement results of at least M1 cells associated with the multiple RLC entities are worse than the first threshold, the first threshold is met; and the M1 is configurable.

[0503] As a subsidiary embodiment of the above sub-embodiment, when the measurement results associated with the multiple RLC entities are worse than the first threshold value which is less than M1, the first threshold value is not met.

[0504] As a subsidiary embodiment of the above sub-embodiment, along with the behavior operation of the first PDCP PDU, the measurement results of at least M1 cells associated with the multiple RLC entities are not better than the first threshold.

[0505] As a sub-embodiment of the above embodiment, when the measurement result of any cell associated with the multiple RLC entities is worse than the first threshold, the first threshold is met.

[0506] As a subsidiary embodiment of the above sub-embodiment, when the measurement results of all cells associated with the multiple RLC entities are better than the first threshold, the first threshold is not met.

[0507] As a subsidiary embodiment of the above sub-embodiment, along with the behavior operation of the first PDCP PDU, the measurement results of all cells associated with the multiple RLC entities are better than the first threshold.

[0508] As an embodiment, the number of RLC entities included in the target RLC entity subset and the first threshold value are determined among the multiple RLC entity subsets.

[0509] As an embodiment, the first threshold being satisfied means that the number of RLC entities included in at least one RLC entity subset among the multiple RLC entity subsets is not greater than the first threshold.

[0510] As a sub-embodiment of the above embodiment, when the number of RLC entities included in at least one RLC entity subset among the multiple RLC entity subsets is greater than the first threshold, the first threshold is not satisfied.

[0511] As a sub-embodiment of the above embodiment, along with the behavior operation of the first PDCP PDU, the number of RLC entities included in each RLC entity subset of the multiple RLC entity subsets is not greater than the first threshold.

[0512] As an embodiment, the default RLC entity subset refers to: a predefined RLC entity subset.

[0513] As an embodiment, the default RLC entity subset refers to: an RLC entity subset including a primary RLC entity.

[0514] As an embodiment, the default RLC entity subset refers to: the RLC entity subset with the smallest RLC entity subset index among the multiple RLC entity subsets.

[0515] As an embodiment, the default RLC entity subset refers to: an RLC entity subset having the largest index among the multiple RLC entity subsets.

[0516] Example 8

[0517] Embodiment 8 illustrates a schematic diagram in which the sum of the first PDCP data amount and the first RLC data amount is not less than the first threshold according to an embodiment of the present application, as shown in FIG8 .

[0518] In Example 8, the target RLC entity subset is determined to depend on a first threshold among the multiple RLC entity subsets; the first message configures the first threshold; accompanied by the behavior operation of the first PDCP PDU, the sum of the first PDCP data volume and the first RLC data volume is not less than the first threshold, and the first PDCP data volume and the first RLC data volume are associated with the first PDCP entity.

[0519] As an embodiment, the phrase “the sum of the first PDCP data amount and the first RLC data amount is not less than the first threshold value” means that the sum of the first PDCP data amount and the first RLC data amount is greater than the first threshold value.

[0520] As an embodiment, the phrase "the sum of the first PDCP data amount and the first RLC data amount is not less than the first threshold" means that the sum of the first PDCP data amount and the first RLC data amount is equal to or greater than the first threshold.

[0521] As an embodiment, the first PDCP data volume is the PDCP data volume of the first PDCP entity.

[0522] As an embodiment, the PDCP data volume includes the PDCP copied data volume.

[0523] As an embodiment, the PDCP data volume does not include the PDCP copied data volume.

[0524] As an embodiment, the PDCP data volume includes the data volume of the PDCP PDU.

[0525] As an embodiment, the PDCP data volume includes the data volume of the PDCP SDU.

[0526] As an embodiment, the PDCP data volume includes the data volume of PDCP PDU and PDCP SDU.

[0527] As an embodiment, the RLC data volume includes the data volume of the RLC SDU.

[0528] As an embodiment, the RLC data volume includes the data volume of the RLC PDU.

[0529] As an embodiment, the RLC data volume includes the data volume of RLC PDU and RLC SDU.

[0530] As an embodiment, the RLC data volume includes the data volume of RLC PDU and RLC SDU.

[0531] As an embodiment, the RLC data amount is the RLC data amount for initial transmission.

[0532] As an embodiment, the RLC data amount includes the data amount for initial transmission and the data amount for retransmission.

[0533] As an embodiment, the first RLC data volume is the RLC data volume of all RLC entities associated with the first PDCP entity.

[0534] As an embodiment, the first RLC data volume is the RLC data volume of the multiple RLC entities associated with the first PDCP entity.

[0535] As an embodiment, the first RLC data volume is the RLC data volume of all RLC entities in all RLC entity subsets among the multiple RLC entity subsets associated with the first PDCP entity.

[0536] As an embodiment, the first RLC data volume is the RLC data volume of all RLC entities in the first candidate RLC entity set associated with the first PDCP entity.

[0537] As an embodiment, the RLC data volume includes the data volume copied by PDCP.

[0538] As an embodiment, the RLC data volume does not include the data volume copied by PDCP.

[0539] As an embodiment, the RLC data volume is the RLC data volume for initial transmission, and the RLC data volume does not include the data volume copied by PDCP.

[0540] Example 9

[0541] Example 9 illustrates a schematic diagram of configuring multiple thresholds for a first message according to an embodiment of the present application, as shown in FIG9 .

[0542] In embodiment 9, the first message is configured with multiple thresholds, and the first threshold is one of the multiple thresholds.

[0543] As an embodiment, the first message includes a reference threshold and at least one offset; the reference threshold is one of the multiple thresholds, and the at least one offset and the reference threshold are used to determine each threshold other than the one of the multiple thresholds.

[0544] As an embodiment, the first message includes the multiple thresholds.

[0545] As an embodiment, one or two of the multiple thresholds are used to determine an RLC entity subset among the multiple RLC entity subsets.

[0546] As an embodiment, the multiple thresholds are used to determine multiple data volume intervals; each data volume interval corresponds to an RLC entity subset.

[0547] As an embodiment, along with the behavior operation of the first PDCP PDU, the target RLC entity subset is determined from the multiple RLC entity subsets according to the data volume interval to which the data volume belongs.

[0548] As an embodiment, the multiple thresholds are used to determine multiple measurement result intervals.

[0549] As an embodiment, along with the behavior operation of the first PDCP PDU, the target RLC entity subset is determined from the multiple RLC entity subsets according to the measurement result interval to which the measurement result belongs.

[0550] Example 10

[0551] Embodiment 10 illustrates a schematic diagram of a relationship between a first PDCP entity and multiple RLC entities according to an embodiment of the present application, as shown in FIG10 . In FIG10 , the first PDCP entity is associated with at least RLC entity #2, RLC entity #3, and RLC entity #4; the multiple RLC entity subsets include RLC entity subset #1 and RLC entity subset #2; the target RLC entity subset is RLC entity subset #2; RLC entity subset #1 includes RLC entity #2; RLC entity subset #2 includes RLC entity #3 and RLC entity #4;

[0552] In embodiment 10, the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU at the first PDCP entity and delivering the first PDCP PDU and the copy of the first PDCP PDU to RLC entity #3 and RLC entity #4 in RLC entity subset #2 respectively.

[0553] As an embodiment, after operating the first PDCP PDU, operating the second PDCP PDU; the behavior of operating the second PDCP PDU includes: copying the second PDCP PDU in the first PDCP entity and delivering the second PDCP PDU and the copy of the second PDCP PDU to RLC entity #1 and RLC entity #2 in RLC entity subset #1 respectively.

[0554] As an embodiment, the first candidate RLC entity set includes the RLC entity #1, the RLC entity #2, the RLC entity #3, the RLC entity #4, the RLC entity #5, the RLC entity #6, the RLC entity #7 and the RLC entity #8.

[0555] As an embodiment, the first candidate RLC entity set includes the RLC entity subset #1, the RLC entity subset #2, the RLC entity subset #3 and the RLC entity subset #4.

[0556] As an embodiment, the RLC entity subset #3 and the RLC entity subset #4 are deactivated.

[0557] As an embodiment, when an RLC entity subset is deactivated, each RLC entity in the RLC entity subset is deactivated.

[0558] As an embodiment, when an RLC entity subset is activated, each RLC entity in the RLC entity subset is activated.

[0559] As an embodiment, when an RLC entity subset is activated, the RLC entity indicated by the RRC message in the RLC entity subset is activated.

[0560] As an embodiment, the RLC entity #5, the RLC entity #6, the RLC entity #7 and the RLC entity #8 are deactivated.

[0561] As an embodiment, the first PDCP entity is associated with at least RLC entity #1; the RLC entity #1 is deactivated.

[0562] As an embodiment, the first signaling indicates the RLC entity subset #1 and the RLC entity subset #2.

[0563] As an embodiment, the first signaling activates the RLC entity subset #1 and the RLC entity subset #2.

[0564] As an embodiment, the first signaling indicates RLC entity #2, RLC entity #3 and RLC entity #4.

[0565] As an embodiment, the first signaling activates RLC entity #2, RLC entity #3 and RLC entity #4.

[0566] As an embodiment, this embodiment only illustrates an implementation method of operating the first PDCP PDU; this embodiment does not limit the number of RLC entities associated with the first PDCP in this application; this embodiment does not limit the number of the multiple RLC entity subsets in this application; this embodiment does not limit the number of RLC entities in each RLC entity subset in this application; this embodiment does not limit the target RLC entity subset in this application to be the RLC entity subset #2.

[0567] Example 11

[0568] Embodiment 11 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in FIG11. In FIG11, the processing device 1200 in the first node includes a first receiver 1101 and a first transmitter 1102.

[0569] A first receiver 1101 receives a first message, where the first message configures a first PDCP entity and multiple RLC entities, where the first PDCP entity is associated with the multiple RLC entities;

[0570] The first transmitter 1102 operates a first PDCP PDU.

[0571] In Example 11, the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

[0572] As an embodiment, the behavior operation of the first PDCP PDU includes: determining the target RLC entity subset among the multiple RLC entity subsets.

[0573] As an embodiment, the first receiver 1101 receives first signaling, which is signaling of the protocol layer below the RRC sublayer; wherein the first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set; the first candidate RLC entity set includes the multiple RLC entities; the first message configures each RLC entity in the first candidate RLC entity set, and the first PDCP entity is associated with each RLC entity in the candidate RLC entity set.

[0574] As an embodiment, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0575] As an embodiment, determining the target RLC entity subset among the multiple RLC entity subsets depends on a first threshold; and the first message configures the first threshold.

[0576] As an embodiment, accompanying the behavior operation of the first PDCP PDU, the sum of the first PDCP data volume and the first RLC data volume is not less than the first threshold, and the first PDCP data volume and the first RLC data volume are associated with the first PDCP entity.

[0577] As an embodiment, the first message configures multiple thresholds, and the first threshold is one of the multiple thresholds.

[0578] As an embodiment, the first receiver 1101 includes at least one of the antenna 452 or the receiver 454 or the multi-antenna receiving processor 458 or the receiving processor 456 or the controller / processor 459 or the memory 460 or the data source 467 in FIG. 4 of the present application.

[0579] As an embodiment, the first receiver 1101 includes at least the antenna 452 and the receiver 454 in FIG. 4 of the present application.

[0580] As an embodiment, the first transmitter 1102 includes at least one of the antenna 452 or transmitter 454 or multi-antenna transmission processor 457 or transmission processor 468 or controller / processor 459 or memory 460 or data source 467 in FIG. 4 of the present application.

[0581] As an embodiment, the first transmitter 1102 includes at least the antenna 452 and the transmitter 454 in FIG. 4 of the present application.

[0582] Example 12

[0583] Embodiment 12 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in FIG12. In FIG12, the processing device 1200 in the second node includes a second transmitter 1201 and a second receiver 1202.

[0584] The second transmitter 1201 sends a first message, where the first message configures a first PDCP entity and multiple RLC entities, where the first PDCP entity is associated with the multiple RLC entities;

[0585] The second receiver 1202 decodes the first PDCP PDU.

[0586] In Example 12, the first PDCP PDU is operated by the receiver of the first message; the operation of the first PDCP PDU by the receiver of the first message includes: the first PDCP PDU is copied and the first PDCP PDU is delivered to the RLC entity in the target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the first PDCP PDU is copied and depends on the target RLC entity subset including at least two RLC entities.

[0587] As an embodiment, the first PDCP PDU being operated by the receiver of the first message includes: the target RLC entity subset being determined among the multiple RLC entity subsets.

[0588] As an embodiment, the second transmitter 1201 sends a first signaling, which is a signaling of the protocol layer below the RRC sublayer; wherein the first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set; the first candidate RLC entity set includes the multiple RLC entities; the first message configures each RLC entity in the first candidate RLC entity set, and the first PDCP entity is associated with each RLC entity in the candidate RLC entity set.

[0589] As an embodiment, the target RLC entity subset is any RLC subset among the multiple RLC entity subsets.

[0590] As an embodiment, determining the target RLC entity subset among the multiple RLC entity subsets depends on a first threshold; and the first message configures the first threshold.

[0591] As an embodiment, as the first PDCP PDU is operated by the recipient of the first message, the sum of the first PDCP data volume and the first RLC data volume is not less than the first threshold, and the first PDCP data volume and the first RLC data volume are associated with the first PDCP entity.

[0592] As an embodiment, the first message configures multiple thresholds, and the first threshold is one of the multiple thresholds.

[0593] As an embodiment, the second transmitter 1201 includes at least one of the antenna 420 or the transmitter 418 or the multi-antenna transmission processor 471 or the transmission processor 416 or the controller / processor 475 or the memory 476 in FIG. 4 of the present application.

[0594] As an embodiment, the second transmitter 1201 includes at least the antenna 420 and the transmitter 418 in FIG. 4 of the present application.

[0595] As an embodiment, the second receiver 1202 includes at least one of the antenna 420 or the receiver 418 or the multi-antenna receiving processor 472 or the receiving processor 470 or the controller / processor 475 or the memory 476 in FIG. 4 of the present application.

[0596] As an embodiment, the second receiver 1202 includes at least the antenna 420 and the receiver 418 in FIG. 4 of the present application.

[0597] Example 13

[0598] Example 13 illustrates a schematic diagram of multiple thresholds being used to determine multiple RLC subsets according to an embodiment of the present application, as shown in Figure 13; the horizontal axis represents the data volume, and threshold #1, threshold #2 and threshold #3 are three data volume thresholds respectively; the threshold #1 is less than the threshold #2, and the threshold #2 is less than the threshold #3; the data volume corresponding to RLC entity subset #1 is less than threshold #1; the data volume corresponding to RLC entity subset #2 is greater than threshold #1 and less than threshold #2; the data volume corresponding to RLC entity subset #3 is greater than threshold #2 and less than threshold #3; the data volume corresponding to RLC entity subset #4 is greater than threshold #3.

[0599] In embodiment 13, the first message configures multiple thresholds, the first threshold is one of the multiple thresholds; the multiple thresholds are threshold #1, threshold #2 and threshold #3; the multiple RLC entity subsets are RLC entity subset #1, RLC entity subset #2, RLC entity subset #3 and RLC entity subset #4.

[0600] As an embodiment, when the data amount is less than threshold #1, the target RLC entity subset is RLC entity subset #1.

[0601] As an embodiment, when the data amount is greater than threshold #1 and less than threshold #2, the target RLC entity subset is RLC entity subset #2.

[0602] As an embodiment, when the data amount is greater than threshold #2 and less than threshold #3, the target RLC entity subset is RLC entity subset #3.

[0603] As an embodiment, when the data amount is greater than threshold #3, the target RLC entity subset is RLC entity subset #4.

[0604] As an embodiment, Example 13 is only used to illustrate that multiple thresholds are used to determine multiple RLC subsets, and does not limit the number of the multiple thresholds in this application, and does not limit the threshold in this application to a data volume threshold; for example, the horizontal axis can also be but not limited to a measurement result, and the threshold can also be but not limited to a measurement result threshold; the horizontal axis can also be but not limited to a quantity, and the threshold can also be but not limited to a quantity threshold.

[0605] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software functional module. This application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in this application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication) terminals, eMTC (enhanced MTC) terminals, data cards, internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR node B) NR node B, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0606] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first message, wherein the first message configures a first PDCP entity and a plurality of RLC entities, wherein the first PDCP entity is associated with the plurality of RLC entities; A first transmitter operates a first PDCP PDU; Among them, the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

2. The first node according to claim 1, characterized in that: The behavior of operating the first PDCP PDU includes: determining the target RLC entity subset among the multiple RLC entity subsets.

3. The first node according to claim 1 or 2, characterized in that: include: The first receiver receives first signaling, where the first signaling is signaling of a protocol layer below the RRC sublayer; Among them, the first signaling indicates at least one RLC entity subset among the multiple RLC entity subsets in the first candidate RLC entity set; the first candidate RLC entity set includes the multiple RLC entities; the first message configures each RLC entity in the first candidate RLC entity set, and the first PDCP entity is associated with each RLC entity in the candidate RLC entity set.

4. The first node according to any one of claims 1 to 3, characterized in that: The target RLC entity subset is any RLC entity subset among the multiple RLC entity subsets.

5. The first node according to any one of claims 1 to 4, characterized in that: Determining the target RLC entity subset among the multiple RLC entity subsets depends on a first threshold; and configuring the first threshold with the first message.

6. The first node according to claim 5, characterized in that: Accompanying the behavior operation of the first PDCP PDU, the sum of the first PDCP data volume and the first RLC data volume is not less than the first threshold, and the first PDCP data volume and the first RLC data volume are associated with the first PDCP entity.

7. The first node according to claim 5 or 6, characterized in that: The first message configures a plurality of thresholds, and the first threshold is one of the plurality of thresholds.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first message, wherein the first message configures a first PDCP entity and a plurality of RLC entities, wherein the first PDCP entity is associated with the plurality of RLC entities; A second receiver, decompressing the first PDCP PDU; Among them, the first PDCP PDU is operated by the receiver of the first message; the operation of the first PDCP PDU by the receiver of the first message includes: the first PDCP PDU is copied and the first PDCP PDU is delivered to the RLC entity in the target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the first PDCP PDU is copied and depends on the target RLC entity subset including at least two RLC entities.

9. A method in a first node for wireless communication, characterized in that: include: receiving a first message, the first message configuring a first PDCP entity and a plurality of RLC entities, the first PDCP entity being associated with the plurality of RLC entities; operating a first PDCP PDU; Among them, the behavior of operating the first PDCP PDU includes: copying the first PDCP PDU and delivering the first PDCP PDU to an RLC entity in a target RLC entity subset; the target RLC entity subset is an RLC subset among multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the behavior of copying the first PDCP PDU depends on the target RLC entity subset including at least two RLC entities.

10. A method in a second node for wireless communication, characterized in that: include: Sending a first message, wherein the first message configures a first PDCP entity and a plurality of RLC entities, wherein the first PDCP entity is associated with the plurality of RLC entities; De-operating a first PDCP PDU; Among them, the first PDCP PDU is operated by the receiver of the first message; the operation of the first PDCP PDU by the receiver of the first message includes: the first PDCP PDU is copied and the first PDCP PDU is delivered to the RLC entity in the target RLC entity subset; the target RLC entity subset is an RLC subset in multiple RLC entity subsets, and each RLC entity subset in the multiple RLC entity subsets includes at least one RLC entity among the multiple RLC entities; the multiple RLC entity subsets depend on at least the first message; the first PDCP PDU is copied and depends on the target RLC entity subset including at least two RLC entities.

Images