JP7610612B2 - Terminal, base station, wireless communication system, and wireless communication method - Google Patents

Description

The present disclosure relates to a terminal that transmits a message to a network including failure information of a second cell group.

The 3rd Generation Partnership Project (3GPP) is developing specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)) and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution or 6G.

3GPP supports dual connectivity (MR-DC (Multi-RAT Dual Connectivity)) using a first cell group (MCG (Master Cell Group)) and a second cell group (SCG (Secondary Cell Group)). Examples of MR-DC include EN-DC (E-UTRA-NR Dual Connectivity), NE-DC (NR-EUTRA Dual Connectivity), and NR-DC (NR-NR Dual Connectivity).

3GPP Release 16 introduces a conditional reconfiguration-based procedure for adding (CPA; Conditional PSCell Addition) or changing (CPC; Conditional PSCell Change) a target cell (target PSCell) to the specifications prior to Release 15. CPA and CPC are procedures that realize a connection to a target cell without sending a re-establishment request message to the network.

Furthermore, for purposes such as SON (Self Organizing Network) and MDT (Minimization of Drive Test), Mobility Robustness Optimization (MRO) for SN change failures of SNs (Secondary Nodes) having SCGs and extended optimization of RACHs (Random Access Channels) are being considered (for example, Non-Patent Document 1).

" New WID on enhancement of data collection for SON/MDT in NR ", RP-201281, 3GPP TSG RAN Meeting #86-e, 3GPP, July 2020

Against the above background, the inventors, after careful consideration, have discovered the need to distinguish whether an SN change failure has occurred due to conditional reconfiguration in order to optimize SN change failure and RACH.

Therefore, the following disclosure has been made in consideration of this situation and aims to provide a terminal and base station that enable optimization of SN change failure and RACH.

One aspect of the present disclosure is a terminal that, in dual connectivity using a first cell group and a second cell group, includes a control unit that performs a connection to a target cell included in the second cell group based on conditional reconfiguration, and a transmission unit that transmits a message including failure information of the second cell group to a network if the connection to the target cell fails, and the control unit includes in the message an information element that identifies the conditional reconfiguration as a type of failure information of the second cell group.

FIG. 1 is a schematic diagram showing the overall configuration of a wireless communication system 10. FIG. 2 is a functional block diagram of the UE 200. FIG. 3 is a diagram for explaining a usage scene. FIG. 4 is a sequence diagram showing the first operation example. FIG. 5 is a sequence diagram showing the second operation example. FIG. 6 is a diagram showing an example of SCG Failure Information (ASN.1 format). FIG. 7 is a diagram showing an example of SCG Failure Information (ASN.1 format). FIG. 8 is a diagram showing an example of SCG Failure Information (ASN.1 format). FIG. 9 is a diagram showing an example of SCG Failure Information (ASN.1 format). FIG. 10 is a diagram showing an example of SCG Failure Information (ASN.1 format). FIG. 11 is a diagram showing an example of SCG Failure Information (ASN.1 format). FIG. 12 is a diagram illustrating an example of a hardware configuration of the UE 200.

Hereinafter, the embodiments will be described with reference to the drawings. Note that the same or similar symbols are used for the same functions and configurations, and the description thereof will be omitted as appropriate.

