Method and device used in wireless communication

Abstract

The invention discloses a method and a device used in wireless communication. A first node receives a first signaling, the first signaling indicates to activate PDCP replication for a PDCP entity, and the PDCP entity is associated with a first RLC entity and a second RLC entity; a PDCP data PDU is submitted to at least one of the first RLC entity and the second RLC entity to be sent; wherein whether the PDCP data PDU is copied or not, and when the PDCP data PDU is not copied, whether the PDCP data PDU is submitted to the first RLC entity to be sent or the PDCP data PDU is submitted to the second RLC entity to be sent at least depends on a second signaling; the second signaling indicates that the SDU discard based on the PDU set importance is activated for a first radio bearer, and the first radio bearer is associated with the PDCP entity. According to the invention, the QoS and robustness of data transmission can be improved while air interface resources are effectively saved.

Description

Technical Field

[0001] The present application relates to a method and a device in a wireless communication system, and more particularly to a method and a device for PDCP (Packet Data Convergence Protocol) protocol layer transmission in wireless communication. Background Art

[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward different performance requirements for the system. In order to meet the different performance requirements of various application scenarios, the 3rd Generation Partner Project (3GPP) RAN

[0003] At the 3GPP RAN (Radio Access Network) plenary meeting #72, it was decided to study the new air interface technology (NR, New Radio) (or 5G). At the 3GPP RAN #75 plenary meeting, the WI (Work Item) of the new air interface technology (NR, New Radio) was passed, and the standardization work on NR began.

[0004] The PDCP sublayer is located between the RRC (Radio Resource Control) layer and the RLC (Radio Link Control) sublayer, or between the SDAP (Service Data Adaptation Protocol) layer and the RLC sublayer, and provides services such as user plane data transmission, control plane data transmission, header compression, encryption, and integrity protection.

[0005] Designing effective PDCP functions for services with different transmission requirements is an important research direction for future wireless communications. Summary of the invention

[0006] Through research, the inventors found that some new services (such as XR (eXtended Reality)) may include data packets with different importance in a QoS (Quality of Service) flow. How to enhance the existing PDCP protocol layer function to differentiate the processing of these data packets with different importance needs to be studied.

[0007] In response to the above problems, the present application discloses a solution that can reduce the risk of network congestion and improve system robustness while ensuring service QoS. In the absence of conflict, the embodiments and features in the embodiments of the first node of the present application can be applied to the second node, and vice versa. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other. Further, although the original intention of the present application is for the Uu air interface, the present application can also be used for the PC5 air interface. Further, although the original intention of the present application is for the terminal and base station scenario, the present application is also applicable to relays and base stations to achieve similar technical effects in terminal and base station scenarios. In addition, the use of a unified solution for different scenarios (including but not limited to V2X scenarios and communication scenarios between terminals and base stations) also helps to reduce hardware complexity and cost. In particular, the interpretation of terms (Terminology), nouns, functions, and variables in this application (if not otherwise specified) can refer to the definitions in the 3GPP specification protocols TS36 series, TS38 series, and TS37 series.

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

[0009] receiving a first signaling indicating activation of PDCP duplication for a PDCP entity, the PDCP entity being associated with a first RLC entity and a second RLC entity;

[0010] Delivering a PDCP data PDU (Protocol Data Unit) to at least one of the first RLC entity and the second RLC entity for transmission;

[0011] Among them, whether to copy the PDCP data PDU, and when the PDCP data PDU is not copied, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending depends on at least a second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for the first radio bearer, and the first radio bearer is associated with the PDCP entity.

[0012] As an embodiment, the present application is applicable to dual connectivity (DC) transmission.

[0013] As an embodiment, the present application is applicable to the transmission of the PDCP replication method.

[0014] As an embodiment, the second signaling implicitly indicates that the network is in a congested state.

[0015] As an embodiment, the second signaling instructs the first node to activate SDU discard based on PDU set importance for the first radio bearer, which can effectively alleviate network congestion.

[0016] As an embodiment, when PDCP replication is activated, the above method further determines whether to copy the PDCP data PDU based on the second signaling, and when it is determined not to copy the PDCP data PDU, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending can effectively reduce the risk of network congestion while ensuring service QoS.

[0017] As an embodiment, the above method is backward compatible, which helps to reduce hardware complexity and cost.

[0018] As an embodiment, the entity in the present application is a module.

[0019] As an embodiment, an entity in the present application is a module that completes a set of functions.

[0020] As an embodiment, the module is a hardware module.

[0021] As an embodiment, the module is a software module.

[0022] According to one aspect of the present application, the above method is characterized in that, when the second signaling is not received, the PDCP data PDU is copied and the PDCP data PDU is delivered to the first RLC entity and the second RLC entity for sending.

[0023] According to one aspect of the present application, the above method is characterized in that it includes:

[0024] Receiving the second signaling at a MAC entity;

[0025] Whether to copy the PDCP data PDU also depends on the PDCP SDU included in the PDCP data PDU.

[0026] As an embodiment, the second signaling indicates activation of PDCP discard based on PDU set importance for the first radio bearer.

[0027] As an embodiment, when the first node does not activate PDCP discard based on PDU set importance, the PDCP data PDU is copied.

[0028] According to one aspect of the present application, the above method is characterized in that, when the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, whether the PDCP data PDU is delivered to the first RLC entity for sending or to the second RLC entity for sending also depends on the MAC entity.

[0029] As an embodiment, the MAC entity is used to serve MCG (Master Cell group) or the MAC entity is used to serve SCG (Secondary Cell group); wherein the MCG includes at least one cell and the SCG includes at least one cell.

[0030] As an embodiment, the maintenance base station of the MCG is a MN (Master Node); the maintenance base station of the SCG is a SN (Secondary Node).

[0031] As an embodiment, the second signaling indicates that the CG (Cell group) served by the MAC entity receiving the second signaling is in a congested state.

[0032] As a sub-embodiment of the above embodiment, when the MAC entity is used to serve MCG, the second signaling indicates that the MCG is in a congested state.

[0033] As a sub-embodiment of the above embodiment, when the MAC entity is used to serve the SCG, the second signaling indicates that the SCG is in a congested state. As an embodiment, determining whether to send the SDU of the low importance PDU set in the first RLCs entity or the second RLC entity according to the MAC entity can effectively alleviate network congestion without causing a significant impact on the service.

[0034] According to one aspect of the present application, the above method is characterized in that when the MAC entity is associated with the first RLC entity, the PDCP data PDU is delivered to the second RLC entity for sending; when the MAC entity is associated with the second RLC entity, the PDCP data PDU is delivered to the first RLC entity for sending.

[0035] As an embodiment, the characteristic of the above method is that when the PDCP data PDU is not copied, to which RLC entity it is delivered depends on the MAC entity that receives the second signaling.

[0036] As an embodiment, the characteristic of the above method is that the first node does not transmit data to the CG that is in a congested state, but only transmits data to the CG that is not in a congested state.

[0037] As an embodiment, the above method can reduce the data transmission demand on a congested network.

[0038] As an embodiment, the above method has the advantage of being helpful in ensuring QoS.

[0039] According to one aspect of the present application, the above method is characterized in that it includes:

[0040] receiving, from the first RLC entity, a confirmation of successful transmission of the PDCP data PDU;

[0041] If the PDCP SDU included in the PDCP data PDU does not belong to the low importance PDU set, and the first RLC entity is not associated with a SRAP (Sidelink Relay Adaptation Protocol) entity, instruct the second RLC entity to discard the PDCP data PDU.

[0042] As an embodiment, the characteristic of the above method is that: when the PDCP data PDU is successfully sent in one RLC entity, the copy of the PDCP data PDU in another RLC entity is discarded; wherein the other RLC entity is not used for relay transmission.

[0043] As an embodiment, the above method has the advantage of reducing unnecessary air interface transmission.

[0044] According to one aspect of the present application, the above method is characterized in that the first RLC entity is applied to MCG and the second RLC entity is applied to SCG, or the first RLC entity is applied to SCG and the second RLC entity is applied to MCG.

[0045] As an embodiment, the characteristic of the above method is that the first RLC entity and the second RLC entity are both used for data transmission on a direct path.

[0046] As an embodiment, the characteristic of the above method is that neither the first RLC entity nor the second RLC entity is used for data transmission on an indirect path.

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

[0048] Sending a first signaling, where the first signaling indicates activation of PDCP replication for a PDCP entity, where the PDCP entity is associated with a first RLC entity and a second RLC entity;

[0049] In which, a PDCP data PDU is delivered to at least one of the first RLC entity and the second RLC entity for sending; whether the PDCP data PDU is copied, and when the PDCP data PDU is not copied, whether the PDCP data PDU is delivered to the first RLC entity for sending or to the second RLC entity for sending depends at least on a second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for a first radio bearer, and the first radio bearer is associated with the PDCP entity.

[0050] According to one aspect of the present application, the above method is characterized in that, when the second signaling is not received, the PDCP data PDU is copied and delivered to the first RLC entity and the second RLC entity for sending.

[0051] According to one aspect of the present application, the above method is characterized in that it includes:

[0052] sending the second signaling;

[0053] Whether the PDCP data PDU is copied also depends on the PDCP SDU included in the PDCP data PDU.

[0054] According to one aspect of the present application, the above method is characterized in that, when the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, whether the PDCP data PDU is delivered to the first RLC entity for sending or delivered to the second RLC entity for sending also depends on the MAC entity.

[0055] According to one aspect of the present application, the above method is characterized in that when the MAC entity is associated with the first RLC entity, the PDCP data PDU is delivered to the second RLC entity for sending; when the MAC entity is associated with the second RLC entity, the PDCP data PDU is delivered to the first RLC entity for sending.

[0056] According to one aspect of the present application, the above method is characterized in that it includes:

[0057] A confirmation of successful transmission of the PDCP data PDU is received from the first RLC entity;

[0058] If the PDCP SDU included in the PDCP data PDU does not belong to a low importance PDU set, and the first RLC entity is not associated with an SRAP entity, the second RLC entity is instructed to discard the PDCP data PDU.

[0059] According to one aspect of the present application, the above method is characterized in that the first RLC entity is applied to MCG and the second RLC entity is applied to SCG, or the first RLC entity is applied to SCG and the second RLC entity is applied to MCG.

[0060] The present application discloses a first node used for wireless communication, characterized in that it includes:

[0061] A first receiver receives a first signaling, wherein the first signaling indicates activation of PDCP replication for a PDCP entity, wherein the PDCP entity is associated with a first RLC entity and a second RLC entity;

[0062] A first transmitter delivers a PDCP data PDU to at least one of the first RLC entity and the second RLC entity for transmission;

[0063] Among them, whether to copy the PDCP data PDU, and when the PDCP data PDU is not copied, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending depends at least on the second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for the first radio bearer, and the first radio bearer is associated with the PDCP entity.

[0064] The present application discloses a second node used for wireless communication, characterized in that it includes:

[0065] A second transmitter sends a first signaling, wherein the first signaling indicates activation of PDCP replication for a PDCP entity, and the PDCP entity is associated with a first RLC entity and a second RLC entity;

[0066] In which, a PDCP data PDU is delivered to at least one of the first RLC entity and the second RLC entity for sending; whether the PDCP data PDU is copied, and when the PDCP data PDU is not copied, whether the PDCP data PDU is delivered to the first RLC entity for sending or to the second RLC entity for sending depends at least on a second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for a first radio bearer, and the first radio bearer is associated with the PDCP entity. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0068] Figure 1An example of a transmission flow chart of a first node according to an embodiment of the present application is provided;

