CN115053593A

CN115053593A - Wireless communication node

Info

Publication number: CN115053593A
Application number: CN202080095623.5A
Authority: CN
Inventors: 高桥秀明; 闵天杨
Original assignee: NTT Docomo Inc
Current assignee: NTT Docomo Inc
Priority date: 2020-02-12
Filing date: 2020-02-12
Publication date: 2022-09-13
Also published as: WO2021161433A1

Abstract

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

Description

Wireless communication node

Technical Field

The present disclosure relates to a wireless communication node that performs wireless communication with a terminal.

Background

In the third Generation Partnership Project (3 GPP), Long Term Evolution (LTE: Long Term Evolution) has been standardized, and for the purpose of further speeding up LTE, standardization of LTE-Advanced (hereinafter, referred to as LTE including LTE-Advanced) and fifth Generation mobile communication system (also referred to as 5G, New Radio (NR: New Radio) or Next Generation (NG: Next Generation) has been developed.

In release 16(NR) of 3GPP, a specification study related to IIoT (Industrial Internet of Things) is being advanced (non-patent document 1). Among them, in order to provide Ultra-Reliable and Low-delay communication (URLLC) of a terminal (User Equipment: UE), an extension of packet duplication (hereinafter, referred to as PDCP duplication) of a packet data convergence protocol layer (PDCP) is being studied.

Specifically, in Carrier Aggregation (CA) or dual connectivity combined with CA (NR-DC), a method of designating PDCP replication by an entity using up to 4 radio link control layers (RLC) set by a radio resource control layer (RRC) is being studied.

In the 3GPP, in a configuration to which CA and DC are applied, a control element (MAC-CE) for introducing a new medium access control layer (MAC) is agreed to control the states of a plurality of RLC entities as described above for a Data Radio Bearer (DRB) that spans 2 nodes (may also be referred to as a radio base station) (non-patent document 2). Further, a format of the MAC-CE is proposed (non-patent document 3).

Documents of the prior art

Non-patent document

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

Non-patent document 2: "LS on Network coding for UL PDCP Duplication", R2-1916576, 3GPP TSG-RAN WG2 Meeting #108, 3GPP, 11 months in 2019

Non-patent document 3: "MAC Running CR for NR IIOT", R2-1916352, 3GPP TSG-RAN WG2 Meeting #108, 3GPP, 11 months in 2019

Disclosure of Invention

However, in the configuration using CA and DC as described above, when implementing PDCP duplication by controlling a plurality of RLC entities as a DRB spanning 2 nodes, that is, spanning a Master Cell Group (MCG) and a Slave Cell Group (SCG), coordination between the nodes is required particularly in the Uplink (UL).

The following disclosure is made in view of such circumstances, and an object thereof is to provide a radio communication node capable of appropriately controlling a plurality of RLC entities even if DRBs are set so as to straddle MCG and SCG when PDCP replication of UL is realized by controlling the RLC entities.

One aspect of the present disclosure is a radio communication node (gNB 100A) that processes a packet data convergence protocol layer, the radio communication node including: a control section (RLC control section 140 and PDCP control section 150) that performs control in a radio link control layer and the packet data convergence protocol layer; a transmission unit (MAC-CE transmission unit (130)) which transmits, to a terminal (UE (200)), a control element of a medium access control layer that instructs an entity of the radio link control layer to operate or stop; and a receiving unit (radio receiving unit 120) that receives node information from a corresponding node corresponding to the radio communication node, the node information including at least one of identification information for identifying the radio link control layer in the corresponding node (gNB 100B) and quality information indicating radio quality of the radio link control layer in the corresponding node, and the control unit causes the control element to be transmitted from the transmitting unit to the terminal according to the content of the node information.

One aspect of the present disclosure is a radio communication node (gNB 100A) that constitutes a master node, the radio communication node including: a control section (RLC control section 140 and PDCP control section 150) that performs control in a radio link control layer and a packet data convergence protocol layer; and a transmitting part (MAC-CE transmitting part 130) that transmits, to a terminal (UE 200), a control element of a medium access control layer that instructs operation or stop of an entity of the radio link control layer; and a receiving unit (wireless receiving unit 120) that receives, from the secondary node, node information including at least either one of identification information for identifying the radio link control layer in the secondary node and quality information indicating radio quality of the radio link control layer in the secondary node, and the control unit causes the control element to be transmitted from the transmitting unit to the terminal in accordance with the content of the node information.

One aspect of the present disclosure is a radio communication node (gNB 100B) that constitutes a secondary node, the radio communication node including: a control section (RLC control section 140 and PDCP control section 150) that performs control in a radio link control layer and a packet data convergence protocol layer; and a transmitting part (MAC-CE transmitting part 130) that transmits, to a terminal (UE 200), a control element of a medium access control layer that instructs an operation or a stop of an entity of the radio link control layer; and a receiving unit (wireless receiving unit 120) that receives, from the master node, node information including at least one of identification information for identifying the radio link control layer in the master node and quality information indicating radio quality of the radio link control layer in the master node, the control unit causing the control element to be transmitted from the transmitting unit to the terminal according to the content of the node information.

One embodiment of the present disclosure is a radio communication node (gNB 100A) that constitutes a master node, a control section (RLC control section 140 and PDCP control section 150) that performs control in a radio link control layer and a packet data convergence protocol layer; and a transmission unit (MAC-CE transmission unit 130) that transmits, to a terminal (UE 200), a control element of a medium access control layer that instructs an entity of the radio link control layer to operate or stop, wherein the control unit transmits, to a secondary node (gNB 100B), node information that includes at least one of the control element, identification information that identifies the radio link control layer in the primary node, and quality information that indicates radio quality of the radio link control layer in the primary node.

One aspect of the present disclosure is a wireless communication node (gNB 100B) that constitutes a secondary node, the wireless communication node including: a control section (RLC control section 140 and PDCP control section 150) that performs control in a radio link control layer and a packet data convergence protocol layer; and a transmission unit (MAC-CE transmission unit 130) that transmits, to a terminal (UE 200), a control element of a medium access control layer that instructs an entity of the radio link control layer to operate or stop, wherein the control unit transmits, to a master node (gNB 100A), node information that includes at least one of the control element, identification information that identifies the radio link control layer in the secondary node, and quality information that indicates radio quality of the radio link control layer in the secondary node.

Drawings

Fig. 1 is a schematic configuration diagram of the entire wireless communication system 10.

Fig. 2 is a functional block diagram of gNB100A and gNB 100B.

Fig. 3 is a functional block diagram of the UE 200.

Fig. 4 is a diagram showing an example of the structure of a Data Radio Bearer (DRB).

Fig. 5 is a diagram showing an example of the structure of the Duplication RLC Activation/Deactivation MAC-CE.

Fig. 6 is a diagram illustrating a communication sequence related to PDCP replication in operation example 1.

Fig. 7 is a diagram showing a communication timing sequence related to PDCP replication according to the action example 2-1.

Fig. 8 is a diagram showing a communication timing related to PDCP replication according to action example 2-2.

Fig. 9 is a diagram showing a communication sequence related to PDCP replication in operation example 3.

Fig. 10 is a diagram showing an example of hardware configurations of the gNB100A, gNB100B and the UE 200.

Detailed Description

Hereinafter, embodiments will be described with reference to the drawings. The same or similar reference numerals are given to the same functions and structures, and the description thereof is appropriately omitted.

(1) General overall structure of wireless communication system

Fig. 1 is a schematic configuration diagram of the entire wireless communication system 10 according to the present embodiment. The Radio communication system 10 is a Radio communication system conforming to a New Radio interface (NR) of 5G, and includes a Next Generation Radio Access Network 20 (hereinafter, referred to as NG-RAN 20) and a terminal 200 (hereinafter, referred to as UE 200).

The NG-RAN 20 includes a radio base station 100A (hereinafter, referred to as a gNB 100A) and a radio base station 100B (hereinafter, referred to as a gNB 100B). In addition, the specific configuration of the wireless communication system 10 including the number of gnbs and UEs is not limited to the example shown in fig. 1.

The NG-RAN 20 actually includes a plurality of NG-RAN nodes (NG-RAN nodes), specifically, a plurality of gnbs (or NG-enbs), and is connected to a core network (5GC, not shown) compliant with 5G. In addition, the NG-RANs 20 and 5GC may be simply expressed as "networks".

The

gnbs

100A and 100B are radio base stations compliant with 5G, and perform radio communication compliant with 5G with the UE 200. In the present embodiment, gNB100A and gNB100B constitute a radio communication node.

gNB100A is included in master cell group 30 (hereinafter, MCG 30), and gNB100B is included in slave cell group 40 (hereinafter, SCG 40). The gNB100A may also be referred to as a primary node (MN), and the gNB100B may also be referred to as a Secondary Node (SN).

The gNB100A, gNB100B and the UE 200 can support massive mimo (massive mimo) in which beams with higher directivity are generated by controlling radio signals transmitted from a plurality of antenna elements, Carrier Aggregation (CA) in which a plurality of Component Carriers (CCs) are bundled, Dual Connectivity (DC) in which communication is simultaneously performed between the UE and a plurality of NG-RAN nodes, respectively, and the like.

Further, the gNB100A, gNB100B and the UE 200 can process a plurality of layers, specifically, a medium access control layer (MAC), a radio link control layer (RLC), a packet data convergence protocol layer (PDCP), a radio resource control layer, and the like.

Further, gNB100A, gNB100B and UE 200 support Ultra-Reliable and Low-delay Communications (URLLC), and support replication of Protocol Data Units (PDU) and Service Data Units (SDU) of PDCP (hereinafter referred to as PDCP replication).

In particular, in the wireless communication system 10, to support higher reliability and/or more preferred PDCP duplication, a set or subset of multiple RLC entities or RLC legs may also be used for PDCP duplication.

Specifically, in order to extend PDCP duplication for the Uplink (UL), a maximum of 4 RLC entities (or RLC legs) can be set. Note that, the following description will be given of an example of the structure of the RLC entity and the RLC leg.

(2) Functional block structure of wireless communication system

Next, a functional block configuration of the radio communication system 10 will be described. Specifically, the functional block structures of the gNB100A, gNB100B and the UE 200 will be explained.

(2.1)gNB 100A

Fig. 2 is a functional block diagram of gNB100A and gNB 100B. As described above, the gNB100A constitutes a Master Node (MN).

As shown in fig. 2, the gNB100A has a radio transmitting section 110, a radio receiving section 120, a MAC-CE transmitting section 130, an RLC control section 140, and a PDCP control section 150.

The radio transmission unit 110 transmits a downlink signal (DL signal) conforming to NR. Further, the radio reception unit 120 receives an uplink signal (UL signal) conforming to NR.

In the present embodiment, radio reception unit 120 can receive node information from gNB100b (sn). In the present embodiment, the radio receiving unit 120 constitutes a receiving unit that receives node information.

The node information may include at least any one of identification information identifying a radio link control layer (RLC) in the gNB100B constituting a corresponding node (specifically, a Secondary Node (SN)) corresponding to the gNB100A (wireless communication node) and quality information indicating radio quality of the RLC in the gNB 100B.

The node information may also be referred to as radio quality condition, and may include at least any one of identification information (DRB identification) of a Data Radio Bearer (DRB), identification information (logical channel identification) of a logical channel, and identification information (cellGroupId) of a cell group, or a combination of the identification information, so that only the RLC leg is shown. Further, the node information may also contain a numerical value indicating the radio quality of RLC (which may also be interpreted as DRB) in the gNB 100B. The details of the node information will be described later.

The MAC-CE transmitting part 130 transmits a control element (MAC-CE) in the MAC to the UE 200. In the present embodiment, the MAC-CE transmitting unit 130 constitutes a transmitting unit that transmits a control element of the medium access control layer to the UE 200.

In particular, in the present embodiment, the MAC-CE transmitting unit 130 can transmit, to the UE 200, a MAC-CE instructing the RLC entity of the UE 200 to operate or stop. Specifically, the MAC-CE transmitting unit 130 can transmit a duplicate RLC Activation MAC-CE (duplicate RLC Activation MAC-CE) for activating an RLC entity for PDCP replication or a duplicate RLC Deactivation MAC-CE (duplicate RLC Deactivation MAC-CE) for deactivating the RLC entity (hereinafter, referred to as duplicate RLC Activation/Deactivation MAC-CE).

The RLC control section 140 performs control in RLC. Further, the PDCP control section 150 performs control in PDCP. In the present embodiment, the RLC controller 140 and the PDCP controller 150 constitute a controller.

The RLC control part 140 can perform control of RLC entities and RLC legs related to the gNB100A and the UE 200. In particular, in the present embodiment, the RLC control unit 140 can perform operations and stops (may be replaced with setting and releasing) of a plurality of RLC entities.

The RLC control unit 140 can transmit the duplicate RLC Activation/Deactivation MAC-CE from the MAC-CE transmission unit 130 to the UE 200 according to the content of the node information (radio quality condition) received from the gNB 100B.

Specifically, the RLC control unit 140 can determine the RLC entity to be activated or deactivated 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. In case of being based on the quality information, an RLC entity having better radio quality can be selected.

RLC control unit 140 may request to gNB100B for transmission of node information. Specifically, the RLC controller 140 may transmit a radio quality condition request (radio quality condition query) requesting transmission of the node information to the gNB 100B.

The RLC controller 140 can also transmit node information (radio quality condition) to the gNB 100B. In this case, the radio quality condition may include at least any one of the dual RLC Activation/Deactivation MAC-CE itself transmitted by the gNB100A to the UE 200, identification information identifying the RLC (which may be interpreted as an RLC entity) in the gNB100A (MN), and quality information indicating the radio quality of the RLC in the MN. In addition, the RLC identification information and quality information may be the same as the node information received from the gNB 100B.

The PDCP control section 150 can perform PDCP duplication of UL and DL using a plurality of RLC entities. Further, the PDCP control section 150 performs assembling/disassembling of PDCP PDUs/SDUs and the like.

(2.2)gNB 100B

As described above, the gNB100B constitutes a secondary node. Hereinafter, a portion different from the gNB100A will be described.

The radio reception unit 120 can receive node information (radio quality condition) from the gNB100a (mn). The node information is transmitted by the gNB100A, and as described above, may include at least any one of identification information of the RLC in the MN and quality information of the RLC in the MN.

The RLC control unit 140 can transmit the duplicate RLC Activation/Deactivation MAC-CE from the MAC-CE transmission unit 130 to the UE 200 according to the contents of the node information.

The RLC controller 140 can also transmit node information (radio quality condition) to the gNB 100A. The radio quality condition in this case may include at least any one of the dual RLC Activation/Deactivation MAC-CE itself transmitted by the gNB100A to the UE 200, identification information identifying RLC (which may also be interpreted as an RLC entity) in the gNB100b (SN), and quality information indicating radio quality of RLC in the SN.

(2.3)UE 200

Fig. 3 is a functional block diagram of the UE 200. As shown in fig. 3, the UE 200 includes a radio transmission unit 210, a radio reception unit 220, a MAC processing unit 230, an RLC processing unit 240, and a PRCP processing unit 250.

The radio transmission unit 210 transmits an uplink signal (UL signal) conforming to NR. Further, the radio receiving section 220 receives a downlink signal (DL signal) conforming to NR.

The MAC processing section 230 performs processing related to MAC. Specifically, MAC processing unit 230 can receive MAC-CE from gNB100A or gNB 100B.

In particular, in the present embodiment, MAC processing unit 230 can receive a duplicate RLC Activation/Deactivation MAC-CE from gNB100A or gNB 100B. The MAC processing unit 230 transmits information included in the MAC-CE to the higher layer, and more specifically, transmits information included in the MAC-CE to the RLC.

The RLC processing section 240 performs RLC-related processing. Specifically, the RLC processor 240 executes the operation or stop of the RLC entity set by the UE 200 in response to an instruction of activation or deactivation of the RLC received from the MAC.

As described above, the UE 200 can simultaneously set up a maximum of 4 RLC entities according to the indication based on the duplexing RLC Activation/Deactivation MAC-CE. In addition, 1 RLC entity among the 4 RLC entities may be necessarily set as a primary (essential) RLC entity.

The PRCP processing unit 250 performs processing related to PDCP (concealment, validity check, sequence alignment, header (header) compression, and the like). In addition, the PRCP processing part 250 performs PDCP duplication using a plurality of RLC entities.

Specifically, the PRCP processing unit 250 duplicates PDCP packets (which may be interpreted as PDUs or SDUs) in the UL direction, and can transmit each of the duplicated PDCP packets via any one of the plurality of RLC entities.

Further, PRCP processing section 250 can receive the copied PDCP packet from gNB100A or gNB100B via the plurality of RLC entities. The PRCP processing section 250 performs reception processing in PDCP using at least any one of the received plurality of PDCP packets.

(3) Operation of a wireless communication system

Next, an operation of the radio communication system 10 will be described. Specifically, the operation related to PDCP replication in the UL direction in the gNB100A, gNB100B and the UE 200 will be described.

(3.1) example of configuration of data radio bearer

Fig. 4 shows an example of the configuration of a Data Radio Bearer (DRB) according to this embodiment. As described above, gNB100a (mn) is included in MCG 30, and gNB100b (sn) is included in SCG 40.

Between the gNB100a (mn), gNB100b (sn), and UE 200, a data radio bearer 50 (hereinafter, referred to as DRB 50) is set. As shown in fig. 4, the DRB 50 may also be set between the UE 200 and the SN via the MN. DRB 50 of this configuration may also be referred to as a split bearer. As described above, the gNB100A, gNB100B and the UE 200 can support CA and DC, and in particular, can support NR-DC. In the case of CA and DC configurations, the user plane (U plane) can be distributed among the 2 nodes (MN, SN).

As described above, in the present embodiment, an architecture (frame) in which a maximum of 4 RLC entities can be set simultaneously via the DRB 50 may be adopted. In this architecture, the number of RLC entities corresponding to 1 CG is 1, 2, or 3 (except for primary).

These 3 RLC entities can dynamically control the status (active) or inactive (inactive)) by the dual RLC Activation/Deactivation MAC-CE.

