Wireless communication node

Abstract

The gNB (100A) processes a packet data convergence protocol layer, and performs control in a radio link control layer and the packet data convergence protocol layer. The gNB (100A) receives, from the gNB (100B), node information including at least any one of identification information identifying a radio link control layer in the gNB (100B) corresponding to the gNB (100A) and quality information indicating a radio quality of the radio link control layer in the gNB (100B). The gNB (100A) transmits, to the UE (200), a control element of a medium access control layer in accordance with a content of the node information.

Description

Technical Field

[0001] This disclosure relates to a wireless communication node that performs wireless communication with a terminal. Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) standardized Long Term Evolution (LTE), and also standardized LTE-Advanced (hereinafter referred to as LTE, including LTE-Advanced) and the 5th generation mobile communication system (also known as 5G, New Radio (NR), or Next Generation (NG)) with the aim of further increasing the speed of LTE.

[0003] In 3GPP Release 16 (NR), specification research related to IIoT (Industrial Internet of Things) is being advanced (Non-Patent Document 1). Among these studies, in order to provide Ultra-Reliable and Low-Latency Communications (URLLC) for User Equipment (UE), an extension of packet replication (hereinafter referred to as PDCP replication) of the Packet Data Convergence Protocol Layer (PDCP) is being investigated.

[0004] Specifically, in carrier aggregation (CA) or dual connectivity with CA (NR-DC), a method is being investigated to specify PDCP replication using up to four Radio Link Control (RLC) entities set by the Radio Resource Control (RRC).

[0005] Furthermore, in 3GPP, in the application of CA and DC architectures, in order to control the state of multiple RLC entities used as data radio bearers (DRBs) spanning two nodes (also referred to as radio base stations), a control element (MAC-CE) for introducing a new Media Access Control (MAC) layer was agreed upon (Non-Patent Document 2). In addition, the format of this MAC-CE was also proposed (Non-Patent Document 3).

[0006] Existing technical documents

[0007] Non-patent literature

[0008] Non-patent document 1: "Support of NR Industrial Internet of Things (IoT)", RP-192324, 3GPP TSG RAN Meeting #85, 3GPP, September 2019

[0009] Non-patent literature 2: "LS on Network Coordination for UL PDCP Duplication", R2-1916576, 3GPP TSG-RAN WG2 Meeting#108, 3GPP, November 2019

[0010] Non-patent literature 3: "MAC Running CR for NR IIOT", R2-1916352, 3GPP TSG-RAN WG2 Meeting#108, 3GPP, November 2019 Summary of the Invention

[0011] However, in the structure of CA and DC as described above, when DRB is used to control multiple RLC entities to achieve PDCP replication, especially in the uplink (UL), coordination between the nodes is required as DRB spans two nodes, namely, the primary cell group (MCG) and the secondary cell group (SCG).

[0012] The following disclosure is made in view of this situation, and its purpose is to provide a wireless communication node that, when controlling multiple RLC entities to achieve UL PDCP replication, can properly control the RLC entities even when configured such that the DRB spans the MCG and SCG.

[0013] One aspect of this disclosure is a wireless communication node (gNB 100A) that processes packet data convergence protocol layers. The wireless communication node includes: a control unit (RLC control unit 140 and PDCP control unit 150) that performs control in the radio link control layer and the packet data convergence protocol layer; a transmission unit (MAC-CE transmission unit 130) that transmits to a terminal (UE 200) control elements of the medium access control layer instructing an entity of the radio link control layer to operate or cease; and a receiving unit (wireless receiving unit 120) that receives node information from a corresponding node corresponding to the wireless communication node. The node information includes at least one of identification information identifying the radio link control layer in the corresponding node (gNB 100B) and quality information indicating the radio quality of the radio link control layer in the corresponding node. The control unit, based on the content of the node information, causes the transmission unit to transmit the control elements to the terminal.

[0014] One aspect of this disclosure is a wireless communication node (gNB 100A), wherein the wireless communication node constitutes a master node, the wireless communication node having: a control unit (RLC control unit 140 and PDCP control unit 150) that performs control in the radio link control layer and the packet data convergence protocol layer; a transmitting unit (MAC-CE transmitting unit 130) that transmits to a terminal (UE 200) control elements of the medium access control layer instructing an entity of the radio link control layer to operate or stop; and a receiving unit (wireless receiving unit 120) that receives node information from the sub-node, the node information including at least one of identification information identifying the radio link control layer in the sub-node and quality information indicating the radio quality of the radio link control layer in the sub-node, the control unit causing the transmitting unit to transmit the control elements to the terminal according to the content of the node information.

[0015] One aspect of this disclosure is a wireless communication node (gNB 100B), wherein the wireless communication node constitutes a secondary node, the wireless communication node having: a control unit (RLC control unit 140 and PDCP control unit 150) that performs control in the radio link control layer and the packet data convergence protocol layer; a transmitting unit (MAC-CE transmitting unit 130) that transmits to a terminal (UE 200) control elements of the medium access control layer instructing an entity of the radio link control layer to operate or stop; and a receiving unit (wireless receiving unit 120) that receives node information from the primary node, the node information including at least one of identification information identifying the radio link control layer in the primary node and quality information indicating the radio quality of the radio link control layer in the primary node, the control unit causing the transmitting unit to transmit the control elements to the terminal based on the content of the node information.

[0016] One aspect of this disclosure is a wireless communication node (gNB 100A), wherein the wireless communication node constitutes a master node, a control unit (RLC control unit 140 and PDCP control unit 150) that performs control in the radio link control layer and packet data convergence protocol layer; and a transmission unit (MAC-CE transmission unit 130) that sends to a terminal (UE 200) control elements of the medium access control layer instructing the entity of the radio link control layer to operate or stop, the control unit sending node information to a sub-node (gNB 100B), the node information including at least one of the control elements, identification information identifying the radio link control layer in the master node, and quality information indicating the radio quality of the radio link control layer in the master node.

[0017] One aspect of this disclosure is a wireless communication node (gNB 100B), wherein the wireless communication node constitutes a secondary node, the wireless communication node having: a control unit (RLC control unit 140 and PDCP control unit 150) that performs control in the radio link control layer and the packet data convergence protocol layer; and a transmission unit (MAC-CE transmission unit 130) that sends to a terminal (UE 200) a medium access control layer control element instructing an entity of the radio link control layer to operate or stop, the control unit sending node information to a primary node (gNB 100A), the node information including at least one of the control element, identification information identifying the radio link control layer in the secondary node, and quality information indicating the radio quality of the radio link control layer in the secondary node. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10.