[0069] Figure 2 A schematic diagram illustrating a network architecture according to an embodiment of the present application is illustrated;

[0070] Figure 3 A schematic diagram illustrating a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0071] Figure 4 A hardware module schematic diagram of a communication device according to an embodiment of the present application is illustrated;

[0072] Figure 5 A signal transmission flow chart according to an embodiment of the present application is illustrated;

[0073] Figure 6 Another signal transmission flow chart according to an embodiment of the present application is illustrated;

[0074] Figure 7 A flowchart illustrating the operation of a first node according to an embodiment of the present application;

[0075] Figure 8 A schematic diagram illustrating a first radio bearer according to an embodiment of the present application is illustrated;

[0076] Fig. 9 A third wireless signal transmission flow chart according to an embodiment of the present application is illustrated;

[0077] Fig.10 An example structural block diagram of a processing device in a first node according to an embodiment of the present application is shown;

[0078] Fig.11 The structural block diagram of the processing device in the second node according to an embodiment of the present application is illustrated. DETAILED DESCRIPTION

[0079] 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, in the absence of conflict, the embodiments of the present application and the features in the embodiments can be arbitrarily combined with each other.

[0080] Example 1

[0081] Embodiment 1 illustrates a transmission flow chart of a first node according to an embodiment of the present application, as shown in the attached Figure 1 shown.

[0082] In Example 1, the first node 100 receives a first signaling in step 101, wherein the first signaling indicates activation of PDCP replication for a PDCP entity, and the PDCP entity is associated with a first RLC entity and a second RLC entity; in step 102, a PDCP data PDU is delivered to at least one of the first RLC entity and the second RLC entity for transmission; wherein, whether to replicate the PDCP data PDU, and whether to deliver the PDCP data PDU to the first RLC entity for transmission or to the second RLC entity for transmission when the PDCP data PDU is not replicated, depends at least on a second signaling; the second signaling indicates activation of SDU discard based on PDU set importance for a first radio bearer, and the first radio bearer is associated with the PDCP entity.

[0083] As an embodiment, the first signaling is received via an air interface.

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

[0085] As an embodiment, the first signaling is a copy of an activation / deactivation (Activation / Deactivation) MAC CE.

[0086] As an embodiment, the first signaling is a copy of the RLC activation / deactivation MAC CE.

[0087] As an embodiment, the first signaling indication activates PDCP replication for the first radio bearer (Radio Bearer, RB).

[0088] As an embodiment, the first signaling consists of one octet.

[0089] As an embodiment, the first signaling implicitly indicates an identifier of the first radio bearer.

[0090] As an embodiment, the P1th bit from right to left in the eight-bit group constituting the first signaling indicates whether PDCP replication is activated for the first radio bearer; wherein, the P1 is the position of the first radio bearer in all radio bearers configured with PDCP replication in the first node and arranged in ascending order according to the radio bearer identifier.

[0091] As an embodiment, P1 is a positive integer.

[0092] As an embodiment, P1 is not greater than 8.

[0093] As an embodiment, at least P1 radio bearers in the first node are configured with PDCP replication.

[0094] As an embodiment, at least one of the RLC entities configured for each of the P1 radio bearers is associated with a MAC entity that receives the first signaling.

[0095] As an embodiment, the first radio bearer is one of the P1 radio bearers.

[0096] As an embodiment, the first radio bearer is configured with PDCP replication.

[0097] As an embodiment, at least one of the RLC entities configured in the first radio bearer is associated with a MAC entity that receives the first signaling.

[0098] As an embodiment, the radio bearer identifier is a DRB (Data Radio Bearer) ID (IDentifier).

[0099] As an embodiment, the value of the bit corresponding to the first radio bearer in the first signaling is 1, indicating that the first radio bearer activates PDCP replication.

[0100] As an embodiment, the value of the P1th bit from right to left in the first signaling is 1, indicating that the first radio bearer activates PDCP replication.

[0101] As an embodiment, the first signaling indicates activation of PDCP duplication for all secondary RLC entities associated with the PDCP entity.

[0102] As an embodiment, all secondary RLC entities associated with the PDCP entity include one of the first RLC entity and the second RLC entity.

[0103] As an embodiment, all the secondary RLC entities associated with the PDCP entity do not include the first RLC entity and the second RLC entity at the same time.

[0104] As an embodiment, the first signaling indicates activation of PDCP duplication for at least one RLC entity associated with the PDCP entity.

[0105] As an embodiment, the first signaling explicitly indicates an identifier of the first radio bearer.

[0106] As an embodiment, the first signaling includes an identifier of the first radio bearer and a Q bit, and the Q bit corresponds to the at least one RLC entity arranged in the order of MCG and SCG and in ascending order of logical channel identifiers.

[0107] As an embodiment, the identifier of the first radio bearer is a DRB ID, which has a length of 5 bits.

[0108] As an embodiment, the value of one of the Q bits is 1, indicating that one of the at least one RLC entities associated with the PDCP entity activates PDCP replication.

[0109] As an embodiment, the value of the bit in the Q bit corresponding to the first RLC entity is 1, indicating that the first RLC entity activates PDCP replication.

[0110] As an embodiment, the value of the bit in the Q bit corresponding to the second RLC entity is 1, indicating that the second RLC entity activates PDCP replication.

[0111] As an embodiment, the at least one RLC entity is a secondary RLC entity.

[0112] As an embodiment, the first RLC entity and the second RLC entity are a primary RLC entity and a secondary RLC entity, respectively.

[0113] As a sub-embodiment of the above embodiment, the first RLC entity is a primary RLC entity; and the second RLC entity is a secondary RLC entity.

[0114] As a sub-embodiment of the above embodiment, the first RLC entity is a secondary RLC entity; and the second RLC entity is a primary RLC entity.

[0115] As an embodiment, the at least one RLC entity includes the second RLC entity but does not include the first RLC entity.

[0116] As an embodiment, the at least one RLC entity includes the first RLC entity but does not include the second RLC entity.

[0117] As an embodiment, one RLC entity corresponds to one logical channel identifier.

