CN116235617A

CN116235617A - Method for controlling a radio link control entity, network node and user equipment

Info

Publication number: CN116235617A
Application number: CN202080104320.5A
Authority: CN
Inventors: 王和俊; 生嘉
Original assignee: JRD Communication Shenzhen Ltd
Current assignee: JRD Communication Shenzhen Ltd
Priority date: 2020-08-07
Filing date: 2020-08-07
Publication date: 2023-06-06
Also published as: WO2022027558A1

Abstract

A method of controlling a radio link control, RLC, entity of a user equipment, the user equipment operating in a primary network, comprising: transmitting RLC entity activation/deactivation signaling to the user equipment; receiving an RLC entity status report message indicating the user equipment, the user equipment responding to the RLC entity activation/deactivation signaling to activate/deactivate an RLC entity; and updating an activation state of the RLC entity of the user equipment according to the report message.

Description

Method for controlling a radio link control entity, network node and user equipment

Technical Field

The present application relates to the field of communication systems, and more particularly to a method, network node and user equipment for controlling activation/deactivation of a Radio Link Control (RLC) entity.

Background

Wireless communication systems and networks have evolved into broadband and mobile systems. In a cellular wireless communication system, a User Equipment (UE) is connected to a Radio Access Network (RAN) through a radio link. The RAN includes a set of Base Stations (BSs) and interfaces to a Core Network (CN). These base stations provide radio links with UEs located within the cell covered by the base stations, the core network provides overall network control, and the RAN and CN each perform their respective functions on the overall network. The third generation partnership project (3 GPP) has developed a Long Term Evolution (LTE) system, i.e., an evolved universal mobile telecommunications system terrestrially incorporated radio access network (E-UTRAN), for mobile access networks in which one or more macro cells are supported by base stations called enodebs or enbs (evolved nodebs). LTE is further evolving towards 5G or NR (new radio) systems, where one or more cells are supported by base stations called gnbs.

Ultra Reliable Low Latency Communication (URLLC) is one of several different types supported by the 5G NR standard specified by release 15 of 3 GPP. URLLC is a communication service that enables successful delivery of data packets with stringent requirements, in particular in terms of availability, delay and reliability. URLLC was developed to support emerging applications and services such as wireless control and automation in industrial plant environments, inter-vehicle communication to improve security and efficiency, and the haptic internet. Therefore, URLLC is important for 5G because it supports vertical industry integration, bringing new business to the whole telecommunications industry.

One of the main functions of URLLC is low latency, which is a key point in enabling automatic driving of automobiles and tele-surgery. The low latency allows the network to be optimized to handle large amounts of data with minimal latency. The URLLC requires a completely different quality of service (QoS) than mobile broadband services.

PDCP duplication is a useful L2 reliability enhancement tool so that under medium channel conditions, the reliability requirements of URLLC can be met even in situations where the reliability requirements of L1 are not strict enough. The most stringent reliability requirement in URLLC is 1-10 ^-9- . Typical reliability requirements for eMBB are 1-10 ^-3 Theoretically 1-10 can be achieved by 3-branch (3-leg) replication of the common link ^-9 Reliability targets of (2).

For carrier aggregation (Carrier Aggregation, CA) replication, each branch should use a set of exclusive carrier components (carrier component, CC). For dual connectivity (Dual Connectivity, DC) duplication, since expanding DC to more than two configured CGs is eliminated, at least one of the CGs should be configured as a 2-branch or 3-branch PDCP duplication when configuring DC duplication.

According to release 16 of 3GPP, NR supports PDCP duplication with more than two RLC entities, which may be determined by a medium access control element (MAC CE). Network coordination facilitates PDCP duplication in the uplink in NR-DC/CA architecture, requiring a mechanism for network coordination RLC entity activation/deactivation.

Disclosure of Invention

Technical problem

For PDCP duplication using more than two RLC entities configured for Data Radio Bearers (DRBs) in a combination of DC architecture and CA architecture, one network node cannot control the active/inactive state of the RLC entity belonging to the other node in some cases. Thus, there is a need for a network coordinated RLC entity activation/deactivation mechanism.

Technical proposal

It is an object of the present application to propose a method for controlling activation/deactivation of a Radio Link Control (RLC) entity, a base station and a user equipment.

A first aspect of the present application provides a method of controlling a radio link control, RLC, entity of a user equipment, the user equipment operating in a primary network, comprising: transmitting RLC entity activation/deactivation signaling to the user equipment; receiving a report message indicating an RLC entity status of the user equipment, the user equipment responding to the RLC entity activation/deactivation signaling to activate an RLC entity; and updating an activation state of the RLC entity of the user equipment according to the report message.

In an embodiment of the present application, the method further comprises determining a delay level of the data packet based on the quality of service QoS information.

In an embodiment of the present application, the method further comprises: transmitting the RLC entity activation/deactivation signaling to the secondary network node when the delay level of the data packet meets the X2/Xn interface delay; and forwarding a report message to the secondary network node.

In an embodiment of the present application, the method further comprises: the RLC entity activation/deactivation signaling is transmitted to the secondary network node over an X2/Xn interface.

In an embodiment of the present application, the method further comprises: and simultaneously transmitting the RLC entity activation/deactivation signaling to the user equipment and the auxiliary network node.

In an embodiment of the present application, the method further comprises transmitting the RLC entity activation/deactivation signaling to the user equipment over a Uu interface.

In an embodiment of the present application, the RLC entity activation/deactivation signaling is in the form of a medium access control component MAC CE.

In an embodiment of the present application, the RLC entity activation/deactivation signaling is in the form of a MAC entity bitmap.

In an embodiment of the present application, the RLC entity activation/deactivation signaling is in the form of a radio bearer RB.

In an embodiment of the present application, the number of RLC entities of the user equipment corresponding to a radio bearer is less than 5.

In an embodiment of the present application, the RLC entity is hosted in a main unit group MCG and a secondary unit group SCG, and the main network node is configured in the main unit group, and the secondary network node is configured in the secondary unit group.

In an embodiment of the present application, the user equipment, the primary unit group and the secondary unit group are in a dual connectivity DC architecture and a carrier aggregation CA architecture.

In an embodiment of the present application, the user equipment is in an rrc_connected state with both the primary network node and the secondary node.

In an embodiment of the present application, the user equipment configures a split data radio bearer, DRB.

In an embodiment of the present application, the RLC entity activation/deactivation signaling includes a configuration of duration.

In an embodiment of the present application, the method further comprises: receiving a timer expiration report message from the user equipment, the expiration report message indicating an active state of the RLC entity of the user equipment when the timer of the user equipment expires within a duration; and updating the activation state of the RLC entity of the user equipment according to the timer expiration report message.

In an embodiment of the present application, the method further comprises: transmitting a modified RLC entity activation/deactivation signaling to the user equipment; receiving the timer restart report message from the user equipment, the timer restart report message indicating that the user equipment activates/deactivates an activation state of the RLC entity in response to a modified RLC entity activation/deactivation signaling when the timer is restarted before the duration is reached; and updating the activation state of the RLC entity of the user equipment according to the timer restart report message.

In an embodiment of the present application, the primary network node is a base station, and the primary network node is in a dual connectivity DC architecture, or a carrier aggregation CA architecture, or a combination of dual connectivity DC architecture and carrier aggregation CA architecture with the user equipment.