(3.2) example of MAC-CE construction

FIG. 5 shows an example of the structure of the duplicate RLC Activation/Deactivation MAC-CE. As shown in FIG. 5, the duplification RLC Activation/Deactivation MAC-CE is composed of 1 octet (octet) and includes RLC _i Field, DRB _dup An Index field and an R field.

The duplicate RLC Activation/Deactivation MAC-CE is identified from the MAC subheader with logical channel I. The duplicate RLC Activation/Deactivation MAC-CE is fixed in size.

RLC _i The field may indicate the PDCP multiplexing of RLC entity i (0, 1, 2)A state of activation or deactivation. At RLC _i The value of 1 in the field indicates that PDCP replication is active, and the value of 0 indicates that PDCP replication is inactive.

i indicates the LCID of the secondary RLC entity in ascending order in the order of MCG and SCG as the DRB.

DRB _dup The Index field indicates the DRB to which the MAC-CE is applied. The value of this field may also indicate the PDCP copy and the DRB ID in the DRB constituted by the RLC entity with which the MAC entity is associated in ascending order.

The R field is a reserved bit and is set to 0.

(3.3) operation example

Next, an operation example related to PDCP duplication will be described. Specifically, an operation example related to PDCP duplication (PDCP duplication) of the UL in the case where a maximum of 4 RLC entities (RLC legs) are set in CA and DC and 1 DRB and the 4 RLC entities span MCG and SCG (see fig. 4) will be described.

