Data transmission method, network node and user equipment using PDCP replication

By transmitting configuration information in PDCP replication, determining the status of DRB and RLC entities, the coordination problem of activation/deactivation of QoS stream image and RLC entity is solved, efficient data transmission is achieved, and the strict reliability and delay requirements of URLLC are met. .

CN116491215BActive Publication Date: 2024-12-03JRD COMM (SHENZHEN) LTD

Patent Information

Application Number
CN202080106599.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-10-22
Publication Date
2024-12-03
Estimated Expiration
2040-10-22

AI Technical Summary

Technical Problem

In PDCP replication, a mechanism is needed to coordinate and optimize the image of QoS flow to DRB and activation/deactivation of RLC entities to meet data transmission of different QoS requirements.

Method used

By transmitting configuration information between user equipment and network nodes, including QoS requirements, DRB type and number of branches, the corresponding DRB is determined for uplink transmission, and a new DRB or deactivate RLC entity is established if necessary to meet the reliability sex and delay requirements.

Benefits of technology

Effectively activate or deactivate RLC entities, ensure that data transmission meets QoS requirements, and improves the reliability and efficiency of PDCP replication, especially in the case of high latency requirements and high reliability requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116491215B_ABST
    Figure CN116491215B_ABST
Patent Text Reader

Abstract

A method for packet data convergence protocol (PDCP) duplicate data transmission executable in a user equipment. The method comprises: receiving configuration information from a network node, the configuration information comprising a relationship between an indication of a quality of service (QoS) requirement, type information of a data radio bearer (DRB), and the number of branches of the DRB; detecting a QoS requirement of a QoS flow; determining a DRB corresponding to the QoS flow, the DRB being determined according to the QoS requirement, the data radio bearer (DRB) type information, and the number of branches of the DRB corresponding to the configuration information; and performing uplink transmission of the QoS flow using the determined DRB.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of communication systems, and more specifically, to a data transmission method, a network node and a user equipment using PDCP replication. Background Art

[0002] Wireless communication systems and networks have evolved into broadband and mobile systems. In a cellular wireless communication system, user equipment (UE) is connected to a radio access network (RAN) via a radio link. The RAN consists of a set of base stations (BS) and an interface to the core network (CN). These base stations provide radio links to UEs located within the cells covered by the base stations, the core network provides overall network control, and the RAN and CN each perform their own functions for the entire network. The 3rd Generation Partnership Project (3GPP) developed the Long Term Evolution (LTE) system, the Evolved Universal Mobile Telecommunications System Territorial Radio Access Network (E-UTRAN), for mobile access networks, in which one or more macro cells are supported by base stations called eNodeB or eNB (evolved NodeB). LTE is further evolving towards 5G or NR (New Radio) systems, in which one or more cells are supported by base stations called gNBs.

[0003] Ultra-Reliable Low-Latency Communications (URLLC) is one of several different types supported by the 5G NR standard as specified by 3GPP Release 15. URLLC is a communication service that successfully delivers data packets with stringent requirements, especially in terms of availability, latency, and reliability. URLLC was developed to support emerging applications and services such as wireless control and automation in industrial factory environments, vehicle-to-vehicle communications for improved safety and efficiency, and the tactile Internet. Therefore, URLLC is important to 5G because it supports vertical industry integration and brings new services to the entire telecommunications industry.

[0004] One of the main features of URLLC is low latency, which is a key point to make self-driving cars and remote surgery possible. Low latency allows the network to be optimized to handle large amounts of data with minimal delay. URLLC requires a completely different quality of service (QoS) than mobile broadband services.

[0005] PDCP duplication is a useful L2 reliability enhancement tool that enables URLLC reliability requirements to be met under moderate channel conditions even when L1 reliability requirements are not stringent. The most stringent reliability requirement in URLLC is 1-10 -9 The typical reliability requirement for eMBB is 1-10 -3 , theoretically 1-10 can be achieved through 3-leg replication of the public link -9 reliability goals.

[0006] For Carrier Aggregation (CA) replication, each branch should use an exclusive carrier component (CC) set. For Dual Connectivity (DC) replication, since extending DC to more than two configured CGs is excluded, when configuring DC replication, at least one of the CGs should be configured as 2-branch or 3-branch PDCP replication.

[0007] According to 3GPP Release 16, NR supports PDCP duplication with more than two RLC entities, and RLC entity activation / deactivation can be determined by the Medium Access Control Component (MAC CE). Network coordination facilitates PDCP duplication in the uplink in the NR-DC / CA architecture, and a mechanism for network coordination of RLC entity activation / deactivation is required. Summary of the invention

[0008] Technical issues

[0009] From the perspective of QoS flow to DRB mapping, to determine which DRB the QoS flow is mapped to, and which RLC entities are activated / deactivated to perform data transmission, a mechanism needs to be provided to coordinate the management and optimization process of PDCP duplication.

[0010] Technical Solution

[0011] The purpose of the present application is to propose a method for controlling activation / deactivation of a Radio Link Control (RLC) entity, a base station and a user equipment.

[0012] An object of the present application is to propose a data transmission method, a network node and a user equipment for PDCP duplication.

[0013] The first aspect of the present application provides a method for packet data convergence protocol (PDCP) duplicate data transmission executable in a user equipment. The method comprises: receiving configuration information from a network node, the configuration information comprising a relationship between an indication of a quality of service QoS requirement, type information of a data radio bearer DRB, and the number of branches of the DRB; detecting the QoS requirement of a QoS flow; determining a DRB corresponding to the QoS flow, the DRB being determined according to the QoS requirement, the data radio bearer DRB type information, and the number of branches of the DRB corresponding to the configuration information; and performing uplink transmission of the QoS flow using the determined DRB.

[0014] In an embodiment of the present application, the method further includes: when no DRB meets the QoS requirements of the QoS flow, establishing a new DRB.

[0015] In an embodiment of the present application, the QoS requirement includes a reliability requirement of the QoS flow and a delay requirement or a QoS value of the QoS flow.

[0016] In an embodiment of the present application, the determination of the DRB corresponding to the QoS flow includes: under the condition that the QoS flow has a higher reliability requirement, determining the first number of branches corresponding to the DRB; under the condition that the QoS flow has a lower reliability requirement, determining the second number of branches corresponding to the DRB, wherein the second number of branches is less than the first number of branches.

[0017] In an embodiment of the present application, the type information of the DRB includes split DRB and DRB corresponding to a PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

[0018] In an embodiment of the present application, the delay requirement is provided by the QoS flow or protocol data unit PDU session.

[0019] In an embodiment of the present application, when the delay requirement is less than or equal to a delay threshold, it is decided to use a DRB that is not in the DC architecture or in a combination of the DC architecture and the CA architecture.