(1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system conforming to Long Term Evolution (LTE) and 5G New Radio (NR). Note that LTE may be called 4G, and NR may be called 5G.

LTE and NR may also be interpreted as radio access technologies (RATs), and in an embodiment, LTE may be referred to as the first radio access technology and NR may be referred to as the second radio access technology.

The wireless communication system 10 includes an Evolved Universal Terrestrial Radio Access Network 20 (hereinafter, E-UTRAN 20) and a Next Generation-Radio Access Network 30 (hereinafter, NG RAN 30). The wireless communication system 10 also includes a terminal 200 (hereinafter, UE 200, User Equipment).

E-UTRAN20 includes eNB100A, a base station conforming to LTE. NG RAN30 includes gNB100B, a base station conforming to 5G (NR).

eNB100A, gNB100B and UE200 are capable of supporting carrier aggregation (CA) that uses multiple component carriers (CC) and dual connectivity (DC) that enables simultaneous communication between the UE and each of multiple nodes.

The E-UTRAN 20 is connected to a core network 40 for LTE. Note that the E-UTRAN 20, the NG RAN 30 and the core network 40 may simply be referred to as a network.

An operation administration and management server 50 (hereinafter, OAM server 50) may be provided within the core network 40. The OAM server 50 may perform processes related to SON (Self Organizing Network) and MDT (Minimization of Drive Test), etc.

eNB100A and gNB100B may form an area (which may be expressed as a cell) in which wireless communication with UE200 can be performed, specifically, area A1 or area A2.

Here, area A1 may be interpreted as an area in which UE200 can communicate with eNB100A. Area A2 may be interpreted as an area in which UE200 can communicate with gNB100B. Area A1 and area A2 may overlap with each other, and in an area in which area A1 and area A2 overlap, EN-DC (E-UTRA-NR Dual Connectivity) or NE-DC (NR-EUTRA Dual Connectivity) may be performed in which UE200 communicates with eNB100A and gNB100B simultaneously. Note that FIG. 2 illustrates a case in which the base station capable of communicating with UE200 in area A1 is eNB100A, but the base station capable of communicating with UE200 in area A1 may be gNB100B provided in NG RAN30. In such a case, NR-DC (NR-NR Dual Connectivity) may be performed in which UE200 communicates with two or more gNB100B (or cells) simultaneously.

Here, in the above-mentioned DC, a group of cells that can perform processing related to the C-plane (control plane) and the U-plane (user plane) may be referred to as a first cell group (MCG; Master Cell Group). In the above-mentioned DC, a group of cells that can perform processing related to the U-plane (user plane) may be referred to as a second cell group (SCG; Secondary Cell Group). For example, in the above-mentioned EN-DC, eNB100A may be referred to as MN (Master Node), and gNB100B may be referred to as SN (Secondary Node). In the above-mentioned NE-DC, eNB100A may be referred to as SN, and gNB100B may be referred to as MN.

In the following, EN-DC, NE-DC and NR-DC may be collectively referred to as MR (Multi-RAT)-DC.

(2) Functional Block Configuration of Wireless Communication System Next, a functional block configuration of the wireless communication system 10 will be described. Specifically, a functional block configuration of the UE 200 will be described.

Figure 2 is a functional block diagram of UE 200. As shown in Figure 2, UE 200 includes a radio signal transmitting/receiving unit 210, an amplifier unit 220, a modulation/demodulation unit 230, a control signal/reference signal processing unit 240, an encoding/decoding unit 250, a data transmitting/receiving unit 260, and a control unit 270.

The radio signal transmission/reception unit 210 transmits and receives radio signals conforming to LTE or NR. The radio signal transmission/reception unit 210 supports Massive MIMO, CA and DC that use multiple CCs bundled together, and the like.

The amplifier unit 220 is composed of a PA (Power Amplifier)/LNA (Low Noise Amplifier) etc. The amplifier unit 220 amplifies the signal output from the modem unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the wireless signal transmission/reception unit 210.

The modem unit 230 performs data modulation/demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (eNB100A or gNB100B). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM)/Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

The control signal/reference signal processing unit 240 performs processing related to various control signals transmitted and received by UE 200, and processing related to various reference signals transmitted and received by UE 200.

Specifically, the control signal/reference signal processor 240 receives various control signals, such as radio resource control layer (RRC) control signals, transmitted from the eNB100A or gNB100B via a predetermined control channel. The control signal/reference signal processor 240 also transmits various control signals to the eNB100A or gNB100B via a predetermined control channel.

The control signal/reference signal processing unit 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

DMRS is a known reference signal (pilot signal) between the base station and the terminal for each terminal, used to estimate the fading channel used for data demodulation. PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

In addition to DMRS and PTRS, reference signals may also include Channel State Information-Reference Signal (CSI-RS), Sounding Reference Signal (SRS), and Positioning Reference Signal (PRS) for location information.

Channels include control channels and data channels. Control channels include PDCCH (Physical Downlink Control Channel), PUCCH (Physical Uplink Control Channel), RACH (Random Access Channel), Downlink Control Information (DCI) including Random Access Radio Network Temporary Identifier (RA-RNTI), and Physical Broadcast Channel (PBCH).

Data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be read as a shared channel.

Here, the control signal/reference signal processor 240 receives downlink control information (DCI). The DCI includes fields that store existing fields such as DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Allocation), TDRA (Time Domain Resource Allocation), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), and RV (Redundancy Version).