[0019] Figure 2 This is the function block structure diagram of gNB 100A and gNB 100B.

[0020] Figure 3 This is the function block structure diagram of UE 200.

[0021] Figure 4 This is a diagram illustrating an example of the structure of a Data Radio Bearer (DRB).

[0022] Figure 5 This is a diagram illustrating a structural example of Duplication RLC Activation / Deactivation MAC-CE.

[0023] Figure 6 This is a diagram showing the communication timing related to PDCP replication involved in Action Example 1.

[0024] Figure 7 This is a diagram showing the communication timing related to PDCP replication involved in Action Example 2-1.

[0025] Figure 8 This is a diagram showing the communication timing related to PDCP replication involved in Action Example 2-2.

[0026] Figure 9 This is a diagram showing the communication timing related to the PDCP replication involved in Action Example 3.

[0027] Figure 10 This is a diagram illustrating an example of the hardware structure of gNB 100A, gNB 100B, and UE 200. Detailed Implementation

[0028] The embodiments will now be described with reference to the accompanying drawings. Furthermore, the same or similar reference numerals will be used for the same functions and structures, and their descriptions will be omitted where appropriate.

[0029] (1) Overall general structure of wireless communication system

[0030] Figure 1 This is a schematic diagram of the overall structure of the wireless communication system 10 in this embodiment. The wireless communication system 10 is a wireless communication system that follows 5G New Radio (NR) and includes a next-generation radio access network 20 (hereinafter referred to as NG-RAN 20) and a terminal 200 (user equipment 200, hereinafter referred to as UE 200)).

[0031] NG-RAN 20 includes radio base station 100A (hereinafter referred to as gNB 100A) and radio base station 100B (hereinafter referred to as gNB 100B). Furthermore, the specific structure of the wireless communication system 10, which includes gNBs and UEs, is not limited to... Figure 1 The example shown.

[0032] NG-RAN 20 actually contains multiple NG-RAN nodes, specifically multiple gNBs (or ng-eNBs), connected to a 5G-compliant core network (5GC, not shown). Additionally, NG-RAN 20 and 5GC can be simply referred to as a "network".

[0033] gNB 100A and gNB 100B are 5G-compliant wireless base stations that perform 5G-compliant wireless communication with UE 200. In this embodiment, gNB 100A and gNB 100B constitute wireless communication nodes.

[0034] gNB 100A is included in primary cell group 30 (hereinafter referred to as MCG 30), and gNB 100B is included in secondary cell group 40 (hereinafter referred to as SCG 40). gNB 100A can also be referred to as primary node (MN), and gNB 100B can also be referred to as secondary node (SN).

[0035] gNB 100A, gNB 100B and UE 200 can support Massive MIMO, which generates more directional beams by controlling radio signals transmitted from multiple antenna elements, carrier aggregation (CA) that uses multiple component carriers (CC), and dual connectivity (DC) that allows the UE to communicate simultaneously with multiple NG-RAN nodes.

[0036] In addition, gNB 100A, gNB 100B and UE 200 can process multiple layers, specifically the Media Access Control (MAC) layer, Radio Link Control (RLC) layer, Packet Data Convergence Protocol (PDCP) layer and Radio Resource Control (RRC) layer.

[0037] Furthermore, gNB 100A, gNB 100B, and UE 200 support the duplication of PDCP Protocol Data Units (PDUs) and Service Data Units (SDUs) in order to support Ultra-Reliable and Low Latency Communications (URLLC).

[0038] In particular, in the wireless communication system 10, in order to support higher reliability and / or better PDCP replication, a set or subset of multiple RLC entities or RLC branches can also be used for PDCP replication.

[0039] Specifically, to extend the PDCP replication of the uplink (UL), up to four RLC entities (or RLC tributaries) can be configured. Furthermore, examples of the structure of RLC entities and RLC tributaries will be described later.

[0040] (2) Functional block structure of wireless communication system

[0041] Next, the functional block structure of the wireless communication system 10 will be described. Specifically, the functional block structures of gNB 100A, gNB 100B, and UE 200 will be described.

[0042] (2.1) gNB 100A

[0043] Figure 2 This is the function block structure diagram of gNB 100A and gNB 100B. As mentioned above, gNB 100A constitutes the master node (MN).

[0044] like Figure 2 As shown, the gNB 100A includes a wireless transmitter 110, a wireless receiver 120, a MAC-CE transmitter 130, an RLC control unit 140, and a PDCP control unit 150.

[0045] The wireless transmitter 110 transmits downlink signals (DL signals) conforming to NR. Additionally, the wireless receiver 120 receives uplink signals (UL signals) conforming to NR.

[0046] In this embodiment, the wireless receiver 120 is capable of receiving node information from the gNB 100B(SN). In this embodiment, the wireless receiver 120 constitutes a receiver for receiving node information.

[0047] The node information may include at least one of the following: identification information of the Radio Link Control Layer (RLC) in the gNB 100B that constitutes the corresponding node (specifically the sub-node (SN)) corresponding to the gNB 100A (wireless communication node) and quality information representing the radio quality of the RLC in the gNB 100B.

[0048] Node information, also known as radio quality condition, can include at least one of the following: Data Radio Bearer (DRB) identity, logical channel identity, and cell group identity (cellGroupId), or a combination of these. Therefore, it suffices to show the RLC branch. Furthermore, node information can also include numerical values ​​representing the radio quality of the RLC (which can also be interpreted as DRB) in the gNB 100B. Details regarding node information will be described later.

[0049] The MAC-CE transmitting unit 130 transmits the control element (MAC-CE) in the MAC to the UE 200. In this embodiment, the MAC-CE transmitting unit 130 constitutes a transmitting unit that transmits the control element of the Media Access Control layer to the UE 200.

[0050] In particular, in this embodiment, the MAC-CE sending unit 130 can send a MAC-CE to the UE 200 indicating whether the RLC entity of the UE 200 is active or deactivated. Specifically, the MAC-CE sending unit 130 can send a Duplication RLC Activation MAC-CE to activate the RLC entity used for PDCP replication, or a Duplication RLC Deactivation MAC-CE to deactivate the RLC entity (hereinafter referred to as Duplication RLC Activation / Deactivation MAC-CE).

[0051] The RLC control unit 140 performs control in the RLC. Furthermore, the PDCP control unit 150 performs control in the PDCP. In this embodiment, the RLC control unit 140 and the PDCP control unit 150 constitute a control unit.