[0118] As an embodiment, the value of Q is 3; the PDCP entity is associated with 3 auxiliary RLC entities.

[0119] Specifically, the PDCP entity is associated with three secondary RLC entities as an example. Among the three secondary RLC entities, RLC entity #1 belongs to MCG, and RLC entity #2 and RLC entity #3 belong to SCG; wherein the logical channel identifiers of RLC entity #1, RLC entity #2 and RLC entity #3 are 8, 15 and 10 respectively; the first signaling includes 3 bits, which correspond to RLC entity #1, RLC entity #3 and RLC entity #2 from right to left respectively.

[0120] As an embodiment, in the prior art, when the PDCP entity is activated for PDCP replication, the PDCP data PDU is delivered to both the first RLC entity and the second RLC entity for sending. The present application is creative in determining whether to deliver the PDCP data PDU to the first RLC entity or to the second RLC entity for sending based on the second signaling.

[0121] As an embodiment, the second signaling is MAC CE.

[0122] As an embodiment, the second signaling is a PSI (PDU Set Importance)-based SDU (Service Data Unit) discard activation (PSI-based SDU DiscardActivation) MAC CE.

[0123] As an embodiment, the second signaling indication activates SDU discard based on PDU set importance for the first radio bearer.

[0124] As an embodiment, the second signaling consists of one octet.

[0125] As an embodiment, the second signaling implicitly indicates the identifier of the first radio bearer.

[0126] As an embodiment, the P2th bit from right to left in the eight-bit group constituting the second signaling indicates whether the first radio bearer activates SDU discard based on PDU set importance; wherein, the P2 is the position of the first radio bearer in all radio bearers arranged in ascending order according to the radio bearer identifier and configured with discardTimerForLowImportance (discard timer of low importance) in the first node.

[0127] As an embodiment, P2 is a positive integer.

[0128] As an embodiment, P2 is not greater than 8.

[0129] As an embodiment, the values ​​of P1 and P2 are the same.

[0130] As an embodiment, the values ​​of P1 and P2 are different.

[0131] As an embodiment, at least P2 radio bearers in the first node are configured with discardTimerForLowImportance.

[0132] As an embodiment, at least one of the RLC entities configured for each of the P2 radio bearers is associated with the MAC entity that receives the second signaling.

[0133] As an embodiment, the first radio bearer is one of the P2 radio bearers.

[0134] As an embodiment, the first radio bearer is configured with discardTimerForLowImportance.

[0135] As an embodiment, at least one of the RLC entities configured in the first radio bearer is associated with the MAC entity receiving the second signaling.

[0136] As an embodiment, the value of the bit corresponding to the first radio bearer in the second signaling is 1, indicating that the first radio bearer activates SDU discard based on PDU set importance.

[0137] As an embodiment, the value of the P2th bit from right to left in the first signaling is 1, indicating that the first radio bearer activates SDU discard based on PDU set importance.

[0138] As an embodiment, whether to copy the PDCP data PDU, and whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending when the PDCP data PDU is not copied, is at least related to the second signaling.

[0139] As an embodiment, whether to copy the PDCP data PDU is determined at least based on whether the second signaling has been received, and when the PDCP data PDU is not copied, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending.

[0140] As an embodiment, when the first node receives the second signaling, whether to copy the PDCP data PDU is at least related to the PDCP SDU included in the PDCP data PDU.

[0141] As an embodiment, when the second signaling is received, it is determined whether to copy the PDCP data PDU at least based on whether the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, and when the PDCP data PDU is not copied, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending.

[0142] As an embodiment, the PDCP entity confirms copying the PDCP data PDU based on at least the former of whether the second signaling is received and whether the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set.

[0143] As an embodiment, the PDCP entity confirms not to copy the PDCP data PDU based on having received the second signaling and the PDCP SDU included in the PDCP data PDU not belonging to a low importance PDU set.

[0144] As an embodiment, when it is determined not to copy the PDCP data PDU, it is determined whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending at least based on the MAC entity that receives the second signaling.

[0145] As an embodiment, the low-importance PDU set is a PDU set with lower importance than other PDU sets in the same QoS flow.

[0146] As an embodiment, the first node determines the relative importance of a PDU set compared to other PDU sets in the same QoS flow based on the PSI.

[0147] As an embodiment, how to identify a PDU set as a low-importance PDCP set depends on the implementation of the UE.

[0148] As an embodiment, the low importance PDU set is indicated by an upper layer, and the upper layer refers to a transport layer.

[0149] As an embodiment, the low importance PDU set is indicated by an upper layer through a PSI field.

[0150] As an embodiment, the first node indicates the importance of the PDU set to which the PDCP SDU included in the PDCP data PDU belongs through the PSI field based on RTP (Real-time Transmission Protocol).

[0151] As an embodiment, the PSI field consists of 4 bits; the valid value of the PSI field is an integer between 1 and 15.

[0152] As an embodiment, the smaller the value of the PSI field is, the higher the importance of the PDU set is.

[0153] As an embodiment, the value of the PSI field is related to the service type associated with the PDCP SDU included in the PDCP data PDU.

[0154] As an embodiment, when the PDCP data PDU is not copied, whether the PDCP data PDU is delivered to the first RLC entity for sending or to the second RLC entity for sending is at least related to the MAC entity.

[0155] As an embodiment, when the PDCP data PDU is not copied, whether the PDCP data PDU is delivered to the first RLC entity for transmission or to the second RLC entity for transmission depends on whether the MAC entity is associated with the second RLC entity or the first MAC entity.

[0156] As an embodiment, the first radio bearer is a DRB.

[0157] As an embodiment, the first radio bearer is a SRB (Signaling Radio Bearer).

[0158] As an embodiment, the first radio bearer is MRB (MBS (Multicast / Broadcast Services) Radio Bearer, multicast broadcast service radio bearer).

[0159] As an embodiment, the first radio bearer is a split bearer.

[0160] As an embodiment, the first radio bearer being associated with the PDCP entity includes: the PDCP entity being used for the first radio bearer.

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

[0162] As an embodiment, the PDCP entity is used to send data of the first radio bearer.

[0163] As an embodiment, the PDCP entity activates PDCP replication for the first wireless bearer.

[0164] As an embodiment, the PDCP entity is located in the PDCP sublayer.

[0165] As an embodiment, the first radio bearer is mapped to logical channels of the types DCCH (Dedicated Control Channel), DTCH (Dedicated Traffic Channel), MTCH (MBSTraffic Channel), SCCH (Sidelink Control Channel) and STCH (Sidelink Traffic Channel).

[0166] Example 2

[0167] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 shown. Figure 2A diagram of a network architecture 200 for NR 5G, LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) systems is illustrated. The NR 5G, LTE or LTE-A network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 may include one or more UEs (User Equipment) 201, NG-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220 and Internet Services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet switching services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit switching services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., a backhaul link). The XnAP protocol of the Xn interface is used to transmit control plane messages of the wireless network, and the user plane protocol of the Xn interface is used to transmit user plane data. gNB 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (Transmission Reception Point, a sending and receiving node) or some other suitable term. In a NTN (NonTerrestrialNetwork, a non-terrestrial / satellite network) network, gNB 203 may be a satellite, an aircraft, or a ground base station relayed by a satellite. gNB203 provides an access point to 5GC / EPC210 for UE201.Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, vehicle-mounted devices, vehicle-mounted communication units, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term. gNB203 is connected to 5GC / EPC210 via the S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, 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 service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and PS (Packet Switching) streaming services.

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

[0169] As an embodiment, the gNB203 corresponds to the second node in this application.

[0170] As an embodiment, the UE201 is a user equipment.

[0171] As an embodiment, the gNB203 is a macro cell base station.

[0172] As an embodiment, the gNB203 is a micro cell base station.

[0173] As an embodiment, the gNB203 is a pico cell base station.

[0174] As an embodiment, the gNB203 is a home base station (Femtocell).

[0175] As an embodiment, the gNB203 is a base station device that supports large delay difference.

[0176] As an embodiment, the gNB203 is a flying platform device.

[0177] As an embodiment, the gNB203 is a satellite device.

[0178] As an embodiment, the gNB203 is a base station device that supports large delay difference.

[0179] As an embodiment, the gNB203 is a testing device (e.g., a transceiver that simulates some functions of a base station, a signaling tester).

[0180] As an embodiment, the wireless link from the UE201 to the gNB203 is an uplink, and the uplink is used to perform uplink transmission.

[0181] As an embodiment, the wireless link from the UE241 to the gNB203 is an uplink, and the uplink is used to perform uplink transmission.

[0182] As an embodiment, the wireless link from the gNB203 to the UE201 is a downlink, and the downlink is used to perform downlink transmission.

[0183] As an embodiment, the wireless link from the gNB203 to the UE241 is a downlink, and the downlink is used to perform downlink transmission.