The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandWidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and an information element (pdsch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in the MCS and an MCS table. The MCS table may be specified by an RRC message or may be specified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ process to which the DCI is applied. The value stored in the NDI is an information element for specifying whether the data to which the DCI is applied is initial transmission data or not. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

In an embodiment, the control signal/reference signal processing unit 240 configures a transmission unit that transmits a message including SCG failure information to the network (MN 300) when a connection to a target cell included in an SCG based on conditional reconfiguration in MR-DC fails. The conditional reconfiguration may include a PSCell addition (CPA; Conditional PSCell Addition) or a PSCell change (CPC; Conditional PSCell Change). The SCG failure information may be referred to as SCG Failure information. Alternatively, the message including the SCG failure information may be referred to as SCG Failure.

Note that CPA and CPC are procedures that achieve connection to a target cell without sending an RRC re-establishment request (re-establishment request message) to the network.

The encoding/decoding unit 250 performs data division/concatenation and channel coding/decoding, etc. for each specified communication destination (eNB100A or gNB100B).

Specifically, the encoding/decoding unit 250 divides the data output from the data transmission/reception unit 260 into pieces of a predetermined size, and performs channel coding on the divided data. The encoding/decoding unit 250 also decodes the data output from the modem unit 230, and concatenates the decoded data.

The data transmission/reception unit 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission/reception unit 260 performs assembly/disassembly of PDUs/SDUs in multiple layers (such as the Medium Access Control layer (MAC), the Radio Link Control layer (RLC), and the Packet Data Convergence Protocol layer (PDCP)). The data transmission/reception unit 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

The control unit 270 controls each functional block constituting the UE 200. In an embodiment, the control unit 270 constitutes a control unit that performs a connection to a target cell included in the SCG based on conditional reconfiguration (CPA or CPC) in the MR-DC. The control unit 270 includes an information element that identifies the conditional reconfiguration in the SCG Failure as a type of failure information of the SCG. The type of failure information of the SCG may be referred to as failure type or failure type-v17xy. The information element that identifies the conditional reconfiguration may be referred to as condSynchReconfigFailureSCG.

Furthermore, the control unit 270 may include an information element regarding the target cell in the message including the SCG failure information. The information element regarding the target cell may include identification information of the target cell (e.g., FailedPSCellID). The identification information of the target cell may include a CGI (Cell Global Identify) of the target cell that uniquely identifies the cell in the wireless communication system 10. The information element regarding the target cell may include a PCI (Physical Cell Identify) of the target cell that uniquely identifies the cell in the SN400. The information element regarding the target cell may include an ARFCN (Absolute Radio-Frequency Channel Number) that identifies the frequency of the target cell. The information element regarding the target cell may include a measurement result of the reception quality of the target cell (e.g., measResultFailedPSCell). The measurement result may include RSRP (Reference Signal Received Power), RSRQ (Reference Signal Received Quality), or SINR (Signal to Interference and Noise Ratio).

The control unit 270 may include an information element regarding the source cell in the message including the SCG failure information. The information element regarding the source cell may include identification information of the source cell (e.g., PreviousPSCellID). The identification information of the source cell may include the CGI of the source cell. The identification information of the source cell may include the PCI of the source cell. The identification information of the source cell may include the ARFCN of the source cell. The information element regarding the source cell may include a measurement result of the reception quality of the source cell (e.g., measResultPreviousPSCell). The measurement result may include RSRP, RSRQ, or SINR.

The control unit 270 may include information elements regarding candidate cells of the target cell in a message including the SCG failure information. The information elements regarding the candidate cells (e.g., measResultCandidatePSCellInfoList) may include measurement results of the candidate cells (e.g., measResultCandidatePSCellInfo). The information elements regarding the candidate cells may include measurement results of two or more candidate cells in a list format. The measurement results of the candidate cells may include identification information of the candidate cells. The identification information of the candidate cells may include the PCI of the candidate cells or the frequency of the candidate cells. The measurement results of the candidate cells may include measurement results of the reception quality of the candidate cells (e.g., measResult). The measurement results may include RSRP, RSRQ, or SINR. The measurement results of the candidate cells may include an information element (e.g., executionConditionSatisfied) indicating whether the measurement results performed on the candidate cells satisfy the execution conditions for conditional reconfiguration. The measurement results of the candidate cells may include an information element (e.g., configuredExecutionConditionEvent) that identifies an execution condition event configured for the candidate cells. Such information elements may include two or more execution condition events. The measurement result of the candidate cell may include an information element (e.g., satisfiedTriggeringQuantity) that specifies a reception quality that satisfies the execution condition for the conditional reconfiguration. Such information elements may include two or more reception qualities that satisfy the execution condition for the conditional reconfiguration. The measurement result of the candidate cell may include an information element (e.g., satisfiedTriggeringEvent) that specifies an execution condition event that satisfies the execution condition for the conditional reconfiguration. Such information elements may include two or more execution condition events that satisfy the execution condition for the conditional reconfiguration.

For example, the execution condition event may include Event A3 (TS38.331 V16.1.0 §5.5.4.4 “Neighbor becomes offset better than SpCell”) and Event A5 (TS38.331 V16.1.0 §5.5.4.6 “SpCell becomes worse than threshold1 and neighbour becomes better than threshold2”). The execution condition of the conditional reconfiguration is a condition defined for each execution condition event. For example, the execution condition of the conditional reconfiguration associated with Event A3 may be that the reception quality of the neighbouring cell (candidate cell) is better than the current PSCell by an offset. The execution condition of the conditional reconfiguration associated with Event A5 may be that the reception quality of the current PSCell is worse than threshold 1 and the reception quality of the neighbouring cell (candidate cell) is better than threshold 2.

The control unit 270 may include an information element regarding a random access procedure to the target cell in the message including the SCG failure information. The information element regarding the random access procedure (e.g., attemptedRAInformation) may include an information element specifying a four-step random access procedure (e.g., fourStepRAInformation) or an information element specifying a two-step random access procedure (e.g., twoStepRAInformation). These information elements may include information elements that specify a frequency to be used in the random access procedure (e.g., absoluteFrequencyPoint), information elements that specify the location and frequency band of the BWP (BandWidth Part) to be used in the random access procedure (e.g., locationAndBandwidth), information elements that specify the SCS (SubCarrier Spacing) to be used in the random access procedure (e.g., subcarrierSpacing), and information elements regarding the random access preamble (msg 1 or msg A) (e.g., FrequencyStart, FrequencyStartCFRA, subcarrierSpacing, subcarrierSpacingCFRA, FDM, FDMCFRA, perRAInfoList).

(3) Application Scenes The application scenes of the embodiment will be described below. In the application scenes, a case where a PSCell change is executed in an MR-DC where a UE 200 communicates with an MN 300 and an SN 400 will be described. In FIG. 3, an MN 300 is illustrated as an example of the MN 300, and SNs 400A to SNs 400D are illustrated as an example of the SN 400. An MC is illustrated as an example of a cell that the MN 300 has, and SCs 1 to 4 are illustrated as an example of a cell that the SN 400 has. For example, the coverage area of SCs 1 to 4 overlaps with the coverage area of an MC. In such a case, the MC is a cell that can be used as a PCell (Primary Cell), and SCs 1 to 4 are cells that can be used as a PSCell.

Under these assumptions, consider a case where connection to a target cell fails when adding (CPA) or changing (CPC) a PSCell. Specifically, consider a case where connection to SC2 fails in a procedure for changing the PSCell from SC1 to SC2 in conditional reconfiguration when MC1 is used as a PCell and SC1 is used as a PSCell. Alternatively, consider a case where connection to SC2 fails in a procedure for adding SC2 as a PSCell in conditional reconfiguration when MC1 is used as a PCell and SC1 is used as a PSCell. In these cases, SC1 is an example of a source cell included in the SCG, and SC2 is an example of a target cell included in the SCG.

In such a case, UE200 sends a message (SCG Failure) including SCG failure information to the network (MN300), but includes in the message an information element (condSynchReconfigFailureSCG) that identifies conditional reconfiguration as the type of SCG failure information (failure type).

(4) Operation Example An operation example of the embodiment will be described below. In the following, a case where an EN-DC is executed as an MR-DC will be illustrated. That is, a case where an eNB100A included in an E-UTRAN 20 is an MN 300, and a gNB100B included in an NG RAN 30 is an SN 400 will be illustrated. However, the embodiment is not limited to this. The MR-DC may be an NE-DC or an NR-DC.

(4.1) Operation example 1
A procedure for adding a target cell as a PSCell based on conditional reconfiguration will be described below. In Fig. 4, T-SN1 (SN400A) and T-SN2 (SN400B) are examples of nodes that manage candidate cells for the target cell.

As shown in FIG. 4, in step S10, UE200 transmits a measurement report to MN300. The measurement report includes measurement results (RSRP, RSRQ, SINR) of the reception quality of the current cell (e.g., SC1 shown in FIG. 3) and neighboring cells (e.g., SC2 to SC4 shown in FIG. 3).

In step S11, MN300 decides to add a PSCell by conditional reconfiguration and determines a candidate cell for the target cell to be added as a PSCell (CPA decision).

In step S12A, MN300 transmits a message (SN Addition Request) to SN400A requesting that gNB100B be added as an SN. Similarly, in step S12B, MN300 transmits a message (SN Addition Request) to SN400B requesting that gNB100B be added as an SN.

In step S13A, SN400A sends a response message (SN Addition Request Ack) to the SN Addition Request to MN300. Similarly, in step S13B, SN400B sends a response message (SN Addition Request Ack) to the SN Addition Request to MN300.

In step S14, MN300 transmits a message (RRC Reconfiguration) including an information element (e.g., conditionalReconfiguration) instructing conditional reconfiguration to UE200. The conditionalReconfiguration includes information elements for identifying candidate cells and execution condition settings. The conditionalReconfiguration may include an information element (condReconfigId) associated with the type of execution condition event (Event A3, Event A5, etc.).

In step S15, UE200 sends a response message (RRC Reconfiguration Complete) to RRC Reconfiguration to MN300.

In step S16, UE200 determines whether there is a candidate cell that satisfies the CPA execution conditions. Here, the explanation will continue assuming that there is a candidate cell that satisfies the CPA execution conditions. If there are two or more candidate cells that satisfy the CPA execution conditions, UE200 selects a target cell from among the two or more candidate cells. Here, the explanation will continue assuming that the cell managed by SN400A is the target cell.

In step S17, UE200 sends a message (RRC Reconfiguration Complete) to MN300 indicating that it will perform connection to the target cell based on CPA.

In step S18, MN300 sends a message (SN Reconfiguration Complete) to SN400A indicating that gNB100B has been added as an SN.

In step S19, MN300 sends a message (SN Status Transfer) to SN400A notifying it of the status regarding the SN.

In step S20, data transfer is performed between UPF (User Plane Function) 500, MN 300 and SN 400A.

In step S21, UE200 executes a random access procedure between UE200 and SN400A. The random access procedure may be a four-step random access procedure or a two-step random access procedure. Here, the description will be continued assuming that UE200 fails in the random access procedure. In other words, UE200 fails to connect to the target cell based on CPA.

In step S22, UE 200 transmits a message (SCG Failure) including SCG failure information to MN 300. SCG Failure includes an information element (condSynchReconfigFailureSCG) that identifies conditional reconfiguration as the type of SCG failure information.

Furthermore, the SCG Failure may include information elements regarding the target cell (FailedPSCellID, measResultFailedPSCell). The SCG Failure may include information elements regarding the source cell (PreviousPSCellID, measResultPreviousPSCell). The SCG Failure may include information elements regarding candidate cells for the target cell (measResultCandidatePSCellInfoList). The measResultCandidatePSCellInfoList may include candidate cell identification information (PCI, frequency), measurement results of the reception quality of the candidate cell (measResult), whether the measurement results satisfy the CPA execution conditions (executionConditionSatisfied), an execution condition event (configuredExecutionConditionEvent), reception quality that satisfies the execution condition (satisfiedTriggeringQuantity), and an execution condition event that satisfies the execution condition (satisfiedTriggeringEvent). The SCG Failure may include information elements regarding the random access procedure to the target cell (attemptedRAInformation).

(4.2) Operation example 2
The procedure for changing the PSCell to a target cell based on conditional reconfiguration will be described below. In Fig. 5, T-SN1 (SN400A) and T-SN2 (SN400B) are examples of nodes that manage candidate cells for the target cell. S-SN (SN400C) is an example of a node that manages a source cell.

As shown in FIG. 5, in step S30, UE200 transmits a measurement report to SN400C. The measurement report includes measurement results (RSRP, RSRQ, SINR) of the reception quality of the current cell (e.g., SC1 shown in FIG. 3) and neighboring cells (e.g., SC2 to SC4 shown in FIG. 3).

In step S31, SN400C decides to change the PSCell by conditional reconfiguration and determines a candidate cell for the target cell to be changed to the PSCell (CPC decision).

In step S32, SN400C sends a message (SN change required) to MN300 requesting a change of the PSCell.

In step S33A, MN300 transmits a message (SN Addition Request) to SN400A requesting that gNB100B be added as an SN. Similarly, in step S33B, MN300 transmits a message (SN Addition Request) to SN400B requesting that gNB100B be added as an SN.

In step S34A, SN400A sends a response message (SN Addition Request Ack) to the SN Addition Request to MN300. Similarly, in step S34B, SN400B sends a response message (SN Addition Request Ack) to the SN Addition Request to MN300.

In step S35, MN300 transmits a message (RRC Reconfiguration) including an information element (e.g., conditionalReconfiguration) instructing conditional reconfiguration to UE200. The conditionalReconfiguration includes information elements for identifying candidate cells and execution condition settings. The conditionalReconfiguration may include an information element (condReconfigId) associated with the type of execution condition event (Event A3, Event A5, etc.).

In step S36, UE200 sends a response message (RRC Reconfiguration Complete) to RRC Reconfiguration to MN300.

In step S37, UE200 determines whether there is a candidate cell that satisfies the CPC execution conditions. Here, the explanation will continue assuming that there is a candidate cell that satisfies the CPC execution conditions. If there are two or more candidate cells that satisfy the CPC execution conditions, UE200 selects a target cell from among the two or more candidate cells. Here, the explanation will continue assuming that the cell managed by SN400A is the target cell.

In step S38, UE200 sends a message (RRC Reconfiguration Complete) to MN300 indicating that it will perform a connection to the target cell based on the CPC.

In step S39, MN300 sends a message (SN Reconfiguration Complete) to SN400A indicating that gNB100B has been added as an SN.

In step S40, SN400C sends a message (SN Status Transfer) to MN300 notifying the status of the SN, and MN300 sends a message (SN Status Transfer) to SN400A notifying the status of the SN.

In step S41, data transfer is performed between UPF500, SN400C, MN300 and SN400A.

In step S42, UE200 executes a random access procedure between UE200 and SN400A. The random access procedure may be a four-step random access procedure or a two-step random access procedure. Here, the description will be continued assuming that UE200 fails in the random access procedure. In other words, UE200 fails to connect to the target cell based on the CPC.

In step S43, UE200 transmits a message (SCG Failure) including SCG failure information to MN200. MN300 may forward the SCG Failure received from UE200 to SN400. SCG Failure includes an information element (condSynchReconfigFailureSCG) that identifies conditional reconfiguration as a type of SCG failure information.

Furthermore, the SCG Failure may include information elements regarding the target cell (FailedPSCellID, measResultFailedPSCell). The SCG Failure may include information elements regarding the source cell (PreviousPSCellID, measResultPreviousPSCell). The SCG Failure may include information elements regarding candidate cells for the target cell (measResultCandidatePSCellInfoList). The measResultCandidatePSCellInfoList may include candidate cell identification information (PCI, frequency), measurement results of the reception quality of the candidate cell (measResult), whether the measurement results satisfy the execution conditions of the CPC (executionConditionSatisfied), an execution condition event (configuredExecutionConditionEvent), reception quality that satisfies the execution condition (satisfiedTriggeringQuantity), and an execution condition event that satisfies the execution condition (satisfiedTriggeringEvent). The SCG Failure may include information elements regarding the random access procedure to the target cell (attemptedRAInformation).

(5) Configuration Examples of Information Elements Figures 6 to 11 show configuration examples of information elements of SCG Failure Information. Figures 6 to 8 show SCG Failure Information used in a case where the MN 300 is the eNB 100A, that is, SCG Failure Information used in the E-UTRAN 20. Figures 9 to 11 show SCG Failure Information used in a case where the MN 300 is the gNB 100B, that is, SCG Failure Information used in the NG RAN 30.

As shown in Figures 6 and 9, the SCG Failure Information may include an information element (condSynchReconfigFailureSCG) that identifies conditional reconfiguration as a type of SCG failure information. The SCG Failure Information may include information elements (FailedPSCellID, measResultFailedPSCell) regarding the target cell. The SCG Failure Information may include information elements (PreviousPSCellID, measResultPreviousPSCell) regarding the source cell.

As shown in Figures 7 and 10, the SCG Failure Information may include information elements (measResultCandidatePSCellInfoList) regarding candidate cells for the target cell. The measResultCandidatePSCellInfoList may include candidate cell identification information (PCI, frequency), measurement results of the reception quality of the candidate cell (measResult), whether the measurement results satisfy the execution conditions of the CPC (executionConditionSatisfied), an execution condition event (configuredExecutionConditionEvent), reception quality that satisfies the execution condition (satisfiedTriggeringQuantity), and an execution condition event that satisfies the execution condition (satisfiedTriggeringEvent).

As shown in FIG. 8 and FIG. 11, the SCG Failure Information may include an information element (attemptedRAInformation) regarding a random access procedure to the target cell. The attemptedRAInformation may include an information element (fourStepRAInformation) that specifies a four-step random access procedure, or an information element (twoStepRAInformation) that specifies a two-step random access procedure. These information elements may include an information element (e.g., absoluteFrequencyPoint) that specifies a frequency to be used in the random access procedure, an information element (e.g., locationAndBandwidth) that specifies the location and frequency band of the BWP (BandWidth Part) to be used in the random access procedure, an information element (e.g., subcarrierSpacing) that specifies the SCS (SubCarrier Spacing) to be used in the random access procedure, and an information element (e.g., FrequencyStart, FrequencyStartCFRA, subcarrierSpacing, subcarrierSpacingCFRA, FDM, FDMCFRA, perRAInfoList) regarding the random access preamble (msg 1 or msg A).

(6) Actions and Effects In the embodiment, in the CPA or CPC in the MR-DC, the UE 200 transmits an SCG Failure including an information element identifying a conditional reconfiguration to the network as a type of SCG failure information. According to such a configuration, it is possible to optimize a decision to add a PSCell (CPA decision) or a decision to change a PSCell (CPC decision). For example, as in the operation example 1, when the CPA decision is made by the MN 300, the MN 300 can optimize the CPA decision by receiving an SCG Failure including an information element identifying a conditional reconfiguration. As in the operation example 2, when the CPC decision is made by the SN 400, the SN 400 can optimize the CPC decision by acquiring an SCG Failure including an information element identifying a conditional reconfiguration from the MN 300.

The SCG Failure includes information elements regarding the target cell, information elements regarding the source cell, and information elements regarding candidate cells for the target cell. With this configuration, the decision to add a PSCell (CPA decision) or change a PSCell (CPC decision) can be further optimized.

The SCG Failure includes information elements regarding the random access procedure to the target cell. With such a configuration, the random access procedure to the target cell can be optimized.

[Other embodiments]
Although the embodiment has been described above, it will be apparent to those skilled in the art that the present invention is not limited to the description of the embodiment and that various modifications and improvements are possible.

In the embodiment, EN-DC is mainly exemplified as an example of MR-DC. However, the embodiment is not limited to this. MR-DC may be NE-DC or NR-DC. In NE-DC, SRB3 is not set in UE200, so operation example 3 described in the embodiment does not need to be used.

In operation example 1 (FIG. 4), a case where the CPA decision is executed by MN300 is illustrated. However, operation example 1 is not limited to this. The CPA decision may be executed by SN400. In such a case, MN300 may forward the SCG Failure received from UE200 to SN400.

In the operation example 2 (FIG. 5), a case where the CPC decision is executed by the SN400 is illustrated. However, the operation example 2 is not limited to this. The CPC decision may be executed by the MN300.

In the embodiment, a case where a connection to a target cell (PSCell) is made based on conditional reconfiguration in MR-DC is illustrated. However, the embodiment is not limited thereto. For example, in MR-DC, the present invention may be applied to PSCell Addition (hereinafter, normal PSCell Addition) in which a PSCell is added without being based on conditional reconfiguration, and PSCell change (hereinafter, normal PSCell Change) in which a PSCell is changed without being based on conditional reconfiguration. For example, in normal PSCell Addition or normal PSCell Change, when a connection to a target cell (PSCell) fails, UE200 may perform the following operation. Specifically, UE200 may include information elements (FailedPSCellID, measResultFailedPSCell) related to the target cell in SCG Failure. UE200 may include information elements (PreviousPSCellID, measResultPreviousPSCell) related to the source cell in SCG Failure. UE 200 may include an information element (attemptedRAInformation) regarding a random access procedure to the target cell in the SCG Failure.

The block diagram (Figure 2) used to explain the above-mentioned embodiment shows functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or may be realized using two or more devices that are physically or logically separated and directly or indirectly connected (e.g., using wires, wirelessly, etc.) and these multiple devices. The functional blocks may be realized by combining the one device or the multiple devices with software.

Functions include, but are not limited to, judgement, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs the transmission function is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on the method of realization for each.

Furthermore, the above-mentioned UE200 (the device) may function as a computer that performs processing of the wireless communication method of the present disclosure. FIG. 12 is a diagram showing an example of the hardware configuration of the device. As shown in FIG. 12, the device may 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.

In the following description, the term "apparatus" may be interpreted as a circuit, device, unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the figure, or may be configured to exclude some of the apparatuses.

Each functional block of the device (see Figure 2) is realized by any hardware element of the computer device, or a combination of such hardware elements.

In addition, each function of the device is realized by loading a specified software (program) onto hardware such as the processor 1001 and memory 1002, causing the processor 1001 to perform calculations, control communication via the communication device 1004, and control at least one of the reading and writing of data in the memory 1002 and storage 1003.

The processor 1001, for example, runs an operating system to control the entire computer. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, registers, etc.

Furthermore, the processor 1001 reads out programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the programs, programs that cause a computer to execute at least a part of the operations described in the above-mentioned embodiments are used. Furthermore, the above-mentioned various processes may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

The memory 1002 is a computer-readable recording medium and may be composed of at least one of, for example, a Read Only Memory (ROM), an Erasable Programmable ROM (EPROM), an Electrically Erasable Programmable ROM (EEPROM), a Random Access Memory (RAM), etc. The memory 1002 may be called a register, a cache, a main memory (main storage device), etc. The memory 1002 can store a program (program code), software module, etc. capable of executing a method according to one embodiment of the present disclosure.

Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. Storage 1003 may be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

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

The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc., to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one configuration (e.g., a touch panel).

In addition, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

Furthermore, the device may 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 some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

In addition, the notification of information is not limited to the aspects/embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of 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 (MIB), System Information Block (SIB))), other signals, or a combination of these. In addition, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