[0020] In an embodiment of the present application, when the delay requirement is less than or equal to the delay threshold, it is decided to use a split DRB that meets the reliability requirement of the minimum number of replicas.

[0021] In an embodiment of the present application, the method further includes: reporting to an upper layer the number of branches of the DRB, the active / inactive status of the RLC entity of the user equipment, and the type information of the DRB.

[0022] In an embodiment of the present application, the method also includes: when the PDCP replication architecture is a DC architecture or a dual-connection DC architecture and a carrier aggregation CA architecture, reporting to the upper layer the number of branches of the primary network node, and / or the number of branches of the secondary network node, and / or the number of branches of the split DRB.

[0023] In an embodiment of the present application, the method further includes: when the delay requirement is greater than the delay threshold and the type information of the DRB is a DRB in the DC architecture or a combination of the DC architecture and the CA architecture, receiving data forwarded by the auxiliary network node.

[0024] In an embodiment of the present application, the relationship also includes a minimum number of transmission copies corresponding to the reliability requirement.

[0025] The second aspect of the present application provides a method for duplicating data transmission in a packet data convergence protocol PDCP, the method being performed in a user equipment, comprising: receiving configuration information from a network node, the configuration information comprising measurement configuration and / or transmission error detection / counting configuration and / or configuration threshold; measuring the RLC channel quality of a data radio bearer DRB to obtain a measurement result, and / or detecting / counting the number of transmission errors / average number of HARQ retransmissions of a radio link control RLC channel to obtain a transmission statistical result; activating / deactivating the RLC entity of the user equipment according to the measurement result and / or the transmission statistical result and / or the configuration threshold.

[0026] In an embodiment of the present application, the RLC channel quality includes reference signal received power RSRP, reference signal received quality RSRQ, received signal strength indicator RSSI or signal to interference plus noise ratio SINR.

[0027] In an embodiment of the present application, the method further includes: when the measurement result is less than or equal to the measurement threshold, deactivating the RLC entity.

[0028] In an embodiment of the present application, the transmission statistics result includes detecting / counting the number of transmission errors or the average number of HARQ retransmissions.

[0029] In an embodiment of the present application, the method further includes: when the transmission statistical result is greater than or equal to the configuration threshold, deactivating the RLC entity.

[0030] In an embodiment of the present application, the method further includes: reporting the measurement result of the DRB and / or the transmission statistical result to an upper layer.

[0031] The third aspect of the present application provides a user equipment, including a transceiver and a processor. The transceiver is electrically connected and configured to perform the following operations, the operations including: receiving configuration information from a network node, the configuration information including a relationship between a quality of service QoS requirement, type information of a data radio bearer DRB, and the number of branches of the DRB; detecting the QoS requirement of a QoS flow; determining a DRB corresponding to the QoS flow, the DRB being determined according to the QoS requirement, the data radio bearer DRB type information, and the number of branches of the DRB corresponding to the configuration information; and performing uplink transmission of the QoS flow using the determined DRB.

[0032] In an embodiment of the present application, the operation further includes: when no DRB meets the QoS requirements of the QoS flow, establishing a new DRB.

[0033] In an embodiment of the present application, the QoS requirement includes a reliability requirement of the QoS flow and a delay requirement or a QoS value of the QoS flow.

[0034] In an embodiment of the present application, the determination of the DRB corresponding to the QoS flow includes: under the condition that the QoS flow has a higher reliability requirement, determining the first number of branches corresponding to the DRB; under the condition that the QoS flow has a lower reliability requirement, determining the second number of branches corresponding to the DRB, wherein the second number of branches is less than the first number of branches.

[0035] In an embodiment of the present application, the type information of the DRB includes split DRB and DRB corresponding to a PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

[0036] In an embodiment of the present application, the delay requirement is provided by the QoS flow or protocol data unit PDU session.

[0037] In an embodiment of the present application, when the delay requirement is less than or equal to a delay threshold, it is decided to use a DRB that is not in the DC architecture or in a combination of the DC architecture and the CA architecture.

[0038] In an embodiment of the present application, when the delay requirement is less than or equal to the delay threshold, it is decided to use a split DRB that meets the reliability requirement of the minimum number of replicas.

[0039] In an embodiment of the present application, the operation further includes: reporting to an upper layer the number of branches of the DRB, the active / inactive status of the RLC entity of the user equipment, and the type information of the DRB.

[0040] In an embodiment of the present application, the operation also includes: when the PDCP replication architecture is a DC architecture or a dual-connection DC architecture and a carrier aggregation CA architecture, reporting to the upper layer the number of branches of the main network node, and / or the number of branches of the auxiliary network node, and / or the number of branches of the split DRB.

[0041] In an embodiment of the present application, the operation also includes: when the delay requirement is greater than the delay threshold and the type information of the DRB is a DRB in the DC architecture or a combination of the DC architecture and the CA architecture, receiving data forwarded by the auxiliary network node.

[0042] In an embodiment of the present application, the relationship also includes a minimum number of transmission copies corresponding to the reliability requirement.

[0043] The fourth aspect of the present application provides a user equipment, including a transceiver and a processor. The transceiver is electrically connected and configured to perform the following operations, the operations including: receiving configuration information from a network node, the configuration information including measurement configuration and / or transmission error detection / counting configuration and / or configuration threshold; measuring the RLC channel quality of a data radio bearer DRB to obtain a measurement result, and / or detecting / counting the number of transmission errors / average number of HARQ retransmissions of a radio link control RLC channel to obtain a transmission statistical result; activating / deactivating the RLC entity of the user equipment according to the measurement result and / or the transmission statistical result and / or the configuration threshold.

[0044] In an embodiment of the present application, the RLC channel quality includes reference signal received power RSRP, reference signal received quality RSRQ, received signal strength indicator RSSI or signal to interference plus noise ratio SINR.

[0045] In an embodiment of the present application, the operation further includes: when the measurement result is less than or equal to the measurement threshold, deactivating the RLC entity.

[0046] In an embodiment of the present application, the transmission statistics result includes detecting / counting the number of transmission errors or the average number of HARQ retransmissions.

[0047] In an embodiment of the present application, the operation further includes: when the transmission statistical result is greater than or equal to the configuration threshold, deactivating the RLC entity.

[0048] In an embodiment of the present application, the operation also includes: reporting the measurement result of the DRB and / or the transmission statistical result to an upper layer.