[0184] As an embodiment, the UE201 and the gNB203 are connected via a Uu air interface.

[0185] As an embodiment, the UE241 and the gNB203 are connected via a Uu air interface.

[0186] As an embodiment, the UE201 and the UE241 are connected via a PC5 air interface.

[0187] Example 3

[0188] Embodiment 3 illustrates a schematic diagram of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application, as shown in the attached figure. Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture of the control plane 300 of the UE and gNB is shown in 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 as PHY 301 in this article. Layer 2 (L2 layer) 305 is above PHY 301 and is responsible for the link between the UE and the gNB through PHY 301. The L2 layer 305 includes the MAC (Medium Access Control) sublayer 302, the RLC (Radio Link Control) sublayer 303, and the PDCP (Packet Data Convergence Protocol) sublayer 304, which terminate at the gNB on the network side. The PDCP sublayer 304 provides data encryption and integrity protection. The PDCP sublayer 304 also provides support for inter-zone mobility of UEs between gNBs. The RLC sublayer 303 provides segmentation and reassembly of data packets, and retransmits lost data packets through ARQ (Automatic Repeat Request). The RLC sublayer 303 also provides duplicate data packet detection and protocol error detection. The MAC sublayer 302 provides mapping between logical channels and transport channels and multiplexing of logical channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell between UEs. The MAC sublayer 302 is also responsible for HARQ (Hybrid Automatic Repeat Request) operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling between the gNB and the UE. The wireless protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). The wireless protocol architecture in the user plane 350 is substantially the same as the corresponding layers and sublayers in the control plane 300 for 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, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce wireless transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping between QoS flows and data radio bearers to support the diversity of services.The wireless protocol architecture of the UE in the user plane 350 may include, at the L2 layer, a SDAP sublayer 356, a PDCP sublayer 354, a portion of or all of the protocol sublayers of the RLC sublayer 353 and the MAC sublayer 352. Although not shown, the UE may also have several upper layers above the L2 layer 355, including a network layer (e.g., an IP layer) terminated at the P-GW on the network side and an application layer terminated at the other end of the connection (e.g., a remote UE, a server, etc.).

[0189] As an embodiment, the PDCP 304 sends data to the RLC 303 or receives data from the RLC 303 through an RLC channel.

[0190] As an embodiment, the PDCP354 sends data to the RLC353 or receives data from the RLC353 through the RLC channel.

[0191] As an embodiment, the RLC 303 sends data to the MAC 302 or receives data from the MAC 302 through a logical channel.

[0192] As an embodiment, the RLC353 sends data to the MAC352 or receives data from the MAC352 through a logical channel.

[0193] As an embodiment, the MAC 302 sends data to the PHY 301 or receives data from the PHY 301 through a transmission channel.

[0194] As an embodiment, the MAC 352 sends data to the PHY 351 or receives data from the PHY 351 through a transmission channel.

[0195] As an embodiment, the first receiver is used for data transmission from a bottom layer to an upper layer.

[0196] As an embodiment, the first transmitter is used for data transmission from an upper layer to a lower layer.

[0197] As a sub-embodiment of the above two embodiments, the upper layer and the bottom layer are adjacent layers.

[0198] As an embodiment, the first receiver is used by the PDCP 304 to receive from the RLC 303 .

[0199] As an embodiment, the first receiver is used by the PDCP354 to receive from the RLC353.

[0200] As an embodiment, the first receiver is used by the RLC303 to receive from the PDCP304.

[0201] As an embodiment, the first receiver is used by the RLC353 to receive from the PDCP354.

[0202] As an embodiment, the first receiver includes an inter-layer reception primitive.

[0203] As an embodiment, the first receiver includes a set of instructions for completing a receiving function.

[0204] As an embodiment, the first transmitter is used by the PDCP304 to send to the RLC303.

[0205] As an embodiment, the first transmitter is used by the PDCP354 to send to the RLC353.

[0206] As an embodiment, the first transmitter is used by the RLC303 to send to the PDCP304.

[0207] As an embodiment, the first transmitter is used by the RLC353 to send to the PDCP354.

[0208] As an embodiment, the first transmitter includes an inter-layer transmission primitive.

[0209] As an embodiment, the first transmitter includes a set of instructions for completing a sending function.

[0210] As an example, Figure 3 The entities of multiple sublayers of the control plane form SRB in the vertical direction.

[0211] As an example, Figure 3 The entities of multiple sublayers of the user plane in the vertical direction form a DRB.

[0212] As an example, Figure 3 The entities of multiple sublayers of the user plane in the vertical direction form an MRB.

[0213] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0214] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.

[0215] As an embodiment, the first signaling in the present application is generated by the MAC302.

[0216] As an embodiment, the second signaling in the present application is generated by the MAC302.

[0217] As an embodiment, the PDCP data PDU in the present application is generated in the PDCP354.

[0218] As an embodiment, a copy of the PDCP data PDU in the present application is generated in the PDCP354.

[0219] As an embodiment, when the PDCP data PDU is generated in the PDCP354, the PDCP entity is located in the PDCP354, the first RLC entity and the second RLC entity are located in the RLC353, and the MAC entity is located in the MAC352.

[0220] As an embodiment, the data packet on the interface between the PDCP sublayer and the RLC sublayer is called PDCP PDU in the PDCP sublayer and is called RLC SDU in the RLC sublayer, that is, the PDCP sublayer transfers the PDCP PDU to the RLC sublayer, and the RLC sublayer receives the RLC SDU from the PDCP sublayer; the RLC sublayer transfers the RLC SDU to the PDCP sublayer, and the PDCP sublayer receives the PDCP PDU from the RLC sublayer.

[0221] As an embodiment, PDCP PDU and RLC SDU are equivalent.

[0222] As an embodiment, the L2 layer 305 or 355 belongs to a higher layer.

[0223] As an embodiment, the RRC sublayer 306 in the L3 layer belongs to a higher layer.

[0224] Example 4

[0225] Embodiment 4 illustrates a hardware module schematic diagram of a communication device according to an embodiment of the present application, as shown in the attached Figure 4 shown. 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.

[0226] 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.

[0227] The second communication device 410 includes a controller / processor 475, a memory 476, a data source 477, 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.

[0228] In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, the upper layer data packets from the core network or the upper layer data packets from the data source 477 are provided to the controller / processor 475. The core network and the data source 477 represent all the protocol layers above the L2 layer. The controller / processor 475 implements the functionality of the L2 layer. In the 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 the 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 FEC (forward error correction) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., BPSK (binary phase shift keying), QPSK (quadrature phase shift keying), M-PSK (M phase shift keying), M-QAM (M quadrature amplitude modulation)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing 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 domain and / or frequency domain, and then uses IFFT (inverse fast Fourier transform) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier 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.

[0229] In the 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 through 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 and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses FFT (Fast Fourier Transform) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream with the first communication device 450 as the destination. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving 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 codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover higher layer data packets from the second communication device 410. 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 for L3 processing.

[0230] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, the upper layer data packets are provided to the controller / processor 459 using the data source 467. The data source 467 represents all the protocol layers above the L2 layer. Similar to the transmission function 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, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0231] In the transmission from the first communication device 450 to the second communication device 410, the functions at the second communication device 410 are similar to the reception functions at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 that stores program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the first communication device 450. The upper layer data packets from the controller / processor 475 may be provided to the core network or all protocol layers above the L2 layer, and various control signals may also be provided to the core network or L3 for L3 processing.

[0232] As an embodiment, the first communication device 450 apparatus 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 apparatus at least: receives a first signaling, the first signaling indicates activation of PDCP replication for a PDCP entity, the PDCP entity is associated with a first RLC entity and a second RLC entity; delivers a PDCP data PDU to at least one of the first RLC entity and the second RLC entity for transmission; wherein whether to replicate the PDCP data PDU, and whether to deliver the PDCP data PDU to the first RLC entity for transmission or to the second RLC entity for transmission when the PDCP data PDU is not replicated depends at least on a second signaling; the second signaling indicates activation of SDU discard based on PDU set importance for a first wireless bearer, and the first wireless bearer is associated with the PDCP entity.

[0233] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: receiving a first signaling; delivering a PDCP data PDU to at least one of the first RLC entity and the second RLC entity for sending.

[0234] As an embodiment, the second communication device 410 device 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 device at least: sends a first signaling, the first signaling indicates activation of PDCP duplication for a PDCP entity, the PDCP entity is associated with a first RLC entity and a second RLC entity; wherein, a PDCP data PDU is delivered to at least one of the first RLC entity and the second RLC entity for delivery; whether the PDCP data PDU is duplicated, and when the PDCP data PDU is not duplicated, whether the PDCP data PDU is delivered to the first RLC entity for delivery or delivered to the second RLC entity for delivery depends at least on the second signaling; the second signaling indicates activation of SDU discard based on PDU set importance for a first radio bearer, the first radio bearer is associated with the PDCP entity.