Each aspect/embodiment described in the present disclosure may 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), CDMA2000, 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), and other suitable systems, and next-generation systems that are extended based on these. In addition, multiple systems may be combined (for example, a combination of at least one of LTE and LTE-A and 5G, etc.).

The processing steps, sequences, flow charts, etc. of each aspect/embodiment described in this disclosure may be reordered unless inconsistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

In the present disclosure, a particular operation performed by a base station may be performed by its upper node in some cases. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal may be performed by at least one of the base station and other network nodes other than the base station (e.g., MME or S-GW, etc., but are not limited to these). Although the above example illustrates a case where there is one other network node other than the base station, it may also be a combination of multiple other network nodes (e.g., MME and S-GW).

Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer). They may be input and output via multiple network nodes.

The input and output information may be stored in a specific location (e.g., memory) or may be managed using a management table. The input and output information may be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to another device.

The determination may be based on a value represented by a single bit (0 or 1), a Boolean (true or false) value, or a numerical comparison (e.g., with a predetermined value).

Each aspect/embodiment described in this disclosure may be used alone, in combination, or switched depending on the execution. In addition, notification of specific information (e.g., notification that "X is the case") is not limited to being done explicitly, but may be done implicitly (e.g., not notifying the specific information).

Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if the software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and/or wireless technologies (such as infrared, microwave, etc.), then these wired and/or wireless technologies are included within the definition of a transmission medium.

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