[0052] The RLC control unit 140 is capable of controlling RLC entities and RLC branches related to gNB 100A and UE 200. In particular, in this embodiment, the RLC control unit 140 is capable of operating and stopping (or setting and releasing) multiple RLC entities.

[0053] The RLC control unit 140 can send a Duplication RLC Activation / Deactivation MAC-CE from the MAC-CE transmission unit 130 to the UE 200 based on the node information (radio quality condition) received from the gNB 100B.

[0054] Specifically, the RLC control unit 140 can determine which RLC entity should be operated or stopped based on the RLC identification information included in the radio quality condition and / or the quality information indicating the radio quality of the RLC in the SN. When based on the quality information, an RLC entity with better radio quality can be selected.

[0055] RLC control unit 140 can request the transmission of node information from gNB 100B. Specifically, RLC control unit 140 can send a radio quality condition query to gNB 100B requesting the transmission of this node information.

[0056] Furthermore, the RLC control unit 140 can also send node information (radio quality condition) to the gNB 100B. In this case, the radio quality condition may include at least one of the following: the Duplication RLC Activation / Deactivation MAC-CE itself sent by the gNB 100A to the UE 200, identification information identifying the RLC (which can also be interpreted as an RLC entity) in the gNB 100A (MN), and quality information indicating the radio quality of the RLC in the MN. Alternatively, the RLC identification information and quality information may be the same as the node information received from the gNB 100B.

[0057] The PDCP control unit 150 is capable of performing PDCP replication using UL and DL with multiple RLC entities. Furthermore, the PDCP control unit 150 performs PDCP PDU / SDU assembly / disassembly, etc.

[0058] (2.2)gNB 100B

[0059] As described above, gNB 100B constitutes a secondary node. The following describes the differences between gNB 100B and gNB 100A.

[0060] The wireless receiver 120 is capable of receiving node information (radio quality condition) from the gNB 100A (MN). This node information is transmitted by the gNB 100A and, as described above, may include at least one of the identification information of the RLC in the MN and the quality information of the RLC in the MN.

[0061] In addition, the RLC control unit 140 can send Duplication RLC Activation / Deactivation MAC-CE from the MAC-CE transmission unit 130 to the UE 200 based on the content of the node information.

[0062] Furthermore, the RLC control unit 140 can also send node information (radio quality condition) to the gNB 100A. In this case, the radio quality condition may include at least one of the following: the Duplication RLC Activation / Deactivation MAC-CE itself sent by the gNB 100A to the UE 200, identification information identifying the RLC (which can also be interpreted as an RLC entity) in the gNB 100B (SN), and quality information indicating the radio quality of the RLC in the SN.

[0063] (2.3)UE 200

[0064] Figure 3 This is the function block structure diagram of UE 200. (Example) Figure 3 As shown, UE 200 includes a radio transmitter 210, a radio receiver 220, a MAC processing unit 230, an RLC processing unit 240, and a PRCP processing unit 250.

[0065] The wireless transmitter 210 transmits an uplink signal (UL signal) conforming to NR. Furthermore, the wireless receiver 220 receives a downlink signal (DL signal) conforming to NR.

[0066] The MAC processing unit 230 performs MAC-related processing. Specifically, the MAC processing unit 230 is capable of receiving MAC-CE from gNB 100A or gNB 100B.

[0067] In particular, in this embodiment, the MAC processing unit 230 is capable of receiving a Duplication RLC Activation / Deactivation MAC-CE from gNB 100A or gNB 100B. The MAC processing unit 230 sends the information contained in the MAC-CE to higher layers, specifically, sends the information contained in the MAC-CE to the RLC.

[0068] The RLC processing unit 240 performs RLC-related processing. Specifically, the RLC processing unit 240 executes the operation or shutdown of the RLC entity set by the UE 200 according to the activation or deactivation instructions of the RLC received from the MAC.

[0069] As described above, UE 200 can simultaneously configure up to four RLC entities based on the Duplication RLC Activation / Deactivation MAC-CE instruction. Furthermore, one of these four RLC entities can be designated as the primary (required) RLC entity.

[0070] The PRCP processing unit 250 performs PDCP-related processing (concealment, legitimacy verification, sequence arrangement, header compression, etc.). Furthermore, the PRCP processing unit 250 uses multiple RLC entities to perform PDCP replication.

[0071] Specifically, the PRCP processing unit 250 replicates PDCP packets (which can also be interpreted as PDUs or SDUs) in the UL direction and can send each replicated PDCP packet via any one of the multiple RLC entities.

[0072] Furthermore, the PRCP processing unit 250 can receive replicated PDCP packets from gNB 100A or gNB 100B via the plurality of RLC entities. The PRCP processing unit 250 performs PDCP reception processing using at least one of the received plurality of PDCP packets.

[0073] (3) Operation of wireless communication system

[0074] Next, the operation of the wireless communication system 10 will be explained. Specifically, the operation related to PDCP replication in the UL direction in gNB 100A, gNB 100B and UE 200 will be explained.

[0075] (3.1) Example of data wireless bearer structure

[0076] Figure 4 This embodiment shows a structural example of the data radio bearer (DRB). As described above, gNB 100A (MN) is included in MCG 30, and gNB 100B (SN) is included in SCG 40.

[0077] A data radio bearer 50 (hereinafter referred to as DRB 50) is configured between gNB 100A(MN), gNB 100B(SN) and UE 200. For example... Figure 4 As shown, the DRB 50 can also be configured between the UE 200 and the SN via the MN. This structure of the DRB 50 can also be referred to as a split bearer. As mentioned above, gNB 100A, gNB 100B, and UE 200 can support CA and DC, specifically, NR-DC. In the case of CA and DC structures, the user plane (U plane) can be distributed across the two nodes (MN, SN).

[0078] As described above, in this embodiment, a framework that allows up to four RLC entities to be configured simultaneously via DRB 50 can also be used. In this framework, the number of RLC entities corresponding to one CG is one, two, or three (excluding the primary one).

[0079] These three RLC entities can dynamically control their state (active or inactive) through Duplication RLC Activation / Deactivation MAC-CE.

[0080] (3.2) Example of MAC-CE structure

[0081] Figure 5 This illustrates a structural example of a Duplication RLC Activation / Deactivation MAC-CE. For example... Figure 5 As shown, the Duplication RLC Activation / Deactivation MAC-CE consists of one octet, containing the RLC... i Fields, DRB dup The Index and R fields are sufficient.

[0082] The Duplication RLC Activation / Deactivation MAC-CE is identified based on the MAC sub-header with logical channel I. The Duplication RLC Activation / Deactivation MAC-CE can be of a fixed size.