[0049] The fifth aspect of the present application provides a method for replicating data transmission in a packet data convergence protocol PDCP, the method being performed in a network node, comprising: transmitting configuration information to a user equipment, the configuration information comprising an indication of a quality of service QoS requirement, type information of a data radio bearer DRB, and a relationship between the number of branches of the DRB; and performing uplink transmission of the QoS flow using the DRB, wherein activation / deactivation of the DRB is determined based on the QoS requirement, the data radio bearer DRB type information, and the number of branches of the DRB corresponding to the configuration information.

[0050] In an embodiment of the present application, the QoS requirement includes a reliability requirement of the QoS flow and a delay requirement or a QoS value of the QoS flow.

[0051] In an embodiment of the present application, the type information of the DRB includes that the DRB corresponds to a PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

[0052] In an embodiment of the present application, the delay requirement is provided by the QoS flow or protocol data unit PDU session.

[0053] In an embodiment of the present application, when the PDCP replication architecture includes a dual-connection DC architecture or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture, the method further includes: transmitting the number of branches of the data radio bearer DRB and the active / inactive status of the RLC entity of the user equipment to the primary network node; receiving the minimum and / or maximum number of copies from the primary network node; selecting / activating an RLC entity according to an indication of the primary network node; and sending the active / inactive status of the RLC entity to the primary network node.

[0054] The sixth aspect of the present application provides a network node, including a transceiver and a processor. The transceiver is electrically connected and configured to perform the following operations, the operations including: transmitting configuration information to a user equipment, the configuration information including an indication of a quality of service QoS requirement, type information of a data radio bearer DRB, and a relationship between the number of branches of the DRB; and performing uplink transmission of the QoS flow using the DRB, wherein activation / deactivation of the DRB is determined according to the QoS requirement, the type information of the data radio bearer DRB, and the number of branches of the DRB corresponding to the configuration information.

[0055] In an embodiment of the present application, the QoS requirement includes a reliability requirement of the QoS flow and a delay requirement or a QoS value of the QoS flow.

[0056] In an embodiment of the present application, the type information of the DRB includes that the DRB corresponds to a PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

[0057] In an embodiment of the present application, the delay requirement is provided by the QoS flow or protocol data unit PDU session.

[0058] In an embodiment of the present application, when the PDCP replication architecture includes a dual-connection DC architecture or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture, the method further includes: transmitting the number of branches of the data radio bearer DRB and the active / inactive status of the RLC entity of the user equipment to the primary network node; receiving the minimum and / or maximum number of copies from the primary network node; selecting / activating an RLC entity according to an indication of the primary network node; and sending the active / inactive status of the RLC entity to the primary network node.

[0059] The seventh aspect of the present application provides a chip, which may include a processor configured to call and run a computer program stored in a memory so that a device installed with the chip executes the method disclosed in the present application.

[0060] The eighth aspect of the present application provides a computer executable instruction that can be programmed and stored in a non-transitory computer readable medium. When the non-transitory computer readable medium is loaded into a computer, it instructs the processor of the computer to execute the method disclosed in the present application. The non-transitory computer readable medium may include at least one of the following readable media: a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an EPROM, an electrically erasable programmable read-only memory, and a flash memory.

[0061] The methods disclosed in the present application can be programmed as a computer program product, which causes a computer to execute the methods disclosed in the present application.

[0062] The methods disclosed in the present application can be programmed as computer programs, which cause computers to execute the methods disclosed in the present application.

[0063] Beneficial Effects

[0064] The embodiments of the present application provide a method, a network node, and a user equipment for duplicating data transmission in PDCP. The present application proposes to link the reliability requirement with the number of PDCP copies. The embodiments of the present application determine which DRB the QoS flow is to be mapped to based on the number of branches of the DRB and the RLC entity state. In addition, the present embodiment selects the DRB based on the delay requirement of the QoS flow and the PDCP replication architecture information. Therefore, data with high delay requirements and its copies are not transmitted on the auxiliary network node. In addition, the embodiments of the present application also measure the number of transmission errors / average number of HARQ retransmissions of the RLC entity channel to check the radio quality of the RLC entity channel when selecting / activating / deactivating the RLC entity. The embodiments of the present application also obtain the radio quality and transmission error / average number of HARQ retransmissions information of the DRB, and map the QoS flow to the DRB. Therefore, the present application can effectively activate / deactivate the RLC entity of the user equipment and effectively perform data transmission in PDCP replication. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present utility model. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0066] Figure 1 is a schematic diagram of a system according to an embodiment of the present application.

[0067] Figure 2 A schematic diagram illustrating a master node acting as a main network node according to an embodiment of the present application.

[0068] Figure 3 A schematic diagram of a secondary node acting as a primary network node according to another embodiment of the present application is shown.

[0069] Figure 4 The embodiments of the present application illustrate the options of MCG, SCG and network-side protocol side of separate bearers in multi-radio (MR)-DC with 5GC.

[0070] Figure 5 The radio protocol architecture of MCG, SCG and split bearers in MR-DC is illustrated from the UE perspective.

[0071] Figure 6 The flowchart of the data transmission method in PDCP duplication according to the first embodiment of the present application is illustrated.

[0072] Figure 7 The flowchart of the data transmission method in PDCP duplication according to the second embodiment of the present application is illustrated.

[0073] Figure 8 The flowchart of the data transmission method in PDCP duplication according to the third embodiment of the present application is illustrated.

[0074] Fig. 9 A structural block diagram of a system for wireless communication according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0075] The embodiments of the present application describe the technical matters, structural features, implementation purposes and effects in detail with reference to the accompanying drawings, as shown below. Specifically, the terms in the embodiments of the present application are only used for the purpose of describing specific embodiments, rather than limiting the disclosure.

[0076] 3GPP NR IIOT Background

[0077] In the revision of NR IIoT RP-192324, the detailed objectives of the NR PDCP duplication enhancement are:

[0078] ● Use RRC to configure up to 4 RLC entities with architecture combinations (including CA and NR-DC with CA [RAN2, RAN3] combinations) to specify PDCP replication.

[0079] ● Mechanisms to specify and dynamically control a set or subset of configured RLC entities or branches for PDCP duplication [RAN2, RAN3].

[0080] ● Lower priority objective: Specify enhancements to enable more resource-efficient PDCP duplication by enhancing the PDCP duplication activation / deactivation mechanism (e.g., MAC CE-based or UE-configurable criteria-based), provided that the increased complexity is justified, and per-packet selective duplication may also be considered [RAN2].

[0081] ● Specify enhancements to enable more efficient DL PDCP duplication without impacting UEs, provided the benefits can be demonstrated with reasonable complexity. [RAN3].

[0082] ●Specify enhancements based on SA2 progress and requests [RAN3] to address the potential impact of higher layer multiple connections.