Note that the terms described in this disclosure and the terms necessary for understanding this 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). Also, the signal may be a message. Also, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

As used in this disclosure, the terms "system" and "network" are used interchangeably.

In addition, the information, parameters, etc. described in this disclosure may be represented using absolute values, may be represented using relative values from a predetermined value, or may be represented using other corresponding information. For example, radio resources may be indicated by an index.

The names used for the above-mentioned parameters are not limiting in any respect. Moreover, the formulas etc. using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not limiting in any respect.

In this disclosure, terms such as "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" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, small cell, femtocell, and picocell.

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 be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH).

The terms "cell" or "sector" refer to part or all of the coverage area of a base station and/or a base station subsystem that provides communication services within that coverage.

In this disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "terminal", etc. may be used interchangeably.

A mobile station may also be referred to by those skilled in the art as a 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, handset, user agent, mobile client, client, or some other suitable terminology.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned moving body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during 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 be read as a mobile station (user terminal, the same applies below). For example, each aspect/embodiment 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 multiple mobile stations (which may be called, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.). In this case, the mobile station may be configured to have the functions that a base station has. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, the uplink channel, downlink channel, etc. may be read as a side channel.

Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.
A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

Numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology may indicate at least one of, for example, Subcarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, a particular filtering operation performed by the transceiver in the frequency domain, a particular windowing operation performed by the transceiver in the time domain, etc.