[0083] RLC i The field can indicate the active or deactivated state of PDCP replication for RLC entity i (0, 1, 2). In RLC i A value of 1 indicates that PDCP replication is active, while a value of 0 indicates that PDCP replication is inactive.

[0084] i is used for this DRB, and the LCID of the sub-RLC entity is represented in ascending order according to the order of MCG and SCG.

[0085] DRB dup The Index field indicates the DRB for which the MAC-CE is applied. The value of this field can also be in ascending order representing the PDCP replication and the DRB ID within the DRB comprised of the RLC entity associated with the MAC entity.

[0086] The R field represents reserved bits and is set to 0.

[0087] (3.3) Example of an action

[0088] Next, examples of actions related to PDCP replication will be explained. Specifically, this applies to the case where a CA and DC are applied, and a maximum of four RLC entities (RLC branches) are configured in one DRB, and these four RLC entities span the MCG and SCG (see [reference]). Figure 4 This section explains the actions related to PDCP duplication in UL under )

[0089] (3.3.1) Example 1 of the action

[0090] In this action example, MN and SN use the user plane (U plane) to share the state of PDCP replication.

[0091] Figure 6 The communication timing related to PDCP replication involved in Action Example 1 is shown. For example... Figure 6 As shown, gNB 100A(MN) sends a radio quality condition query (or polling flag = 1) from gNB 100B(MN) to gNB 100B to query the PDCP replication status (S10). Here, gNB 100A can also be interpreted as the node that processes PDCP, specifically, as the node that hosts the NR PDCP. Furthermore, gNB 100B can also be interpreted as the node corresponding to gNB 100A (corresponding node).

[0092] gNB 100B sends assistance information data containing radio quality conditions back to gNB 100A (S20). Assistance information data, etc., are specified in 3GPP TS 38.425.

[0093] The radio quality condition of a DRB (also known as an RLC bearer or RLC branch) can include at least one of DRBidentity, logical channel identity, or cellGroupId, or a combination thereof.

[0094] Wireless quality can be expressed numerically. For example, "0" can mean the worst quality. Alternatively, when wireless quality includes measurement results from the UE 200, such as the Sounding Reference Signal (SRS), the Reference Signal Received Power (RSRP), Reference Signal Received Quality (RSRQ), and Signal-to-Interference Plus Noise Power Ratio (SINR), in addition to the ID mentioned above, RSRP / RSRQ / SINR can also be notified to the gNB 100A (PDCP master node). In this case, at least one of RSRP, RSRQ, or SINR can be notified.

[0095] As a notification method, the measurement results for the RLC bearer (RLC entity) with the best wireless quality can also be notified, while for the remaining RLC bearers (i.e., the second and third RLC bearers with wireless quality), only the difference between the measurement results and those of the RLC bearer with the best wireless quality can be notified.

[0096] In addition, the radio quality condition transmitted by gNB 100B may also include information suggesting which RLC bearer (RLC tributary) should be activated, based on the aforementioned DRB identity, logical channel identity, or cellGroupId (or a combination thereof).

[0097] Furthermore, gNB 100A and gNB 100B can estimate the radio quality of the RLC bearer (RLC tributary) based on the aforementioned RSRP, RSRQ, or SINR.

[0098] Based on the received radio quality condition, gNB 100A determines which RLC entity to activate (or deactivate) and sends a Duplication RLC Activation / Deactivation MAC-CE (S30) to UE 200 to activate or deactivate that RLC entity.

[0099] Upon receiving the Duplication RLC Activation / Deactivation MAC-CE, the UE 200 enables or deactivates the RLC entity based on the content of the Duplication RLC Activation / Deactivation MAC-CE and performs PDCP settings (S40).

[0100] In addition, gNB 100A and gNB 100B also enable or disable the RLC entity and execute PDCP settings (S50, S60).

[0101] Thus, it is possible to start (or end) PDCP replication in the UL direction using multiple RLC entities, perform PDCP replication, and start (or end) UL communication (S70).

[0102] (3.3.2) Example 2 of the action

[0103] In this action example, MN and SN use the control plane (C plane) and share the state of PDCP replication. The following mainly explains the parts that differ from action example 1; for the parts that are the same, explanations are omitted as appropriate.

[0104] (3.3.2.1) Action Example 2-1

[0105] Figure 7 The communication timing related to PDCP replication involved in Action Example 2-1 is shown. In this action example, gNB100A(MN) always sends Duplication RLC Activation / Deactivation MAC-CE to UE 200.

[0106] like Figure 7As shown, gNB 100A sends an S-NODE MODIFICATION REQUEST (PDU Session Resource Modification Info - SN terminated) to gNB 100B (S110). The S-NODE MODIFICATION REQUEST is specified in 3GPP TS38.423. The S-NODE MODIFICATION REQUEST can contain the same radio quality condition query as in Action Example 1.

[0107] Based on the received S-NODE MODIFICATION REQUEST, gNB 100B returns an S-NODE MODIFICATION REQUEST ACKNOWLEDGE (PDU Session Resource Modification ResponseInfo-SN terminated) to gNB 100A (S120). The S-NODE MODIFICATION REQUEST ACKNOWLEDGE contains a radioquality condition.

[0108] The content of the radio quality condition and the actions based on the radio quality condition are the same as in Action Example 1. Additionally, in this action example, the information element (IE) of Duplication Activation in the PDU Session Resource Modification ResponseInfo-SN terminated can contain the content of the radio quality condition.

[0109] Alternatively, in the PDU Session Resource Modification Response Info-SN terminated, a new IE (e.g., RLC radioquality IE) can be set for radio quality conditions.

[0110] Alternatively, you can have "PDU Session Resource Modification Confirm Info-SN terminated" instead of "PDU Session Resource Modification Response Info-SN terminated".

[0111] Based on the received radio quality condition, gNB 100A determines which RLC entity to activate (or deactivate) and sends a Duplication RLC Activation / Deactivation MAC-CE (S130) to UE 200 to activate or deactivate that RLC entity.

[0112] The actions of S140 to S170 are the same as those of S40 to S70 in Action Example 1.

[0113] (3.3.2.2) Action Example 2-2

[0114] Figure 8 The communication timing related to PDCP replication involved in Action Example 2-2 is shown. In this action example, gNB100B(SN) always sends Duplication RLC Activation / Deactivation MAC-CE to UE 200.

[0115] like Figure 8 As shown, gNB 100B sends S-NODE MODIFICATION REQUIRED (PDUSession Resource Modification Info-MN terminated) (S210) to gNB 100A. S-NODE MODIFICATION REQUIRED is specified in 3GPP TS38.423. S-NODE MODIFICATION REQUIRED can contain the same radio quality condition query as in Action Example 1.