(3.3.1) operation example 1

In this operation example, the MN and the SN share the status of PDCP duplication using a user plane (U-plane).

Fig. 6 shows a communication sequence related to PDCP replication in operation example 1. As shown in fig. 6, the gNB100a (mn) sends a radio quality condition request (which may also be set to poll flag (polling flag) 1) inquiring about the status of PDCP copy in the gNB100B (mn) to the gNB100B (S10). Here, the gNB100A may also be interpreted as a node that handles PDCP, and more particularly, may also be interpreted as a node that hosts (host) NR PDCP. Furthermore, the gNB100B may also be interpreted as a node (correspondent node) corresponding to the gNB 100A.

The gNB100B sends back association information data (auxiliary information data) including the radio quality condition to the gNB100A (S20). The association information data and the like are specified in 3GPP TS 38.425.

The radio quality condition of the DRB (which may also be referred to as an RLC bearer or an RLC leg) may include at least any one of a DRB Identity, a local channel Identity, or a cellGroupId, or may include a combination thereof.

The radio quality may be expressed as a numerical value (numericaly). For example, "0" may mean the worst quality. Alternatively, when the radio Quality includes a measurement result (measurement result) from UE 200, a Sounding Reference Signal (SRS: Sounding Reference Signal), etc., a Reference Signal Received Power (RSRP: Reference Signal Received Power) of a UL Signal, a Reference Signal Received Quality (RSRQ: Reference Signal Received Quality), a Signal-to-Interference Noise Power Ratio (SINR: Signal-to-Interference Noise Power Ratio), etc., RSRP/RSRQ/SINR may be notified to the gsb 100A (PDCP) master node in addition to the above-described ID. In this case, at least one of RSRP, RSRQ, and SINR may be notified.