A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.). A slot may be a numerology-based unit of time.

A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

Radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals. Radio frame, subframe, slot, minislot, and symbol may each be referred to by a different name.

For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. In other words, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit expressing the TTI may be called a slot, minislot, etc., instead of a subframe.

Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal by allocating radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

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

When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit of scheduling. In addition, the number of slots (minislots) constituting the minimum time unit of scheduling may be controlled.

A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

Note that a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length exceeding 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length less than the TTI length of a long TTI and equal to or greater than 1 ms.

A resource block (RB) is a resource allocation unit in the time domain and frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

In addition, the time domain of an RB may include one or more symbols and may be one slot, one minislot, one subframe, or one TTI in length. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may be referred to as a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

A resource block may also be composed of one or more resource elements (REs). For example, one RE may be a radio resource area of one subcarrier and one symbol.

A Bandwidth Part (BWP), which may also be referred to as a partial bandwidth, may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by the index of the RBs relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within the BWP.

A BWP may include a BWP for the UL (UL BWP) and a BWP for the DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.

At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal/channel outside the active BWP. Note that the terms "cell", "carrier", etc. in this disclosure may be read as "BWP".

The above-mentioned structures of radio frames, subframes, slots, minislots, and symbols are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, as well as the number of symbols in a TTI, the symbol length, and the cyclic prefix (CP) length can be changed in various ways.