[0083] For 3GPP Release 16, up to 4 RLC entities can be configured for DRBs utilizing DC and CA architectures, thus allowing different combinations of numbers of RLC entities to be hosted in the MCG and SCG.

[0084] As described in RAN3 LS R3-201664, RLC channel quality is taken into account in the PDCP duplication architecture, for example, in UL transmission, the best UL link should be used. On the DL side, if the primary network node directly controls the secondary network node without channel quality information from the secondary network node, it may not be able to track the rapid changes in radio quality. At the user level, the management and optimization process of PDCP duplication is a topic. Assistance information data is regarded as reference information in related enhancements. Descriptions of similar issues are also mentioned in the TP of TS 38.423 (R3-201665).

[0085] Therefore, there is a need for a network coordination mechanism that controls RLC entity activation / deactivation for PDCP duplication.

[0086] Protocols for delivering accurate reference timing for TSN

[0087] 3GPP RAN2#106 agreement

[0088] ● Dynamic network control of DRB replication is performed by MAC CE

[0089] ● Through MAC CE, the network controls which configured RLC entities are active

[0090] In RAN2#107, the following agreement was reached to introduce a duplication control MAC CE (using a new LCID) in 3GPP Release 16 to dynamically control the activation (deactivation) of RLC entities for PDCP duplication configured in the uplink:

[0091] RAN2#107 protocol:

[0092] ●The number of copies generated is equal to the number of active RLC entities, that is, each branch / RLC entity corresponds to one copy, and the active / inactive status is determined by the MAC CE.

[0093] ● The network provides only one LCH cell restriction configuration per LCH in RRC, just like in 3GPP Release 15. Changes to the LCH cell restriction configuration can only be made through RRC.

[0094] ● In case of PDCP duplication, the application of configured cell limits does not change dynamically when activating or deactivating PDCP duplication beyond 3GPP Release 15. (CA duplication case)

[0095] ●MAC CE signaling structure is:

[0096] a. Each DRB signaling with an associated RLC entity activation state, or

[0097] b. All DRBs with associated RLC entity activation status for each DRB

[0098] ● New LCID is used for 3GPP Release 16 MAC CE to control PDCP duplication.