As the notification method, it is also possible to notify the measurement result of the RLC bearer (RLC entity) with the best radio quality, and notify only the difference between the measurement results of the RLC bearers with the best radio quality with respect to the remaining RLC bearers (i.e., the 2 nd and 3rd RLC bearers with radio quality).

In addition, the radio quality condition sent by the gNB100B may also include information that proposes which RLC bearer (RLC leg) should be operated (activated) according to the above-mentioned DRB Identity, local channel Identity, or cellGroupId (or a combination thereof).

Furthermore, the

gnbs

100A and 100B may estimate the radio quality of the RLC bearers (RLC legs) according to the RSRP, RSRQ, or SINR described above.

The gNB100A determines an RLC entity to be activated (or deactivated) according to the received radio quality condition, and transmits a dual RLC Activation/Deactivation MAC-CE to activate or deactivate the RLC entity to the UE 200 (S30).

The UE 200 that receives the dualization RLC Activation/Deactivation MAC-CE makes the RLC entity operate or stop according to the contents of the dualization RLC Activation/Deactivation MAC-CE, and performs PDCP setting (S40).

In addition, the gNB100A and gNB100B also operate or stop the RLC entity in the same manner, and perform PDCP setting (S50, S60).

Thereby, it is possible to start (or end) PDCP replication in the UL direction using a plurality of RLC entities, perform PDCP replication, and start (or end) UL communication (S70).

(3.3.2) operation example 2

In this operation example, the MN and the SN share the state of PDCP replication using the control plane (C-plane). Hereinafter, the description will be mainly given of portions different from those in operation example 1, and the description of the same portions will be omitted as appropriate.

(3.3.2.1) operation example 2-1

Fig. 7 shows a communication sequence related to PDCP replication according to the action example 2-1. In this operation example, the gNB100A (MN) always sends a duplicate RLC Activation/Deactivation MAC-CE to the UE 200.

As shown in FIG. 7, gNB100A sends a S-NODE MODIFICATION REQUEST (PDU Session Resource MODIFICATION Info-SN terminated: PDU Session Resource MODIFICATION information SN termination) to gNB100B (S110). S-NODE MODIFICATION REQUEST and the like are specified in 3GPP TS 38.423. The S-NODE MODIFICATION REQUEST may contain the same radio quality condition REQUEST as in action example 1.

gNB100B returns an S-NODE MODIFICATION REQUEST ACKNOWLEDGE (PDU Session Resource MODIFICATION Response Info-SN determined) to gNB100A based on the received S-NODE MODIFICATION REQUEST (S120). The S-NODE MODIFICATION REQUEST ACKNOWLEDGE contains the radio quality condition.

The contents of the radio quality condition and the operation based on the radio quality condition may be the same as in operation example 1. In the present embodiment, the content of the radio quality condition may be included in the Information Element (IE) of the duplicate Activation in the PDU Session Resource Modification Response Info-SN determined.

Alternatively, a new IE for radio quality control (e.g., RLC radio quality IE) may be set in the PDU Session Resource Modification Response Info-SN specified.

In addition, it is also possible to have PDU Session Resource Modification ConfirmInfo-SN determined instead of PDU Session Resource Modification Response Info-SN determined.

The gNB100A determines an RLC entity to be activated (or deactivated) according to the received radio quality condition, and transmits a dual RLC Activation/Deactivation MAC-CE to activate or deactivate the RLC entity to the UE 200 (S130).

The operations at S140 to S170 are the same as those at S40 to S70 in operation example 1.

(3.3.2.2) action example 2-2

Fig. 8 shows a communication timing for PDCP replication according to action example 2-2. In this example, gNB100B (SN) always sends a duplicate RLC Activation/Deactivation MAC-CE to UE 200.

As shown in fig. 8, gNB100B transmits S-NODE MODIFICATION request (PDU Session Resource MODIFICATION Info-MN determined) to gNB100A (S210). S-NODE MODIFICATION REQUIRED et al are specified in 3GPP TS 38.423. The S-NODE MODIFICATION REQUIRED may contain the same radio quality condition request as in working example 1.

gNB100A returns an S-NODE MODIFICATION CONFIRM (PDU Session Resource MODIFICATION con Info-MN determined) to gNB100B based on the received S-NODE MODIFICATION REQUERED (S220). The S-NODE MODIFICATION contains the radio quality condition.

The content of the radio quality condition and the operation based on the radio quality condition may be the same as in operation example 1. In this operation example, as in operation example 2-1, the Information Element (IE) of the duplicate Activation in the PDU Session Resource Modification confirmation Info-MN terminated may include the content of the radio quality condition.