The terms "connected" and "coupled", or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access". As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables, and printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and light (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

The reference signal may also be abbreviated as Reference Signal (RS) or may be called a pilot depending on the applicable standard.

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

The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

Any reference to elements using designations such as "first," "second," etc., used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, as is the term "comprising." Additionally, the term "or," as used in this disclosure, is not intended to be an exclusive or.

In this disclosure, where articles have been added by translation, such as a, an, and the in English, this disclosure may include that the nouns following these articles are in the plural form.

As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. In addition, "judgment" and "decision" can include considering resolving, selecting, choosing, establishing, comparing, etc., to be a "judgment" or "decision." In other words, "judgment" and "decision" can include considering some action to be a "judgment" or "decision." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

In this disclosure, the term "A and B are different" may mean "A and B are different from each other." In addition, the term may mean "A and B are each different from C." Terms such as "separate" and "combined" may also be interpreted in the same way as "different."

Although the present disclosure has been described in detail above, it is 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 in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

10. Wireless communication systems
20 E-UTRAN
30 NGRAN
40 Core Network
50 E-SMLC
100A eNB
100B gNB
200UE
210 Radio signal transmitter/receiver
220 Amplifier section
230 Modulation and demodulation section
240 Control signal/reference signal processing unit
250 Encoding/Decoding Unit
260 Data transmission and reception unit
270 Control Unit
300 MN
400SN
500 UPF
1001 Processor
1002 Memory
1003 Storage
1004 Communication equipment
1005 Input Device
1006 Output device
1007 Bus