[0116] Based on the received S-NODE MODIFICATION REQUIRED, gNB 100A returns S-NODE MODIFICATION CONFIRM (PDU Session Resource Modification confirm Info-MN terminated) (S220) to gNB 100B. The S-NODE MODIFICATION CONFIRM contains the radio quality condition.

[0117] The content of the radio quality condition and the actions based on the radio quality condition are the same as in Action Example 1. Additionally, in this action example, similar to Action Example 2-1, the Duplication Activation information element (IE) in the PDU Session ResourceModification confirm Info-MN terminated can contain the content of the radio quality condition.

[0118] Alternatively, in PDU Session Resource Modification confirm Info-MN terminated, a new IE (e.g., RLC radio quality IE) can be set for radio quality conditions.

[0119] Based on the received radio quality condition, gNB 100B determines which RLC entity to activate (or deactivate) and sends a Duplication RLC Activation / Deactivation MAC-CE (S230) to UE 200 to activate or deactivate that RLC entity.

[0120] The actions of S240 to S270 are the same as those of S40 to S70 in Action Example 1.

[0121] Additionally, in Action Examples 2-1 and 2-2, either the MN or the SN sends a Duplication RLC Activation / Deactivation MAC-CE. However, it is also possible for the node in the MN or SN that first sent an S-NODEMODIFICATION REQUEST or S-NODE MODIFICATION REQUIRED to send a Duplication RLC Activation / Deactivation MAC-CE to the UE 200.

[0122] Furthermore, in this scenario, the node receiving an S-NODE MODIFICATION REQUEST or S-NODE MODIFICATION REQUIRED can start a timer (e.g., a radiocondition valid timer), while the node on the target side (also referred to as the corresponding node) disables the transmission of S-NODE MODIFICATION REQUEST or S-NODE MODIFICATION REQUIRED until the timer expires. This avoids the transmission and reception of useless messages, allowing the MN or SN to more effectively enable or disable the RLC entity.

[0123] (3.3.3) Example 3 of the action

[0124] In this action example, MN or SN can blindly send Duplication RLC Activation / Deactivation MAC-CE to UE200 without considering the state of the node on the target side.

[0125] Figure 9 The communication timing related to PDCP replication involved in Action Example 3 is shown. Figure 9 The example shown illustrates how the MN first sends a Duplication RLC Activation / Deactivation MAC-CE.

[0126] like Figure 9 As shown, gNB 100A(MN) sends Duplication RLC Activation / Deactivation MAC-CE (S310) to UE 200. gNB 100A blindly sends Duplication RLC Activation / Deactivation MAC-CE to UE 200 without considering the state of gNB 100B(SN).

[0127] The gNB 100A sends the MCG and SCG RLC activation / deactivation state to the gNB 100B simultaneously with the transmission of the Duplication RLC Activation / Deactivation MAC-CE (S320). Alternatively, the MCG and SCG RLC activation / deactivation state can be transmitted at the same timing as the Duplication RLC Activation / Deactivation MAC-CE transmission, or it can be transmitted at a predetermined time after the transmission of the Duplication RLC Activation / Deactivation MAC-CE.

[0128] The MCG and SCG RLC activation / deactivation state can also be referred to by other names. The MCG and SCG RLC activation / deactivation state can contain radio quality conditions related to the RLC entity (RLC bearer) of the gNB 100A. Alternatively, the MCG and SCG RLC activation / deactivation state can contain the Duplication RLC Activation / Deactivation MAC-CE itself sent to the UE 200. Furthermore, similar to Action Example 2, the MCG and SCG RLC activation / deactivation state can also contain settings related to the radio condition valid timer (timer start timing, time until expiration, etc.).

[0129] gNB 100A starts the timer (radio condition valid timer) based on the transmission of Duplication RLC Activation / Deactivation MAC-CE, and gNB 100B starts the timer based on the reception of MCG and SCG RLC activation / deactivation state (S330).

[0130] Here, as Figure 9As shown, as long as the timer expires, gNB 100B can further send DuplicationRLC Activation / Deactivation MAC-CE (S340) to UE 200 based on the content of the received MCG and SCG RLC activation / deactivation state. In this case, gNB 100B can also send the MCG and SCG RLC activation / deactivation state to gNB 100A (S350). The MCG and SCG RLC activation / deactivation state sent by gNB 100B can be the same as the MCG and SCG RLC activation / deactivation state sent by gNB 100A, but it can also include radio quality conditions related to the RLC entity (RLC bearer) of gNB 100B.

[0131] After the radio condition valid timer expires, gNB 100A and gNB 100B may also blindly send Duplication RLC Activation / Deactivation MAC-CE to UE 200 without considering the content of the MCG and SCG RLC activation / deactivation state or radioquality condition received from the target node.

[0132] exist Figure 9 In the example shown, gNB 100B sends Duplication RLC Activation / Deactivation MAC-CE (S360) to UE 200.

[0133] The actions of S370 to S400 are the same as those of S40 to S70 in Action Example 1.

[0134] (4) Function / Effect

[0135] According to the above implementation method, the following effects can be obtained. Specifically, gNB 100A can send a Duplication RLC Activation / Deactivation MAC-CE to UE 200 based on the radio quality condition (node ​​information) received from gNB 100B. Specifically, gNB 100A determines the RLC entity to be activated or deactivated based on the RLC identification information and / or quality information indicating the radio quality of the RLC in the SN contained in the radio quality condition, and can send a Duplication RLC Activation / Deactivation MAC-CE to UE 200 to indicate the activation or deactivation of the determined RLC entity. In addition, gNB 100B can also send a Duplication RLC Activation / Deactivation MAC-CE to UE 200 through the same operation as gNB 100A.

[0136] Therefore, when UL PDCP replication is achieved by controlling multiple RLC entities, even if DRB 50 is set to span MCG and SCG, the state of the multiple RLC entities can be shared between MCG (specifically gNB 100A(MN)) and SCG (specifically gNB100B(SN)).

[0137] This enables proper control over multiple RLC entities spanning MCG and SCG, and allows for more efficient provision of advanced services such as URLLC.

[0138] In addition, gNB 100A (gNB 100B) can send node information (radio quality condition) to gNB 100B (gNB 100A), including at least one of the following: the Duplication RLC Activation / Deactivation MAC-CE sent to UE 200, identification information identifying the RLC (which can also be interpreted as an RLC entity) in gNB 100A (MN), and quality information indicating the radio quality of the RLC in MN.

