Method for controlling a radio link control entity, network node and user equipment
By transmitting RLC entity activation/deactivation signaling between network nodes, the problem that network nodes in DC and CA architectures cannot control the state of RLC entity is solved, and effective activation and deactivation of RLC entities is realized, meeting the high latency requirements service needs.
Patent Information
- Application Number
- CN202080104320.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-08-07
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2040-08-07
AI Technical Summary
In the combination of DC architecture and CA architecture, one network node cannot effectively control the activation/deactivation state of the RLC entity belonging to another network node, resulting in problems with the configuration of the data radio bearer.
By transmitting RLC entity activation/deactivation signaling between the primary network node and the secondary network node, signaling is passed to the user equipment using the X2/Xn interface and the Uu interface, ensuring that the status of the RLC entity is updated and through the auxiliary if necessary Node forwards signaling to achieve network coordination.
Effectively activate/deactivate RLC entities, meet services with high latency requirements, and provide flexible network coordination mechanisms in the absence of high latency requirements, solving the problem that network nodes cannot control the status of RLC entities of user equipment.
Smart Images

Figure CN116235617B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of communication systems, and more particularly, to a method for controlling activation / deactivation of a Radio Link Control (RLC) entity, a network node, and a user equipment. 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 -9reliability 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] For PDCP duplication using more than two RLC entities configured for Data Radio Bearers (DRBs) in a combination of DC architecture and CA architecture, in some cases, one network node cannot control the active / inactive state of the RLC entity belonging to another node. Therefore, a network-coordinated RLC entity activation / deactivation mechanism is required.
[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] The first aspect of the present application provides a method for controlling a radio link control RLC entity of a user equipment, wherein the user equipment operates in a primary network, comprising: sending RLC entity activation / deactivation signaling to the user equipment; receiving a report message indicating the RLC entity status of the user equipment, the user equipment responding to the RLC entity activation / deactivation signaling to activate the RLC entity; and updating the activation status of the RLC entity of the user equipment according to the report message.
[0013] In an embodiment of the present application, the method further includes determining a delay level of the data packet according to quality of service QoS information.
[0014] In an embodiment of the present application, the method further includes: when the delay level of the data packet meets the X2 / Xn interface delay, transmitting the RLC entity activation / deactivation signaling to the auxiliary network node; and forwarding the report message to the auxiliary network node.
[0015] In an embodiment of the present application, the method further includes: transmitting the RLC entity activation / deactivation signaling to the auxiliary network node via an X2 / Xn interface.
[0016] In an embodiment of the present application, the method further includes: sending the RLC entity activation / deactivation signaling to the user equipment and the auxiliary network node at the same time.
[0017] In an embodiment of the present application, the method further includes transmitting the RLC entity activation / deactivation signaling to the user equipment via a Uu interface.
[0018] 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.
[0019] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
[0020] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
[0021] 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.
[0022] In an embodiment of the present application, the RLC entity is hosted in a main cell group MCG and a secondary cell group SCG, and the main network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
[0023] In an embodiment of the present application, the user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
[0024] In an embodiment of the present application, the user equipment, the primary network node and the auxiliary node are all in RRC_CONNECTED state.
[0025] In an embodiment of the present application, the user equipment configures a split data radio bearer DRB.
[0026] In an embodiment of the present application, the RLC entity activation / deactivation signaling includes a configuration of duration.
[0027] In an embodiment of the present application, the method also includes: receiving a timer expiration report message from the user equipment, the expiration report message indicating the activity status of the RLC entity of the user equipment when the timer of the user equipment expires within a duration; and updating the activation status of the RLC entity of the user equipment according to the timer expiration report message.
[0028] In an embodiment of the present application, the method also includes: sending 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 reaching the duration, the user equipment responds to the modified RLC entity activation / deactivation signaling to activate / deactivate the activation status of the RLC entity; and updating the activation status of the RLC entity of the user equipment according to the timer restart report message.
[0029] In an embodiment of the present application, the main network node is a base station, and the main network node and the user equipment are in a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual-connection DC architecture and the carrier aggregation CA architecture.
[0030] In an embodiment of the present application, the configuration further includes separating a data radio bearer (DRB) ID, an RLC ID, and operations related to activation / deactivation of an RLC entity.
[0031] In an embodiment of the present application, the split data radio bearer is configured for the user equipment.
[0032] In an embodiment of the present application, the user equipment and the primary network node are in RRC_CONNECTED state.
[0033] In an embodiment of the present application, the method further includes: periodically sending the RLC entity activation / deactivation signaling to the user equipment.
[0034] In an embodiment of the present application, the information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic number of times.
[0035] 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 to the transceiver and configured to perform the following operations, the operations including: sending RLC entity activation / deactivation signaling to a user equipment; receiving a report message indicating the RLC entity state of the user equipment, the user equipment responding to the RLC entity activation / deactivation signaling to activate the RLC entity; and updating the activation state of the RLC entity of the user equipment according to the report message.
[0036] In an embodiment of the present application, the operation further includes determining a delay level of the data packet according to quality of service QoS information.
[0037] In an embodiment of the present application, the operation further includes: when the delay level of the data packet meets the X2 / Xn interface delay, transmitting the RLC entity activation / deactivation signaling to the auxiliary network node; and forwarding the report message to the auxiliary network node.
[0038] In an embodiment of the present application, the operation further includes: transmitting the RLC entity activation / deactivation signaling to the auxiliary network node via an X2 / Xn interface.
[0039] In an embodiment of the present application, the operation further includes: sending the RLC entity activation / deactivation signaling to the user equipment and the auxiliary network node at the same time.
[0040] In an embodiment of the present application, the operation further includes transmitting the RLC entity activation / deactivation signaling to the user equipment via a Uu interface.
[0041] 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.
[0042] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
[0043] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
[0044] 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.
[0045] In an embodiment of the present application, the RLC entity is hosted in a main cell group MCG and a secondary cell group SCG, and the main network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
[0046] In an embodiment of the present application, the user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
[0047] In an embodiment of the present application, the user equipment, the primary network node and the auxiliary node are all in RRC_CONNECTED state.
[0048] In an embodiment of the present application, the user equipment configures a split data radio bearer DRB.
[0049] In an embodiment of the present application, the RLC entity activation / deactivation signaling includes a configuration of duration.
[0050] In an embodiment of the present application, the operation also includes: receiving a timer expiration report message from the user equipment, the expiration report message indicating the activity status of the RLC entity of the user equipment when the timer of the user equipment expires within a duration; and updating the activation status of the RLC entity of the user equipment according to the timer expiration report message.
[0051] In an embodiment of the present application, the operation also includes: sending 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 reaching the duration, the user equipment responds to the modified RLC entity activation / deactivation signaling to activate / deactivate the activation status of the RLC entity; and updating the activation status of the RLC entity of the user equipment according to the timer restart report message.
[0052] In an embodiment of the present application, the main network node is a base station, and the main network node and the user equipment are in a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual-connection DC architecture and the carrier aggregation CA architecture.
[0053] In an embodiment of the present application, the configuration further includes separating a data radio bearer (DRB) ID, an RLC ID, and operations related to activation / deactivation of an RLC entity.
[0054] In an embodiment of the present application, the split data radio bearer is configured for the user equipment.
[0055] In an embodiment of the present application, the user equipment and the primary network node are in RRC_CONNECTED state.
[0056] In an embodiment of the present application, the operation further includes: periodically sending the RLC entity activation / deactivation signaling to the user equipment.
[0057] In an embodiment of the present application, the information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic number of times.
[0058] The third aspect of the present application provides a method for controlling a physical radio link control RLC of a user equipment, comprising: the user equipment receives an RLC entity activation / deactivation signaling from a primary network node; the user equipment activates / deactivates the RLC entity in response to the RLC entity activation / deactivation signaling; and sends a report message from the user equipment to the primary network node, the report message indicating the activity status of the RLC entity of the user equipment.
[0059] In an embodiment of the present application, the method also includes: when the delay level of the data packet meets the X2 / Xn interface delay, receiving RLC entity activation / deactivation signaling from the auxiliary network node, the RLC entity activation / deactivation signaling is forwarded by the main network node to the auxiliary network node through the X2 / Xn interface; and activating / deactivating the RLC entity according to the RLC entity activation / deactivation signaling from the main network node or the auxiliary network node.
[0060] In an embodiment of the present application, the method further includes: receiving RLC entity activation / deactivation signaling from the primary network node or the secondary network node through a Uu interface.
[0061] 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.
[0062] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
[0063] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
[0064] 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.
[0065] In an embodiment of the present application, the RLC entity is hosted in a main cell group MCG and a secondary cell group SCG, and the main network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
[0066] In an embodiment of the present application, the user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
[0067] In an embodiment of the present application, the user equipment, the primary network node and the auxiliary node are all in RRC_CONNECTED state.
[0068] In an embodiment of the present application, the user equipment configures a split data radio bearer DRB.
[0069] In an embodiment of the present application, the RLC entity activation / deactivation signaling includes a configuration of duration.
[0070] In an embodiment of the present application, the method further includes starting a timer of the user equipment when receiving the RLC entity activation / deactivation signaling.
[0071] In an embodiment of the present application, the method also includes: when the timer reaches the duration, restoring the activity state of the RLC entity of the user equipment; and sending the timer expiration report message to the main network node, wherein the timer expiration report message indicates the activity state of the RLC entity of the user equipment.
[0072] In an embodiment of the present application, the method also includes: restarting the timer of the user equipment after receiving a modified RLC entity activation / deactivation signal until the duration is reached; activating / deactivating the RLC entity according to the modified RLC entity activation / deactivation signaling from the main network node; and sending a timer restart report message to the main network node, wherein the timer restart report message indicates the activity status of the RLC entity of the user equipment.
[0073] In an embodiment of the present application, the main network node is a base station, and the main network node and the user equipment are in a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual-connection DC architecture and the carrier aggregation CA architecture.
[0074] In an embodiment of the present application, the configuration further includes separating a data radio bearer (DRB) ID, an RLC ID, and operations related to activation / deactivation of an RLC entity.
[0075] In an embodiment of the present application, the split data radio bearer is configured for the user equipment.
[0076] In an embodiment of the present application, the user equipment and the primary network node are in RRC_CONNECTED state.
[0077] In an embodiment of the present application, the method further comprises: periodically sending a report message from the user equipment to a primary network node, wherein the report message indicates an activity status of the RLC entity of the user equipment.
[0078] In an embodiment of the present application, the information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic number of times.
[0079] 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 to the transceiver and configured to perform the following operations, the operations including: receiving RLC entity activation / deactivation signaling from a primary network node; activating / deactivating an RLC entity in response to the RLC entity activation / deactivation signaling; and sending a report message to the primary network node, the report message indicating the activity status of the RLC entity of the user equipment.
[0080] In an embodiment of the present application, the operation also includes: when the delay level of the data packet meets the X2 / Xn interface delay, receiving RLC entity activation / deactivation signaling from the auxiliary network node, the RLC entity activation / deactivation signaling is forwarded by the main network node to the auxiliary network node through the X2 / Xn interface; and activating / deactivating the RLC entity according to the RLC entity activation / deactivation signaling from the main network node or the auxiliary network node.
[0081] In an embodiment of the present application, the operation further includes: receiving RLC entity activation / deactivation signaling from the primary network node or the secondary network node through a Uu interface.
[0082] 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.
[0083] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
[0084] In an embodiment of the present application, the RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
[0085] 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.
[0086] In an embodiment of the present application, the RLC entity is hosted in a main cell group MCG and a secondary cell group SCG, and the main network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
[0087] In an embodiment of the present application, the user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
[0088] In an embodiment of the present application, the user equipment, the primary network node and the auxiliary node are all in RRC CONNECTED state.
[0089] In an embodiment of the present application, the user equipment configures a split data radio bearer DRB.
[0090] In an embodiment of the present application, the RLC entity activation / deactivation signaling includes a configuration of duration.
[0091] In an embodiment of the present application, the operation further includes starting a timer of the user equipment when the RLC entity activation / deactivation signaling is received.
[0092] In an embodiment of the present application, the operation also includes: when the timer reaches the duration, restoring the activity state of the RLC entity of the user equipment; and sending the timer expiration report message to the main network node, wherein the timer expiration report message indicates the activity state of the RLC entity of the user equipment.
[0093] In an embodiment of the present application, the operation also includes: restarting the timer of the user equipment after receiving a modified RLC entity activation / deactivation signal until the duration is reached; activating / deactivating the RLC entity according to the modified RLC entity activation / deactivation signaling from the main network node; and sending a timer restart report message to the main network node, wherein the timer restart report message indicates the activity status of the RLC entity of the user equipment.
[0094] In an embodiment of the present application, the main network node is a base station, and the main network node and the user equipment are in a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual-connection DC architecture and the carrier aggregation CA architecture.
[0095] In an embodiment of the present application, the configuration further includes separating a data radio bearer (DRB) ID, an RLC ID, and operations related to activation / deactivation of an RLC entity.
[0096] In an embodiment of the present application, the split data radio bearer is configured for the user equipment.
[0097] In an embodiment of the present application, the user equipment and the primary network node are in RRC_CONNECTED state.
[0098] In an embodiment of the present application, the operation further includes: periodically sending a report message from the user equipment to the primary network node, the report message indicating an activity status of the RLC entity of the user equipment.
[0099] In an embodiment of the present application, the information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic number of times.
[0100] The fifth 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.
[0101] The sixth 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.
[0102] 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.
[0103] 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.
[0104] Beneficial Effects
[0105] The embodiment of the present application provides a method for controlling the activation / deactivation of a radio link control (RLC) entity, a base station, and a user equipment, which is used to solve the problem that a network node cannot control the active / inactive state of the RLC entity of a user equipment belonging to another network node when the DRB used in the combination of the DC architecture and the CA architecture is configured with PDCP replication of more than two RLC entities. However, the present application proposes that the RLC entity activation / deactivation configuration can be sent by a network node to the CN and forwarded to another network node, and then the other network node sends the configuration to the UE, or the primary node can send the activation / deactivation signal to the auxiliary node, and then the auxiliary node forwards the RLC entity activation / deactivation signal to the UE. In addition, for services with high latency requirements, the network node directly sends the RLC entity activation / deactivation signaling to the UE via the Uu interface. For data packets that can meet the delay requirements by introducing X2 / Xn delay, the network node transmits the RLC entity activation / deactivation signaling to the UE via the Uu interface and other network nodes. Due to the introduction of X2 / Xn interface delay, it can be used for services that do not require high latency. Therefore, the present application can effectively activate / deactivate the device of the RLC entity. BRIEF DESCRIPTION OF THE DRAWINGS
[0106] 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.
[0107] Figure 1 is a schematic diagram of a system according to an embodiment of the present application.
[0108] Figure 2 A schematic diagram showing a master node acting as a main network node according to an embodiment of the present application is shown.
[0109] Figure 3 A schematic diagram showing a secondary node acting as a primary network node according to another embodiment of the present application is shown.
[0110] Figure 4 The embodiments of the present application illustrate the options of MCG, SCG and network-side protocol ends of separate bearers in multi-radio (MR)-DC with 5GC.
[0111] Figure 5 The radio protocol architecture of MCG, SCG and split bearers in MR-DC is explained from the UE perspective.
[0112] Figure 6A flowchart of a method for controlling activation / deactivation of a radio link control (RLC) entity according to an embodiment of the present application is shown.
[0113] Figure 7 is a schematic diagram of a system according to another embodiment of the present application.
[0114] Figure 8 A flow chart of a method for controlling activation / deactivation of a radio link control (RLC) entity according to another embodiment of the present application is shown.
[0115] Fig. 9 A timing diagram of an RLC entity according to another embodiment of the present application is shown.
[0116] Fig.10 It is a structural block diagram of a system for wireless communication according to an embodiment of the present application. DETAILED DESCRIPTION
[0117] The embodiments of the present application describe in detail the technical matters, structural features, implementation purposes and effects with reference to the accompanying drawings. 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.
[0118] 3GPP NR IIOT Background
[0119] In the revision of NR IIoT RP-192324, the detailed objectives of the NR PDCP duplication enhancement are:
[0120] · PDCP duplication is specified for up to 4 RLC entities configured with RRC in an architecture combination including CA and NR-DC with CA [RAN2, RAN3] combination.
[0121] Mechanisms to specify and dynamically control how a set or subset of configured RLC entities or branches are used for PDCP duplication [RAN2, RAN3].
[0122] Lower priority objective: To 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].
[0123] Specify enhancements to enable more efficient DL PDCP duplication without impacting UEs, provided the benefits can be demonstrated with reasonable complexity. [RAN3].
[0124] · Specify enhancements to address the potential impact of higher layer multiple connections based on SA2 progress and requests [RAN3]
[0125] For 3GPP Release 16 (Rel-16) content, up to 4 RLC entities can be configured for DRBs utilizing DC and CA architectures, thus allowing different numbers of RLC entity combinations to be hosted in the MCG and SCG.
[0126] At 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:
[0127] RAN2#107 protocol:
[0128] The number of copies generated is equal to the number of active RLC entities, i.e. one copy per branch / RLC entity, and the active / inactive status is determined by the MAC CE.
[0129] 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.
[0130] In case of PDCP duplication, the application of the configured cell limit does not change dynamically when activating or deactivating PDCP duplication beyond 3GPP Release 15.
[0131] MAC CE signaling structure is:
[0132] a. Each DRB signaling with an associated RLC entity activity status, or
[0133] b. All DRBs with associated RLC entity active status for each DRB
[0134] The new LCID is used to control the MAC CE of PDCP duplication.
[0135] Regardless of which MAC CE structure RAN2 will adopt (listed in RAN2#107 protocol), the RLC entity activation / deactivation signaling will include duplicate activity states corresponding to all RLC entities configured for DRB, and therefore belonging to both MCG and SCG in DC or DC and CA scenarios.
[0136] RAN2#108 mentions that network coordination facilitates 3GPP Release 16 PDCP duplication under DC and CA architectures, which is a question of how nodes coordinate RLC entity activation / deactivation between each other.
[0137] RAN2#108 protocol:
[0138] Network coordination facilitates PDCP duplication in the uplink in the NR-DC / CA architecture.
[0139] Therefore, a mechanism for network coordination of RLC entity activation / deactivation, namely, PDCP duplication, is needed.
[0140] Protocols for delivering accurate reference timing for TSN
[0141] 3GPP RAN2#106 agreement:
[0142] Dynamic network control of DRB replication is performed by MAC CE.
[0143] · Through MAC CE, the network controls which configured RLC entities are active.
[0144] 3GPP RAN2#107 agreement:
[0145] The number of copies generated is equal to the number of active RLC entities, i.e. one copy per branch / RLC entity, and the active / inactive status is determined by the MAC CE.
[0146] The network provides only one LCH cell restriction configuration per LCH in RRC, as specified in 3GPP Release 15. Changes to the LCH cell restriction configuration can only be made via RRC.
[0147] MAC CE signaling structure is:
[0148] a. Each DRB signaling with an associated RLC entity activity status, or
[0149] b. All DRBs with associated RLC entity active status for each DRB
[0150] New LCID is used for 3GPP Release 16 MAC CE to control PDCP duplication.
[0151] 3GPP RAN2#108 agreement:
[0152] Network coordination facilitates PDCP duplication in uplink in NR-DC / CA architecture.
[0153] 3GPP RAN2#110-e protocol:
[0154] · The UE only follows the received MAC CE, even if the RLCi field belongs to another node. No specification changes are required.
[0155] PDCP duplication with more than two RLC entities is supported only in NR. Needs clarification in 37.340 and 38.331.
[0156] Clarify the DC+CA repeat in 38.300. The 3+1 repeat scheme also needs to be considered. The CA repeat may need clarification.
[0157] 1. Related prior art
[0158] According to the 3GPP Release 16 meeting, the following conclusions can be drawn:
[0159] PDCP duplication with more than two RLC entities is supported only on NR
[0160] ■A PDCP entity has one primary path.
[0161] ■ The primary path for data PDUs should not be deactivated.
[0162] ■ The number of copies generated is equal to the number of active RLC entities, ie one copy per branch / RLC entity.
[0163] Dynamic network control of DRB replication is performed by MAC CE
[0164] ■The active / inactive state of the RLC entity is determined by the MAC CE.
[0165] ■ For PDCP duplication controlling the MAC CE format, per DRB signalling with associated RLC entity activity status shall be adopted in Rel-16.
[0166] ■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.
[0167] ■R16 MAC CE for outrigger selection and on / off.
[0168] ■ The UE only follows the received MAC CE, even if the RLCi field belongs to another node.
[0169] The network provides only one LCH cell restriction configuration per LCH in RRC.
[0170] ■Changes to LCH cell limit configuration can only be made through RRC.
[0171] ■ 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.
[0172] ■New LCID is used to control the Rel-16 MAC CE for PDCP duplication.
[0173] Network coordination facilitates PDCP duplication in uplink in NR-DC / CA architecture.
[0174] refer to Figure 1 , the communication system includes UE 10a, 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 10a may include a processor 11a, a memory 12a and a transceiver 13a. 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 11a, 201b, 201a 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 11a, 201b, 201a and 301. Each memory 12a, 202a, 202b and 302 may store various programs and information to cooperate with the operation of the connected processor. Each transceiver 13a, 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 may be a base station, such as an eNB, a gNB or one of other types of radio nodes, and may configure radio resources for the UE 10a.
[0175] Processors 11a, 201b, 201a and 301 may include application specific integrated circuits (ASICs), other chipsets, logic circuits and / or data processing devices. Memory 12a, 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 13a, 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.
[0176] The network entity device 300 may be a node in the CN. The CN may include an LTE CN or a 5G core (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).
[0177] 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.
[0178] Figure 3 A schematic diagram showing an auxiliary node as a main network node in another embodiment of the present application is shown. The first network node 200a as a main node MN located in a main unit group MCG can be a main 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 10a 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 main network node.
[0179] 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 ends 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 the device 10a is in the RRC_CONNECTED state with the primary network node 200a and the secondary network node 200b at the same time, a data radio bearer (DRB) is established by the primary network node 200a and the secondary network node 200b and configured for the user equipment 10a. The UE 10a supports up to four RLC entities configured for the radio bearer.
[0180] See also Figure 4 , Figure 5 and Figure 6 . Figure 6The flow chart of the method for controlling activation / deactivation of a radio link control (RLC) entity according to an embodiment of the present application is shown. The primary network node 200a directly sends RLC entity activation / deactivation signaling to the UE 10a, and sends the RLC entity activation / deactivation signaling to the secondary network node 200b. Figure 4 As shown, since the Service Data Adaptation Protocol (SDAP) handles the mapping between QoS flows and data radio bearers, the primary network node 200a determines the delay level of the data packet based on the Quality of Service (QoS) information (step 600).
[0181] For services with high delay requirements, the primary network node 200a directly sends RLC entity activation / deactivation signaling to UE 10a via the Uu interface. For services where the delay requirement can be met by X2 / Xn interface delay, RLC entity activation / deactivation signaling is sent to UE 10a via the Uu interface or / and the auxiliary network node 200b. In this embodiment, there is no specific order in the time of operation for the primary network node 200a to send RLC entity activation / deactivation signals to UE 10a and the auxiliary network node 200b. The primary network node 200a sends RLC entity activation / deactivation signaling to UE 10a via the Uu interface (step 601), and then the primary network node 200a sends the RLC entity activation / deactivation signaling to the auxiliary network node 200b via the X2 / Xn interface, as shown in step 602. In another embodiment, the network node 200a may send the RLC entity activation / deactivation signaling to the auxiliary network node 200b as in step 602, and then send the RLC entity activation / deactivation signaling to the UE 10a as in step 601. In another embodiment, the network node 200a sends the RLC entity activation / deactivation signal to the UE 10a and the auxiliary network node 200b at the same time. The RLC entity activation / deactivation signaling may be in any form, such as a MAC CE. The RLC entity activation / deactivation signaling may also be in the form of each MAC entity bitmap or each radio bearer. The RLC entity activation / deactivation signaling sent by the primary network node 200a to the UE 10a and the RLC entity activation / deactivation signaling sent to the auxiliary network node 200b may take different forms or formats.
[0182] The auxiliary network node 200b forwards the RLC entity activation / deactivation signaling received from the primary network node 200a to the UE 10a via the Uu interface. (Step 604) The RLC entity activation / deactivation signaling may be in any form, such as MAC CE.
[0183] UE 10a may perform RLC entity activation / deactivation according to RLC entity activation / deactivation signaling received from primary network node 200a (step 603), or UE 10a may activate / deactivate the RLC entity belonging to the MAC entity configuration DRB corresponding to primary network node 200a (step 605). When primary network node 200a receives RLC entity activation / deactivation signaling of split DRB (i.e., DRB1), UE 10a may activate / deactivate RLC0 belonging to DRB1. UE 10a may perform RLC entity activation / deactivation according to RLC entity activation / deactivation signaling received from secondary network node 200b (step 605).
[0184] In another embodiment, UE 10a may activate / deactivate RLC entities belonging to configured DRBs in a MAC entity corresponding to auxiliary network node 200b. For example, if auxiliary network node 200b acts as an auxiliary node, UE 10a may activate / deactivate RLC1 and RLC2 belonging to DRB1.
[0185] UE 10a may not activate / deactivate the RLC entity before receiving signaling from primary network node 200a and secondary network node 200b, and then UE 10a may activate / deactivate the RLC entity according to the RLC entity activation / deactivation signaling, including the operations shown in steps 603 and 605.
[0186] UE 10a may generate an activity / inactivity report message of the RLC entity and then send 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 the activity / inactivity status information of the RLC entity after UE 10a performs an activation / deactivation operation. The report message may be for each RB, i.e., only including the activity / inactivity status information of the RLC entity of a certain DRB, or the report message may be for each MAC entity, i.e., including the activity / inactivity status information of the RLC entity of a certain MAC entity, or the report message may be for each UE 10a, including the activity / inactivity status information of the RLC entity of UE10a.
[0187] After performing RLC entity activation / deactivation, UE 10a may generate a report message including the status information of the RLC entity of the DRB corresponding to the MAC entity of the primary network node 200a, and send it to the primary network node 200a (step 606). For example, if the report message is directed to each DRB, for DRB1, the report message includes the status information of RLC0 of DRB1.
[0188] After executing step 605, UE 10a may generate a report message including the status information of the RLC entity of the DRB corresponding to the MAC entity of the auxiliary network node 200b, and send it to the auxiliary network node 200b (step 608). If the report message is directed to each DRB, for DRB1, the report message includes the status information of RLC1 and RLC2 of DRB1.
[0189] UE 10a may generate a report message after both step 603 and step 605 are executed, including the status information of the DRB corresponding to the MAC entity of the primary network node 200a and the RLC entity corresponding to the MAC entity of the secondary network node 200b, and send 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 the status information of RLC0, RLC1 and RLC2 of DRB1.
[0190] The 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 via an X2 / Xn interface, as shown in steps 608 and 610 .
[0191] The primary network node 200a and the secondary network node 200b may update the state information according to the RLC entity activity / inactivity report message received from the UE 10a. The state information may be for each MAC entity, for example, the state information includes the state information of RLC0 and the state information of RLC1 of DRB0, and the state information of RLC0 of DRB1. The state information may be for each UE 10a, for example, the state information includes the state information of RLC0 and RLC1 of DRB0, and the state information of RLC0, RLC1 and RLC2 of DRB0.
[0192] The auxiliary network node 200b may maintain the state information of the RLC entity of the UE 10a. The state information may be the state information of each MAC entity, for example, the state information includes the state information of RLC1 and the state information of RLC2 of DRB1. The state information may be the state information of each UE 10a, for example, the state information includes the state information of RLC0 and RLC1 of DRB0, RLC0, RLC1 and RLC2 of DRB1.
[0193] The primary network node 200a and the secondary network node 200b may simultaneously maintain the RLC entity of the UE 10a. The state information may be state information of each UE 10a, for example, the state information includes state information of RLC0 and RLC1 of DRB0, RLC0, RLC1 and RLC2 of DRB1.
[0194] This embodiment also introduces an indicator of RLC entity status information to indicate whether the RLC entity status information is available. When the primary network node 200a sends 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 information to perform RLC entity activation / deactivation from the primary network node 200a and via the auxiliary network node 200b, it will directly send a confirmation message to the primary network node 200a through the Uu interface or through the auxiliary network node 200b (the confirmation message may include RLC entity active / inactive status information), and the primary network node 200a may set the value of the indicator to "available". The 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 the RLC entity activation / deactivation signaling is transmitted to the UE 10a through the Uu interface and the auxiliary node. The RLC entity activation / deactivation signaling is transmitted to the UE 10a through the Uu interface. If the delay introduced by the X2 / Xn interface cannot meet the requirement, the indicator is set to "unavailable" and the RLC entity activation / deactivation signaling is directly transmitted to the UE 10a. The values of "available" and "unavailable" of the indicator can be digital "1", "0" or any other form.
[0195] The method disclosed in the embodiment of the present application is that the delay requirement for the data packet can be met by introducing an activation / deactivation operation with an X2 / Xn interface delay, and the RLC entity activation / deactivation signaling can be sent from the primary network node 200a to the secondary network node 200b through the X2 / Xn interface. Then the secondary network node 200b forwards the RLC entity activation / deactivation signaling to the UE 10a through the Uu interface. After receiving the RLC entity activation / deactivation signaling from the primary network node 200a, the UE 10a activates / deactivates the RLC entity according to the content of the RLC entity activation / deactivation signaling. Then the UE 10a generates an RLC entity activity / inactivity report message and sends it to the primary network node 200a. According to 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 content of the RLC entity activation / deactivation signaling. Then UE 10a generates an RLC entity activity / inactivity report message and sends it to auxiliary network node 200b. Then auxiliary network node 200b updates the local state information of the RLC entity according to the RLC entity report message received from UE 10a. At the same time, auxiliary network node 200b forwards the RLC entity report message to primary network node 200a via X2 / Xn interface, and primary network node 200a updates the local state information of the RLC entity accordingly.
[0196] Example 2
[0197] See also Figure 7 , Figure 7A schematic diagram of a communication system including UE 10, network node 200 and network entity device 30 according to another embodiment of the present application is shown. UE 10 is configured with a dual connection (DC) architecture, or a carrier aggregation (CA) architecture, or a combination of a DC architecture and a CA architecture. 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. Network entity device 300 may include a processor 301, a memory 302 and a transceiver 303. Each processor 11, 201 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 processors 11, 201 and 301. Various programs and information may be stored in each memory 12, 202 and 302 to cooperate with the operation of the connected processor. Each transceiver 13, 203 and 303 is coupled to the processor for sending and / or receiving radio signals or wired signals. Each network node 200 may be a base station, such as an eNB, a gNB, or one of other types of radio nodes, and may configure wireless resources for the UE 10.
[0198] Each processor 11, 201 and 301 may include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. Each memory 12, 202 and 302 may include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and / or other storage devices. Each transceiver 13a, 203 and 303 may include a baseband circuit and a radio frequency (RF) circuit for processing radio frequency signals. When the embodiment is implemented by software, the technology described herein can be implemented with modules, processes, functions, entities, etc. that perform the functions described herein. The module can be stored in a memory and executed by a processor. The memory can be implemented inside or outside the processor, and those can be coupled to the processor by various means known in the art.
[0199] See also Figure 7 and Figure 8 . Figure 8 A flow chart of a method for controlling activation / deactivation of a radio link control (RLC) entity according to another embodiment of the present application is shown. When the user equipment 10 and the network node 200 are in the RRC_CONNECTED state, a data radio bearer (DRB) is established and configured by the network node 200 for the user equipment 10. 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 can support up to four RLC entities configured for radio bearers.
[0200] The network node 200 sends an RLC entity activation / deactivation signal to the UE 10 (step 801). The configuration carried by the RLC entity activation / deactivation signaling includes a duration, a data radio bearer (DRB) ID, an RLC ID, and operations related to RLC entity activation / deactivation. The DRB ID included in the configuration can identify a DRB in a CA architecture, an MCG DRB, an SCG DRB, or a split DRB in a DC architecture, or a combination of DC and CA architectures. In addition, the duration is used to set the value of the timer 14. The timer 14 can be configured for each radio bearer.
[0201] UE 10 can activate / deactivate the RLC entity according to the RLC entity activation / deactivation signaling received from the base station, and can set the duration of timer 14 and start timer 14 (step 802). The active / inactive state of the RLC entity should remain unchanged until the timing time of timer 14 expires.
[0202] UE 10 may report the active / inactive state information of the RLC entity to the base station (step 803). When the timer 14 expires, UE 10 restores the state of the RLC entity (step 804). UE 10 may restore the RLC entity to the state before the RLC entity activation / deactivation signal performs RLC entity activation / deactivation, or UE 10 may restore the RLC entity to a default state, which may be an active or inactive state.
[0203] The UE 10 may report the timer expiration report message to the network node 200 (step 805). The timer expiration report message indicates the active / inactive state of the RLC entity of the user equipment when the timer 14 expires within the duration.
[0204] If the network node 100 sends a modified RLC entity activation / deactivation signaling to the UE 10 of the same DRB before the duration is reached (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 the modification of the activity state of the RLC entity of the user equipment (step 809). The network node 200 updates the activity state of the RLC entity of the user equipment based on the timer restart report message.
[0205] The embodiment of the present 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, and duration. After receiving the RLC entity activation / deactivation signal, the UE 10 should activate / deactivate the RLC entity according to the RLC entity activation / deactivation configuration, and start the timer 14 at the same time. Then the UE 10 reports the active / inactive state information of the RLC entity to the network node 200. When the timing time of the timer 14 is reached, the UE 10 can restore the RLC entity to the active / inactive state or the default state before the activation / deactivation operation. If the modified RLC entity activation / deactivation signaling is received from the network node 200 before the timer 14 reaches the timing time, the UE 10 can execute the indicated latest configuration, restart the timer 14, and then report the RLC entity status information to the network node 200.
[0206] 2. Example 3
[0207] See also Figure 7 , Figure 8 and Fig. 9 . Fig. 9 A timing diagram of an RLC entity according to another embodiment of the present application is shown. The embodiment discloses a method, which discloses that an RLC entity activation / deactivation configuration can periodically activate / deactivate an RLC entity. The RLC entity activation / deactivation configuration may include parameters such as a DRB ID, an RLC ID, an activation / deactivation operation, a periodicity, an activity / inactivity duration, and a number of times.
[0208] 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 for a period of time according to the configuration, and then restores 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 periodically activate / deactivate the RLC entity until the timer 14 reaches the set duration or the configured number of times. Alternatively, the UE 10 may periodically perform activation / deactivation until new signaling of the DRB is received.
[0209] like Fig. 9 As shown, after receiving the RLC entity activation signal, UE 10 can activate the RLC entity RLCi at time t0 for a duration of t active , then for duration t active When it expires, deactivate it at time t1. Then, for a duration of T pWhen it expires, the RLC entity RLCi is activated again at time t2 and the T p Repeat the operation in a cycle. Duration t active和 T p It is a configuration parameter. The parameter may be different for each RLC entity or each DRB. That is, for different RLC entities, the parameter may be the same or different.
[0210] UE 10 may report the active / inactive state information of the RLC entity to network node 200. The report may be performed at a regularly specified period or may be performed every time the state of the RLC entity is changed.
[0211] Fig.10 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.
[0212] 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.
[0213] 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.
[0214] 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.
[0215] 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).
[0216] 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.
[0217] 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.
[0218] 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.
[0219] 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.
[0220] 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.
[0221] 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.
[0222] 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.
[0223] The embodiment of the present application provides a method for controlling the activation / deactivation of a radio link control (RLC) entity, a base station, and a user equipment, which is used to solve the problem that a network node cannot control the active / inactive state of the RLC entity of a user equipment belonging to another network node when the DRB used in the combination of the DC architecture and the CA architecture is configured with PDCP replication of more than two RLC entities. However, the present application proposes that the RLC entity activation / deactivation configuration can be sent by a network node to the CN and forwarded to another network node, and then the other network node sends the configuration to the UE, or the primary node can send the activation / deactivation signal to the auxiliary node, and then the auxiliary node forwards the RLC entity activation / deactivation signal to the UE. In addition, for services with high latency requirements, the network node directly sends the RLC entity activation / deactivation signaling to the UE via the Uu interface. For data packets that can meet the delay requirements by introducing X2 / Xn delay, the network node transmits the RLC entity activation / deactivation signaling to the UE via the Uu interface and other network nodes. Due to the introduction of X2 / Xn interface delay, it can be used for services that do not require high latency. Therefore, the present application can effectively activate / deactivate the device of the RLC entity.
[0224] 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 controlling a radio link control (RLC) entity of a user equipment, wherein the user equipment operates in a primary network, wherein the primary network includes a primary network node, comprising: Determine the delay level of the data packet according to the quality of service QoS information; When the delay level of the data packet meets the X2 / Xn interface delay, RLC entity activation / deactivation signaling is sent to the user equipment and the auxiliary network node at the same time; receiving a report message indicating an RLC entity state of the user equipment, the user equipment responding to the RLC entity activation / deactivation signaling to activate / deactivate the RLC entity; forwarding the report message to the auxiliary network node; as well as The activity state of the RLC entity of the user equipment is updated according to the report message.
2. The method according to claim 1, characterized in that: Also includes: The RLC entity activation / deactivation signaling is transmitted to the auxiliary network node via an X2 / Xn interface.
3. The method according to claim 1, characterized in that Also includes: The RLC entity activation / deactivation signaling is transmitted to the user equipment via a Uu interface.
4. The method according to claim 1, characterized in that: The RLC entity activation / deactivation signaling is in the form of a medium access control component MAC CE.
5. The method according to claim 4, characterized in that The RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
6. The method according to claim 4, characterized in that The RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
7. The method according to claim 1, characterized in that The number of RLC entities of the user equipment corresponding to a radio bearer is less than 5.
8. The method according to claim 7, characterized in that The RLC entity is hosted in a main cell group MCG and a secondary cell group SCG, and the main network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
9. The method according to claim 8, characterized in that The user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
10. The method according to claim 1, characterized in that The user equipment, the primary network node and the auxiliary network node are all in RRC_CONNECTED state.
11. The method according to claim 1, characterized in that: The user equipment configures a separate data radio bearer DRB.
12. The method according to claim 1, characterized in that The RLC entity activation / deactivation signaling includes the configuration of the duration.
13. The method according to claim 12, further comprising: receiving a timer expiration report message from the user equipment, the expiration report message indicating an activity state of the RLC entity of the user equipment when the timer of the user equipment expires within a duration; as well as The activity state of the RLC entity of the user equipment is updated according to the timer expiration report message.
14. The method according to claim 12, further comprising: Sending the modified RLC entity activation / deactivation signaling to the user equipment; receiving a timer restart report message from the user equipment, the timer restart report message indicating that when the timer is restarted before reaching the duration, the user equipment responds to the modified RLC entity activation / deactivation signaling to activate / deactivate the active state of the RLC entity; and The activity state of the RLC entity of the user equipment is updated according to the timer restart report message.
15. The method according to claim 12, characterized in that The main network node is a base station, and the main network node and the user equipment are in a dual connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual connection DC architecture and the carrier aggregation CA architecture.
16. The method according to claim 12, characterized in that The configuration also includes separating data radio bearer DRBID, RLC ID, and operations related to activation / deactivation of RLC entities.
17. The method according to claim 16, characterized in that The separate data radio bearer is configured for the user equipment.
18. The method according to claim 12, characterized in that The user equipment and the primary network node are in RRC_CONNECTED state.
19. The method according to claim 1, characterized in that Also includes: The RLC entity activation / deactivation signaling is periodically sent to the user equipment.
20. The method according to claim 19, characterized in that The information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic times.
21. 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: Determine the delay level of the data packet according to the quality of service QoS information; When the delay level of the data packet meets the X2 / Xn interface delay, RLC entity activation / deactivation signaling is sent to the user equipment and the auxiliary network node at the same time; receiving a report message indicating an RLC entity state of the user equipment, the user equipment responding to the RLC entity activation / deactivation signaling to activate / deactivate the RLC entity; forwarding the report message to the auxiliary network node; and The activity state of the RLC entity of the user equipment is updated according to the report message.
22. The network node according to claim 21, characterized in that The operations also include: The RLC entity activation / deactivation signaling is transmitted to the auxiliary network node via an X2 / Xn interface.
23. The network node according to claim 21, characterized in that The operations also include: The RLC entity activation / deactivation signaling is transmitted to the user equipment via a Uu interface.
24. The network node according to claim 21, characterized in that The RLC entity activation / deactivation signaling is in the form of a medium access control component MAC CE.
25. The network node according to claim 24, characterized in that The RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
26. The network node according to claim 24, characterized in that The RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
27. The network node according to claim 21, characterized in that The number of RLC entities of the user equipment corresponding to a radio bearer is less than 5.
28. The network node according to claim 27, wherein the RLC entity is hosted in a main cell group (MCG) and a secondary cell group (SCG), and the network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
29. The network node according to claim 28, characterized in that The user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
30. The network node according to claim 21, characterized in that The user equipment, the network node and the auxiliary network node are all in RRC_CONNECTED state.
31. The network node according to claim 21, characterized in that The user equipment configures a separate data radio bearer DRB.
32. The network node according to claim 21, characterized in that The RLC entity activation / deactivation signaling includes the configuration of the duration.
33. The network node according to claim 32, characterized in that The operations also include: receiving a timer expiration report message from the user equipment, the expiration report message indicating an activity state of the RLC entity of the user equipment when the timer of the user equipment expires within a duration; and The activity state of the RLC entity of the user equipment is updated according to the timer expiration report message.
34. The network node according to claim 32, characterized in that The operations also include: Sending the modified RLC entity activation / deactivation signaling to the user equipment; receiving a timer restart report message from the user equipment, the timer restart report message indicating that when the timer is restarted before reaching the duration, the user equipment responds to the modified RLC entity activation / deactivation signaling to activate / deactivate the active state of the RLC entity; and The activity state of the RLC entity of the user equipment is updated according to the timer restart report message.
35. The network node according to claim 32, characterized in that The network node is a base station, and the network node and the user equipment are in a dual-connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual-connection DC architecture and the carrier aggregation CA architecture.
36. The network node according to claim 32, characterized in that The configuration also includes separating data radio bearer DRB ID, RLC ID, and operations related to activation / deactivation of RLC entities.
37. The network node according to claim 36, characterized in that The separate data radio bearer is configured for the user equipment.
38. The network node according to claim 32, characterized in that The user equipment and the network node are in RRC_CONNECTED state.
39. The network node according to claim 21, characterized in that The operations also include: An RLC entity that periodically sends activation / deactivation signals to user equipment.
40. The network node according to claim 39, characterized in that The information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic times.
41. A method for controlling a radio link control RLC of a user equipment, characterized in that: include: When a delay level of a received data packet complies with an X2 / Xn interface delay, wherein the delay level of the data packet is determined according to quality of service (QoS) information, the user equipment receives an RLC entity activation / deactivation signaling from a primary network node, and receives an RLC entity activation / deactivation signaling from an auxiliary network node, wherein the RLC entity activation / deactivation signaling is forwarded by the primary network node to the auxiliary network node through an X2 / Xn interface; The user equipment activates / deactivates the RLC entity according to RLC entity activation / deactivation signaling from the primary network node and the secondary network node; and A report message is sent from the user equipment to the primary network node, the report message indicating an activity status of an RLC entity of the user equipment.
42. The method according to claim 41, characterized in that Also includes: The RLC entity activation / deactivation signaling is received from the primary network node or the secondary network node through the Uu interface.
43. The method according to claim 41, characterized in that The RLC entity activation / deactivation signaling is in the form of a medium access control component MAC CE.
44. The method according to claim 43, characterized in that The RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
45. The method according to claim 43, characterized in that The RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
46. The method according to claim 41, characterized in that The number of RLC entities of the user equipment corresponding to a radio bearer is less than 5.
47. The method according to claim 41, characterized in that The RLC entity is hosted in a main cell group MCG and a secondary cell group SCG, and the main network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
48. The method according to claim 47, characterized in that The user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
49. The method according to claim 41, characterized in that The user equipment, the primary network node and the auxiliary network node are all in RRC_CONNECTED state.
50. The method according to claim 41, characterized in that The user equipment configures a separate data radio bearer DRB.
51. The method according to claim 41, characterized in that The RLC entity activation / deactivation signaling includes the configuration of the duration.
52. The method according to claim 51, characterized in that Also includes: When the RLC entity activation / deactivation signaling is received, a timer of the user equipment is started.
53. The method according to claim 52, characterized in that Also includes: When the timer reaches the duration, restoring the activity state of the RLC entity of the user equipment; as well as The timer expiration report message is sent to the primary network node, wherein the timer expiration report message indicates an activity status of an RLC entity of the user equipment.
54. The method of claim 52, further comprising: restarting the timer of the user equipment after receiving the modified RLC entity activation / deactivation signal until the duration is reached; activating / deactivating an RLC entity 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 activity status of an RLC entity of the user equipment.
55. The method according to claim 51, characterized in that The main network node is a base station, and the main network node and the user equipment are in a dual connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual connection DC architecture and the carrier aggregation CA architecture.
56. The method according to claim 51, characterized in that The configuration also includes separating data radio bearer DRBID, RLC ID, and operations related to activation / deactivation of RLC entities.
57. The method according to claim 56, characterized in that The separate data radio bearer is configured for the user equipment.
58. The method according to claim 51, characterized in that The user equipment and the primary network node are in RRC_CONNECTED state.
59. The method according to claim 41, characterized in that Also includes: A report message is periodically sent from the user equipment to a primary network node, the report message indicating an activity status of the RLC entity of the user equipment.
60. The method according to claim 51, characterized in that The information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic times.
61. A user device comprising: Transceiver; and A processor is electrically connected to the transceiver and configured to perform the following operations, wherein the operations include: receiving, when the delay level of the data packet meets the X2 / Xn interface delay, receiving an RLC entity activation / deactivation signaling from the primary network node, and receiving an RLC entity activation / deactivation signaling from the secondary network node, wherein the RLC entity activation / deactivation signaling is forwarded by the primary network node to the secondary network node through the X2 / Xn interface; activating / deactivating the RLC entity according to RLC entity activation / deactivation signaling from the primary network node and the secondary network node; and A report message is sent to the primary network node, the report message indicating an activity status of an RLC entity of the user equipment.
62. The user equipment according to claim 61, characterized in that The operations also include: The RLC entity activation / deactivation signaling is received from the primary network node or the secondary network node through the Uu interface.
63. The user equipment according to claim 61, characterized in that The RLC entity activation / deactivation signaling is in the form of a medium access control component MAC CE.
64. The user equipment according to claim 63, characterized in that The RLC entity activation / deactivation signaling is in the form of a MAC entity bitmap.
65. The user equipment according to claim 63, characterized in that The RLC entity activation / deactivation signaling is in the form of a radio bearer RB.
66. The user equipment according to claim 61, characterized in that The number of RLC entities of the user equipment corresponding to a radio bearer is less than 5.
67. The user equipment according to claim 61, characterized in that The RLC entity is hosted in a main cell group MCG and a secondary cell group SCG, and the main network node is configured in the main cell group, and the secondary network node is configured in the secondary cell group.
68. The user equipment according to claim 67, characterized in that The user equipment, the primary unit group and the secondary unit group are in a dual connection DC architecture and a carrier aggregation CA architecture.
69. The user equipment according to claim 61, characterized in that The user equipment, the primary network node and the auxiliary network node are all in RRC_CONNECTED state.
70. The user equipment according to claim 61, characterized in that The user equipment configures a separate data radio bearer DRB.
71. The user equipment according to claim 61, characterized in that The RLC entity activation / deactivation signaling includes the configuration of the duration.
72. The user equipment according to claim 71 further comprises a timer, characterized in that: The operations also include: The timer is started when the RLC entity activation / deactivation signaling is received.
73. The user equipment according to claim 72, characterized in that The operations also include: When the timer reaches the duration, restoring the activity state of the RLC entity of the user equipment; and The timer expiration report message is sent to the primary network node, wherein the timer expiration report message indicates an activity status of an RLC entity of the user equipment.
74. The user equipment according to claim 72, characterized in that The operations also include: restarting the timer of the user equipment after receiving the modified RLC entity activation / deactivation signal until the duration is reached; activating / deactivating an RLC entity 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 activity status of an RLC entity of the user equipment.
75. The user equipment according to claim 71, characterized in that The main network node is a base station, and the main network node and the user equipment are in a dual connection DC architecture, or a carrier aggregation CA architecture, or a combination of the dual connection DC architecture and the carrier aggregation CA architecture.
76. The user equipment according to claim 71, characterized in that The configuration also includes separating data radio bearer DRB ID, RLC ID, and operations related to activation / deactivation of RLC entities.
77. The user equipment according to claim 76, characterized in that The separate data radio bearer is configured for the user equipment.
78. The user equipment according to claim 71, characterized in that The user equipment and the primary network node are in RRC_CONNECTED state.
79. The user equipment of claim 61, the operations further comprising: A report message is periodically sent from the user equipment to a primary network node, the report message indicating an activity status of the RLC entity of the user equipment.
80. The user equipment according to claim 71, characterized in that The information carried by the RLC entity activation / deactivation signaling includes duration, separate data radio bearer DRB ID, RLC ID, operations associated with activation / deactivation of the RLC entity, and periodic times.
81. 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 20.
82. 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 a method according to any one of claims 41 to 60.
83. A computer-readable storage medium storing a computer program, wherein the computer program executes the method according to any one of claims 1 to 20 through a computer.
84. A computer-readable storage medium storing a computer program, wherein the computer program executes the method of any one of claims 41 to 60 through a computer.
85. A computer program product, comprising a computer program, wherein the computer program executes the method of any one of claims 1 to 20 via a computer.
86. A computer program product comprising a computer program, wherein the computer program executes the method of any one of claims 41 to 60 via a computer.