Claims (5)

A control unit that adds a cell to the second cell group based on conditional reconfiguration in dual connectivity using a first cell group and a second cell group;
A transmitter that transmits a message including failure information of the second cell group to a network when a connection to a target cell to be added to the second cell group fails in the conditional reconfiguration ,
The message includes an information element regarding the target cell to which connection failed in the conditional reconfiguration and which is to be added to the second cell group . The terminal of claim 1 , wherein the message includes an information element related to a random access procedure to the target cell. A control unit that instructs, in dual connectivity using a first cell group and a second cell group, to add a cell to the second cell group based on conditional reconfiguration;
A receiving unit that receives, when a connection to a target cell to be added to the second cell group fails in the conditional reconfiguration, a message including failure information of the second cell group from a terminal;
The message includes information elements regarding the target cell that failed to be connected to in the conditional reconfiguration and that is to be added to the second cell group, the base station. A terminal and a base station,
The base station instructs, in dual connectivity using a first cell group and a second cell group, to add a cell to the second cell group based on conditional reconfiguration;
When the terminal fails to connect to a target cell to be added to the second cell group in the conditional reconfiguration, the terminal transmits a message including failure information of the second cell group to a network;
A wireless communication system, wherein the message includes information elements regarding the target cell to which connection failed in the conditional reconfiguration and which is to be added to the second cell group. In dual connectivity using a first cell group and a second cell group, adding a cell to the second cell group based on conditional reconfiguration;
When a connection to a target cell to be added to the second cell group fails in the conditional reconfiguration, transmitting a message including failure information of the second cell group to a network;
A wireless communication method, wherein the message includes an information element regarding the target cell to which connection failed in the conditional reconfiguration and which is to be added to the second cell group.

Images