[0139] Therefore, even if gNB 100A (gNB 100B) blindly sends DuplicationRLC Activation / Deactivation MAC-CE to UE 200, gNB 100B can reliably identify the status of the RLC entity on the gNB100A side.

[0140] In this embodiment, the radio quality condition may include the DRB identity and / or quality information representing the radio quality of the RLC on the transmitting side. Therefore, understanding the state of the RLC entity in the target node helps determine the appropriate RLC entity to be activated or deactivated.

[0141] (5) Other implementation methods

[0142] The above describes the embodiments, but the present invention is not limited to the embodiments described herein. It will be obvious to those skilled in the art that various modifications and improvements can be made.

[0143] For example, in the above implementation, it was described that a maximum of 4 RLC entities can work simultaneously, but the number of RLC entities is as many as possible, which can be less than 4 or more than 5.

[0144] Furthermore, actions 1 to 3 described above can also be combined. For example, actions 1 and 3 can be combined, as can actions 2-1 or 2-2 and 3.

[0145] In addition, radio quality condition can simply refer to the identification information and / or quality information of the RLC entity in the node on the object side, and can also be called by other names.

[0146] In the above implementation, NR-DC is the premise, but it can also be applied to other DCs when the PDCP entity on the UE 200 side is set by a total of 3 or 4 RLC entities by the MN RLC entity and the SN RLC entity.

[0147] Furthermore, the block diagrams used in the description of the above embodiments ( Figure 2 , 3The diagram illustrates blocks organized by function. These functional blocks (structural units) are implemented through any combination of at least one of hardware and software. Furthermore, there are no particular limitations on the implementation method of each functional block. That is, each functional block can be implemented using a single device that is physically or logically combined, or by directly or indirectly (e.g., using wired, wireless, etc.) connecting two or more physically or logically separate devices. Functional blocks can also be implemented by combining software with one or more of the aforementioned devices.

[0148] The functions include, but are not limited to, judgment, determination, calculation, processing, derivation, investigation, search, confirmation, receiving, sending, output, access, resolution, selection, choosing, establishing, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, the functional block (structural part) that enables the sending function is called the transmitting unit or transmitter. In short, as mentioned above, there are no particular limitations on the implementation method.

[0149] Furthermore, the aforementioned gNB 100A, gNB 100B, and UE 200 (the device) can also function as a computer for processing the wireless communication method disclosed herein. Figure 10 This is a diagram illustrating an example of the hardware structure of the device. (As shown...) Figure 10 As shown, the device can also be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0150] Additionally, in the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware structure of this device can be configured to include one or more of the devices shown in Figures 1001 to 1006, or it can be configured to include no part of the device.

[0151] The functional blocks of the device (refer to) Figure 2 , 3 This can be achieved through any hardware element or combination of hardware elements of the computer device.

[0152] Furthermore, the functions of the device are implemented by reading predetermined software (programs) into hardware such as processor 1001 and memory 1002, thereby enabling processor 1001 to perform calculations and control communication of communication device 1004 or control at least one of reading and writing data in memory 1002 and storage 1003.

[0153] The processor 1001 controls the computer as a whole, for example, by enabling the operating system to function. The processor 1001 may also be a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc.

[0154] Furthermore, the processor 1001 reads programs (program code), software modules, data, etc., from at least one direction of the memory 1002 in the memory 1003 and the communication device 1004, and performs various processes accordingly. The program is used to cause the computer to perform at least a portion of the actions described in the above embodiments. Regarding the various processes described above, although it has been stated that the various processes are executed by one processor 1001, the various processes can also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be installed using more than one chip. Additionally, the program can also be transmitted from a network via a telecommunications line.

[0155] Memory 1002 is a computer-readable recording medium, and may be composed of at least one of the following: Read Only Memory (ROM), Erasable Programmable Memory (EPROM), Electrically Erasable Programmable Memory (EEPROM), Random Access Memory (RAM). Memory 1002 may also be referred to as a register, cache, main memory (main storage device), etc. Memory 1002 can store programs (program code), software modules, etc., capable of executing the methods involved in one embodiment of this disclosure.

[0156] The memory 1003 is a computer-readable recording medium, such as at least one of the following: CD-ROM (Compact Disc ROM), hard disk drive, floppy disk, magneto-optical disk (e.g., compact disc, digital multipurpose disk, Blu-ray disc, smart card), flash memory (e.g., card, stick, key drive), floppy disk, magnetic stripe, etc. The memory 1003 may also be referred to as an auxiliary storage device. The aforementioned recording medium may, for example, be a database, server, or other suitable medium that includes at least one of the memory 1002 and the storage 1003.

[0157] The communication device 1004 is hardware (transceiver) used for communication between computers via at least one of a wired network and a wireless network, and is also known as a network device, network controller, network card, communication module, etc.

[0158] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., in order to realize at least one of frequency division duplex (FDD) and time division duplex (TDD).

[0159] Input device 1005 is an input device that accepts input from external sources (e.g., keyboard, mouse, microphone, switch, button, sensor, etc.). Output device 1006 is an output device that performs output to external sources (e.g., display, speaker, LED, etc.). Alternatively, input device 1005 and output device 1006 can also be integrated (e.g., a touch panel).

[0160] Furthermore, devices such as processor 1001 and memory 1002 are connected via bus 1007 for communicating information. Bus 1007 can be configured using a single bus or different buses for each device.

[0161] Furthermore, the device can be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a field-programmable gate array (FPGA), and can also implement some or all of the functional blocks using this hardware. For example, the processor 1001 can also be implemented using at least one of these hardware components.

[0162] Furthermore, the notification of information is not limited to the forms / implementations described in this disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. In addition, RRC signaling may also be referred to as an RRC message, for example, it may be an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0163] The various forms / implementations described in this disclosure can also be applied to at least one of Long Term Evolution (LTE), LTE-Advanced (LTE-A), Super 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA 2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (registered trademark), systems using other suitable systems, and next-generation systems extended therefrom. Furthermore, multiple systems can be combined (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) for application.

[0164] The processing procedures, timing, and flow of the various forms / implementations described in this disclosure may be changed in order, provided there is no contradiction. For example, the elements of various steps are indicated using an illustrative order in the methods described in this disclosure, but are not limited to the specific order indicated.

[0165] In this disclosure, specific actions performed by the base station are sometimes also performed through its upper node, depending on the circumstances. In a network consisting of one or more network nodes having a base station, it is obvious that various actions for communicating with a terminal can be performed by at least one of the base station and other network nodes besides the base station (e.g., considering an MME or S-GW, but not limited to these). The above example illustrates a case where there is only one other network node besides the base station, but other network nodes can also be a combination of multiple other network nodes (e.g., an MME and an S-GW).