Alternatively, a new IE for radio quality control (for example, RLC radio quality IE) may be set in the PDU Session Resource Modification control Info-MN specified.

The gNB100B determines an RLC entity to be activated (or deactivated) according to the received radio quality condition, and transmits a dual RLC Activation/Deactivation MAC-CE to activate or deactivate the RLC entity to the UE 200 (S230).

The operations of S240 to S270 are the same as those of S40 to S70 of operation example 1.

In addition, in the action example 2-1 and the action example 2-2, either one of the MN or the SN transmits the dualization RLC Activation/Deactivation MAC-CE, but the NODE of the MN or the SN, which first transmits the S-NODE MODIFICATION REQUEST or the S-NODE MODIFICATION REQUEST, may transmit the dualization RLC Activation/Deactivation MAC-CE to the UE 200.

In this case, it is also possible to cause a NODE that receives the S-NODE modulation REQUEST or the S-NODE modulation REQUEST to start a timer (referred to as a radio condition validity timer, for example), and to prohibit transmission of the S-NODE modulation REQUEST or the S-NODE modulation REQUEST by a NODE on the object side (which may also be referred to as a corresponding NODE) until the timer expires. Thus, reception and transmission of unnecessary messages can be avoided, and the MN or the SN can operate or stop the RLC entity more efficiently.

(3.3.3) operation example 3

In the present operation example, the MN or the SN can blindly (blindly) transmit the duplicate RLC Activation/Deactivation MAC-CE to the UE 200 regardless of the state of the node on the subject side.

Fig. 9 shows a communication sequence related to PDCP replication according to action example 3. In fig. 9, an example is shown in which the MN first transmits the duplicate RLC Activation/Deactivation MAC-CE.

As shown in fig. 9, the gNB100a (mn) transmits a duplicate RLC Activation/Deactivation MAC-CE to the UE 200 (S310). gNB100A blindly sends the duplification RLC Activation/Deactivation MAC-CE to UE 200 regardless of the status of gNB100B (SN).

The gsb 100A transmits MCG and SCG RLC Activation/Deactivation states (MCG and SCG RLC Activation/Deactivation state) to the gsb 100B together with the transmission of the dual RLC Activation/Deactivation MAC-CE (S320). The MCG and SCG RLC Activation/Deactivation state may be transmitted at the same timing as the transmission of the Deactivation RLC Activation/Deactivation MAC-CE, or may be transmitted after the transmission of the Deactivation RLC Activation/Deactivation MAC-CE within a predetermined time.

The MCG and SCG RLC activation/deactivation state may also be referred to by other names. The MCG and SCG RLC activation/deactivation state may contain radio quality conditions related to the RLC entity (RLC bearer) of the gNB 100A. Alternatively, the MCG and SCG RLC Activation/Deactivation state may include the dualization RLC Activation/Deactivation MAC-CE itself transmitted to the UE 200. Similarly to the operation example 2, the MCG and SCG RLC activation/deactivation state may include a set value (timer start timing, time until expiration, etc.) related to the radio control value timer.

The gNB100A starts a timer (radio condition timer) in response to transmission of the dual RLC Activation/Deactivation MAC-CE, and the gNB100B starts the timer in response to reception of the MCG and SCG RLC Activation/Deactivation state (S330).

As shown in fig. 9, the gNB100B may further transmit the dual RLC Activation/Deactivation MAC-CE to the UE 200 according to the contents of the received MCG and SCG RLC Activation/Deactivation state (S340), as long as the timer expires. In this case, gNB100B may also transmit MCG and SCG RLC activation/deactivation state to gNB100A (S350). MCG and SCG RLC activation/deactivation state sent by gNB100B may be the same as MCG and SCG RLC activation/deactivation state sent by gNB100A, but may include radio quality condition related to the RLC entity (RLC bearer) of gNB 100B.

After the radio condition validity timer expires, the gNB100A and the gNB100B may blindly transmit the duplicate RLC Activation/Deactivation MAC-CE to the UE 200 regardless of the contents of the MCG and SCG RLC Activation/Deactivation state or radio quality condition received from the node on the object side.

In the example shown in fig. 9, the gNB100B transmits the duplicate RLC Activation/Deactivation MAC-CE to the UE 200 (S360).

The operations at S370 to S400 are the same as those at S40 to S70 in operation example 1.

(4) action/Effect

According to the above embodiment, the following operational effects can be obtained. Specifically, the gNB100A can transmit the duplicate RLC Activation/Deactivation MAC-CE to the UE 200 according to the radio quality condition (node information) received from the gNB 100B. Specifically, the gNB100A determines an RLC entity to be activated or deactivated 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, and can transmit the dual RLC Activation/Deactivation MAC-CE instructing the UE 200 to activate or deactivate the determined RLC entity. Furthermore, the gsb 100B can also transmit the duplicate RLC Activation/Deactivation MAC-CE to the UE 200 by the same operation as the gsb 100A.

Therefore, when a plurality of RLC entities are controlled to implement PDCP duplication of UL, even if DRB 50 is set to span MCG and SCG, the plurality of RLC entities can be shared between MCG (specifically, gNB100a (mn)) and SCG (specifically, gNB100b (sn)).

This enables appropriate control of a plurality of RLC entities spanning MCG and SCG, and enables more efficient provision of advanced services such as URLLC.

Furthermore, the gNB100A (gNB 100B) can transmit, to the gNB100B (gNB 100A), node information (radio quality condition) including at least any one of the duplicate RLC Activation/Deactivation MAC-CE itself transmitted to the UE 200, identification information identifying the RLC (which may also be interpreted as an RLC entity) in the gNB100A (MN), and quality information indicating the radio quality of the RLC in the MN.

Therefore, even when the duplicate RLC Activation/Deactivation MAC-CE is blindly (blindly) transmitted to UE 200 by gNB100A (gNB 100B), gNB100B can reliably recognize the status of the RLC entity on the side of gNB 100A.

In the present embodiment, the radio quality condition may include identification information (DRB identity) of a Data Radio Bearer (DRB) and/or quality information indicating radio quality of RLC on the transmitting side of the radio quality condition. Therefore, the status of the RLC entity in the node on the target side can be grasped, and it is possible to contribute to determining an appropriate RLC entity to be operated or stopped.

(5) Other embodiments

While the embodiments have been described above, it is obvious to those skilled in the art that the present invention is not limited to the description of the embodiments, and various modifications and improvements can be made.

For example, in the above-described embodiment, it is described that a maximum of 4 RLC entities can operate simultaneously, but the number of RLC entities may be smaller than 4, or may be 5 or more as long as it is a plurality of RLC entities.