In an embodiment of the present application, the configuration further comprises a separate Data Radio Bearer (DRB) ID, RLC ID, operations related to activation/deactivation of RLC entities.

In an embodiment of the present application, the split data radio bearer is configured for the user equipment.

In an embodiment of the present application, the user equipment is in an rrc_connected state with the primary network node.

In an embodiment of the present application, the method further comprises: and sending the RLC entity activation/deactivation signaling to the user equipment periodically.

In an embodiment of the present application, the information carried by the RLC entity activation/deactivation signaling includes duration, split data radio bearer DRB ID, RLC ID, operation associated with activation/deactivation of the RLC entity, and number of periodicity.

A second aspect of the present application provides a network node. The network node includes a transceiver and a processor. The processor is electrically connected with the transceiver and configured to perform operations comprising: transmitting RLC entity activation/deactivation signaling to the user equipment; receiving a report message indicating an RLC entity status of the user equipment, the user equipment responding to the RLC entity activation/deactivation signaling to activate an RLC entity; and updating an activation state of the RLC entity of the user equipment according to the report message.

In an embodiment of the present application, the operations further comprise determining a delay level of the data packet based on the quality of service QoS information.

In an embodiment of the present application, the operations further include: transmitting the RLC entity activation/deactivation signaling to the secondary network node when the delay level of the data packet meets the X2/Xn interface delay; and forwarding a report message to the secondary network node.

In an embodiment of the present application, the operations further include: the RLC entity activation/deactivation signaling is transmitted to the secondary network node over an X2/Xn interface.

In an embodiment of the present application, the operations further include: and simultaneously transmitting the RLC entity activation/deactivation signaling to the user equipment and the auxiliary network node.

In an embodiment of the present application, the operations further comprise transmitting the RLC entity activation/deactivation signaling to the user equipment over a Uu interface.

In an embodiment of the present application, the operations further include: receiving a timer expiration report message from the user equipment, the expiration report message indicating an active state of the RLC entity of the user equipment when the timer of the user equipment expires within a duration; and updating the activation state of the RLC entity of the user equipment according to the timer expiration report message.

In an embodiment of the present application, the operations further include: transmitting a modified RLC entity activation/deactivation signaling to the user equipment; receiving the timer restart report message from the user equipment, the timer restart report message indicating that the user equipment activates/deactivates an activation state of the RLC entity in response to a modified RLC entity activation/deactivation signaling when the timer is restarted before the duration is reached; and updating the activation state of the RLC entity of the user equipment according to the timer restart report message.

In an embodiment of the present application, the operations further include: and sending the RLC entity activation/deactivation signaling to the user equipment periodically.

A third aspect of the present application provides a method for controlling an entity radio link control, RLC, of a user equipment, comprising: the user equipment receives RLC entity activation/deactivation signaling from the primary network node; the user equipment activating/deactivating an RLC entity in response to the RLC entity activation/deactivation signaling; and sending a report message from the user equipment to the primary network node, the report message indicating an active state of an RLC entity of the user equipment.

In an embodiment of the present application, the method further comprises: when the delay level of the data packet accords with the delay of the X2/Xn interface, receiving an RLC entity activation/deactivation signaling from an auxiliary network node, wherein the RLC entity activation/deactivation signaling is forwarded to the auxiliary network node by the main network node through the X2/Xn interface; and activating/deactivating the RLC entity according to RLC entity activation/deactivation signaling from the primary network node or the secondary network node.

In an embodiment of the present application, the method further comprises: RLC entity activation/deactivation signaling is received from the primary network node or the secondary network node over a Uu interface.

In an embodiment of the present application, the method further comprises starting a timer of the user equipment upon receiving the RLC entity activation/deactivation signaling.

In an embodiment of the present application, the method further comprises: restoring an active state of the RLC entity of the user equipment when the timer reaches a duration; and sending the timer expiration report message to the primary network node, the timer expiration report message indicating an active state of an RLC entity of the user equipment.

In an embodiment of the present application, the method further comprises: restarting the timer of the user equipment after receiving a modified RLC entity activation/deactivation signal until a duration is reached; activating/deactivating RLC entities according to the modified RLC entity activation/deactivation signaling from the primary network node; and sending a timer restart report message to the primary network node, the timer restart report message indicating an active state of an RLC entity of the user equipment.

In an embodiment of the present application, the method further comprises: reporting messages are periodically sent from the user equipment to a primary network node, the reporting messages indicating an activity state of the RLC entity of the user equipment.

A fourth aspect of the present application provides a user equipment. The user equipment includes a transceiver and a processor. The processor is electrically connected with the transceiver and configured to perform operations comprising: receiving RLC entity activation/deactivation signaling from a primary network node; activating/deactivating an RLC entity in response to the RLC entity activating/deactivating signaling; and sending a report message to the primary network node, the report message indicating an activity state of an RLC entity of the user equipment.

In an embodiment of the present application, the operations further include: when the delay level of the data packet accords with the delay of the X2/Xn interface, receiving an RLC entity activation/deactivation signaling from an auxiliary network node, wherein the RLC entity activation/deactivation signaling is forwarded to the auxiliary network node by the main network node through the X2/Xn interface; and activating/deactivating the RLC entity according to RLC entity activation/deactivation signaling from the primary network node or the secondary network node.

In an embodiment of the present application, the operations further include: RLC entity activation/deactivation signaling is received from the primary network node or the secondary network node over a Uu interface.

In an embodiment of the present application, the user equipment is in an rrcconnectioned state with both the primary network node and the secondary node.

In an embodiment of the present application, the operations further comprise starting a timer of the user equipment upon receiving the RLC entity activation/deactivation signaling.

In an embodiment of the present application, the operations further include: restoring an active state of the RLC entity of the user equipment when the timer reaches a duration; and sending the timer expiration report message to the primary network node, the timer expiration report message indicating an active state of an RLC entity of the user equipment.

In an embodiment of the present application, the operations further include: restarting the timer of the user equipment after receiving a modified RLC entity activation/deactivation signal until a duration is reached; activating/deactivating RLC entities according to the modified RLC entity activation/deactivation signaling from the primary network node; and sending a timer restart report message to the primary network node, the timer restart report message indicating an active state of an RLC entity of the user equipment.

In an embodiment of the present application, the operations further include: reporting messages are periodically sent from the user equipment to a primary network node, the reporting messages indicating an activity state of the RLC entity of the user equipment.

A fifth aspect of the present application provides a chip that may include a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is installed to perform the methods disclosed herein.

A sixth aspect of the present application provides a computer-executable instruction that may be programmed and stored in a non-transitory computer-readable medium. The non-transitory computer readable medium, when loaded into a computer, instructs the processor of the computer to perform the methods disclosed herein. The non-transitory computer readable medium may include at least one of the following readable media: hard disks, CD-ROMs, optical storage devices, magnetic storage devices, read-only memory, programmable read-only memory, erasable programmable read-only memory, EPROM, electrically erasable programmable read-only memory, and flash memory.

The methods disclosed herein may be programmed as a computer program product that causes a computer to perform the methods disclosed herein.

The methods disclosed herein may be programmed as a computer program that causes a computer to perform the methods disclosed herein.

Advantageous effects