[0099] Regardless of which MAC CE structure RAN2 will adopt (already present in RAN2#107 protocol), the RLC entity for activation / deactivation signaling will include duplicate activation states corresponding to all RLC entities configured for DRB, and therefore belong to both MCG and SCG in DC or DC and CA scenarios.

[0100] As agreed in RAN2#108, network coordination facilitates 3GPP Release 16 PDCP duplication in both DC and CA architectures, and it is a question of how nodes coordinate RLC entity activation / deactivation between each other.

[0101] 3GPP RAN2#108 agreement:

[0102] ●Network coordination facilitates PDCP duplication in the uplink in the NR-DC / CA architecture.

[0103] 3GPP RAN2#110-e protocol:

[0104] ● The UE only follows the received MAC CE, even if the RLCi field belongs to another node. No specification changes are required.

[0105] ● PDCP duplication with more than two RLC entities is supported only in NR. Needs clarification in 37.340 and 38.331.

[0106] ● Clarify DC+CA repeats in 38.300. Also needs to consider 3+1 repeat scheme. CA repeats may need clarification. Wording to be addressed.

[0107] Related prior art

[0108] According to the 16th edition of the conference, the following conclusions can be drawn:

[0109] ●PDCP duplication with more than two RLC entities is supported only in NR

[0110] ■A PDCP entity has one primary path.

[0111] ■ The primary path for data PDUs should not be deactivated.

[0112] ■ The number of copies generated is equal to the number of active RLC entities, ie one copy per branch / RLC entity.

[0113] ● Dynamic network control of DRB replication is performed by MAC CE

[0114] ■The active / inactive state of the RLC entity is determined by the MAC CE.

[0115] ■ For PDCP duplication controlling the MAC CE format, per DRB signalling with associated RLC entity activation state shall be adopted in Rel-16.

[0116] ■The index I of the RLCi field of the Rel-16 MAC CE is determined by the ascending order of the logical channel IDs of the auxiliary RLC entities in the MCG and SCG.

[0117] ■R16 MAC CE for outrigger selection and on / off.

[0118] ■ The UE only follows the received MAC CE, even if the RLCi field belongs to another node.

[0119] ● The network provides only one LCH cell restriction configuration for each LCH in RRC.

[0120] ■Changes to LCH cell limit configuration can only be made through RRC.

[0121] ■ In case of PDCP duplication, the application of the configured cell limit does not change dynamically when activating or deactivating PDCP duplication beyond Rel-15.

[0122] ■New LCID is used to control the Rel-16 MAC CE for PDCP duplication.

[0123] ●Network coordination facilitates PDCP duplication in the uplink in the NR-DC / CA architecture.

[0124] refer to Figure 1, the communication system includes UE 10, a first network node 200a, a second network node 200b and a network entity device 30. The connections between the devices and device components are shown as lines and arrows in the figure. UE 10 may include a processor 11, a memory 12 and a transceiver 13. The first network node 200a may include a processor 201a, a memory 202a and a transceiver 203a. The second network node 200b may include a processor 201b, a memory 202b and a transceiver 203b. The network entity device 300 may include a processor 301, a memory 302 and a transceiver 303. Each processor 11, 201a, 201b and 301 may implement the functions, processes and / or methods provided by the embodiment after execution. The wireless interface protocol layer may be implemented in the processors 11, 201b, 201a and 301. Each memory 12, 202a, 202b and 302 may store various programs and information to cooperate with the operation of the connected processor. Each transceiver 13, 203a, 203b and 303 is coupled to the processor for sending and / or receiving radio signals or wired signals. The first network node 200a and the second network node 200b can be a base station, such as an eNB, a gNB or one of other types of radio nodes, and can configure wireless resources for the UE 10.

[0125] Processors 11, 201b, 201a and 301 may include application specific integrated circuits (ASICs), other chipsets, logic circuits and / or data processing devices. Memory 12, 202a, 202b and 302 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and / or other storage devices. Transceivers 13, 203a, 203b and 303 may include baseband circuits and radio frequency (RF) circuits to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented by executing the functional modules, processes, functions, entities, etc. described herein. The modules may be stored in memory and executed by a processor. The memory may be implemented inside or outside the processor, and various devices known in the art may be coupled to the processor.

[0126] The network entity device 300 may be a node in the CN. The CN may include an LTE CN or a 5G core network (5GC), including a user plane function (UPF), a session management function (SMF), a mobility management function (AMF), a unified data management (UDM), a policy control function (PCF), a control plane (CP) / user plane (UP) separation (CUPS), an identity authentication server (AUSF), a network slice selection function (NSSF) and a network open function (NEF).

[0127] See also Figure 1 , Figure 2 and Figure 3 . Figure 2 A schematic diagram illustrating a master node according to an embodiment of the present application as a main network node. Figure 3 A schematic diagram showing another embodiment of the present application in which an auxiliary node is used as a primary network node. The first network node 200a as a main node MN located in a main unit group MCG can be a primary network node, and the second network node 200b as an auxiliary node SN located in an auxiliary unit group SCG can be an auxiliary network node. UE 10 configures a dual connection (DC) architecture and a carrier aggregation (CA) architecture through RRC signaling. The first network node 200a refers to a base station where separate bearers are located in the DC and CA architectures, and the second network node 200b is an auxiliary node. In another embodiment, the first network node 200a can be an auxiliary network node, and the second network node 200b can be a primary network node.

[0128] See also Figure 4 and Figure 5 . Figure 4 The embodiments of the present application illustrate the options of MCG, SCG and network-side protocol side of separate bearers in multi-radio (MR)-DC with 5GC. Figure 5 The radio protocol architecture of MCG, SCG and split bearer in MR-DC is described from the UE perspective. When UE 10 is in RRC_CONNECTED state with primary network node 200a and secondary network node 200b at the same time, a data radio bearer (DRB) is established by primary network node 200a and secondary network node 200b and configured for UE 10. UE 10 supports up to four RLC entities configured for radio bearers.

[0129] See also Figure 4 , Figure 5 and Figure 6 . Figure 6 The process of the data transmission method using packet data convergence protocol (PDCP) replication in an embodiment of the present application is illustrated. This embodiment discloses a method based on QoS requirements and PDCP replication architecture, which can correspond QoS flows to PDCP replicated DRBs that support up to 4 RLC entities. The network node 200a sends the association configuration information indicating the quality of service (QoS) requirements, DRB type information, and several branches of the DRB to the UE 10 (step 602). The UE 10 meets the QoS requirements of the QoS process. Figure 4As shown, the mapping between QoS flows and data radio bearers is processed in the Service Data Adaptation Protocol (SDAP), and the QoS requirements of the QoS flows are thus detected. The delay requirement is provided with the QoS flow or the Protocol Data Unit (PDU) session. The QoS requirement includes the reliability of the QoS flow and the delay requirement of the QoS flow, or the QoS requirement is a QoS value. The type information of the data radio bearer (DRB) includes the split DRB and the DRB in the PDCP duplication architecture, which includes the use of a dual connectivity (DC) architecture, a carrier aggregation (CA) architecture, or a combination of a dual connectivity (DC) architecture and a carrier aggregation (CA) architecture.

[0130] When the user equipment 10 and the network node 200a are both in the RRC_CONNECTED state, the data radio bearer (DRB) is established by the network node 200a and configured in the user equipment 10. The network node 200a and the user equipment 10 can select to use a dual connectivity (DC) architecture, or a carrier aggregation (CA) architecture, or a combination of a dual connectivity (DC) architecture and a carrier aggregation (CA) architecture according to the type information of the data radio bearer. The user equipment 10 supports up to four RLC entities configured for the radio bearer.

[0131] The user equipment 10 determines the DRB for transmitting the QoS flow according to the QoS requirement of the QoS flow, and determines the type information of the data radio bearer (DRB) and the number of legs of the data radio bearer (DRB) based on the QoS requirement according to the QoS requirement (step 604). The type information of the data radio bearer (DRB) includes the DRB in the split DRB and PDCP replication architecture, and the number of legs of the DRB may be related to the split DRB and PDCP replication architecture.

[0132] 2 to 4 branches used to support PDCP duplication are associated with the DRB, supporting up to 4 RLC entities. For example, 3 or 4 branches are provided for PDCP duplication with more than 2 RLC entities. Taking into account the reliability requirements, information related to PDCP duplication, such as the minimum number of copies required, should be provided with the QoS flow or PDU session. In addition to providing an association between QoS requirements (especially reliability requirement related parameters) and the minimum number of branches of the DRB, the reliability requirements of QoS mapping to the minimum number of transmission copies can also be included. The upper layer (such as the SDAP layer) determines the DRB to which the QoS flow is mapped based on the reliability requirements, the minimum number of branches required, and the number of branches of the DRB. In addition, the active / inactive state can also be taken into account. In the operation of the SDAP layer, QoS flows with higher reliability requirements must be mapped to DRBs with more branches. That is, the QoS flow with the highest reliability is mapped to a DRB with 4 branches, and the QoS flow with the lowest reliability can only be mapped to a DRB with 2 branches. For example, the user equipment 10 may determine that DRB1 has four entities RLC0, RLC1, RLC2, and RLC3 (ie, four branches). The user equipment 10 activates / deactivates the physical radio link control (RLC) entity of the user equipment 10 (step 606). Then, link transmission of the QoS flow is performed based on the determined DRB1.

[0133] The CA architecture, DC architecture, and the combination of CA and DC architectures involve PDCP replication using more than 2 RLC entities. Due to the Xn / X2 interface delay used for DC and the combination of CA and DC, the PDCP replication implemented using split DRBs in such DC and the combination of CA and DC may not meet the delay requirements of services with stricter delay requirements. Therefore, the design must determine which DRB the QoS flow should be mapped to so that the delay requirement can be guaranteed. The delay requirement can be a delay threshold, which is used to set a situation where a delay requirement less than (or equal to) the delay threshold cannot be mapped to a split DRB of a DC or a combination of CA and DC architectures that supports PDCP replication. That is, if the delay requirement is less than or equal to the delay threshold, a decision is made to use a DRB running in the CA architecture, or a decision is made to use a split DRB that meets the reliability requirement of the minimum number of copies.

[0134] In other words, the delay requirement can be divided into several levels, such as high, medium, and low, or into level 0, level 1, level 2...level N. In particular, the level of the delay requirement can be represented by a number or a string, and the level of the delay requirement can be provided together with the QoS flow or PDU session. The level of the delay requirement can be mapped to the PDCP replication can be defined to determine which DRB the QoS flow should be mapped to. QoS flows with strict delay requirements (i.e., high delay requirements less than or equal to the delay threshold) are mapped to DRBs other than the combination of DC and CA architectures or the DC architecture, or are mapped to split DRBs with a minimum number of replicas that meet the reliability requirements. Otherwise, QoS flows with less stringent delay requirements (i.e., low delay requirements exceeding the delay threshold) can be mapped to DRBs of the combination of DC and CA architectures or the DC architecture or split DRBs. For example, if the delay requirement of the QoS flow is level 0, level 1, level 2 less than or equal to the delay threshold, the UE 10 will decide to use the DRB in the CA architecture to transmit the QoS flow. If the delay requirement of the QoS flow belongs to level 3, level 4, ..., level n which is greater than the delay threshold, the UE 10 decides to use split DRB or DRB or DRB in a combination of DC and CA architecture to transmit the QoS flow.

[0135] Reports the number and active / inactive status of branches and architectures (i.e. CA architecture, DC architecture, combination of CA and DC architecture) to upper layers. QoS flows should be mapped to appropriate DRBs based on QoS requirements and the type of DRB. If there is no DRB that meets the QoS requirements of the QoS flow, a new DRB will be established.

[0136] Example 2

[0137] refer to Figure 1 and Figure 7 . Figure 7 The process of the packet data convergence protocol (PDCP) duplicate data transmission method according to another embodiment of the present disclosure is illustrated. In this embodiment, the primary network node 200b refers to the second network node, and the auxiliary network node refers to the first network node 200a. This embodiment focuses on the DC architecture and the combination of the CA and DC architectures that support PDCP duplication, which may include up to 4 RLC entities. The auxiliary network node 200a shares the information of the number of branches and the active / inactive status of the RLC entity with the primary network node 200b, so that the primary network node 200b can decide how many copies to transmit on the auxiliary network node 200a.

[0138] After the QoS flow whose delay requirement exceeds the delay threshold is mapped to the split DRB, or when data comes, the number, minimum number and / or maximum number of copies to be transmitted are sent to the auxiliary network node 200a. The auxiliary network node 200a selects and activates the RLC entity according to the instruction from the primary network node 200b, and sends the active / inactive state of the RLC entity to the primary network node 200b. Then the data is transmitted on the auxiliary network node 200a.

[0139] Using this information, such as the minimum and / or maximum number of replicas from the primary network node 200b, the secondary network node 200a dynamically allocates / activates RLC entities accordingly, so that data can be transmitted immediately through the secondary network node 200a and radio resources can be used efficiently.

[0140] Example 3

[0141] refer to Figure 1 and Figure 8 . Figure 8 The flow of a data transmission method in a packet data convergence protocol (PDCP) duplication according to another embodiment of the present disclosure is depicted. This embodiment focuses on selecting / activating / deactivating an RLC entity according to RLC channel quality. Since radio quality is one of the factors affecting data transmission, it is necessary to select / activate / deactivate an RLC entity to ensure the reliability of traffic.

[0142] Since the reliability of data transmission cannot be guaranteed in the case of poor radio quality, the RLC channel quality must be considered when activating / deactivating / selecting an RLC entity. The UE 10 measures the RLC channel quality of each channel of the RLC entity to obtain a measurement result based on the measurement threshold of the base station 200a. The RLC channel quality includes reference signal received power (RSRP), reference signal received quality (RSRQ), received signal strength indication (RSSI) and / or signal to interference plus noise ratio (SINR). The UE 10 activates / deactivates the channel of the RLC entity according to the measurement result. If the measurement result is less than or equal to the measurement threshold, that is, the radio quality of the RLC channel is too poor to perform data transmission, the UE 10 will deactivate the channel of the RLC entity. Alternatively, the RLC channel can be marked as unavailable so that it is not selected to perform data transmission or activation. Or the data transmission on it should be switched to another suitable RLC entity with better radio quality.

[0143] In another embodiment, the RLC channel quality includes the number of transmission errors or the average number of hybrid automatic repeat request (HARQ) retransmissions (i.e., transmission statistics). A high number of RLC channel transmission errors / average HARQ retransmissions means that the reliability requirements of the service are difficult to guarantee. Therefore, the UE 10 measures the number of transmission errors or average hybrid automatic repeat request (HARQ) retransmissions within a predefined time period. If the RLC channel quality (i.e., the number of transmission errors or average hybrid automatic repeat request (HARQ) retransmissions) exceeds a measurement threshold, the UE 10 will deactivate the channel of the RLC entity, or the transmission thereon should be switched to another available RLC entity. Alternatively, other RLC entities are selected / activated to transmit another copy to ensure that the reliability requirements are guaranteed.

[0144] In DC or a combination of CA and DC architecture, assistance information is shared between the primary network node 200b and the auxiliary network node 200a so that the RLC entity can be dynamically activated / deactivated according to measurement / statistical results.

[0145] In addition, the measurement results and / or transmission statistics can be per DRB. Information about the RLC failure should be included in the assistance information of the DRB. With the help of the information, the upper layer should select a suitable DRB for the upcoming QoS flow so that the QoS of the service can be guaranteed. The measurement results and / or transmission statistics of the DRB are re-reported to the upper layer.

[0146] Fig. 9 7 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present application. The embodiments of the present application may use any appropriately configured hardware and / or software for implementation into the system 700. The system 700 includes a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780.

[0147] The processing unit 730 may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor may include any combination of general-purpose processors and special-purpose processors, such as a graphics processor and an application processor. The processor may be coupled to a memory / storage and configured to execute instructions stored in the memory / storage to enable various applications and / or operating systems running on the system.

[0148] The baseband circuit 720 may include circuits, such as but not limited to one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuit may handle various radio control functions, which may communicate with one or more radio networks through RF circuits. The radio control functions may include but are not limited to signal modulation, encoding, decoding, radio frequency conversion, etc. In some embodiments, the baseband circuit may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit may support communications with 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), wireless personal area networks (WPAN). An embodiment in which the baseband circuit is configured to support radio communications of more than one wireless protocol may be referred to as a multimode baseband circuit. In different embodiments, the baseband circuit 720 may include circuits that operate with signals of baseband frequencies. For example, in some embodiments, the baseband circuit may include circuits that work with signals having an intermediate frequency, which is between the baseband frequency and the radio frequency.