Further, the above-described operation examples 1 to 3 may be combined. For example, operation example 1 and operation example 3, and operation example 2-1 or 2-2 and operation example 3 may be combined.

The radio quality condition may be referred to by other names as long as it indicates RLC entity identification information and/or RLC quality information in the target node.

In the above-described embodiment, NR-DC is assumed, but when the PDCP entity on the UE 200 side is configured by the MN RLC entity and the SN RLC entity at the same time by 3 or 4 RLC entities in total, the present invention can be applied to other DC.

The block diagrams (fig. 2 and 3) used in the description of the above embodiments show blocks in units of functions. These functional blocks (components) are realized by any combination of at least one of hardware and software. The method of implementing each functional block is not particularly limited. That is, each functional block may be implemented by one device that is physically or logically combined, or may be implemented by two or more devices that are physically or logically separated and that are directly or indirectly (for example, wired or wireless) connected and implemented by these plural devices. The functional blocks may also be implemented by a combination of software and one or more of the above-described devices.

The functions include, but are not limited to, judgment, decision, determination, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, establishment, comparison, assumption, expectation, viewing, broadcasting (broadcasting), notification (notification), communication (communicating), forwarding (forwarding), configuration (reconfiguration), reconfiguration (reconfiguration), allocation (allocation, mapping), assignment (allocation), and the like. For example, a function block (a configuration unit) that functions transmission is referred to as a transmission unit (transmitter) or a transmitter (transmitter). In short, as described above, the method of implementation is not particularly limited.

The above-described gNB100A, gNB100B and UE 200 (this apparatus) may also function as computers that perform the processing of the radio communication method of the present disclosure. Fig. 10 is a diagram showing an example of the hardware configuration of the apparatus. As shown in fig. 10, the apparatus may be a computer apparatus including a processor 1001, a memory 1002(memory), a storage 1003(storage), a communication apparatus 1004, an input apparatus 1005, an output apparatus 1006, a bus 1007, and the like.

In the following description, the term "device" may be replaced with "circuit", "device", "unit", and the like. The hardware configuration of the apparatus may include one or more of the apparatuses 1001 to 1006 shown in the drawings, or may be configured as an apparatus not including a part thereof.

Each functional block (see fig. 2 and 3) of the apparatus is realized by an arbitrary hardware element of the computer apparatus or a combination of the hardware elements.

Furthermore, the functions in the apparatus are realized by the following method: when predetermined software (program) is read into hardware such as the processor 1001 and the memory 1002, the processor 1001 performs an operation to control communication of the communication device 1004 or at least one of reading and writing of data in the memory 1002 and the storage 1003.

The processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be configured by a Central Processing Unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like.

Further, the processor 1001 reads out a program (program code), a software module, data, and the like from at least one of the memory 1003 and the communication device 1004 to the memory 1002, and executes various processes according to the read-out program. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. While the various processes described above are described as being executed by one processor 1001, the various processes described above may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may also be mounted by more than one chip. In addition, the program may also be transmitted from the network via a telecommunication line.

The Memory 1002 is a computer-readable recording medium, and may be configured by at least one of a Read Only Memory (ROM), an Erasable Programmable Read Only Memory (EPROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Random Access Memory (RAM), and the like. Memory 1002 may also be referred to as registers, cache, main memory (primary storage), etc. The memory 1002 may store a program (program code), a software module, and the like capable of executing the method according to one embodiment of the present disclosure.

The storage 1003 is a computer-readable recording medium, and may be constituted by at least one of an optical disk such as a CD-rom (compact Disc rom), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact Disc, a digital versatile Disc, a Blu-ray (registered trademark) Disc, a smart card, a flash memory (for example, a card, a stick, a Key drive), a Floppy (registered trademark) Disc, a magnetic stripe, and the like.

The communication device 1004 is hardware (a transmitting/receiving device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, or the like.

Communication apparatus 1004 may be configured to include a high-Frequency switch, a duplexer, a filter, a Frequency synthesizer, and the like, for example, in order to realize at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a key, a sensor, and the like) for receiving an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, or the like) that outputs to the outside. The input device 1005 and the output device 1006 may be integrally formed (for example, a touch panel).

The processor 1001 and the memory 1002 are connected to each other via a bus 1007 for communicating information. The bus 1007 may be configured by using a single bus, or may be configured by using different buses for each device.

The apparatus may include hardware such as a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), and a Field Programmable Gate Array (FPGA), and a part or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may also be implemented using at least one of these hardware.

Note that the information is not limited to the form and embodiment described in the present disclosure, and may be notified by other methods. For example, the notification of the Information may be performed by 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), System Information Block (SIB), other signals, or a combination thereof).

The forms/embodiments described in the present disclosure may also be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-a), SUPER 3G, IMT-Advanced, fourth generation mobile communication system (4G: 4th generation mobile communication system), fifth generation mobile communication system (5G: 5th generation mobile communication system), Future Radio Access (FRA: Future Radio Access), New air interface (NR: New Radio), 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: Ultra-WideBand), Bluetooth (registered trademark), a system using other appropriate systems, and a next generation system extended therefrom. Furthermore, a plurality of systems (for example, a combination of 5G and at least one of LTE and LTE-a) may be combined and applied.

For the processing procedures, timings, flows, and the like of the respective forms/embodiments described in the present disclosure, the order may be changed without contradiction. For example, elements of the various steps are suggested using an exemplary sequence for the methods described in this disclosure, but are not limited to the particular sequence suggested.

In the present disclosure, a specific operation performed by the base station may be performed by an upper node (upper node) of the base station depending on the case. In a network including one or more network nodes (network nodes) having a base station, it is obvious that various operations to be performed for communication with a terminal can be performed by the base station and at least one of other network nodes (for example, MME, S-GW, or the like, but not limited thereto) other than the base station. In the above, the case where there is one network node other than the base station is exemplified, but the other network node may be a combination of a plurality of other network nodes (e.g., MME and S-GW).

Information and signals (information and the like) can be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). Or may be input or output via a plurality of network nodes.

The input or output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The information that is input or output may be overwritten, updated or appended. The output information may also be deleted. The entered information may also be sent to other devices.

The determination may be made by a value (0 or 1) represented by 1 bit, may be made by a Boolean value (true or false), or may be made by comparison of values (for example, comparison with a predetermined value).

The forms/embodiments described in the present disclosure may be used alone or in combination, and may be switched depending on the execution. Note that the notification of the predetermined information is not limited to be explicitly (for example, notification of "yes X"), and may be implicitly (for example, notification of the predetermined information is not performed).