[0235] As an embodiment, the second communication device 410 device includes: at least one processor and at least one memory, the at least one memory includes computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The second communication device 410 device at least: sends a first signaling.

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

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

[0238] As an embodiment, the first communication device 450 is a UE.

[0239] As an embodiment, the first communication device 450 is a layer 3 relay node.

[0240] As an embodiment, the first communication device 450 is a RSU (Road Side Unit).

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

[0242] As an embodiment, the second communication device 410 is a distribution unit of a base station.

[0243] As an embodiment, the second communication device 410 is a piece of code in a distributed unit of a base station.

[0244] As an embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456 or the controller / processor 459 is used to receive the first signaling in the present application.

[0245] As an embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller / processor 475 is used to transmit the first signaling in the present application.

[0246] As an embodiment, at least one of the antenna 452, the receiver 454, the multi-antenna receiving processor 458, the receiving processor 456 or the controller / processor 459 is used to receive the second signaling in the present application.

[0247] As an embodiment, at least one of the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416 or the controller / processor 475 is used to transmit the second signaling in the present application.

[0248] As an embodiment, at least one of the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468 or the controller / processor 459 is used to send the PDCP data PDU in the present application.

[0249] Example 5

[0250] Embodiment 5 illustrates a signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 As shown in the attached Figure 5 In the present application, the PDCP entity E51, the first RLC entity E52 and the second RLC entity E53 are all located at the first node, the PDCP entity E51 and the first RLC entity E52 communicate through an inter-layer interface, and the PDCP entity E51 and the second RLC entity E53 communicate through an inter-layer interface.

[0251] for PDCP entity E51 In step S511, the PDCP data PDU is copied and delivered to both the first RLC entity and the second RLC entity for transmission.

[0252] for First RLC entity E52 , in step S521, receive PDCP data PDU.

[0253] for Second RLC entity E53 , in step S531, receive PDCP data PDU.

[0254] In Example 5, the first node receives a first signaling, the first signaling indicating activation of PDCP replication for a PDCP entity, the PDCP entity being associated with a first RLC entity and a second RLC entity; delivering a PDCP data PDU to at least one of the first RLC entity and the second RLC entity for transmission; wherein, whether to replicate the PDCP data PDU, and when the PDCP data PDU is not replicated, whether to deliver the PDCP data PDU to the first RLC entity for transmission or to the second RLC entity for transmission depends at least on a second signaling; the second signaling indicating activation of SDU discard based on PDU set importance for a first wireless bearer, the first wireless bearer being associated with the PDCP entity; when the second signaling is not received, replicating the PDCP data PDU, and delivering the PDCP data PDU to the first RLC entity and the second RLC entity for transmission; receiving the second signaling at a MAC entity; wherein, whether to replicate the PDCP data PDU also depends on the PDCP SDU included in the PDCP data PDU.

[0255] As an embodiment, the second node sends the first signaling, and the first node receives the first signaling before step S511.

[0256] As an embodiment, the first RLC entity is a master RLC entity, and the first signaling indicates activation of PDCP replication of the second RLC entity.

[0257] As an embodiment, the second RLC entity is a master RLC entity, and the first signaling indicates activation of PDCP replication of the first RLC entity.

[0258] As an embodiment, the PDCP entity receives an indication of activating PDCP replication from a lower layer before receiving the PDCP SDU included in the PDCP data PDU delivered by an upper layer; wherein the upper layer is an SDAP layer and the lower layer is a MAC layer.

[0259] As an embodiment, the indication for activating PDCP replication is an inter-layer indication.

[0260] As an embodiment, the first receiver is used to receive the PDCP data PDU delivered by an upper layer.

[0261] As an embodiment, the first transmitter is used to send the indication of activating PDCP duplication, and the first receiver is used to receive the indication of activating PDCP duplication.

[0262] As an embodiment, the first node does not receive the second signaling before step S511.

[0263] As an embodiment, when the first node does not receive the second signaling, the PDCP entity copies the PDCP data PDU regardless of whether the PDCP SDU included in the PDCP data PDU belongs to the low importance PDU set.

[0264] As an embodiment, the PDCP entity delivers the copied PDCP data PDU to both the first RLC entity and the second RLC entity for transmission.

[0265] As an embodiment, the second node sends the second signaling, and the first node receives the second signaling before step S511.

[0266] As an embodiment, the first node receives the second signaling via an air interface.

[0267] As an embodiment, the PDCP entity receives an indication from a lower layer to activate PSI-based SDU discard before receiving the PDCP SDU included in the PDCP data PDU delivered by an upper layer; wherein the upper layer is an SDAP layer and the lower layer is a MAC layer.

[0268] As an embodiment, the indication for activating PSI-based SDU discard is an inter-layer indication.

[0269] As an embodiment, the first transmitter is used to send the indication of activating PSI-based SDU discard, and the first receiver is used to receive the indication of activating PSI-based SDU discard.

[0270] As an embodiment, the PDCP SDU included in the PDCP data PDU does not belong to the low-importance PDUset, and the PDCP entity copies the PDCP data SDU.

[0271] As an embodiment, the first node receives the second signaling, and the PDCP SDU does not belong to the low-importance PDU set, and the PDCP entity copies the PDCP data SDU.

[0272] As an embodiment, the PDCP entity delivers the copied PDCP data SDU to the first RLC entity and the second RLC entity respectively for transmission.

[0273] As an embodiment, the first transmitter is used by the PDCP entity to send the copied PDCP data SDU to the first RLC entity and the second RLC entity.

[0274] Embodiment 5 is applicable to the sending of all PDCP data PDUs when the second signaling is not received.

[0275] Embodiment 5 is applicable to sending a PDU that does not belong to a low importance PDU set after receiving the second signaling.

[0276] Example 6

[0277] Embodiment 6 illustrates another signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 6 As shown in the attached Figure 6 In (a) and (b), the PDCP entity E61, the first RLC entity E62 and the second RLC entity E63 are all located at the first node in the present application, the PDCP entity E61 and the first RLC entity E62 communicate through an inter-layer interface, and the PDCP entity E61 and the second RLC entity E63 communicate through an inter-layer interface.

[0278] In the attached Figure 6 (a),

[0279] for PDCP entity E61a , in step S611a, the PDCP data PDU is delivered to the first RLC entity for transmission.

[0280] for First RLC entity E62 , in step S621, receive PDCP data PDU.

[0281] Or, in the attached Figure 6 (b),

[0282] for PDCP entity E61b , in step 611b, the PDCP data PDU is delivered to the second RLC entity for transmission.

[0283] for Second RLC entity E63 , in step S631, receive PDCP data PDU.

[0284] Embodiment 6 is applicable to sending a PDU belonging to a low importance PDU set after receiving the second signaling.

[0285] As an embodiment, when the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, whether the PDCP data PDU is delivered to the first RLC entity for sending or to the second RLC entity for sending also depends on the MAC entity; when the MAC entity is associated with the first RLC entity, the PDCP data PDU is delivered to the second RLC entity for sending; when the MAC entity is associated with the second RLC entity, the PDCP data PDU is delivered to the first RLC entity for sending.

[0286] As an embodiment, the second node sends the first signaling and the second signaling, and the first node receives the first signaling and the second signaling before step S611a.

[0287] As an embodiment, the second node sends the first signaling and the second signaling, and the first node receives the first signaling and the second signaling before step S611b.

[0288] As an embodiment, the PDCP SDU included in the PDCP data PDU belongs to a low-importance PDU set, and the PDCP entity does not copy the PDCP data PDU.

[0289] As an embodiment, a MAC entity receiving the second signaling determines whether to deliver the PDCP data PDU to the first RLC entity for transmission or to deliver it to the second RLC entity for transmission.

[0290] As an embodiment, the MAC entity receiving the second signaling associates with the second RLC entity, and the PDCP entity delivers the PDCP data PDU to the first RLC entity for transmission, as shown in the attached Figure 6 (a) shown.

[0291] As an embodiment, the MAC entity receiving the second signaling associates with the first RLC entity, and the PDCP entity delivers the PDCP data PDU to the second RLC entity for transmission, as shown in the attached Figure 6 (b) as shown.

[0292] Example 7

[0293] Embodiment 7 illustrates a flowchart of the operation of the first node according to an embodiment of the present application, as shown in the attached Figure 7 As shown in the attached Figure 7 In the example, the first node N71 is the first node in this application.

[0294] for First node N71, in step S711, receiving a first signaling;

[0295] In step S712, determining whether the second signaling is received;

[0296] If the second signaling is received in step S712, then in step S713, it is determined whether the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set;