[0149] RF circuitry 710 may communicate with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate communication with the wireless network. In various embodiments, the RF circuitry 710 may include circuitry that operates using signals that are not strictly considered to be radio frequencies. For example, in some embodiments, the RF circuitry may include circuitry that operates with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

[0150] In different embodiments, the transmitter circuits, control circuits, or receiver circuits discussed above regarding the UE, eNB, or gNB may be embodied in whole or in part in one or more RF circuits, baseband circuits, and / or processing units. As used herein, a "circuit" may be a portion of an application-specific integrated circuit (ASIC), an electronic circuit, a processor, and / or a memory that executes one or more software or firmware programs, a combination of logic circuits, and / or other suitable hardware components that provide the functionality. In some embodiments, an electronic device circuit may be implemented in one or more software or firmware modules, or the functionality associated with the circuit may be implemented by one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuit, processing unit, and / or memory / storage may be implemented together on a system on a chip (SOC).

[0151] The memory 740 can be used to load and store data and / or instructions, such as for the system. The memory for one embodiment can include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)) and / or non-volatile memory (such as flash memory). In different embodiments, the I / O interface 780 can include one or more user interfaces designed to enable a user to interact with the system and / or a peripheral component interface designed to interact with the peripheral components of the system. The user interface can include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. The peripheral component interface can include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power interface.