[0166] Information and signals (such as data) can be output from higher (or lower) layers to lower (or higher) layers. They can also be input or output through multiple network nodes.

[0167] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0168] The determination can be made by the value represented by 1 bit (0 or 1), by a Boolean value (Boolean: true or false), or by comparing numerical values ​​(e.g., comparing with a predetermined value).

[0169] The various forms / implementations described in this disclosure can be used individually or in combination, and can be switched depending on the execution. Furthermore, the notification of predetermined information is not limited to explicit notification (e.g., a "Yes X" notification) but can also be implicit notification (e.g., not notifying the predetermined information).

[0170] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted as commands, command sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0171] Furthermore, software, commands, and information can be sent and received via a transmission medium. For example, when software is sent from a website, server, or other remote source using at least one of wired technologies (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL) etc.) and wireless technologies (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0172] The information, signals, etc., described in this disclosure can also be represented using any of a variety of different technologies. For example, the data, commands, instructions, information, signals, bits, symbols, chips, etc., that may be involved in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination of these.

[0173] Furthermore, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms that have the same or similar meanings. For example, at least one of the channel and symbol may also be a signal (signaling). Additionally, a signal may also be a message. Furthermore, a component carrier (CC) may be referred to as a carrier frequency, cell, frequency carrier, etc.

[0174] The terms “system” and “network” as used in this disclosure are used interchangeably.

[0175] Furthermore, the information, parameters, etc., described in this disclosure may be represented using absolute values, relative values ​​to predetermined values, or other corresponding information. For example, wireless resources may also be indicated by indexes.

[0176] The names used for the above parameters are not limiting in any way. Furthermore, the formulas, etc., using these parameters sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by appropriate names, therefore the various names assigned to these various channels and information elements are not limiting in any way.

[0177] In this disclosure, the terms "Base Station (BS)," "wireless base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Sometimes, terms such as macro cell, small cell, femtocell, and picocell are also used to refer to base stations.

[0178] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services through the base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0179] Terms such as “cell” or “sector” refer to a portion or the entire coverage area of ​​at least one of the base stations and base station subsystems that provide communication services within that coverage area.

[0180] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" are used interchangeably.

[0181] For mobile stations, those skilled in the art sometimes also use the following terms: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handheld device, user agent, mobile client, client, or some other appropriate terms.

[0182] At least one of the base station and mobile station can also be referred to as a transmitting device, receiving device, communication device, etc. Furthermore, at least one of the base station and mobile station can be a device mounted on a mobile body, the mobile body itself, etc. The mobile body can be a vehicle (e.g., a car, an airplane, etc.), a mobile body moving in an unmanned manner (e.g., a drone, an autonomous vehicle, etc.), or a robot (humanized or unmanned). Additionally, at least one of the base station and mobile station also includes devices that do not necessarily move during communication operations. For example, at least one of the base station and mobile station can be an Internet of Things (IoT) device such as a sensor.

[0183] Furthermore, the base station in this disclosure can also be replaced by a mobile station (user terminal, hereinafter the same). For example, various forms / implementations of this disclosure can also be applied to structures that replace communication between the base station and the mobile station with communication between multiple mobile stations (e.g., also referred to as D2D (Device-to-Device), Vehicle-to-Everything (V2X), etc. In this case, the structure can also be configured such that the mobile station has the functions of the base station. In addition, terms such as "uplink" and "downlink" can also be replaced with terms corresponding to communication between terminals (e.g., "side"). For example, uplink channel, downlink channel, etc. can also be replaced with side channel.

[0184] Similarly, the mobile station in this disclosure can be replaced by a base station. In this case, the base station can also be configured to have the functions of a mobile station.

[0185] A radio frame can consist of one or more frames in the time domain. In the time domain, one or more frames can be called subframes. A subframe can consist of one or more time slots in the time domain. A subframe can be of a fixed duration (e.g., 1 ms) independent of the parameter set (numerology).

[0186] A parameter set can be communication parameters applied to at least one side of the transmission and reception of a signal or channel. For example, a parameter set can represent at least one of the following: Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, and specific windowing processing performed by the transceiver in the time domain.

[0187] In the time domain, a time slot can be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.). A time slot can be a time unit based on a set of parameters.

[0188] A time slot can contain multiple mini-time slots. Each mini-time slot can consist of one or more symbols in the time domain. Furthermore, a mini-time slot can also be called a sub-time slot. A mini-time slot can consist of fewer symbols than a time slot. PDSCH (or PUSCH) transmitted in time units larger than mini-time slots can be called PDSCH (or PUSCH) mapping type (type) A. PDSCH (or PUSCH) transmitted using mini-time slots can be called PDSCH (or PUSCH) mapping type (type) B.

[0189] Radio frames, subframes, time slots, mini-time slots, and symbols all represent time units for transmitting signals. Radio frames, subframes, time slots, mini-time slots, and symbols can also be referred to by their respective alternative names.

[0190] For example, one subframe can be called a Transmission Time Interval (TTI), multiple consecutive subframes can also be called a TTI, and one time slot or one mini-time slot can also be called a TTI. That is, at least one of the subframe and TTI can be a subframe (1ms) in the existing LTE, a period shorter than 1ms (e.g., symbols 1-13), or a period longer than 1ms. In addition, the unit representing TTI may not be called a subframe, but a time slot, mini-time slot, etc.

[0191] Here, TTI refers, for example, to the smallest unit of time for scheduling in wireless communication. For instance, in an LTE system, the base station schedules the allocation of radio resources (bandwidth, transmit power, etc., available to each user terminal) in units of TTI. However, the definition of TTI is not limited to this.

[0192] The Time Interval (TTI) can be the transmission time unit for channel-coded data packets (transmission blocks), code blocks, codewords, etc., or it can be a processing unit for scheduling, link adaptation, etc. Furthermore, when a TTI is given, the actual time interval (e.g., the number of symbols) in which the transmission block, code block, codeword, etc., are mapped can be shorter than that TTI.

[0193] Furthermore, when one time slot or one mini-time slot is referred to as a TTI, more than one TTI (i.e., more than one time slot or more than one mini-time slot) can constitute the minimum time unit for scheduling. Moreover, the number of time slots (mini-time slots) constituting this minimum time unit for scheduling can be controlled.