[0297] If the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set in step S713, then determining in step S714 whether the MAC entity receiving the second signaling is associated with a second RLC entity;

[0298] If the MAC entity receiving the second signaling in step S714 is associated with the second RLC entity, then in step S716 the PDCP entity delivers the PDCP data PDU to the first RLC entity for transmission;

[0299] If the MAC entity receiving the second signaling is not associated with the second RLC entity in step S714, determining in step S715 whether the MAC entity receiving the second signaling is associated with the first RLC entity;

[0300] If the MAC entity receiving the second signaling in step S715 is associated with the first RLC entity, then in step S717 the PDCP entity delivers the PDCP data PDU to the second RLC entity for transmission;

[0301] Otherwise (the second signaling is not received in step S712, or the PDCP SDU included in the PDCP data PDU in step S713 does not belong to the low importance PDU set, or the MAC entity receiving the second signaling in step S715 is not associated with the first RLC entity), then in step S718 the PDCP entity copies the PDCP data PDU and delivers the PDCP data PDU to both the first RLC entity and the second RLC entity for sending.

[0302] As an embodiment, PDCP duplication is activated for one of the first RLC entity and the second RLC entity.

[0303] As an embodiment, the first node does not receive the second signaling, and the PDCP entity copies the PDCP data PDU.

[0304] As an embodiment, when the first node receives the second signaling, whether the PDCP entity copies the PDCP data PDU depends on whether the PDCP SDU included in the PDCP data PDU belongs to a low importance PDUset.

[0305] As an embodiment, when the first node receives the second signaling and the PDCP data PDU belongs to a low importance PDU set, the PDCP entity copies the PDCP data PDU.

[0306] As an embodiment, when the PDCP entity copies the PDCP data PDU, the PDCP entity delivers the copied PDCP data PDU to both the first RLC entity and the second RLC entity for transmission.

[0307] As an embodiment, when the first node receives the second signaling and the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, the PDCP entity does not copy the PDCP data PDU.

[0308] As an embodiment, when the PDCP entity does not copy the PDCP data PDU, the PDCP data PDU is delivered to one of the first RLC entity and the second RLC entity for transmission.

[0309] As a sub-embodiment of the above embodiment, when the MAC entity receiving the second signaling is associated with the second RLC entity, the PDCP data PDU is delivered to the first RLC entity for transmission.

[0310] As a sub-embodiment of the above embodiment, when the MAC entity receiving the second signaling is associated with the first RLC entity, the PDCP data PDU is delivered to the second RLC entity for transmission.

[0311] As an embodiment, when PDCP duplication and PSI-based SDU discard are activated simultaneously, the above method is beneficial to improving the robustness of low-importance PDCP data PDU delivery.

[0312] Example 8

[0313] Embodiment 8 illustrates a schematic diagram of a first radio bearer according to an embodiment of the present application, as shown in the attached figure. Figure 8 shown.

[0314] In the attached Figure 8In the embodiment, the SDAP entity, the PDCP entity, the first RLC entity, the second RLC entity, the first MAC entity and the second MAC entity are all located at the first node, the SDAP entity and the PDCP entity communicate through an inter-layer interface, the PDCP entity and the first RLC entity communicate through an inter-layer interface, the PDCP entity and the second RLC entity communicate through an inter-layer interface, the first RLC entity and the first MAC entity communicate through an inter-layer interface, and the second RLC entity and the second MAC entity communicate through an inter-layer interface.

[0315] As an example, Figure 8 Applicable to DRB.

[0316] As an example, Figure 8 Applicable to MRB.

[0317] As an example, Figure 8 The protocol structure shown is for the first radio bearer.

[0318] As an embodiment, the first radio bearer is an uplink radio bearer.

[0319] As an embodiment, the first radio bearer is a split DRB, namely, split DRB.

[0320] As an embodiment, the first radio bearer is a split DRB, namely, split MRB (MBS radiobearer).

[0321] As an example, Figure 8 Suitable for sending and receiving.

[0322] As an example, Figure 8 It is for DRB or MRB.

[0323] As an embodiment, the PDCP entity is configured with PDCP replication, the PDCP entity is associated with the first RLC entity, and the PDCP entity is associated with the second RLC entity.

[0324] As an embodiment, the phrase "the PDCP entity is associated with the first RLC entity" includes: the bearer served by the first RLC entity is the first radio bearer, and the PDCP entity is used for the first radio bearer.

[0325] As an embodiment, the phrase that the PDCP entity is associated with the first RLC entity includes: the first RLC entity is used to transmit data from the PDCP entity.

[0326] As an embodiment, the phrase associating the PDCP entity with the second RLC entity includes: the bearer served by the second RLC entity is the first radio bearer, and the PDCP entity is used for the first radio bearer.

[0327] As an embodiment, the phrase that the PDCP entity is associated with the second RLC entity includes: the second RLC entity is used to transmit data from the PDCP entity. As an embodiment, the PDCP entity is configured with PDCP replication includes: data sent through the PDCP entity is replicated and distributed to at least the first RLC entity and the second RLC entity for transmission.

[0328] As an embodiment, the PDCP entity is configured with PDCP replication including: replicating the PDCP data PDU at the PDCP entity and distributing the PDCP data PDU to at least the first RLC entity and the second RLC entity for transmission.

[0329] As an embodiment, a data packet received from the SDAP protocol entity is processed by the PDCP entity to form a PDCP PDU, which is copied and sent simultaneously through the first RLC entity and the second RLC entity.

[0330] As an embodiment, the first RLC entity and the second RLC entity are both for uplink communication.

[0331] As an embodiment, the first RLC entity is used to serve the MCG and the second RLC entity is used to serve the SCG.

[0332] As an embodiment, the first RLC entity is used to serve the SCG and the second RLC entity is used to serve the MCG.

[0333] As an embodiment, the first RLC entity is a primary RLC entity, and the second RLC entity is a split secondary RLC entity.

[0334] As an embodiment, the first RLC entity is a split secondary RLC entity, and the second RLC entity is a primary RLC entity.

[0335] As an embodiment, the primary RLC entity is used for data transmission on a primary path in the DC; and the at least one split secondary RLC entity is used for data transmission on a path other than the primary path.

[0336] As an embodiment, both the primary RLC entity and the at least one split secondary RLC entity are used for data transmission on the Uu air interface.

[0337] As an embodiment, the primary RLC entity and the at least one split secondary RLC entity are both used for data transmission on the data plane.As an embodiment, the primary RLC entity is configurable.

[0338] As an embodiment, the main RLC entity is associated with a CG.

[0339] As an embodiment, the cell group is one of a primary cell group or a secondary cell group.

[0340] As an embodiment, data belonging to the first radio bearer is sent through at least two connections, and each of the at least two connections is sent through the first RLC entity or the second RLC entity.

[0341] As an embodiment, the at least 2 connections include MCG.

[0342] As an embodiment, the at least two connections include MCG and SCG.

[0343] As an embodiment, the direct connection path refers to data being transmitted from an original node to a destination receiver through only one air interface.

[0344] As an embodiment, the non-direct path refers to data being transmitted from an original node to a destination receiver through at least two air interfaces.

[0345] As an embodiment, the at least two air interfaces include a Uu air interface.

[0346] As an embodiment, the MAC entity receiving the second signaling is one of the first MAC entity and the second MAC entity.

[0347] As an embodiment, the MAC entity receiving the second signaling is the first MAC entity.

[0348] As an embodiment, the MAC entity receiving the second signaling is the second MAC entity

[0349] As an embodiment, the first MAC entity and the second MAC entity are not the same MAC entity.

[0350] As an embodiment, the MAC entity receiving the second signaling is associated with one of the first RLC entity and the second RLC entity.

[0351] As an embodiment, the first RLC entity is associated with the first MAC entity, and the second RLC entity is associated with the second MAC entity.

[0352] As an embodiment, at least one of the first RLC entity and the second RLC entity is configured as a sending RLC entity.

[0353] As an embodiment, the association between an RLC entity and a MAC entity includes: data of the RLC entity is transmitted via a CG served by the MAC entity.

[0354] As an embodiment, the phrase "the first RLC entity is associated with the first MAC entity" includes: the bearer served by the first MAC entity is the first radio bearer, and the first MAC entity is used for the first radio bearer.

[0355] As an embodiment, the phrase "the first RLC entity is associated with the first MAC entity" includes: the first MAC entity is used to transmit data from the first RLC entity; and the data includes at least one of an RLC PDU and an inter-layer transmission primitive.

[0356] As an embodiment, the phrase "the first RLC entity is associated with the first MAC entity" includes: the first RLC entity is used to receive data from the first MAC entity; the data includes at least one of an RLC PDU and an inter-layer reception primitive.

[0357] As an embodiment, the phrase "the second RLC entity is associated with the second MAC entity" includes: the bearer served by the second MAC entity is the first radio bearer, and the second MAC entity is used for the first radio bearer.