The embodiments of the present application provide a method for controlling activation/deactivation of a Radio Link Control (RLC) entity, a base station, and a user equipment, for solving the problem that a network node cannot control an active/inactive state of an RLC entity of a user equipment belonging to another network node when a DRB applied in a combination of a DC architecture and a CA architecture is configured with PDCP duplication of more than two RLC entities. However, the present application proposes that the RLC entity activation/deactivation configuration may be sent by one network node to the CN and forwarded to another network node, which then sends the configuration to the UE, or the primary node may send an activation/deactivation signal to the secondary node, which then forwards the RLC entity activation/deactivation signal to the UE. Furthermore, for services with high latency requirements, the network node sends RLC entity activation/deactivation signaling directly to the UE over the Uu interface. For data packets that may meet the delay requirement for transmissions that introduce an X2/Xn delay, the network node transmits RLC entity activation/deactivation signaling to the UE over the Uu interface and other network nodes. Due to the introduction of the X2/Xn interface delay, it can be used for services that do not require high delay requirements. Therefore, the present application can effectively activate/deactivate the devices of the RLC entity.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present utility model, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a system according to an embodiment of the present application.

Fig. 2 shows a schematic diagram of a master node acting as a primary network node according to an embodiment of the present application.

Fig. 3 shows a schematic diagram of an auxiliary node acting as a primary network node according to another embodiment of the present application.

Fig. 4 shows the options of MCG, SCG and network side protocol side for split bearers in a multi-radio frequency (MR) -DC with 5GC according to an embodiment of the present application.

Fig. 5 illustrates the radio protocol architecture of MCG, SCG and split bearers in MR-DC from the UE perspective.

Fig. 6 shows a flowchart of a control method of activation/deactivation of a Radio Link Control (RLC) entity according to an embodiment of the present application.

Fig. 7 is a system schematic diagram illustrating another embodiment according to the present application.

Fig. 8 shows a flowchart of a method of controlling activation/deactivation of a Radio Link Control (RLC) entity according to another embodiment of the present application.

Fig. 9 shows a timing diagram of an RLC entity according to another embodiment of the present application.

Fig. 10 is a block diagram of a system for wireless communication according to an embodiment of the present application.

Detailed Description

The embodiments of the present application describe in detail technical matters, structural features, achieving objects and effects with reference to the accompanying drawings. In particular, the terminology used in the embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure.

3GPP NR IIOT background

In the revision of NR IIoT RP-192324, the detailed goal of NR PDCP duplication enhancement is:

PDCP duplication is specified using RRC for up to 4 RLC entities configured in an architectural combination (including CA and NR-DC combined with CA RAN2, RAN 3).

A mechanism to specify and dynamically control how a subset of a set or configured RLC entities or branches are used for PDCP duplication RAN2, RAN 3.

Lower priority targets: enhanced functionality is specified by enhanced PDCP duplication activation/deactivation mechanisms (e.g., based on MAC CE or based on UE configurable criteria) to achieve more resource efficient PDCP duplication, provided that the increase in complexity is reasonable, selective duplication per packet may also be considered. RAN 2.

Enhanced functionality is specified to enable more efficient DL PDCP duplication without affecting the UE, provided that the benefit can be acknowledged with reasonable complexity. RAN 3.

Specifying enhanced functionality to address the potential impact of higher layer multi-connectivity according to SA2 schedule and request RAN 3.

For the content of release 16 (Rel-16) of 3GPP, up to 4 RLC entities can be configured for DRBs that utilize DC and CA architecture, thus allowing different numbers of RLC entity combinations to be hosted in MCG and SCG.

On RANs 2#107, the following protocol is achieved, and duplicate control MAC CE (using new LCID) is introduced in release 16 of 3GPP to dynamically control the RLC entity configured in the active (deactivated) uplink of the RLC entity for PDCP duplication:

RAN2#107 protocol:

the number of copies generated is equal to the number of active RLC entities, i.e. one copy per branch/RLC entity, the active/inactive state being determined by the MAC CE.

The network provides only one LCH cell restriction configuration per LCH in RRC, as in release 15 of 3 GPP. The change of LCH cell restriction configuration can only be done by RRC.

At PDCP duplication, the application of configured element restrictions will not change dynamically when PDCP duplication beyond release 15 of 3GPP is activated or deactivated.

The MAC CE signaling structure is:

a. DRB signaling each with associated RLC entity activity status, or

b. All DRB's with associated RLC entity activity status for each DRB

The new LCID is used to control the MAC CE of PDCP duplication.

Whichever MAC CE structure (listed in the RAN2#107 protocol) the RAN2 will employ, the RLC entity activation/deactivation signaling will include duplicate active states corresponding to all RLC entities configured for DRBs, and thus belong to both MCG and SCG in DC or DC and CA scenarios.

RAN2#108 mentions that network coordination facilitates PDCP duplication of release 16 of 3GPP under DC and CA architecture, which is a problem how nodes coordinate RLC entity activation/deactivation with each other.

RAN2#108 protocol:

network coordination facilitates PDCP duplication in the uplink in NR-DC/CA architecture.

Therefore, a mechanism for the network to coordinate RLC entity activation/deactivation, i.e., PDCP duplication, is needed.

Related protocols for TSN accurate reference timing delivery

3gpp ran2#106 protocol:

dynamic network control of DRB replication is performed by MAC CE.

Control which configured RLC entities are active through MAC CE, network.

3gpp ran2#107 protocol:

The network provides only one LCH cell restriction configuration per LCH in RRC, as specified by release 15 of 3 GPP. The change of LCH cell restriction configuration can only be done by RRC.

The MAC CE signaling structure is:

a. DRB signaling each with associated RLC entity activity status, or

b. All DRB's with associated RLC entity activity status for each DRB

New LCID is used for 3GPP release 16 MAC CE to control PDCP duplication.

3gpp ran2#108 protocol:

3GPP RAN2#110-e protocol:

the UE only follows the received MAC CE even if the RLCi field belongs to another node. No specification change is required.

Only NR supports PDCP duplication with more than two RLC entities. Clarification is required in 37.340 and 38.331.

Dc+ca repeat in clear 38.300. A 3+1 repetition scheme also needs to be considered. CA repetition may require clarification.

1. Related art

According to the 3GPP release 16 conference, the following conclusions can be drawn:

NR only supports PDCP duplication with more than two RLC entities

■ One PDCP entity has one main path.

■ The main path of the data PDU should not be deactivated.

■ The number of copies generated is equal to the number of active RLC entities, i.e. one copy per branch/RLC entity.

Dynamic network control of DRB replication by MAC CE

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

■ For PDCP duplication in control MAC CE format, each DRB signaling with associated RLC entity activity status should be employed in Rel-16.

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

■ R16 MAC CE is used for leg selection and on/off.

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

The network provides only one LCH cell restriction configuration per LCH in RRC.

■ The change of LCH cell restriction configuration can only be done by RRC.

■ At PDCP duplication, the configured cell limited application is not dynamically changed when PDCP duplication exceeding Rel-15 is activated or deactivated.

■ The new LCID is used to control the Rel-16 MAC CE of PDCP duplication.

Referring to fig. 1, the communication system comprises a UE 10a, a first network node 200a, a second network node 200b and a network entity device 30. The connections between the devices and the device components are shown as lines and arrows in the figures. The UE 10a may include a processor 11a, a memory 12a, and a transceiver 13a. The first network node 200a may comprise a processor 201a, a memory 202a and a transceiver 203a. The second network node 200b may comprise 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 11a, 201b, 201a, and 301, when executed, may implement the functions, processes, and/or methods provided by the embodiments. The radio interface protocol layers may be implemented in the processors 11a, 201b, 201a and 301. Various programs and information may be stored in each

memory

12a, 202b, and 302 to coordinate the operation of the connected processors. Each

transceiver

13a, 203b, 303 is coupled to a processor for transmitting and/or receiving radio signals or wired signals. The first network node 200a and the second network node 200b may be base stations, such as one of enbs, gnbs or other types of radio nodes, and may configure radio resources for the UE 10 a.

The processors 11a, 201b, 201a, 301 may include Application Specific Integrated Circuits (ASICs), other chipsets, logic circuits, and/or data processing devices. The

memory

12a, 202b, 302 may include Read Only Memory (ROM), random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. The

transceivers

13a, 203b, and 303 may include baseband circuitry and Radio Frequency (RF) circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules, procedures, functions, entities, etc. that perform the functions described herein. Modules may be stored in memory and executed by a processor. The memory may be implemented within the processor or external to the processor, as can various means known in the art can be coupled to the processor.

The network entity device 300 may be a node in the CN. The CN may include an LTE CN or 5G core (5 GC) 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) split (cup), an authentication server (AUSF), a Network Slice Selection Function (NSSF), and a network open function (NEF).