[0194] A TTI with a duration of 1ms is also known as a normal TTI (in LTE Rel.8-12), a long TTI, a normal subframe, a normal subframe, a long subframe, or a time slot. A TTI shorter than a normal TTI can be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini time slot, a sub-time slot, or a time slot.

[0195] Additionally, for long TTIs (e.g., regular TTIs, subframes, etc.), they can be replaced with TTIs with a duration of more than 1ms. For short TTIs (e.g., shortened TTIs, etc.), they can be replaced with TTIs with a duration of less than long TTIs and a duration of more than 1ms.

[0196] A resource block (RB) is a unit of resource allocation in both the time and frequency domains. In the frequency domain, it can contain one or more consecutive subcarriers. The number of subcarriers contained in an RB can be the same regardless of the parameter set; for example, it can be 12. The number of subcarriers contained in an RB can also be determined based on the parameter set.

[0197] Furthermore, the temporal domain of an RB can contain one or more symbols, and can be 1 time slot, 1 mini-time slot, 1 subframe, or 1 TTI in length. 1 TTI, 1 subframe, etc., can each be composed of one or more resource blocks.

[0198] In addition, one or more RBs can be referred to as Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0199] Furthermore, a resource block can consist of one or more resource elements (REs). For example, 1 RE can be a radio resource area consisting of 1 subcarrier and 1 symbol.

[0200] The Bandwidth Part (BWP) (also known as partial bandwidth, etc.) represents a contiguous subset of common resource blocks (RBs) used for a specific parameter set on a given carrier. Here, common resource blocks can be determined by indexing RBs based on a common reference point of that carrier. PRBs can be defined and numbered within a BWP.

[0201] A BWP can include a UL BWP and a DL BWP. One or more BWPs can be set for a UE within one carrier.

[0202] At least one of the configured BWPs can be active, and it is not assumed that the UE will transmit or receive predetermined signals / channels outside of an active BWP. Furthermore, the terms "cell," "carrier," etc., used in this disclosure can be replaced with "BWP."

[0203] The structures of radio frames, subframes, time slots, mini-time slots, and symbols described above are merely illustrative. For example, the number of subframes contained in a radio frame, the number of time slots in each subframe or radio frame, the number of mini-time slots contained in a time slot, the number of symbols and RBs contained in a time slot or mini-time slot, the number of subcarriers contained in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc., can be varied in many ways.

[0204] The terms “connected,” “coupled,” or any variations thereof are intended to indicate any direct or indirect connection or combination between two or more elements, including situations where there is one or more intermediate elements between the two mutually “connected” or “coupled” elements. The combination or connection between elements can be physical, logical, or a combination of these. For example, “access” can be used instead of “connected.” In the context of this disclosure, for two elements, it can be considered that they are mutually “connected” or “coupled” by using at least one of one or more wires, cables, and printed electrical connections, and as some non-limiting and non-inclusive examples, by using electromagnetic energy with wavelengths having wireless frequency domains, microwave regions, and light (including both visible and invisible regions).

[0205] The reference signal can be simply called the Reference Signal (RS), or, depending on the standard applied, the pilot signal.

[0206] As used in this disclosure, the word "based on" does not mean "based on only" unless otherwise expressly stated. In other words, the word "based on" means both "based on only" and "based on at least" both.

[0207] Alternatively, the term "unit" in the structure of the above devices can be replaced with "section," "circuit," "equipment," etc.

[0208] Any reference to elements using the designations "first," "second," etc., as used in this disclosure does not necessarily limit the number or order of these elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Therefore, reference to the first or second element does not imply that only two elements can be taken here, or that in any form the first element must precede the second element.

[0209] When the terms "include," "including," and their variations are used in this disclosure, these terms, like the term "comprising," imply inclusion. Furthermore, the term "or" as used in this disclosure implies non-exclusivity.

[0210] In this disclosure, for example, in cases where articles are added through translation, such as in English (e.g., a, an, and the), this disclosure may also include cases where the noun following these articles is in a plural form.

[0211] The terms "determining" and "determining" as used in this disclosure sometimes encompass a variety of actions. For example, "determining" and "determining" can include actions such as judging, calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, database, or other data structure), and ascertaining, which are considered as actions of "determining" and "determining." Furthermore, "determining" and "determining" can include actions such as receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, and accessing (e.g., accessing data in memory), which are considered as actions of "determining" and "determining." Additionally, "determining" and "determining" can include actions such as resolving, selecting, choosing, establishing, and comparing, which are considered as actions of "determining" and "determining." That is, "judgment" and "decision" can include matters in which any action has been "judged" or "decided". In addition, "judgment (decision)" can also be replaced by "assuming", "expecting", "considering", etc.

[0212] In this disclosure, the phrase "A and B are different" can also mean "A and B are not the same." Furthermore, this phrase can also mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0213] The present disclosure has been described in detail above, but it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the present disclosure is for illustrative purposes only and is not intended to be limiting.

[0214] Label Explanation

[0215] 10: Wireless communication system;

[0216] 20: NG-RAN;

[0217] 30: MCG;

[0218] 40: SCG;

[0219] 50: DRB;

[0220] 100A, 100B: gNB;

[0221] 110: Wireless Transmission Department;

[0222] 120: Wireless receiver unit;

[0223] 130: MAC-CE Transmitter;

[0224] 140: RLC control unit;

[0225] 150: PDCP control unit;

[0226] 200: UE;

[0227] 210: Wireless Transmission Unit;

[0228] 220: Wireless receiver unit;

[0229] 230: MAC Processing Unit;

[0230] 240: RLC processing unit;

[0231] 250: PRCP Processing Department;

[0232] 1001: Processor;

[0233] 1002: Memory;

[0234] 1003: Memory;

[0235] 1004: Communication devices;

[0236] 1005: Input device;

[0237] 1006: Output device;

[0238] 1007: Bus.

Claims

1. A wireless communication node, wherein the wireless communication node is provided with: a control section that performs control in a radio link control layer and a packet data convergence protocol layer; and a reception section that receives node information from another wireless communication node corresponding to the wireless communication node, the node information including quality information indicating a radio quality of the radio link control layer in the other wireless communication node and notifying a measurement result on a part of entities of the radio link control layer, the wireless communication node and the other wireless communication node together communicate with a terminal.

2. The wireless communication node according to claim 1, wherein the wireless communication node is provided with a transmission section that transmits a control element of a medium access control layer indicating operation or stop of an entity of the radio link control layer to a terminal.

3. The wireless communication node according to claim 2, wherein the control section causes the transmission section to transmit the control element to the terminal in accordance with a content of the node information.

Images