[0358] As an embodiment, the phrase second RLC entity is associated with the second MAC entity includes: the second MAC entity is used to transmit data from the second RLC entity; the data includes at least one of RLC PDU and inter-layer transmission primitives.

[0359] As an embodiment, the phrase second RLC entity is associated with the second MAC entity includes: the second RLC entity is used to receive data from the second MAC entity; the data includes at least one of RLC PDU and inter-layer reception primitive.

[0360] Example 9

[0361] Embodiment 9 illustrates a third wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Fig. 9 As shown in the attached Fig. 9In the embodiment, the first PDCP entity E91, the first RLC entity E92 and the second RLC entity E93 are all located in the first node, the first PDCP entity E91 and the first RLC entity E92 communicate through an inter-layer interface, and the first PDCP entity E91 and the second RLC entity E93 communicate through an inter-layer interface.

[0362] for PDCP entity E91 , receiving a first indication in step S911; and sending a second indication in step S912.

[0363] for First RLC entity E92 , in step S921, a first indication is sent.

[0364] for Second RLC entity E93 , receiving a second indication in step S931.

[0365] As an embodiment, the step S911 is as follows Figure 5 After step S511 described in the above; step S921 is in the above Figure 5 After step S521 described in the above; step S931 is in the attached Figure 5 After step S531 described in.

[0366] As an embodiment, the first indication is a confirmation of successful transmission of the PDCP data PDU.

[0367] As an embodiment, the PDCP entity receives the first indication from the first RLC entity, and the first indication is used to confirm the successful transmission of the PDCP data PDU.

[0368] As an embodiment, the first indication is an inter-layer indication.

[0369] As an embodiment, the first indication is used to confirm the successful sending of the PDCP data PDU.

[0370] As an embodiment, the first indication includes a sequence number (SN) of the PDCP data PDU.

[0371] As an embodiment, a PDCP data PDU includes a PDCP sequence number.

[0372] As an embodiment, the PDCP sequence number is a non-negative integer.

[0373] As an embodiment, the PDCP sequence number includes 12 bits.

[0374] As an embodiment, the PDCP sequence number includes 18 bits.

[0375] As an embodiment, the first RLC entity sends a poll to a peer RLC entity of the first RLC entity, and the poll is used to trigger the peer RLC entity of the first RLC entity to feedback a status (STATUS) PDU.

[0376] As an embodiment, the status PDU indicates whether the first RLC SDU is successfully sent.

[0377] As an embodiment, the first RLC SDU is a copy of the PDCP data PDU delivered to the first RLC entity.

[0378] As an embodiment, the PDCP data PDU and the first RLC SDU are equivalent.

[0379] As an embodiment, the first RLC entity is an AM (Acknowledged Mode) RLC entity.

[0380] As an embodiment, the first RLC entity is configured as a sending RLC entity.

[0381] As an embodiment, when the logical channel corresponding to the first RLC entity is scheduled, the data transmitted by the first RLC entity is passed to the bottom layer; the bottom layer is the MAC layer.

[0382] As an embodiment, when the PDCP data PDU is processed by the first RLC entity, the first PDCP PDU is passed to the bottom layer; the bottom layer is the MAC layer.

[0383] As an embodiment, the AM RLC entity is configured to submit / receive RLC PDU through logical channels such as DL (Downlink) / UL (Uplink) DCCH, DL / UL DTCH, SCCH and STCH.

[0384] As an embodiment, the AM RLC entity submits / receives an RLC data PDU, wherein the RLC data PDU is an AMD PDU, and the AMD PDU includes a complete RLC SDU or an RLC SDU segment.

[0385] As an embodiment, the AM RLC entity submits / receives an RLC control PDU, where the RLC control PDU is a status PDU.

[0386] As an embodiment, a status PDU is received from the counterpart RLC entity of the first RLC entity, and when the status PDU indicates a positive acknowledgement for the first RLC SDU, the first RLC entity sends the first indication to the PDCP entity.

[0387] As an embodiment, the first RLC entity consists of a transmitting side and a receiving side.

[0388] As an embodiment, the counterpart RLC entity of the first RLC entity is located at a node other than the first node.

[0389] As an embodiment, the first node and a node other than the first node are not co-located.

[0390] As an embodiment, the first node and a node other than the first node are connected via a Uu air interface.

[0391] As an embodiment, a node other than the first node is the second node.

[0392] As an embodiment, if the PDCP SDU included in the PDCP data PDU does not belong to a low importance PDUset, and the first RLC entity is not associated with an SRAP entity, the PDCP entity sends the second indication to the second RLC entity.

[0393] As an embodiment, the first RLC entity is not associated with the SRAP entity, including: the first RLC entity is not for sidelink transmission.

[0394] As an embodiment, the second indication is an indication to discard the PDCP data PDU.

[0395] As an embodiment, when neither the second RLC SDU nor a segment of the second RLC SDU is delivered to the bottom layer, the second RLC entity discards the second RLC SDU.

[0396] As an embodiment, the second RLC SDU is a copy of the PDCP data PDU delivered to the second RLC entity.

[0397] As an embodiment, the PDCP data PDU and the second RLC SDU may be interchangeable.

[0398] As an embodiment, the bottom layer is a layer below the RLC sublayer.

[0399] As an embodiment, the bottom layer is the MAC sublayer.

[0400] As an embodiment, the segmentation of the second RLC SDU includes at least 1 bit of the second RLC SDU.

[0401] As an embodiment, in response to receiving the second indication, if the second RLC SDU or a segment of the second RLC SDU is not delivered to the bottom layer, the second RLC entity discards the second RLC SDU indicated by the second indication.

[0402] As an embodiment, when the logical channel corresponding to the second RLC entity is scheduled, the data transmitted through the second RLC entity is passed to the bottom layer.

[0403] As an embodiment, the second RLC SDU is passed to the bottom layer after the second RLC entity completes processing.

[0404] As an embodiment, when the second indication is received, the second RLC SDU is delivered to the bottom layer, and the second RLC entity does not discard the second RLC SDU indicated by the second indication.

[0405] As an embodiment, the second RLC entity is an AM RLC entity.

[0406] As an embodiment, the second RLC entity consists of a transmitting side and a receiving side.

[0407] As an embodiment, the second RLC entity is configured as a sending RLC entity.

[0408] Example 10

[0409] Embodiment 10 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in the attached figure. Fig.10 shown.

[0410] In the attached Fig.10 In the embodiment, the first node processing device 1000 includes a first receiver 1001 and a first transmitter 1002; the first node 1000 is a UE.

[0411] In embodiment 10, a first receiver 1001 receives a first signaling, wherein the first signaling indicates activation of PDCP replication for a PDCP entity, and the PDCP entity is associated with a first RLC entity and a second RLC entity; a first transmitter 1002 delivers a PDCP data PDU to at least one of the first RLC entity and the second RLC entity for transmission; wherein whether to replicate the PDCP data PDU, and whether to deliver the PDCP data PDU to the first RLC entity for transmission or to the second RLC entity for transmission when the PDCP data PDU is not replicated, depends at least on a second signaling; the second signaling indicates activation of SDU discard based on PDU set importance for a first radio bearer, and the first radio bearer is associated with the PDCP entity.

[0412] As an embodiment, when the second signaling is not received, the first transmitter 1002 copies the PDCP data PDU and delivers the PDCP data PDU to the first RLC entity and the second RLC entity for transmission.

[0413] As an embodiment, the first receiver 1001 receives the second signaling in a MAC entity; wherein, whether to copy the PDCP data PDU also depends on the PDCP SDU included in the PDCP data PDU.

[0414] As an embodiment, the first receiver 1001 receives the second signaling at a MAC entity; wherein, whether to copy the PDCP data PDU also depends on the PDCP SDU included in the PDCP data PDU; when the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending also depends on the MAC entity.

[0415] As an embodiment, the first receiver 1001 receives the second signaling at a MAC entity; wherein, whether to copy the PDCP data PDU also depends on the PDCP SDU included in the PDCP data PDU; the first transmitter 1002, when the MAC entity is associated with the first RLC entity, delivers the PDCP data PDU to the second RLC entity for sending; when the MAC entity is associated with the second RLC entity, delivers the PDCP data PDU to the first RLC entity for sending.

[0416] As an embodiment, the first receiver 1001 receives the second signaling at a MAC entity; wherein, whether to copy the PDCP data PDU also depends on the PDCP SDU included in the PDCP data PDU; the first receiver 1001 receives confirmation of successful sending of the PDCP data PDU from the first RLC entity; the first transmitter 1002 instructs the second RLC entity to discard the PDCP data PDU if the PDCP SDU included in the PDCP data PDU does not belong to a low importance PDU set and the first RLC entity is not associated with an SRAP entity.