See fig. 1, 2 and 3. Fig. 2 is a schematic diagram of a master node as a primary network node according to an embodiment of the present application.

Fig. 3 shows a schematic diagram of an auxiliary node as a primary network node according to another embodiment of the present application. The first network node 200a may be a primary network node as a primary node MN located in a primary unit group MCG and the second network node 200b may be a secondary network node as a secondary node SN located in a secondary unit group SCG. The UE 10a configures a Dual Connectivity (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 architecture, and the second network node 200b is an auxiliary node. In another embodiment, the first network node 200a may be a secondary network node and the second network node 200b may be a primary network node.

Please refer to fig. 4 and 5. Fig. 4 shows the options of MCG, SCG and network side protocol side for split bearers in a multi-radio frequency (MR) -DC with 5GC according to an embodiment of the present application. Fig. 5 illustrates the radio protocol architecture of MCG, SCG and split bearers in MR-DC from the UE perspective. When the device 10a is in the rrc_connected state simultaneously with the primary network node 200a and the secondary network node 200b, a Data Radio Bearer (DRB) is established through the primary network node 200a and the secondary network node 200b and is configured for the user equipment 10 a. The UE 10a supports at most four RLC entities configured for radio bearers.

Please refer to fig. 4, 5 and 6. Fig. 6 shows a flow of a method of controlling activation/deactivation of a Radio Link Control (RLC) entity according to an embodiment of the present application. The primary network node 200a sends RLC entity activation/deactivation signaling directly to the UE 10a and sends RLC entity activation/deactivation signaling to the secondary network node 200b. As shown in fig. 4, since the Service Data Adaptation Protocol (SDAP) processes the mapping between QoS flows and data radio bearers, the primary network node 200a determines a delay level of a data packet based on quality of service (QoS) information (step 600).

For traffic with high delay requirements, the primary network node 200a sends RLC entity activation/deactivation signaling directly to the UE 10a over the Uu interface. For services where the X2/Xn interface delay satisfies the delay requirement, RLC entity activation/deactivation signaling is sent to the UE 10a over the Uu interface or/and the auxiliary network node 200b. In this embodiment, the primary network node 200a transmits RLC entity activation/deactivation signals to the UE 10a and the secondary network node 200b in no particular order in time of operation. The primary network node 200a transmits RLC entity activation/deactivation signaling to the UE 10a through the Uu interface (step 601), and then the primary network node 200a transmits RLC entity activation/deactivation signaling to the secondary network node 200b through the X2/Xn interface, as shown in step 602. In another embodiment, the network node 200a may send RLC entity activation/deactivation signaling to the secondary network node 200b as in step 602 and then to the UE 10a as in step 601. In another embodiment, the network node 200a transmits RLC entity activation/deactivation signals to both the UE 10a and the secondary network node 200b. RLC entity activation/deactivation signaling may be in any form, such as MAC CE. RLC entity activation/deactivation signaling may also be in the form of per MAC entity bitmap or per radio bearer. The RLC entity activation/deactivation signaling sent by the primary network node 200a to the UE 10a and RLC entity activation/deactivation signaling sent to the secondary network node 200b may take different forms or formats.

The secondary network node 200b forwards RLC entity activation/deactivation signaling received from the primary network node 200a to the UE 10a over the Uu interface. (step 604). RLC entity activation/deactivation signaling may be in any form, such as MAC CE.

The UE 10a may perform RLC entity activation/deactivation according to RLC entity activation/deactivation signaling received from the primary network node 200a (step 603), or the UE 10a may activate/deactivate an RLC entity belonging to a MAC entity configuration DRB corresponding to the primary network node 200a (step 605). When the primary network node 200a receives signaling for the RLC entity to activate/deactivate the split DRB (i.e., DRB 1), the UE 10a may activate/deactivate RLC0 belonging to DRB 1. The UE 10a may perform RLC entity activation/deactivation according to RLC entity activation/deactivation signaling received from the secondary network node 200b (step 605).

In another embodiment, the UE 10a may activate/deactivate RLC entities belonging to configured DRBs among MAC entities corresponding to the secondary network node 200 b. For example, if the auxiliary network node 200b acts as an auxiliary node, the UE 10a may activate/deactivate RLC1 and RLC2 belonging to DRB 1.

The UE 10a may not perform the activation/deactivation of the RLC entity until the signaling from the primary network node 200a and the secondary network node 200b is received, and then the UE 10a may activate/deactivate the RLC entity according to the RLC entity activation/deactivation signaling, including the operations shown in step 603 and step 605.

The UE 10a may generate an activity/inactivity report message of the RLC entity and then transmit the activity/inactivity report message of the RLC entity to the primary network node 200a and the secondary network node 200b. The report message includes active/inactive state information of the RLC entity after the UE 10a performs an activation/deactivation operation. The report message may be active/inactive state information for each RB, i.e., RLC entity including only a certain DRB, or the report message may be active/inactive state information for each MAC entity, i.e., RLC entity including a certain MAC entity, or the report message may be active/inactive state information for each UE 10a, including RLC entity of UE 10 a.

The UE 10a may generate a report message including state information of the RLC entity corresponding to the DRB of the MAC entity of the primary network node 200a after performing RLC entity activation/deactivation and transmit to the primary network node 200a (step 606). For example, if the report message is directed to each DRB, the report message includes status information of RLC0 of DRB1 for DRB 1.

The UE 10a may generate a report message including the status information of the RLC entity corresponding to the DRB of the MAC entity of the secondary network node 200b after performing step 605 and transmit to the secondary network node 200b (step 608). If the reporting message is directed to each DRB, then for DRB1, the reporting message includes status information for RLC1 and RLC2 of DRB 1.

The UE 10a may generate a report message including the DRB corresponding to the MAC entity of the primary network node 200a and the RLC entity of the MAC entity of the secondary network node 200b after performing both steps 603 and 605 and transmit the message to the primary network node 200a and the secondary network node 200b as shown in steps 606 and 608. If the report message is directed to each DRB, for DRB1, the report message should include status information of RLC0, RLC1, and RLC2 of DRB 1.

Report messages received by the primary network node 200a and the secondary network node 200b from the UE 10a may be shared between the primary network node 200a and the secondary network node 200b over the X2/Xn interface, as shown in steps 608 and 610.

The primary network node 200a and the secondary network node 200b may update the status information according to RLC entity activity/inactivity report messages received from the UE 10 a. The status information may be each MAC entity, for example, the status information includes RLC0 status information and RLC1 of DRB0, RLC0 status information of DRB 1. The status information may be status information of each UE 10a, for example, the status information includes RLC0 and RLC1 of DRB0, RLC1 and RLC2 of DRB 0.

The secondary network node 200b may maintain state information of the RLC entity of the UE 10a. The status information may be status information providing each MAC entity, for example, the status information includes status information of RLC1 and status information of RLC2 of DRB 1. The status information may be status information of each UE 10a, for example, status information including RLC0 and RLC1 of DRB0, RLC1, and RLC2 of DRB 1.

The primary network node 200a and the secondary network node 200b may simultaneously maintain RLC entities of the UE 10a. The status information may be status information of each UE 10a, for example, status information including RLC0 and RLC1 of DRB0, RLC1, and RLC2 of DRB 1.

The present embodiment also introduces an indicator of RLC entity status information to indicate whether RLC entity status information is available. When the primary network node 200a transmits an RLC entity activation/deactivation signal to the UE 10a, it sets the value of the indicator to "unavailable". After the UE 10a receives the performing RLC entity activation/deactivation information from the primary network node 200a and via the secondary network node 200b, an acknowledgement message (which may include RLC entity active/inactive status information) may be sent to the primary network node 200a directly over the Uu interface or through the secondary network node 200b, and the primary network node 200a may set the value of the indicator to "available". An indicator is introduced to indicate whether the delay introduced by the X2/Xn interface can meet the requirements for transmitting data packets. If the delay introduced by the X2/Xn interface can meet the requirements, the value of the indicator is set to "available" and RLC entity activation/deactivation signaling is transmitted to the UE 10a over the Uu interface and the auxiliary node. RLC entity activation/deactivation signaling is transmitted to the UE 10a over the Uu interface. If the delay introduced by the X2/Xn interface is not satisfactory, the indicator is set to "unavailable" and RLC entity activation/deactivation signaling is transmitted directly to the UE 10a. The "available", "unavailable" values of the indicators may be the numbers "1", "0" or any other form.

The method disclosed in the embodiments of the present application is that the delay requirement for the data packet may be satisfied by an activation/deactivation operation introducing an X2/Xn interface delay, and RLC entity activation/deactivation signaling may be sent from the primary network node 200a to the secondary network node 200b through the X2/Xn interface. The secondary network node 200b then forwards RLC entity activation/deactivation signaling to the UE 10a over the Uu interface. Upon receiving the RLC entity activation/deactivation signaling from the primary network node 200a, the UE 10a activates/deactivates the RLC entity in accordance with the RLC entity activation/deactivation signaling content. The UE 10a then generates and sends an RLC entity activity/inactivity report message to the primary network node 200a. Based on the RLC entity status information received from the UE 10a, the primary network node 200a updates the local status information of the RLC entity. Or after receiving the RLC entity activation/deactivation signaling from the secondary network node 200b, the UE 10a should activate/deactivate the RLC entity according to the RLC entity activation/deactivation signaling content. The UE 10a then generates and sends an RLC entity activity/inactivity report message to the secondary network node 200b. The secondary network node 200b then updates the local state information of the RLC entity according to the RLC entity report message received from the UE 10a. Meanwhile, the auxiliary network node 200b forwards the RLC entity report message to the primary network node 200a through the X2/Xn interface, and the primary network node 200a updates the local state information of the RLC entity accordingly.

Example 2

Referring to fig. 7, fig. 7 shows a schematic diagram of a communication system comprising a UE 10, a network node 200 and a network entity device 30 according to another embodiment of the present application. The UE 10 is configured with a Dual Connectivity (DC) architecture, or a Carrier Aggregation (CA) architecture, or a combination of DC and CA architectures. The UE 10 may include a processor 11, a memory 12, a timer 14, and a transceiver 13. Network node 200 may include a processor 201, a memory 202, and a transceiver 203. The network entity device 300 may include a processor 301, a memory 302, and a transceiver 303. Each

processor

11, 201, and 301, when executed, may implement the functions, processes, and/or methods provided by the embodiments. The radio interface protocol layer may be implemented in the

processor

11, 201, 301. Various programs and information may be stored in each

memory

12, 202, and 302 to coordinate the operation of the connected processors. Each transceiver 13, 203, 303 is coupled to a processor for transmitting and/or receiving radio signals or wired signals. Each network node 200 may be a base station, such as one of an eNB, a gNB, or other type of radio node, and may configure radio resources for the UE 10.

An Application Specific Integrated Circuit (ASIC), other chipset, logic circuit, and/or data processing device may be included in each

processor

11, 201, 301. Each

memory

12, 202, and 302 may include Read Only Memory (ROM), random Access Memory (RAM), flash memory, memory cards, storage media, and/or other storage devices. Each

transceiver

13a, 203, 303 may include baseband circuitry and Radio Frequency (RF) circuitry that processes radio frequency signals. When the embodiments are implemented in software, the techniques described herein may be implemented with modules, procedures, functions, entities, and so on that perform the functions described herein. Modules may be stored in memory and executed by a processor. The memory may be implemented within the processor or external to the processor, in which case it can be communicatively coupled to the processor via various means as is known in the art.

Please refer to fig. 7 and 8. Fig. 8 shows a flowchart of a method of controlling activation/deactivation of a Radio Link Control (RLC) entity according to another embodiment of the present application. A Data Radio Bearer (DRB) is established and configured by the network node 200 for the user equipment 10 when the user equipment 10 is in an rrc_connected state with the network node 200. The network node 200 and the user equipment 10 are in 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. The UE 10 may support up to four RLC entities configured for radio bearers.

The network node 200 transmits an RLC entity activation/deactivation signal to the UE 10 (step 801). The configuration carried by the RLC entity activation/deactivation signaling includes duration, data Radio Bearer (DRB) ID, RLC ID, operations related to RLC entity activation/deactivation. The DRB ID contained in the configuration may identify a DRB in the CA architecture, an MCG DRB, an SCG DRB, or a split DRB in the DC architecture, or a combination of DC and CA architectures. Further, the duration is used to set the value of the timer 14. The timer 14 may be configured for each radio bearer.

The UE 10 may activate/deactivate the RLC entity according to RLC entity activation/deactivation signaling received from the base station and may set the duration of the timer 14 and start the timer 14 (step 802). The active/inactive state of the RLC entity should remain unchanged until the timing of the timer 14 ends.

The UE 10 may report active/inactive status information of the RLC entity to the base station (step 803). When the timer 14 expires, the UE 10 resumes the state of the RLC entity (step 804). The UE 10 may restore the RLC entity to a state before the RLC entity activation/deactivation signal performs RLC entity activation/deactivation, or the UE 10 may restore the RLC entity to a default state, which may be an active or inactive state.

The UE 10 may report a timer expiration report message to the network node 200 (step 805). The timer expiration report message indicates an active/inactive state of the RLC entity of the user equipment when the timer 14 expires within the duration.

If the network node 100 transmits modified RLC entity activation/deactivation signaling to the UE 10 of the same DRB before reaching the duration (step 806), the UE 10 performs RLC entity activation/deactivation signaling according to the modified RLC entity activation/deactivation signaling and restarts the timer 14 (step 807). The UE 10 may then send a timer restart report message to the network node 200 indicating a modification of the active state of the RLC entity of the user equipment (step 809). The network node 200 updates the active state of the RLC entity of the user equipment based on the timer restart report message.

The embodiment of the invention also discloses a method which discloses that the RLC entity can be activated/deactivated within a specified duration through the RLC entity activation/deactivation configuration. The RLC entity activation/deactivation configuration may include DRBID, RLC ID, activation/deactivation operation, duration. Upon receipt of the RLC entity activation/deactivation signal, the UE 10 should activate/deactivate the RLC entity in the RLC entity activation/deactivation configuration and simultaneously start the timer 14. The UE 10 then reports the active/inactive status information of the RLC entity to the network node 200. When the timing of the timer 14 arrives, the UE 10 may restore the RLC entity to an active/inactive state or a default state prior to the activation/deactivation operation. If modified RLC entity activation/deactivation signaling is received from the network node 200 before the timer 14 has not reached the timing time, the UE 10 may perform the indicated latest configuration and restart the timer 14 and then report RLC entity status information to the network node 200.

2. Example 3

See fig. 7, 8 and 9. Fig. 9 shows a timing diagram of an RLC entity according to another embodiment of the present application. This embodiment discloses a method that reveals that RLC entity activation/deactivation configuration may allow periodic activation/deactivation of RLC entities. The RLC entity activation/deactivation configuration may include parameters such as DRB ID, RLC ID, activation/deactivation operation, periodicity, active/inactive duration, number of times, etc.

The UE 10 may periodically activate/deactivate the RLC entity according to the RLC entity activation/deactivation configuration received from the network node 200. The UE 10 periodically activates/deactivates the RLC entity in this configuration for a period of time and then resumes the original RLC entity state. If the RLC entity activation/deactivation configuration sets the number or duration of activation/deactivation operations, the UE 10 may perform activation/deactivation of the RLC entity periodically until the timer 14 reaches the set duration or reaches the configured number. Or the UE 10 may perform activation/deactivation periodically until new signaling of the DRB is received.

As shown in fig. 9, after receiving the RLC entity activation signal, the UE 10 may at time t ₀ The duration of activation of RLC entity RLCi is t _active Then at duration t _active At the time t when it expires ₁ Deactivating it. Then at duration T _p Upon expiration, at time t ₂ Re-activating RLC entity RLCi and pressing T _p Is repeated for a period of time. Duration t _{active and active} T _p Is a parameter of the configuration. The parameters may be different for each RLC entity or each DRB. That is, the parameters may be the same or different for different RLC entities.

The UE 10 may report active/inactive status information of the RLC entity to the network node 200. Reporting may be performed periodically with a specified period or each time the RLC entity status is changed.

Fig. 10 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present application. Embodiments of the present application may use any suitably configured hardware and/or software for implementation into system 700. The system 700 includes Radio Frequency (RF) circuitry 710, baseband circuitry 720, processing unit 730, memory 740, display 750, camera 760, sensor 770, and input/output (I/O) interface 780.

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

Baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor may comprise a baseband processor. The baseband circuitry may handle various radio control functions that may communicate with one or more radio networks through the RF circuitry. Radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency conversion, and the like. In some embodiments, baseband circuitry may provide communications compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with 5G NR, LTE, evolved Universal Terrestrial Radio Access Network (EUTRAN), and/or other Wireless Metropolitan Area Networks (WMANs), wireless Local Area Networks (WLANs), wireless Personal Area Networks (WPANs). An embodiment in which the baseband circuitry is configured to support radio communications for more than one wireless protocol may be referred to as a multimode baseband circuitry. In various embodiments, baseband circuitry 720 may include circuitry to operate with signals at baseband frequencies. For example, in some embodiments, the baseband circuitry may include circuitry that operates with signals having intermediate frequencies, which are between baseband frequencies and radio frequencies.

The 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, RF circuit 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 intermediate frequencies, which are between baseband frequencies and radio frequencies.

In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the UE, eNB, or gNB may be embodied in whole or in part in one or more RF circuitry, baseband circuitry, 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 memory that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in or functions associated with one or more software or firmware modules. In some embodiments, part or all of the constituent components of the baseband circuitry, processing unit, and/or memory/storage may be implemented together on a system on a chip (SOC).

Memory 740 may be used to load and store data and/or instructions, for example, for the system. The memory for one embodiment may include any combination of suitable volatile memory, such as Dynamic Random Access Memory (DRAM), and/or non-volatile memory, such as flash memory. In various embodiments, I/O interface 780 may include one or more user interfaces designed to enable a user to interact with the system and/or peripheral component interfaces designed to enable interaction with peripheral components of the system. The user interface may include, but is not limited to, a physical keyboard or keypad, a touchpad, a speaker, a microphone, and the like. Peripheral component interfaces may include, but are not limited to, non-volatile memory ports, universal Serial Bus (USB) ports, audio jacks, and power interfaces.

In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, gyroscopic sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of or interact with baseband circuitry and/or RF circuitry to communicate with components of a positioning network, such as Global Positioning System (GPS) satellites. In various embodiments, display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, system 700 may be a mobile computing device such as, but not limited to, a notebook computing device, a tablet computing device, a smart phone, and the like. In different embodiments, the system may have more or less components, and/or different architectures. The methods described herein may be implemented as computer programs, where appropriate. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

Embodiments of the present application are a combination of techniques/procedures that may be employed in the 3GPP specifications to create the end product.

Those of ordinary skill in the art will appreciate that each of the elements, algorithms, and steps described and disclosed in the embodiments of the present application are implemented using software or a combination of software for both computer and electronic hardware. Whether a function is implemented in hardware or software depends upon the application conditions and design requirements of the technical program. Those having ordinary skill in the art may implement the functionality of each particular application in different ways without such implementation being beyond the scope of the present application. It will be appreciated by those of ordinary skill in the art that since the operation of the above-described systems, devices and units are substantially identical, he/she may refer to the operation of the systems, devices and units in the above-described embodiments. For ease of description and simplicity, these workflows will not be described in detail.

It will be appreciated that the systems, devices, and methods disclosed in embodiments of the present application may be implemented in other ways. The above-described embodiments are merely exemplary. The division of units is based solely on logic functions, while other divisions exist in the implementation. Multiple units or components may be combined or integrated into another system. It is also possible to omit or skip certain features. In another aspect, the mutual coupling, direct coupling, or communicative coupling shown or discussed may be through some ports, devices, or units, which may be operated indirectly or in communication through electrical, mechanical, or other means.

The units that are separate components for explanation are physically separate or may not be physically separate. The units used for display may or may not be physical units, i.e. located in one place or distributed over a plurality of 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 in one processing unit, physically separate, or integrated in one processing unit having two or more units.

If the software functional unit is implemented and used and sold as a product, it may be stored in a readable storage medium of a computer. Based on this understanding, the technical solutions presented in the present application may be implemented substantially or partly in the form of a software product. Alternatively, a portion of the technical program that facilitates conventional techniques may be implemented as a software product. The software product in the computer is stored in a storage medium comprising a plurality of commands for running all or part of the steps of the computing device (such as a personal computer, server or network device) disclosed by embodiments of the present application. Storage media include USB magnetic disks, removable hard disks, read-only memory (ROM), random Access Memory (RAM), floppy disks, or other types of media capable of storing program code.

The foregoing description of the embodiments is only used to facilitate the understanding of the method and core ideas of the present application; meanwhile, those skilled in the art will have variations in the specific embodiments and application scope in light of the ideas of the present application, and the present description should not be construed as limiting the present application in view of the above.

Claims

1. A method of controlling a radio link control, RLC, entity of a user equipment, the user equipment operating in a primary network, comprising:

transmitting RLC entity activation/deactivation signaling to the user equipment;

receiving a report message indicating an RLC entity status of the user equipment, the user equipment responding to the RLC entity activation/deactivation signaling to activate/deactivate the RLC entity; and

and updating the activity state of the RLC entity of the user equipment according to the report message.

2. The method as recited in claim 1, further comprising:

the delay level of the data packet is determined based on the quality of service QoS information.

3. The method as recited in claim 2, further comprising:

transmitting the RLC entity activation/deactivation signaling to the secondary network node when the delay level of the data packet meets the X2/Xn interface delay; a kind of electronic device with high-pressure air-conditioning system

Forwarding a reporting message to the secondary network node.

4. A method according to claim 3, further comprising:

the RLC entity activation/deactivation signaling is transmitted to the secondary network node over an X2/Xn interface.

5. A method according to claim 3, further comprising:

and simultaneously transmitting the RLC entity activation/deactivation signaling to the user equipment and the auxiliary network node.

6. The method as recited in claim 1, further comprising:

transmitting the RLC entity activation/deactivation signaling to the user equipment over a Uu interface.

7. The method according to claim 1, characterized in that the RLC entity activation/deactivation signaling is in the form of medium access control component MAC CE.

8. The method of claim 7 wherein the RLC entity activation/deactivation signaling is in the form of a MAC entity bitmap.

9. The method of claim 7 wherein the RLC entity activation/deactivation signaling is in the form of radio bearer, RB.

10. The method of claim 1, wherein the number of RLC entities corresponding to the user equipment for a radio bearer is less than 5.

11. The method according to claim 10, characterized in that the RLC entity is hosted in a main unit group MCG and a secondary unit group SCG, and the main network node is configured in the main unit group, and the secondary network node is configured in the secondary unit group.

12. The method of claim 11, wherein the user equipment, the primary unit group, and the secondary unit group are in a dual connectivity DC architecture and a carrier aggregation CA architecture.

13. A method according to claim 3, wherein the user equipment is in an rrc_connected state with both the primary network node and the secondary node.

14. The method of claim 1, wherein the user equipment configures a split data radio bearer, DRB.

15. The method of claim 1, wherein the RLC entity activation/deactivation signaling comprises a configuration of duration.

16. The method of claim 15, further comprising:

receiving a timer expiration report message from the user equipment, the expiration report message indicating an active state of the RLC entity of the user equipment when the timer of the user equipment expires within a duration; and

And updating the activity state of the RLC entity of the user equipment according to the timer expiration report message.

17. The method of claim 15, further comprising:

transmitting a modified RLC entity activation/deactivation signaling to the user equipment;

receiving the timer restart report message from the user equipment, the timer restart report message indicating that when the timer is restarted before the duration is reached, the user equipment responds to modified RLC entity activation/deactivation signaling to activate/deactivate an active state of the RLC entity; and

and updating the active state of the RLC entity of the user equipment according to the timer restart report message.

18. The method of claim 15, wherein the primary network node is a base station and the primary network node is in a dual connectivity DC architecture, or a carrier aggregation CA architecture, or a combination of dual connectivity DC architecture and carrier aggregation CA architecture with the user equipment.

19. The method of claim 15 wherein the configuring further comprises separating a Data Radio Bearer (DRB) ID, an RLC ID, operations related to activation/deactivation of an RLC entity.

20. The method of claim 19, wherein the split data radio bearer is configured for the user equipment.

21. The method of claim 15, wherein the user equipment is in an rrc_connected state with the primary network node.

22. The method as recited in claim 1, further comprising:

and sending the RLC entity activation/deactivation signaling to the user equipment periodically.

23. The method of claim 22 wherein the information carried by the RLC entity activation/deactivation signaling includes a duration, a separate data radio bearer DRB ID, an RLC ID, an operation associated with activation/deactivation of the RLC entity, and a number of periodicity.

24. A network node, comprising:

a transceiver; and

a processor electrically connected to the transceiver and configured to perform operations comprising:

receiving a report message indicating an RLC entity status of the user equipment, the user equipment responding to the RLC entity activation/deactivation signaling to activate an RLC entity; and

25. The network node of claim 24, wherein the operations further comprise:

the delay level of the data packet is determined based on quality of service (QoS) information.

26. The network node of claim 25, wherein the operations further comprise:

transmitting the RLC entity activation/deactivation signaling to the secondary network node when the delay level of the data packet meets an X2/Xn interface delay; a kind of electronic device with high-pressure air-conditioning system

Forwarding a reporting message to the secondary network node.

27. The network node of claim 26, wherein the operations further comprise:

28. The network node of claim 26, wherein the operations further comprise:

29. The network node of claim 24, wherein the operations further comprise:

30. The network node according to claim 24, characterized in that the RLC entity activation/deactivation signaling is in the form of medium access control component MAC CE.

31. The network node of claim 30, wherein the RLC entity activation/deactivation signaling is in the form of a MAC entity bitmap.

32. The network node according to claim 30, characterized in that the RLC entity activation/deactivation signaling is in the form of radio bearer, RB.

33. The network node according to claim 24, characterized in that the number of RLC entities of the user equipment corresponding to a radio bearer is less than 5.

34. The network node of claim 33, the RLC entity is hosted in a main unit group MCG and a secondary unit group SCG, and the main network node is configured in the main unit group, and the secondary network node is configured in the secondary unit group.

35. The network node of claim 34, wherein the user device, the primary unit group, and the secondary unit group are in a dual connectivity DC architecture and a carrier aggregation CA architecture.

36. The network node of claim 26, wherein the user device is in an rrc_connected state with both the primary network node and the secondary node.

37. The network node of claim 24, wherein the user equipment configures a split data radio bearer, DRB.

38. The network node according to claim 1, characterized in that the RLC entity activation/deactivation signaling comprises a configuration of duration.

39. The network node of claim 38, wherein the operations further comprise:

40. The network node of claim 38, wherein the operations further comprise:

41. The network node of claim 38, wherein the primary network node is a base station and the primary network node is in a dual connectivity DC architecture, or a carrier aggregation CA architecture, or a combination of dual connectivity DC architecture and carrier aggregation CA architecture with the user equipment.

42. The network node of claim 38, wherein the configuration further comprises operations relating to separate Data Radio Bearer (DRB) IDs, RLC IDs, and activation/deactivation of RLC entities.

43. The network node of claim 42, wherein the split data radio bearer is configured for the user equipment.

44. The network node of claim 38, wherein the user device is in an rrc_connected state with the primary network node.

45. The network node of claim 24, wherein the operations further comprise:

RLC entity periodically transmits an activation/deactivation signal to the user equipment.

46. The network node of claim 45, wherein the information carried by the RLC entity activation/deactivation signaling includes a duration, a separate data radio bearer, DRB ID, an RLC ID, an operation associated with activation/deactivation of the RLC entity, and a number of periodicity.

47. A method for controlling an physical radio link control, RLC, of a user equipment, comprising:

the user equipment receives RLC entity activation/deactivation signaling from the primary network node;

the user equipment activating/deactivating an RLC entity in response to the RLC entity activation/deactivation signaling; and

a report message is sent from the user equipment to the primary network node, the report message indicating an active state of an RLC entity of the user equipment.

48. The method as recited in claim 47, further comprising:

when the delay level of the data packet accords with the delay of the X2/Xn interface, receiving an RLC entity activation/deactivation signaling from an auxiliary network node, wherein the RLC entity activation/deactivation signaling is forwarded to the auxiliary network node by the main network node through the X2/Xn interface; and

activating/deactivating the RLC entity according to RLC entity activation/deactivation signaling from the primary network node or the secondary network node.

49. The method as recited in claim 48, further comprising:

RLC entity activation/deactivation signaling is received from the primary network node or the secondary network node over a Uu interface.

50. The method of claim 47, wherein the RLC entity activation/deactivation signaling is in the form of medium access control component, MAC CE.

51. The method of claim 50 wherein the RLC entity activation/deactivation signaling is in the form of a MAC entity bitmap.

52. The method of claim 50 wherein the RLC entity activation/deactivation signaling is in the form of radio bearer, RB.

53. The method of claim 47, wherein the number of RLC entities corresponding to the user equipment for a radio bearer is less than 5.

54. The method of claim 48, wherein the RLC entity is hosted in a main unit group MCG and a secondary unit group SCG, and the main network node is configured in the main unit group, and the secondary network node is configured in the secondary unit group.

55. The method of claim 54, wherein the user equipment, the primary unit group, and the secondary unit group are in a dual connectivity DC architecture and a carrier aggregation CA architecture.

56. The method of claim 48, wherein the user equipment is in an RRC_CONNECTED state with both the primary network node and the secondary node.

57. The method of claim 47, wherein the user equipment configures a split data radio bearer, DRB.

58. The method of claim 47, wherein the RLC entity activation/deactivation signaling comprises a configuration of duration.

59. The method as recited in claim 58, further comprising:

starting a timer of the user equipment upon receiving the RLC entity activation/deactivation signaling.

60. The method of claim 59, further comprising:

restoring an active state of the RLC entity of the user equipment when the timer reaches a duration; and

the method further comprises sending the timer expiration report message to the primary network node, the timer expiration report message indicating an active state of an RLC entity of the user equipment.

61. The method of claim 58, further comprising:

restarting the timer of the user equipment after receiving a modified RLC entity activation/deactivation signal until a duration is reached;

activating/deactivating RLC entities according to the modified RLC entity activation/deactivation signaling from the primary network node; and

A timer restart report message is sent to the primary network node, the timer restart report message indicating an active state of an RLC entity of the user equipment.

62. The method of claim 58, wherein the primary network node is a base station and the primary network node is in a dual connectivity DC architecture, or a carrier aggregation CA architecture, or a combination of dual connectivity DC architecture and carrier aggregation CA architecture with the user equipment.

63. The method of claim 58, wherein the configuring further comprises separating a Data Radio Bearer (DRB) ID, an RLC ID, and operations related to activation/deactivation of an RLC entity.

64. The method of claim 63, wherein the split data radio bearer is configured for the user equipment.

65. The method of claim 58, wherein the user equipment is in an RRC_CONNECTED state with the primary network node.

66. The method as recited in claim 47, further comprising:

reporting messages are periodically sent from the user equipment to a primary network node, the reporting messages indicating an activity state of the RLC entity of the user equipment.

67. The method of claim 58 wherein the information carried by the RLC entity activation/deactivation signaling includes a duration, a separate data radio bearer, DRB ID, an RLC ID, operations associated with activation/deactivation of the RLC entity, and a number of periodicity.

68. A user equipment comprising:

a transceiver; and

receiving RLC entity activation/deactivation signaling from a primary network node;

activating/deactivating an RLC entity in response to the RLC entity activating/deactivating signaling; and

a reporting message is sent to the primary network node, the reporting message indicating an activity status of an RLC entity of the user equipment.

69. The user device of claim 68, wherein the operations further comprise:

70. The user device of claim 69, wherein the operations further comprise:

71. The user equipment of claim 68, wherein the RLC entity activation/deactivation signaling is in the form of medium access control component, MAC CE.

72. The user equipment of claim 71 wherein the RLC entity activation/deactivation signaling is in the form of a MAC entity bitmap.

73. The user equipment of claim 71, wherein the RLC entity activation/deactivation signaling is in the form of a radio bearer RB.

74. The user equipment of claim 68, wherein the number of RLC entities of the user equipment corresponding to a radio bearer is less than 5.

75. The user equipment of claim 69, wherein the RLC entity is hosted in a main unit group MCG and a secondary unit group SCG, and wherein the main network node is configured in the main unit group and the secondary network node is configured in the secondary unit group.

76. The user equipment of claim 75 wherein the user equipment, the primary unit group, and the secondary unit group are in a dual connectivity DC architecture and a carrier aggregation CA architecture.

77. The user equipment of claim 69, wherein the user equipment is in an RRC_CONNECTED state with both the primary network node and the secondary node.

78. The user equipment of claim 68, wherein the user equipment configures a split data radio bearer, DRB.

79. The user equipment of claim 68, wherein the RLC entity activation/deactivation signaling comprises a configuration of duration.

80. The user device of claim 79, further comprising a timer, wherein the operations further comprise:

the timer is started upon receiving the RLC entity activation/deactivation signaling.

81. The user device of claim 80, wherein the operations further comprise:

82. The user device of claim 80, wherein the operations further comprise:

83. The user device of claim 79, wherein the primary network node is a base station and the primary network node and the user device are in a dual connectivity DC architecture, or a carrier aggregation CA architecture, or a combination of dual connectivity DC architecture and carrier aggregation CA architecture.

84. The user equipment of claim 79, wherein the configuration further comprises operations of separating a Data Radio Bearer (DRB) ID, an RLC ID, and an activation/deactivation related to an RLC entity.

85. The user equipment of claim 84, wherein the split data radio bearer is configured for the user equipment.

86. The user equipment of claim 79, wherein the user equipment is in an rrc_connected state with the primary network node.

87. The user equipment of claim 68, the operations further comprising:

88. The user equipment of claim 79, wherein the information carried by the RLC entity activation/deactivation signaling includes a duration, a separate data radio bearer, DRB ID, an RLC ID, operations associated with activation/deactivation of the RLC entity, and a number of periodicity.

89. A chip, comprising:

a processor configured to invoke and run a computer program stored in a memory to cause a device on which the chip is installed to perform the method of any of claims 1 to 23.

90. A chip, comprising:

a processor for invoking and running a computer program stored in memory to cause a device on which the chip is installed to perform the method of any of claims 25 to 47.

91. A computer readable storage medium in which a computer program is stored, wherein the computer program is for executing the method of any one of claims 1 to 23 by a computer.

92. A computer readable storage medium in which a computer program is stored, wherein the computer program is for performing the method of any one of claims 47 to 67 by a computer.

93. A computer program product comprising a computer program, wherein the computer program is adapted to perform the method of any one of claims 1 to 23 by a computer.

94. A computer program product comprising a computer program, wherein the computer program is adapted to perform the method of any of claims 47 to 67 by a computer.

95. A computer program, wherein the computer program performs the method of any one of claims 1 to 23 by a computer.

96. A computer program, wherein the computer program performs the method of any one of claims 47 to 67 by a computer.