Software, whether referred to as software, firmware, middleware, microcode, hardware description languages, or by other names, should be construed broadly to mean commands, command sets, code segments, program code, programs (routines), subroutines, software modules, applications, software packages, routines, subroutines (subroutines), objects, executables, threads of execution, procedures, functions, and the like.

Further, software, commands, information, and the like may be transmitted and received via a transmission medium. For example, where software is transmitted from a website, server, or other remote source using at least one of wired technology (coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technology (infrared, microwave, etc.), at least one of these is included within the definition of transmission medium.

Information, signals, etc. described in this disclosure may also be represented using any of a variety of different technologies. For example, data, commands, instructions (commands), information, signals, bits, symbols (symbols), chips (chips), etc., that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination thereof.

Further, terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). Further, the signal may also be a message. In addition, a Component Carrier (CC) may be referred to as a Carrier frequency, a cell, a frequency Carrier, and the like.

The terms "system" and "network" as used in this disclosure may be used interchangeably.

In addition, information, parameters, and the like described in the present disclosure may be expressed using absolute values, may be expressed using relative values to predetermined values, and may be expressed using other corresponding information. For example, the radio resource may also be indicated by an index.

The names used for the above parameters are in no way limiting. Further, the numerical expressions and the like using these parameters may be different from those explicitly disclosed in the present disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by appropriate names, and thus the various names assigned to these various channels and information elements are non-limiting in any respect.

In the present disclosure, terms such as "Base Station (BS)", "wireless Base Station", "fixed Station (fixed Station)", "NodeB", "enodeb (enb)", "gnnodeb (gnb)", "access point (access point)", "transmission point", "reception point", "cell", "sector", "cell group", "carrier", "component carrier" may be used interchangeably. A base station may also be referred to by terms such as macro cell, small cell, femto cell, pico cell, etc.

A base station can accommodate one or more (e.g., 3) cells (also referred to as sectors). When a base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH) for indoor use).

The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of a base station and a base station subsystem that performs communication service within the coverage area.

In the present disclosure, terms such as "Mobile Station (MS)", "User terminal (User terminal)", "User Equipment (UE)", "terminal" and the like may be used interchangeably.

For a mobile station, those skilled in the art will sometimes also refer to the following terms: a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent (user agent), a mobile client, a client, or some other suitable terminology.

At least one of the base station and the mobile station may also be referred to as a transmitting apparatus, a receiving apparatus, a communication apparatus, or the like. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving body may be a vehicle (e.g., an automobile, an airplane, etc.), may be a moving body that moves in an unmanned manner (e.g., an unmanned aerial vehicle, an autonomous automobile, etc.), or may be a robot (manned or unmanned). At least one of the base station and the mobile station includes a device that does not necessarily move during a communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

In addition, the base station in the present disclosure may also be replaced with a mobile station (user terminal, the same applies hereinafter). For example, the various aspects and embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between a plurality of mobile stations (for example, a configuration may also be referred to as D2D (Device-to-Device), a Vehicle-to-all system (V2X), or the like.

Likewise, the mobile station in the present disclosure may be replaced with a base station. In this case, the base station may have a function of the mobile station.

A radio frame may consist of one or more frames in the time domain. In the time domain, one or more individual frames may be referred to as subframes. A subframe may consist of one or more slots in the time domain. The subframe may be a fixed time length (e.g., 1ms) independent of a parameter set (numerology).

The parameter set may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The parameter set may indicate, for example, at least one of 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, specific windowing processing performed by the transceiver in the Time domain, and the like.

A slot may be composed of one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. The time slot may be a time unit based on a parameter set.

A timeslot may contain multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may be composed of a smaller number of symbols than a slot. The PDSCH (or PUSCH) transmitted in a unit of time greater than the mini slot may be referred to as PDSCH (or PUSCH) mapping type (type) a. The PDSCH (or PUSCH) transmitted using the mini-slot may be referred to as PDSCH (or PUSCH) mapping type (type) B.

The radio frame, subframe, slot, mini-slot, and symbol all represent a unit of time when a signal is transmitted. The radio frame, subframe, slot, mini-slot, and symbol may each be referred to by corresponding other terms.

For example, 1 subframe may be referred to as a Transmission Time Interval (TTI), a plurality of consecutive subframes may be referred to as TTIs, and 1 slot or 1 mini-slot may be referred to as a TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in the conventional LTE, may be a period shorter than 1ms (for example, 1-13 symbols), or may be a period longer than 1 ms. The unit indicating TTI may be referred to as a slot, a mini slot, or the like, instead of a subframe.

Here, the TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling for allocating radio resources (frequency bandwidths, transmission powers, and the like that can be used by each user terminal) to each user terminal in units of TTIs. In addition, the definition of TTI is not limited thereto.

The TTI may be a transmission time unit of a channel-coded data packet (transport block), code block, code word, or the like, or may be a processing unit of scheduling, link adaptation, or the like. In addition, given a TTI, the time interval (e.g., number of symbols) to which a transport block, code block, codeword, etc. is actually mapped may be shorter than the TTI.

In addition, in a case where a 1-slot or a 1-mini-slot is referred to as a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute a minimum time unit for scheduling. Further, the number of slots (mini-slots) constituting the minimum time unit of the schedule can be controlled.

TTIs having a time length of 1ms are also referred to as normal TTIs (TTIs in LTE rel.8-12), normal TTIs (normal TTIs), long TTIs (long TTIs), normal subframes (normal subframes), long (long) subframes, slots, etc. A TTI shorter than a normal TTI may be referred to as a shortened TTI, a short TTI (short TTI), a partial TTI, a shortened subframe, a short (short) subframe, a mini-slot, a sub-slot, a slot, etc.

In addition, for a long TTI (long TTI) (e.g., normal TTI, subframe, etc.), a TTI having a time length exceeding 1ms may be substituted, and for a short TTI (short TTI) (e.g., shortened TTI, etc.), a TTI having a TTI length smaller than that of the long TTI (long TTI) and having a TTI length of 1ms or more may be substituted.

A Resource Block (RB) is a resource allocation unit of time and frequency domains, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in the RB may be the same regardless of the parameter set, and may be 12, for example. The number of subcarriers included in the RB may also be decided according to the parameter set.

Further, the time domain of the RB may contain one or more symbols, and may be 1 slot, 1 mini-slot, 1 subframe, or 1TTI in length. The 1TTI, 1 subframe, etc. may be respectively composed of one or more resource blocks.

In addition, one or more RBs may be referred to as Physical Resource blocks (Physical RBs: PRBs), Sub-Carrier groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB peers, and so on.

In addition, a Resource block may be composed of one or more Resource Elements (REs). For example, 1RE may be a 1 subcarrier and 1 symbol radio resource region.

The Bandwidth Part (BWP) (also called partial Bandwidth, etc.) represents a subset of consecutive common rbs (common resource blocks) for a certain set of parameters in a certain carrier. Here, the common RB may be determined by an index of an RB with reference to a common reference point of the carrier. PRBs may be defined in a certain BWP and numbered within that BWP.

The BWP may include BWP (UL BWP) for UL and BWP (DL BWP) for DL. One or more BWPs may be set for a UE within 1 carrier.

At least one of the set BWPs may be active (active), and a case where the UE transmits and receives a predetermined signal/channel outside the active BWP may not be assumed. In addition, "cell", "carrier", and the like in the present disclosure may be replaced with "BWP".

The above-described structures of radio frames, subframes, slots, mini slots, symbols, and the like are merely examples. For example, the number of subframes included in the radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the Cyclic Prefix (CP) length, and the like may be variously changed.

The terms "connected" and "coupled" or any variation thereof are intended to mean that two or more elements are directly or indirectly connected or coupled to each other, and may include one or more intermediate elements between two or more elements that are "connected" or "coupled" to each other. The combination or connection between the elements may be physical, logical, or a combination of these. For example, "connect" may be replaced with "access". As used in this disclosure, for two elements, it may be considered that they are "connected" or "coupled" to each other by using at least one of one or more electrical wires, cables, and printed electrical connections, and by using electromagnetic energy or the like having wavelengths in the radio frequency domain, the microwave domain, and the optical (including both visible and invisible) domain, as some non-limiting and non-inclusive examples.

The Reference Signal may be referred to as Reference Signal (RS) or Pilot (Pilot) depending on the applied standard.

As used in this disclosure, a statement "according to" is not intended to mean "solely according to" unless explicitly stated otherwise. In other words, the expression "according to" means both "according to" and "at least according to".

The "unit" in the configuration of each of the above-described apparatuses may be replaced with a "section", "circuit", "device", and the like.

Any reference to an element using the designations "first", "second", etc. used in this disclosure is not intended to limit the number or order of such elements. These terms may be used in the present disclosure as a convenient way to distinguish between more than two elements. Thus, references to first and second elements do not imply that only two elements are possible here or that in any case the first element must precede the second element.

Where the disclosure uses the terms "including", "comprising" and variations thereof, these terms are intended to be inclusive in the same way as the term "comprising". Also, the term "or" used in the present disclosure means not exclusive or.

In the present disclosure, where articles are added by translation, for example, as in the english language a, an, and the, the present disclosure may also include the plural forms of nouns that follow the articles.

Terms such as "determining" and "determining" used in the present disclosure may include various operations. The terms "determination" and "decision" may include, for example, determining that a determination (judging), calculation (calculating), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry) (for example, searching in a table, a database, or another data structure), or confirmation (ascertaining) has been made as a term indicating that a determination (judging) or a decision) has been made. The "determination" may include a case where a reception (e.g., reception), a transmission (e.g., transmission), an input (input), an output (output), an access (access) (e.g., access to data in the memory) is regarded as a case where the "determination" and the "determination" are performed. The "determination" and "decision" may include matters regarding the "determination" and "decision" as being performed, such as the solution (resolving), the selection (selecting), the selection (breathing), the establishment (evaluating), and the comparison (comparing). That is, "judgment" and "determination" may include "judgment" and "determination" of any item of action. The "determination (decision)" may be replaced by "assumption (associating)", "expectation (expecting)", "consideration (associating)", or the like.