[0152] In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and / or location information associated with the system. In some embodiments, the sensor may include, but is not limited to, a gyroscope sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of or interact with a baseband circuit and / or an RF circuit to communicate with components of a positioning network, such as a global positioning system (GPS) satellite. In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 700 may be a mobile computing device, such as, but not limited to, a laptop computing device, a tablet computing device, a smart phone, etc. In various embodiments, the system may have more or less components, and / or different architectures. Where appropriate, the methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-temporary storage medium.

[0153] The embodiments of the present application are a combination of techniques / processes that can be adopted in the 3GPP specifications to create a final product.

[0154] It is understood by those skilled in the art that each unit, algorithm and step described and disclosed in the embodiments of the present application is implemented using software or a combination of software for computers and electronic hardware. Whether the function is run in hardware or software depends on the application conditions and design requirements of the technical plan. A person of ordinary skill in the art can use different ways to implement the functions of each specific application, and such implementation should not exceed the scope of the present application. It is understood by those skilled in the art that since the working processes of the above-mentioned systems, devices and units are basically the same, he / she can refer to the working processes of the systems, devices and units in the above-mentioned embodiments. For ease of description and simplicity, these workflows will not be described in detail.

[0155] It is understood that the systems, devices and methods disclosed in the embodiments of the present application can be implemented in other ways. The above embodiments are exemplary only. The division of units is based only on logical functions, while other divisions exist in the implementation. Multiple units or components can be combined or integrated into another system. Certain features may also be omitted or skipped. On the other hand, the mutual coupling, direct coupling or communication coupling shown or discussed can be operated indirectly or in a communication manner through certain ports, devices or units through electrical, mechanical or other forms.

[0156] The units used as separate components for explanation may or may not be physically separated. The units used for display may or may not be physical units, i.e., located in one place or distributed over multiple network units. Some or all of the units are used according to the purpose of the embodiment. Moreover, each functional unit in each embodiment may be integrated into one processing unit, physically independent, or integrated into one processing unit having two or more units.

[0157] If the software functional unit is implemented and used and sold as a product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution proposed in the present application can be substantially or partially implemented in the form of a software product. Alternatively, a part of the technical plan that is beneficial to conventional technology can be implemented in the form of a software product. The software product in the computer is stored in a storage medium, including multiple commands for running a computing device (such as a personal computer, a server, or a network device) of all or part of the steps disclosed in the embodiments of the present application. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other types of media capable of storing program code.

[0158] Embodiments of the present application provide a method, a network node, and a user equipment for duplicating data transmission in PDCP. The present application proposes to link reliability requirements with the number of PDCP copies. Embodiments of the present application determine which DRB the QoS flow is to be mapped to based on the number of branches of the DRB and the RLC entity state. In addition, the present embodiment selects the DRB based on the delay requirements of the QoS flow and the PDCP duplication architecture information. Therefore, data with high delay requirements and its copies are not transmitted on the auxiliary network node. In addition, the embodiments of the present application also measure the number of transmission errors / average number of HARQ retransmissions of the RLC entity channel to check the radio quality of the RLC entity channel when selecting / activating / deactivating the RLC entity. The embodiments of the present application also obtain the radio quality and transmission error / average number of HARQ retransmissions information of the DRB, and map the QoS flow to the DRB. Therefore, the present application can effectively activate / deactivate the RLC entity of the user equipment and effectively perform data transmission in the packet data convergence protocol (PDCP) duplication.

[0159] In the embodiments of the present application, specific examples are used to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea. At the same time, for technical personnel in this field, according to the idea of ​​the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A method for duplicating data transmission in a Packet Data Convergence Protocol (PDCP), the method being performed in a user equipment, comprising: receiving configuration information from a network node, the configuration information including information indicating a quality of service (QoS) requirement, type information of a data radio bearer (DRB), and a relationship between a number of branches of the DRB; Detecting a QoS requirement of a QoS flow, wherein the QoS requirement includes a reliability requirement of the QoS flow and a delay requirement or a QoS value of the QoS flow; Under the condition that the QoS flow has a higher reliability requirement, determining a first number of branches corresponding to the DRB, wherein the DRB is determined according to the QoS requirement corresponding to the configuration information, the data radio bearer DRB type information, and the number of branches of the DRB; Under the condition that the QoS flow has a lower reliability requirement, determining a second branch number corresponding to the DRB, wherein the second branch number is less than the first branch number; and Uplink transmission of the QoS flow is performed using the determined DRB.

2. The method according to claim 1, characterized in that It also includes: When no DRB meets the QoS requirement of the QoS flow, a new DRB is established.

3. The method according to claim 1, characterized in that The type information of the DRB includes split DRB and DRB corresponding to the PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

4. The method according to claim 1, characterized in that The delay requirement is provided by the QoS flow or protocol data unit PDU session.

5. The method according to claim 3, characterized in that: When the delay requirement is less than or equal to a delay threshold, it is decided to use a DRB that is not in the DC architecture or in a combination of the DC architecture and the CA architecture.

6. The method according to claim 1, characterized in that When the delay requirement is less than or equal to the delay threshold, it is decided to use a split DRB that meets the reliability requirement of the minimum number of replicas.

7. The method according to claim 3, characterized in that It also includes: Report the number of branches of the DRB, the active / inactive status of the RLC entity of the user equipment, and the type information of the DRB to the upper layer.

8. The method according to claim 7, characterized in that It also includes: When the PDCP replication architecture is a DC architecture or a dual-connection DC architecture and a carrier aggregation CA architecture, the number of branches of the primary network node, and / or the number of branches of the secondary network node, and / or the number of branches of the split DRB are reported to the upper layer.

9. The method according to claim 8, characterized in that It also includes: When the delay requirement is greater than a delay threshold and the type information of the DRB is a DRB in the DC architecture or in a combination of the DC architecture and the CA architecture, data forwarded by the auxiliary network node is received.

10. The method according to claim 1, characterized in that The relationship also includes a minimum number of transmission copies corresponding to the reliability requirement.