[0417] As an embodiment, the first RLC entity is applied to MCG and the second RLC entity is applied to SCG, or the first RLC entity is applied to SCG and the second RLC entity is applied to MCG.

[0418] As an embodiment, the first node 1000 is the first node in this application.

[0419] As an embodiment, the first receiver 1001 includes the attached Figure 4 The receiver 454 (including antenna 452), receive processor 456, multi-antenna receive processor 458 and controller / processor 459.

[0420] As an embodiment, the first receiver 1001 includes the attached Figure 4 At least one of the receiver 454 (including antenna 452), receive processor 456, multi-antenna receive processor 458 or controller / processor 459.

[0421] As an embodiment, the first transmitter 1002 includes the attached Figure 4 The transmitter 454 (including antenna 452), transmit processor 468, multi-antenna transmit processor 457 and controller / processor 459.

[0422] As an embodiment, the first transmitter 1002 includes the attached Figure 4 At least one of the transmitter 454 (including antenna 452), the transmit processor 468, the multi-antenna receive processor 457 or the controller / processor 459.

[0423] Embodiment 11

[0424] Embodiment 11 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in the attached figure. Fig.11 shown.

[0425] In the attached Fig.11 In the embodiment, the second node processing device 1100 includes a second transmitter 1101. The second node 1100 is a base station.

[0426] In embodiment 11, the second transmitter 1101 sends a first signaling, wherein the first signaling indicates activation of PDCP replication for a PDCP entity, and the PDCP entity is associated with a first RLC entity and a second RLC entity; wherein, a PDCP data PDU is delivered to at least one of the first RLC entity and the second RLC entity for transmission; whether the PDCP data PDU is replicated, and whether the PDCP data PDU is delivered to the first RLC entity for transmission or to the second RLC entity for transmission when the PDCP data PDU is not replicated depends at least on the second signaling; the second signaling indicates activation of SDU discard based on PDU set importance for a first radio bearer, and the first radio bearer is associated with the PDCP entity.

[0427] As an embodiment, when the second signaling is not received, the PDCP data PDU is copied and delivered to the first RLC entity and the second RLC entity for transmission.

[0428] As an embodiment, the second transmitter 1101 sends the second signaling; wherein, whether the PDCP data PDU is copied also depends on the PDCP SDU included in the PDCP data PDU.

[0429] As an embodiment, the second transmitter 1101 sends the second signaling; wherein, whether the PDCP data PDU is copied also depends on the PDCP SDU included in the PDCP data PDU; when the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, whether the PDCP data PDU is delivered to the first RLC entity for sending or delivered to the second RLC entity for sending also depends on the MAC entity.

[0430] As an embodiment, the second transmitter 1101 sends the second signaling; wherein, whether the PDCP data PDU is copied also depends on the PDCP SDU included in the PDCP data PDU; when the MAC entity is associated with the first RLC entity, the PDCP data PDU is delivered to the second RLC entity for sending; when the MAC entity is associated with the second RLC entity, the PDCP data PDU is delivered to the first RLC entity for sending.

[0431] As an embodiment, the second transmitter 1101 sends the second signaling; wherein, whether the PDCP data PDU is copied also depends on the PDCP SDU included in the PDCP data PDU; confirmation of successful sending of the PDCP data PDU is received from the first RLC entity; if the PDCP SDU included in the PDCP data PDU does not belong to a low importance PDU set, and the first RLC entity is not associated with an SRAP entity, the second RLC entity is instructed to discard the PDCP data PDU.

[0432] As an embodiment, the first RLC entity is applied to MCG and the second RLC entity is applied to SCG, or the first RLC entity is applied to SCG and the second RLC entity is applied to MCG.

[0433] As an embodiment, the second node 1100 is the second node in this application.

[0434] As an embodiment, the second transmitter 1101 includes the attached Figure 4 The transmitter 418 (including antenna 420), transmit processor 416, multi-antenna transmit processor 471 and controller / processor 475.

[0435] As an embodiment, the second transmitter 1101 includes the attached Figure 4 At least one of the transmitter 418 (including antenna 420), the transmit processor 416, the multi-antenna transmit processor 471 and the controller / processor 475.

[0436] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing related 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. The present application is not limited to any specific form of combination of software and hardware. The first type of communication node or UE or terminal in the present application includes but is not limited to mobile phones, tablet computers, notebooks, Internet cards, low-power devices, eMTC (enhanced Machine Type Communication) equipment, NB-IoT equipment, vehicle-mounted communication equipment, aircraft, airplanes, drones, remote-controlled aircraft and other wireless communication equipment. The second category of communication nodes or base stations or network-side devices in the present application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, eNBs, gNBs, transmission and reception nodes TRP (Transmission and Reception Point), relay satellites, satellite base stations, aerial base stations, test equipment, such as transceivers that simulate some functions of base stations, signaling testers and other wireless communication equipment.

[0437] It should be understood by those skilled in the art that the present invention may be implemented in other specified forms without departing from its core or essential features. Therefore, the embodiments disclosed herein should be considered illustrative rather than restrictive in any way. The scope of the invention is determined by the appended claims rather than the preceding description, and all modifications within their equivalent meanings and regions are considered to be included therein.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first signaling, wherein the first signaling indicates activation of PDCP replication for a PDCP entity, wherein the PDCP entity is associated with a first RLC entity and a second RLC entity; A first transmitter delivers a PDCP data PDU to at least one of the first RLC entity and the second RLC entity for transmission; Among them, whether to copy the PDCP data PDU, and when the PDCP data PDU is not copied, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending depends at least on the second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for the first radio bearer, and the first radio bearer is associated with the PDCP entity.

2. The first node according to claim 1, characterized in that: When the second signaling is not received, the PDCP data PDU is copied and the PDCP data PDU is delivered to the first RLC entity and the second RLC entity for transmission.

3. The first node according to claim 1 or 2, characterized in that: include: The first receiver receives the second signaling at a MAC entity; Whether to copy the PDCP data PDU also depends on the PDCP SDU included in the PDCP data PDU.

4. The first node according to claim 3, characterized in that: When the PDCP SDU included in the PDCP data PDU belongs to a low importance PDU set, whether the PDCP data PDU is delivered to the first RLC entity for transmission or to the second RLC entity for transmission also depends on the MAC entity.

5. The first node according to claim 3 or 4, characterized in that: When the MAC entity is associated with the first RLC entity, the PDCP data PDU is delivered to the second RLC entity for sending; when the MAC entity is associated with the second RLC entity, the PDCP data PDU is delivered to the first RLC entity for sending.

6. The first node according to any one of claims 3 to 5, characterized in that: include: The first receiver receives, from the first RLC entity, a confirmation that the PDCP data PDU was successfully sent; The first transmitter instructs the second RLC entity to discard the PDCP data PDU if the PDCP SDU included in the PDCP data PDU does not belong to a low importance PDUset and the first RLC entity is not associated with a SRAP entity.

7. The first node according to any one of claims 1 to 6, characterized in that: The first RLC entity is applied to the MCG and the second RLC entity is applied to the SCG, or the first RLC entity is applied to the SCG and the second RLC entity is applied to the MCG.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first signaling, wherein the first signaling indicates activation of PDCP replication for a PDCP entity, and the PDCP entity is associated with a first RLC entity and a second RLC entity; In which, a PDCP data PDU is delivered to at least one of the first RLC entity and the second RLC entity for sending; whether the PDCP data PDU is copied, and when the PDCP data PDU is not copied, whether the PDCP data PDU is delivered to the first RLC entity for sending or to the second RLC entity for sending depends at least on a second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for a first radio bearer, and the first radio bearer is associated with the PDCP entity.

9. A method for a first node used in wireless communication, characterized in that: include: receiving a first signaling indicating activation of PDCP duplication for a PDCP entity, the PDCP entity being associated with a first RLC entity and a second RLC entity; delivering a PDCP data PDU to at least one of the first RLC entity and the second RLC entity for transmission; Among them, whether to copy the PDCP data PDU, and when the PDCP data PDU is not copied, whether to deliver the PDCP data PDU to the first RLC entity for sending or to the second RLC entity for sending depends at least on the second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for the first radio bearer, and the first radio bearer is associated with the PDCP entity.

10. A method for a second node used in wireless communication, characterized in that: include: Sending a first signaling, where the first signaling indicates activation of PDCP replication for a PDCP entity, where the PDCP entity is associated with a first RLC entity and a second RLC entity; In which, a PDCP data PDU is delivered to at least one of the first RLC entity and the second RLC entity for sending; whether the PDCP data PDU is copied, and when the PDCP data PDU is not copied, whether the PDCP data PDU is delivered to the first RLC entity for sending or to the second RLC entity for sending depends at least on a second signaling; the second signaling indicates the activation of SDU discard based on PDU set importance for a first radio bearer, and the first radio bearer is associated with the PDCP entity.

Images