In the present disclosure, the phrase "a and B are different" may also mean "a and B are different from each other". The term "A and B are different from C" may be used. The terms "separate", "join", and the like can also be interpreted in the same manner as "different".

While the present disclosure has been described in detail, it should be apparent to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and alterations without departing from the spirit and scope of the present disclosure as defined by the claims. Accordingly, the disclosure is intended to be illustrative, and not limiting.

Description of the reference symbols

10: a wireless communication system;

20：NG-RAN；

30：MCG；

40：SCG；

50：DRB；

100A、100B：gNB；

110: a wireless transmission unit;

120: a wireless receiving unit;

130: a MAC-CE transmission unit;

140: an RLC control section;

150: a PDCP control unit;

200：UE；

210: a wireless transmission unit;

220: a wireless receiving unit;

230: a MAC processing unit;

240: an RLC processing section;

250: a PRCP processing unit;

1001: a processor;

1002: a memory;

1003: a memory;

1004: a communication device;

1005: an input device;

1006: an output device;

1007: a bus.

Claims

1. A wireless communication node, wherein:

the wireless communication node processes a packet data convergence protocol layer,

the wireless communication node is provided with:

a control section that performs control in a radio link control layer and the packet data convergence protocol layer;

a transmitting unit 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; and

a reception unit that receives node information from a corresponding node corresponding to the wireless communication node, the node information including at least one of identification information for identifying the radio link control layer in the corresponding node and quality information indicating radio quality of the radio link control layer in the corresponding node,

the control section causes the control element to be transmitted from the transmission section to the terminal according to the content of the node information.

2. A wireless communication node, wherein:

the wireless communication node constitutes a master node,

the wireless communication node has:

a control section that performs control in a radio link control layer and a packet data convergence protocol layer; and

a receiving unit that receives, from a secondary node, node information including at least one of identification information for identifying the radio link control layer in the secondary node and quality information indicating radio quality of the radio link control layer in the secondary node,

3. A wireless communication node, wherein:

the wireless communication node constitutes a secondary node,

the wireless communication node has:

a receiving unit that receives, from a master node, node information including at least one of identification information for identifying the radio link control layer in the master node and quality information indicating radio quality of the radio link control layer in the master node,

4. A wireless communication node, wherein:

the wireless communication node constitutes a master node,

the wireless communication node has:

a transmitting part that transmits a control element of a medium access control layer indicating an operation or a stop of an entity of the radio link control layer to a terminal,

the control unit transmits, to a secondary node, node information including at least any one of the control element, identification information identifying the radio link control layer in the primary node, and quality information indicating radio quality of the radio link control layer in the primary node.

5. A wireless communication node, wherein:

the wireless communication node constitutes a secondary node,

the wireless communication node has:

a transmitting 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,

the control unit transmits node information to a master node, the node information including at least any one of the control element, identification information identifying the radio link control layer in the slave node, and quality information indicating radio quality of the radio link control layer in the slave node.