11. A user equipment, comprising: Transceiver; and A processor is electrically connected to the transceiver and configured to perform the following operations, wherein the operations include: receiving configuration information from a network node, the configuration information including information indicating a quality of service (QoS) requirement, type information of a data radio bearer (DRB), and a relationship between a number of branches of the DRB; Detecting a QoS requirement of a QoS flow, wherein the QoS requirement includes a reliability requirement of the QoS flow and a delay requirement or a QoS value of the QoS flow; Under the condition that the QoS flow has a higher reliability requirement, determining a first number of branches corresponding to the DRB, wherein the DRB is determined according to the QoS requirement corresponding to the configuration information, the data radio bearer DRB type information, and the number of branches of the DRB; Under the condition that the QoS flow has a lower reliability requirement, determining a second branch number corresponding to the DRB, wherein the second branch number is less than the first branch number; and Uplink transmission of the QoS flow is performed using the determined DRB.

12. The user equipment according to claim 11, characterized in that The operations also include: When no DRB meets the QoS requirement of the QoS flow, a new DRB is established.

13. The user equipment according to claim 11, characterized in that The type information of the DRB includes split DRB and DRB corresponding to the PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

14. The user equipment according to claim 11, characterized in that The delay requirement is provided by the QoS flow or protocol data unit PDU session.

15. The user equipment according to claim 13, characterized in that When the delay requirement is less than or equal to a delay threshold, it is decided to use a DRB that is not in the DC architecture or in a combination of the DC architecture and the CA architecture.

16. The user equipment according to claim 11, characterized in that When the delay requirement is less than or equal to the delay threshold, it is decided to use a split DRB that meets the reliability requirement of the minimum number of replicas.

17. The user equipment according to claim 11, characterized in that The operations also include: Report the number of branches of the DRB, the active / inactive status of the RLC entity of the user equipment, and the type information of the DRB to the upper layer.

18. The user equipment according to claim 17, characterized in that The operations also include: When the PDCP replication architecture is a DC architecture or a dual-connection DC architecture and a carrier aggregation CA architecture, the number of branches of the primary network node, and / or the number of branches of the secondary network node, and / or the number of branches of the split DRB are reported to the upper layer.

19. The user equipment according to claim 18, characterized in that The operations also include: When the delay requirement is greater than a delay threshold and the type information of the DRB is a DRB in the DC architecture or in a combination of the DC architecture and the CA architecture, data forwarded by the auxiliary network node is received.

20. The user equipment according to claim 11, characterized in that The relationship also includes a minimum number of transmission copies corresponding to the reliability requirement.

21. A method for duplicating data transmission in a Packet Data Convergence Protocol (PDCP), the method being performed in a network node, comprising: Transmitting configuration information to a user equipment, the configuration information including a relationship between a quality of service QoS requirement, type information of a data radio bearer DRB, and a number of branches of the DRB, wherein the QoS requirement includes a reliability requirement of a QoS flow and a delay requirement or a QoS value of the QoS flow; as well as Perform uplink transmission of the QoS flow using a DRB, wherein activation / deactivation of the DRB is determined according to the QoS requirement corresponding to the configuration information, the data radio bearer DRB type information, and the number of branches of the DRB, and under the condition that the QoS flow has a higher reliability requirement, determining a first number of branches corresponding to the DRB; Under the condition that the QoS flow has a lower reliability requirement, a second branch number corresponding to the DRB is determined, wherein the second branch number is less than the first branch number.

22. The method according to claim 21, characterized in that The type information of the DRB includes that the DRB corresponds to a PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

23. The method according to claim 22, characterized in that The delay requirement is provided by the QoS flow or protocol data unit PDU session.

24. The method according to claim 22, characterized in that When the PDCP replication architecture includes a dual connection DC architecture or a combination of a dual connection DC architecture and a carrier aggregation CA architecture, the method further includes: transmitting the number of branches of the data radio bearer DRB and the active / inactive state of the RLC entity of the user equipment to the primary network node; receiving a minimum and / or maximum number of replicas from the primary network node; selecting / activating an RLC entity according to an instruction of the primary network node; and The active / inactive status of the RLC entity is sent to the primary network node.

25. A network node, comprising: Transceiver; and A processor is electrically connected to the transceiver and configured to perform the following operations, wherein the operations include: Transmitting configuration information to a user equipment, the configuration information including a relationship between a quality of service QoS requirement, type information of a data radio bearer DRB, and a number of branches of the DRB, wherein the QoS requirement includes a reliability requirement of a QoS flow and a delay requirement or a QoS value of the QoS flow; and Use DRB to perform uplink transmission of the QoS flow, wherein activation / deactivation of the DRB is determined based on the QoS requirement corresponding to the configuration information, the data radio bearer DRB type information, and the number of branches of the DRB. Under the condition that the QoS flow has a higher reliability requirement, the first number of branches corresponding to the DRB is determined; under the condition that the QoS flow has a lower reliability requirement, the second number of branches corresponding to the DRB is determined, wherein the second number of branches is less than the first number of branches.

26. The network node according to claim 25, characterized in that The type information of the DRB includes that the DRB corresponds to a PDCP replication architecture, wherein the PDCP replication architecture includes a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of a dual-connection DC architecture and a carrier aggregation CA architecture.

27. The network node according to claim 26, characterized in that The delay requirement is provided by the QoS flow or protocol data unit PDU session.

28. The network node according to claim 26, characterized in that When the PDCP replication architecture includes a dual connection DC architecture or a combination of a dual connection DC architecture and a carrier aggregation CA architecture, the operation further includes: transmitting the number of branches of the data radio bearer DRB and the active / inactive state of the RLC entity of the user equipment to the primary network node; receiving a minimum and / or maximum number of replicas from the primary network node; selecting / activating an RLC entity according to an instruction of the primary network node; and The active / inactive status of the RLC entity is sent to the primary network node.

29. A chip, comprising: A processor configured to call and run a computer program stored in a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 10.

30. A chip, comprising: A processor configured to call and run a computer program stored in a memory so that a device equipped with the chip executes the method according to any one of claims 21 to 24.

31. A computer-readable storage medium storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 10.

32. A computer-readable storage medium storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 21 to 24.

33. A computer program product comprising a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 10.

34. A computer program product comprising a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 21 to 24.

Citation Information

Patent Citations

  • Method for improving direct communication interface to support double connection and network node

    CN104812088A

  • Method and apparatus for establishing default data radio bearer

    CN108513727A

  • Packet duplication at a packet data convergence protocol (PDCP) entity

    US20180324642A1

  • Method for data replication, data counting method, corresponding entities and media

    WO2020159168A1

  • Method for determining bearer type, and communication device

    WO2020200103A1

Cited By

  • RAN and UE driven L4S marking and processing for congestion management in an O-RAN based network architecture

    US12684410B2