Terminal, base station, wireless communication system, and wireless communication method

Abstract

To provide a terminal, a base station, a wireless communication system, and a wireless communication method that appropriately perform a function of retaining information about conditional setting in a network and a terminal.SOLUTION: A terminal 200 includes a receiving unit that receives setting information about conditional re-setting and a control unit that executes a procedure related to the conditional re-setting. The control unit executes specific control to retain the setting information after the procedure related to the conditional re-setting is completed when a specific condition is satisfied.SELECTED DRAWING: Figure 4

Description

Technical Field

[0001] The present disclosure relates to a terminal, a base station, a wireless communication system, and a wireless communication method corresponding to a multicast / broadcast service.

Background Art

[0002] The 3rd Generation Partnership Project (3GPP) is standardizing the 5th generation mobile communication system (also called 5G, New Radio (NR), or Next Generation (NG)), and is also proceeding with the standardization of the next generation, called Beyond 5G, 5G Evolution, or 6G.

[0003] In 3GPP Release 16, conditional reconfiguration was introduced to execute connection to a target cell without transmitting a re-establishment request message to the target cell. Conditional reconfiguration may include Conditional Handover (CHO), and may also include Conditional PSCell (Primary Secondary Cell) Change (CPC), Conditional PSCell Addition (CPA).

[0004] By the way, in CPC, the CPC configuration is released in response to the completion of CPC (completion of connection to the target cell). However, assuming a case where a terminal (hereinafter, UE; User Equipment) repeatedly moves between two or more cells, the setting and release of the CPC configuration may be repeated.

[0005] From this perspective, 3GPP Release 16 discusses support for a function that maintains information about CPC (e.g., UE context on the network side and CPC configuration on the UE side) in the network and UE (hereinafter referred to as Selective activation) (see, for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] “New WID on Further NR mobility enhancements”, RP213564, 3GPP TSG RAN Meeting #94e, 3GPP, December 2021 [Overview of the project]

[0007] Against this backdrop, the inventors, after diligent study, found a need to define how selective activation should be performed, including the triggers for selective activation.

[0008] Therefore, the present invention has been made to solve the above-mentioned problems and aims to provide a terminal, base station, wireless communication system, and wireless communication method that can appropriately perform selective activation.

[0009] One aspect of the present disclosure is a terminal comprising a receiving unit that receives setting information relating to conditional resetting, and a control unit that executes a procedure relating to the conditional resetting, wherein the control unit executes a specific control to retain the setting information after the procedure relating to the conditional resetting is completed, when specific conditions are met.

[0010] One aspect of the disclosure is a base station comprising a transmitting unit that transmits configuration information relating to conditional resetting, and a control unit that executes a procedure relating to the conditional resetting, wherein the control unit assumes that, when certain conditions are met, a terminal performs a specific control to retain the configuration information after the procedure relating to the conditional resetting is completed.

[0011] One aspect of the disclosure is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises a receiving unit for receiving setting information relating to conditional resetting and a control unit for executing a procedure relating to the conditional resetting, and the control unit executes a specific control to retain the setting information after the procedure relating to the conditional resetting is completed, provided that specific conditions are met.

[0012] One aspect of the disclosure is a wireless communication method comprising the steps of: receiving setting information relating to conditional resetting; performing a procedure relating to the conditional resetting; and, if certain conditions are met, performing a specific control to retain the setting information after the procedure relating to the conditional resetting is completed. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10. [Figure 2] Figure 2 shows the frequency range used in the wireless communication system 10. [Figure 3] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10. [Figure 4] Figure 4 is a functional block diagram of the UE200. [Figure 5] Figure 5 is a functional block diagram of the gNB100. [Figure 6] Figure 6 is a diagram illustrating example 1 of operation. [Figure 7]FIG. 7 is a diagram for explaining Operation Example 2. [Figure 8] FIG. 8 is a diagram for explaining Operation Example 3. [Figure 9] FIG. 9 is a diagram for explaining Operation Example 4. [Figure 10] FIG. 10 is a diagram for explaining Operation Example 5. [Figure 11] FIG. 11 is a diagram for explaining Operation Example 6. [Figure 12] FIG. 12 is a diagram for explaining Operation Example 7. [Figure 13] FIG. 13 is a diagram for explaining Operation Example 8. [Figure 14] FIG. 14 is a diagram showing an example of UE Assistance Information (in ASN.1 format). [Figure 15] FIG. 15 is a diagram showing an example of CondReconfigToAddModList (in ASN.1 format). [Figure 16] FIG. 16 is a diagram showing an example of SN Addition request (in ASN.1 format). [Figure 17] FIG. 17 is a diagram showing an example of HO request (in ASN.1 format). [Figure 18] FIG. 18 is a diagram showing an example of the hardware configuration of gNB100 and UE200. [Figure 19] FIG. 19 is a diagram showing a configuration example of vehicle 2001.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Hereinafter, embodiments will be described based on the drawings. Note that the same or similar reference numerals are assigned to the same functions and configurations, and the description thereof will be omitted as appropriate.

[0015] [Embodiments] (1) Overall schematic configuration of the wireless communication system Figure 1 is a schematic diagram of the overall configuration of the wireless communication system 10 according to the embodiment. The wireless communication system 10 is a wireless communication system in accordance with 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN20) and a terminal 200 (hereinafter referred to as UE (User Equipment) 200).

[0016] The wireless communication system 10 may also be a wireless communication system that conforms to a method called Beyond 5G, 5G Evolution, or 6G.

[0017] NG-RAN20 includes base station 100 (hereinafter referred to as gNB100). The specific configuration of the wireless communication system 10, including the number of gNB100 and UE200, is not limited to the example shown in Figure 1.

[0018] NG-RAN20 actually includes multiple NG-RAN Nodes, specifically gNBs (or ng-eNBs), and is connected to a 5G-compliant core network (5GC, not shown). Note that NG-RAN20 and 5GC may also be simply referred to as the "network".

[0019] The gNB100 is a 5G-compliant radio base station that performs 5G-compliant wireless communication with the UE200. The gNB100 and UE200 can support Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beamband by controlling radio signals transmitted from multiple antenna elements; carrier aggregation (CA), which uses multiple component carriers (CCs) bundled together; and dual connectivity (DC), which enables simultaneous communication to two or more transport blocks between the UE and each of the two NG-RAN Nodes.

[0020] Furthermore, the wireless communication system 10 supports multiple frequency ranges (FR). Figure 2 shows the frequency ranges used in the wireless communication system 10.

[0021] As shown in Figure 2, the wireless communication system 10 corresponds to FR1 and FR2. The frequency bands of each FR are as follows:

[0022] • FR1: 410 MHz ~ 7.125 GHz • FR2: 24.25 GHz ~ 52.6 GHz In FR1, a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz may be used, and a bandwidth (BW) of 5 to 100 MHz may be used. FR2 is a higher frequency than FR1, and a 60 or 120 kHz (240 kHz may be included) SCS may be used, and a bandwidth (BW) of 50 to 400 MHz may be used.

[0023] Note that SCS may also be interpreted as numerology. Numerology is defined in 3GPP TS38.300 and corresponds to a single subcarrier interval in the frequency domain.

[0024] Furthermore, the wireless communication system 10 also supports higher frequency bands than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands exceeding 52.6 GHz up to 71 GHz or 114.25 GHz. Such high frequency bands may be conveniently referred to as "FR2x".

[0025] To address the problem of increased phase noise in high-frequency bands, when using bandwidths exceeding 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with a larger Sub-Carrier Spacing (SCS) may be applied.

[0026] Figure 3 shows an example of the configuration of wireless frames, subframes, and slots used in the wireless communication system 10.

[0027] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc., may be used.

[0028] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols, 56 symbols). In addition, the number of slots per subframe may differ depending on the SCS.

[0029] The time direction (t) shown in Figure 3 may also be called the time domain, symbol period, or symbol time. The frequency direction may also be called the frequency domain, resource block, subcarrier, or bandwidth part (BWP).

[0030] DMRS is a type of reference signal, prepared for various channels. Here, unless otherwise specified, it may refer to the DMRS for the downlink data channel, specifically the PDSCH (Physical Downlink Shared Channel). However, the DMRS for the uplink data channel, specifically the PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as the DMRS for the PDSCH.

[0031] DMRS can be used for channel estimation in a device, for example, as part of coherent demodulation in the UE200. DMRS may only be present in the resource block (RB) used for PDSCH transmission.

[0032] A DMRS may have multiple mapping types. Specifically, a DMRS may have mapping type A and mapping type B. In mapping type A, the first DMRS is placed on the second or third symbol of the slot. In mapping type A, the DMRS may be mapped relative to the slot boundary, regardless of where in the slot the actual data transmission begins. The reason the first DMRS is placed on the second or third symbol of the slot may be interpreted as being placed after the control resource sets (CORESET).

[0033] In mapping type B, the first DMRS may be placed on the first symbol of the data allocation. That is, the position of the DMRS may be given relative to where the data is located, rather than relative to the slot boundary.

[0034] Furthermore, DMRS may have multiple types. Specifically, DMRS may have Type 1 and Type 2. Type 1 and Type 2 differ in their frequency domain mapping and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, while Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.

[0035] Here, the DC mentioned above may include any of the following DCs: EN-DC (E-UTRA-NR Dual Connectivity), NE-DC (NR-EUTRA Dual Connectivity), and NR-DC (NR-NR Dual Connectivity).

[0036] In the CA or DC described above, a group of cells capable of performing operations related to the C-plane (control plane) and U-plane (user plane) may be referred to as the first cell group (MCG; Master Cell Group). In the DC described above, a group of cells capable of performing operations related to the U-plane (user plane) may be referred to as the second cell group (SCG; Secondary Cell Group). Cells included in the MCG may include Primary Cells (hereinafter referred to as PCells). A node having cells included in the MCG may be referred to as an MN (Master Node). Cells included in the SCG may be referred to as Secondary Cells (hereinafter referred to as PCells). An SCell may include Primary Secondary Cells (hereinafter referred to as PSCells). A node having cells included in the SCG may be referred to as an SN (Secondary Node).

[0037] (2) Functional block configuration of the wireless communication system Next, the functional block configuration of the wireless communication system 10 will be described.

[0038] First, we will describe the functional block configuration of the UE200.

[0039] Figure 4 is a functional block diagram of the UE200. As shown in Figure 4, the UE200 comprises a wireless signal transmission / reception 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 transmission / reception unit 260, and a control unit 270.

[0040] The wireless signal transceiver unit 210 transmits and receives wireless signals in accordance with NR. The wireless signal transceiver unit 210 supports Massive MIMO, CA which uses multiple CCs bundled together, and DC which communicates simultaneously between the UE and each of the two NG-RAN Nodes.

[0041] The amplifier section 220 consists of components such as a PA (Power Amplifier) ​​and an LNA (Low Noise Amplifier). The amplifier section 220 amplifies the signal output from the modulation / demodulation section 230 to a predetermined power level. The amplifier section 220 also amplifies the RF signal output from the wireless signal transmission / reception section 210.

[0042] The modulation / demodulation unit 230 performs data modulation / demodulation, transmit power setting, and resource block allocation for each predetermined communication destination (gNB100 or other gNB). The modulation / demodulation 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).

[0043] The control signal / reference signal processing unit 240 performs processing related to various control signals transmitted and received by the UE200, and processing related to various reference signals transmitted and received by the UE200.

[0044] Specifically, the control signal / reference signal processing unit 240 receives various control signals transmitted from the gNB100 via a predetermined control channel, such as control signals for the radio resource control layer (RRC). The control signal / reference signal processing unit 240 also transmits various control signals to the gNB100 via a predetermined control channel.

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

[0046] DMRS is a terminal-specific, known reference signal (pilot signal) between the base station and the 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 a problem in the high-frequency band.

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

[0048] Furthermore, 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), among others.

[0049] Furthermore, data channels include PDSCH (Physical Downlink Shared Channel) and PUSCH (Physical Uplink Shared Channel), among others. "Data" refers to data transmitted through a data channel. A data channel can also be interpreted as a shared channel.

[0050] Here, the control signal / reference signal processing unit 240 may receive 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 Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), and RV (Redundancy Version).

[0051] The value stored in the DCI Format field is an information element that specifies the DCI format. 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, push-TimeDomainAllocationList) included in the RRC message. The time domain resource may also be identified by the value stored in the TDRA field and the 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 MCS and the MCS table. The MCS table may be specified by the RRC message or identified by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ Process to which DCI is applied. The value stored in NDI is an information element that determines whether the data to which DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which DCI is applied.

[0052] In this embodiment, the control signal / reference signal processing unit 240 constitutes a receiving unit that receives setting information related to conditional reconfiguration. Conditional reconfiguration may include Conditional Handover (CHO), Conditional PSCell (Primary Secondary Cell) Change (CPC), and Conditional PSCell Addition (CPA). The setting information may be referred to as ConditionalReconfiguration. ConditionalReconfiguration may include Special Cell (hereinafter, SpCell) configuration. SpCell may include PCell or PSCell. That is, SpCell configuration is setting information related to target cell candidates in conditional reconfiguration (CHO, CPC, or CPA). ConditionalReconfiguration may be included in RRC Reconfiguration.

[0053] The encoding / decoding unit 250 performs data splitting / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or other gNB).

[0054] Specifically, the encoding / decoding unit 250 divides the data output from the data transmission / reception unit 260 into predetermined sizes and performs channel coding on the divided data. The encoding / decoding unit 250 also decodes the data output from the modulation / demodulation unit 230 and concatenates the decoded data.

[0055] The data transmission / reception unit 260 performs the transmission and reception of Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmission / reception unit 260 performs assembly / decomposition of PDUs / SDUs at multiple layers (such as the Media Access Control Layer (MAC), Radio Link Control Layer (RLC), and Packet Data Convergence Protocol Layer (PDCP)). In addition, the data transmission / reception unit 260 performs error correction and retransmission control of data based on HARQ (Hybrid Automatic Repeat Request).

[0056] The control unit 270 controls each functional block that constitutes the UE200. In this embodiment, the control unit 270 is configured to execute a procedure related to conditional reconfiguration. When certain conditions are met, the control unit 270 executes a specific control (hereinafter referred to as Selective Activation) that retains the configuration information (hereinafter referred to as SpCell configuration) after the procedure related to conditional reconfiguration is completed.

[0057] The specific conditions may include a condition for receiving an indication from the network that commands Selective Activation (hereinafter referred to as the first condition). The indication may be included in the RRC Reconfiguration for conditional reconfiguration. The specific conditions may also include a condition for sending a message to the network requesting Selective Activation (hereinafter referred to as the second condition). The message may be UE Assistance Information. The specific conditions may include both the first and second conditions.

[0058] Whether or not to perform Selective Activation may be determined based on the mobility perk of the UE200. For example, the control unit 270 may determine whether or not to perform Selective Activation based on an information element (VisitedCellInfoList) specified in 3GPP TS38.331. VisitedCellInfoList may include up to 16 cells as the cells where the UE200 most recently stayed. The control unit 270 may determine to perform Selective Activation if the pattern of Cell IDs included in VisitedCellInfoList is a pattern in which the same Cell ID appears repeatedly (for example, "Cell #1", "Cell #2", "Cell #1", "Cell #2", ...).

[0059] Secondly, the functional block configuration of the gNB100 will be described.

[0060] Figure 5 is a functional block diagram of the gNB100. As shown in Figure 5, the gNB100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0061] The receiver 110 receives various signals from the UE200. The receiver 110 may also receive the UL signal via PUCCH or PUSCH.

[0062] The transmitter 120 transmits various signals to the UE200. The transmitter 120 may also transmit DL signals via PDCCH or PDSCH. In this embodiment, the transmitter 120 is configured as a transmitter that transmits setting information related to conditional resetting.

[0063] The control unit 130 controls the gNB100. In this embodiment, the control unit 130 constitutes a control unit that executes a procedure related to conditional reconfiguration. The control unit 130 assumes that the UE will perform Selective Activation when certain conditions are met.

[0064] The specific conditions may include a condition (first condition) that sends an indication to the UE200 that prompts Selective Activation. The indication may be included in the RRC Reconfiguration for conditional reconfiguration. The specific conditions may also include a condition (second condition) that receives a message from the UE200 requesting Selective Activation. The message may be UE Assistance Information. The specific conditions may include both the first and second conditions.

[0065] Whether or not to perform Selective Activation may be determined based on the mobility perk of the UE200. For example, the control unit 130 may determine whether or not to perform Selective Activation based on information elements (UE History Information) specified in 3GPP TS38.423. The Last Visited Cell List included in the UE History Information may include up to 16 cells as the cells where the UE200 most recently stayed. The control unit 270 may determine to perform Selective Activation if the pattern of Cell IDs included in the Last Visited Cell List is a pattern in which the same Cell ID appears repeatedly (for example, "Cell #1", "Cell #2", "Cell #1", "Cell #2", ...). Alternatively, the control unit 130 may determine whether or not to perform Selective Activation based on the UE trajectory. The UE trajectory may include the UE's position information (latitude, longitude, altitude), timestamp, and velocity (horizontal velocity, vertical velocity). The control unit 130 may determine the path of the UE200 based on the UE trajectory and decide to perform Selective Activation if the path of the UE200 repeats a certain path.

[0066] In this case, if the control unit 130 determines that Selective Activation should be performed, it may retain the UE context after the procedure for conditional reconfiguration is completed, even if the UE200 was not connected to its own cell during conditional reconfiguration. In such a case, the control unit 130 may retain one or more information elements selected from UE Config, SCG Config, and CPC config in addition to the UE context.

[0067] (3) Challenges In conditional reconfiguration, the SpCell configuration is released upon completion of the conditional reconfiguration (i.e., completion of connection to the target cell). However, in cases where the UE200 repeatedly moves between two or more cells, the setting and release of the SpCell configuration may be repeated.

[0068] From this perspective, support for a function that maintains information regarding conditional reconfiguration in the network and UE (e.g., UE context on the network side and SpCell configuration on the UE side) (hereinafter referred to as Selective activation) is being discussed.

[0069] Against this backdrop, the inventors, after diligent study, found a need to define how selective activation should be performed, including the triggers for selective activation.

[0070] (4) Example of operation Next, an example of the operation of the embodiment will be described. The example of operation will describe the procedure for performing selective activation.

[0071] (4.1) Example of operation 1 Operation Example 1 describes the CPC (Critical Process Control) from Source SN (hereinafter referred to as S-SN) to Target SN (T-SN). In Operation Example 1, the S-SN makes the decision on whether or not to execute the CPC, and the MN derives the mobility pattern of the UE200. Note that the T-SN shown in Figure 6 can be considered a candidate for T-SN.

[0072] As shown in Figure 6, in step S10, the UE200 sends a Measurement Report to the S-SN. The Measurement Report includes the quality of the S-SN and the quality of the surrounding cells of the S-SN.

[0073] In step S11, S-SN determines whether or not to perform CPC based on the Measurement Report. This section continues the explanation of cases where it is determined that CPC should be performed.

[0074] In step S12, S-SN sends a message to MN requesting a CPC (SN change required). The SN change required message includes information about the candidate T-SN (e.g., CellID).

[0075] In step S13, the MN derives the mobility pattern of the UE200. The mobility pattern of the UE200 is derived based on the UE History Information or UE trajectory. Based on the mobility pattern of the UE200, the MN determines whether or not to perform Selective activation. Here, we will continue the explanation of the case in which it is determined that Selective activation should be performed.

[0076] In step S14, the MN sends a message (SN Addition Request) to one or more T-SN candidates requesting them to be prepared to be added as PSCells. The SN Addition Request may include an indication that Selective activation is required.

[0077] In step S15, one or more T-SN candidates send an SN Addition Request ACK message to the MN.

[0078] In step S16, the MN sends a message (RRC Reconfiguration) to the UE200 instructing CPC. The RRC Reconfiguration includes configuration information (SpCell configuration) regarding the T-SN candidates. The RRC Reconfiguration includes an indication to instruct Selective activation.

[0079] In step S17, UE200 sends a response message to MN for RRC Reconfiguration (RRC Reconfiguration Complete).

[0080] In step S20, the UE200 executes a connection procedure for the T-SN selected from the candidates. Specifically, the UE200 executes a Random Access (RA) procedure for the selected T-SN.

[0081] In step S21, after the CPC procedure is completed (in other words, after the connection to the T-SN is completed), the UE200 retains configuration information for the CPC (e.g., SpCell configuration or CPC configuration). The SpCell configuration may also be referred to as PSCell Config. The SpCell configuration includes configuration information for candidate T-SNs that the UE200 did not connect to during the CPC procedure.

[0082] In step S22, the T-SN candidate may retain the UE context after the CPC procedure is completed (in other words, after the connection to the T-SN is completed). In such a case, the T-SN candidate may retain one or more information elements selected from the UE Config, SCG Config, and CPC config in addition to the UE context. Here, the T-SN candidate can be thought of as the T-SN candidate to which UE200 did not connect in the CPC procedure.

[0083] In Operation Example 1, the specific condition may be considered as condition 1, which is the condition in step S16 of receiving an indication that prompts for selective activation.

[0084] (4.2) Example of operation 2 Operation Example 2 describes the CPC from S-SN to T-SN. In Operation Example 2, the S-SN makes the decision on whether or not to execute the CPC (CPC decision), and the UE200 derives the mobility pattern. Note that the T-SN shown in Figure 7 can be considered a candidate for T-SN.

[0085] In the following, the same step numbers are used for processes that are the same as in Operation Example 1. Therefore, the differences from Operation Example 1 will be explained primarily. Specifically, step S10X is executed instead of step S13 described above.

[0086] As shown in Figure 7, in step S10X, UE200 derives its mobility pattern. The mobility pattern of UE200 is derived based on VisitedCellInfoList. Based on its mobility pattern, UE200 determines whether or not to perform Selective activation. Here, we will continue the explanation for the case where it is determined that Selective activation should be performed. UE200 sends a message (UE Assistance Information) to MN requesting Selective activation. The UE Assistance Information includes informational elements related to the mobility pattern of UE200.

[0087] In Operation Example 2, the decision of whether or not to perform Selective activation may be made by the MN based on UE Assistance Information received from UE200.

[0088] In example 2, the specific condition may include a second condition that sends a message requesting selective activation. The specific condition may also be considered to include condition 1, which receives an indication that performs selective activation in step S16.

[0089] (4.3) Example of operation 3 Operation Example 3 describes the CPC from S-SN to T-SN. In Operation Example 3, the S-SN makes the decision on whether or not to execute the CPC (CPC decision), and the S-SN also derives the mobility pattern of the UE200. Note that the T-SN shown in Figure 8 can be considered a candidate for T-SN.

[0090] In the following, the same step numbers are used for processes that are the same as in Operation Example 1. Therefore, the differences from Operation Example 1 will be explained primarily. Specifically, step S31 is executed instead of step S13 described above.

[0091] As shown in Figure 8, in step S31, S-SN derives the mobility pattern of UE200. The mobility pattern of UE200 is derived based on UE History Information or UE trajectory. Based on the mobility pattern of UE200, S-SN determines whether or not to perform Selective activation. Here, we will continue the explanation of the case in which it is determined that Selective activation should be performed.

[0092] In operation example 3, in step S12, S-SN may send an SN change required message to MN that includes an indication to perform Selective activation.

[0093] In example 3, the specific condition may be considered to be condition 1, which is the condition in step S16 that receives an indication to perform selective activation.

[0094] (4.4) Example of operation 4 Operation Example 4 describes the CPC from S-SN to T-SN. In Operation Example 4, the S-SN makes the decision on whether or not to execute the CPC (CPC decision), and the UE200 derives the mobility pattern. Note that the T-SN shown in Figure 9 can be considered a candidate for T-SN.

[0095] In the following, the same step numbers are used for processes similar to those in Operation Example 3. Therefore, the differences from Operation Example 3 will be explained primarily. Specifically, step S10Y is executed instead of step S31 described above.

[0096] As shown in Figure 9, in step S10Y, UE200 derives its mobility pattern. The mobility pattern of UE200 is derived based on VisitedCellInfoList. Based on the mobility pattern of UE200, UE200 determines whether or not to perform Selective activation. Here, we will continue the explanation of the case where it is determined that Selective activation should be performed. UE200 sends a message (UE Assistance Information) requesting Selective activation to S-SN. The UE Assistance Information includes information elements related to the mobility pattern of UE200.

[0097] In Operation Example 4, the decision of whether or not to perform Selective activation may be made by S-SN based on UE Assistance Information received from UE200.

[0098] In example 4, the specific condition may include a second condition that sends a message requesting selective activation. The specific condition may also be considered to include condition 1 in step S16, which receives an indication that prompts selective activation.

[0099] (4.5) Example of operation 5 Operation Example 5 describes the CPC from S-SN to T-SN. In Operation Example 5, the decision of whether or not to execute CPC (CPC decision) is performed by MN, and the derivation of the UE200 mobility pattern is also performed by MN. Note that the T-SN shown in Figure 10 can be considered a candidate for T-SN.

[0100] In the following, the same step numbers are used for processes that are the same as in Operation Example 1. Therefore, the differences from Operation Example 1 will be explained primarily. Specifically, steps S40 to S41 are executed instead of steps S10 to S12 described above.

[0101] As shown in Figure 10, in step S40, UE200 sends a Measurement Report to MN. The Measurement Report includes the quality of S-SN and the quality of the surrounding cells of S-SN.

[0102] In Step S41, the MN determines whether or not to perform a CPC based on the Measurement Report. This section continues the explanation of the case where it is determined that a CPC should be performed.

[0103] In example 5, the specific condition may be considered as condition 1, which is the condition in step S16 of receiving an indication that prompts for selective activation.

[0104] (4.6) Example of operation 6 Operation Example 6 describes the CPC from S-SN to T-SN. In Operation Example 6, the decision of whether or not to execute CPC (CPC decision) is performed by MN, and the derivation of the mobility pattern of UE200 is performed by UE200. Note that the T-SN shown in Figure 11 can be considered a candidate for T-SN.

[0105] In the following, the same step numbers are used for processes similar to those in Operation Example 5. Therefore, the differences from Operation Example 5 will be explained primarily. Specifically, step S40X is executed instead of step S13 described above.

[0106] As shown in Figure 11, in step S40X, UE200 derives its mobility pattern. The mobility pattern of UE200 is derived based on VisitedCellInfoList. Based on the mobility pattern of UE200, UE200 determines whether or not to perform Selective activation. Here, we will continue the explanation of the case where it is determined that Selective activation should be performed. UE200 sends a message (UE Assistance Information) to MN requesting Selective activation. The UE Assistance Information includes informational elements related to the mobility pattern of UE200.

[0107] In example 6, the decision of whether or not to perform Selective activation may be made by the MN based on UE Assistance Information received from UE200.

[0108] In example 6, the specific condition may include a second condition that sends a message requesting selective activation. The specific condition may also be considered to include condition 1 in step S16, which receives an indication that prompts selective activation.

[0109] (4.7) Example of operation 7 Operation Example 7 describes the CHO from Source MN (hereinafter referred to as S-MN) to Target MN (T-MN). In Operation Example 7, the case in which the decision of whether or not to execute the CHO (HO decision) is performed by S-MN, and the derivation of the UE200 mobility pattern is performed by MN. Note that the T-MN shown in Figure 12 can be considered a candidate for T-MN.

[0110] As shown in Figure 12, in step S60, the UE200 sends a Measurement Report to the S-MN. The Measurement Report includes the quality of the S-MN and the quality of the surrounding cells of the S-MN.

[0111] In Step S61, S-MN determines whether or not to perform a CHO based on the Measurement Report. This section continues the explanation of cases where it is determined that a CHO should be performed.

[0112] In step S62, the MN derives the mobility pattern of the UE200. The mobility pattern of the UE200 is derived based on the UE History Information or UE trajectory. Based on the mobility pattern of the UE200, the MN determines whether or not to perform Selective activation. Here, we will continue the explanation of the case in which it is determined that Selective activation should be performed.

[0113] In step S63, the MN sends a Handover request message to one or more T-MN candidates requesting them to prepare to be added as PCells. The Handover request may include an indication that Selective activation is required.

[0114] In step S64, one or more T-MN candidates send a Handover request ACK message to the MN.

[0115] In step S65, the MN sends a message (RRC Reconfiguration) to the UE200 instructing the CHO. The RRC Reconfiguration includes configuration information (PCell configuration) for the T-MN candidate. The RRC Reconfiguration includes an indication for Selective activation.

[0116] In step S66, UE200 sends a response message to RRC Reconfiguration (RRC Reconfiguration Complete) to MN.

[0117] In step S70, the UE200 executes a connection procedure for the T-MN selected from the candidates for T-MN. Specifically, the UE200 executes a Random Access (RA) procedure for the selected T-MN.

[0118] In step S71, after the procedure for the CHO is completed (in other words, after the connection to the T-MN is completed), the UE200 retains configuration information for the CHO (e.g., SpCell configuration). The SpCell configuration may also be referred to as PCell Config. The SpCell configuration includes configuration information for candidate T-MNs that the UE200 did not connect to in the procedure for the CPC.

[0119] In step S72, the candidate T-MN may retain the UE context after the procedure for the CHO is completed (in other words, after the connection to the T-MN is completed). In such a case, the candidate T-MN may retain the UE Config and / or MCG Config in addition to the UE context. Here, the candidate T-MN may be considered as the candidate T-MN that UE200 did not connect to in the procedure for the CHO.

[0120] In example 7, the specific condition may be considered to be condition 1, which is the condition in step S66 of receiving an indication that prompts for selective activation.

[0121] (4.8) Example of operation 8 Operation Example 8 describes a CHO from S-MN to T-MN. In Operation Example 8, the decision of whether or not to execute the CHO (HO decision) is performed by S-MN, and the derivation of the mobility pattern of UE200 is performed by UE200. Note that T-MN shown in Figure 13 can be considered a candidate for T-MN.

[0122] In the following, the same step numbers are used for processes similar to those in Operation Example 7. Therefore, the differences from Operation Example 7 will be explained primarily. Specifically, step S60X is executed instead of step S62 described above.

[0123] As shown in Figure 13, in step S60X, UE200 derives its mobility pattern. The mobility pattern of UE200 is derived based on VisitedCellInfoList. Based on its mobility pattern, UE200 determines whether or not to perform Selective activation. Here, we will continue the explanation for the case where it is determined that Selective activation should be performed. UE200 sends a message (UE Assistance Information) to MN requesting Selective activation. The UE Assistance Information includes informational elements related to the mobility pattern of UE200.

[0124] In Operation Example 8, the decision of whether or not to perform Selective activation may be made by S-MN based on UE Assistance Information received from UE200.

[0125] In example 8, the specific condition may include a second condition that sends a message requesting selective activation. The specific condition may also be considered to include condition 1 in step S66, which receives an indication that prompts selective activation.

[0126] (5) Example of information element configuration Firstly, we will describe the UE Assistance Information used in steps S10X, S10Y, S40X, and S60X of operation examples 2, 4, 6, and 8. As shown in Figure 14, the UE Assistance Information may include a selectiveActivationrequest. A selectiveActivationrequest is an example of an information element that requests selective activation.

[0127] Secondly, we will describe the CondReconfigToAddModList included in RRC Reconfiguration used in step S16 of operation examples 1 to 6 and step S65 of operation examples 7 to 8. As shown in Figure 15, CondReconfigToAddModList may also include maintainCandidateCellConfig. maintainCandidateCellConfig is an information element that instructs the retention of the target cell's SpCell configuration, and can be considered an example of an information element that instructs Selective activation.

[0128] Thirdly, we will describe the SN Addition request used in step S14 of operation examples 1 to 6. As shown in Figure 16, the SN Addition request may include a Maintain UE config indication. The Maintain UE config indication is an information element that instructs the retention of configuration information such as UE context, UE Config, SCG config, and CPC Config, and can be considered an example of an information element that instructs Selective activation.

[0129] Fourth, we will describe the HO request used in step S63 of operation examples 7-8. As shown in Figure 17, the HO request may include a Maintain UE config indication. The Maintain UE config indication is an information element that instructs the retention of configuration information such as UE context, UE Config, and MCG Config, and can be considered an example of an information element that instructs Selective activation.

[0130] (6) Action and Effects In this embodiment, the UE200 may perform a Selective Activation that retains the configuration information (SpCell configuration) without releasing it after the procedure for conditional reconfiguration is completed, provided certain conditions are met. With this configuration, Selective Activation can be performed appropriately by defining specific conditions.

[0131] In this embodiment, if gNB100 determines that Selective Activation should be performed, it may retain the configuration information (such as the UE context) after the completion of the conditional reconfiguration procedure, even if the UE200 is not connected to its own cell during conditional reconfiguration. With this configuration, Selective Activation can be performed appropriately.

[0132] (7) Other embodiments Although the present invention has been described above in accordance with the embodiments, it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0133] In the disclosure described above, UE200 performs a Selective Activation that retains the SpCell configuration after the conditional reconfiguration procedure is completed, provided certain conditions are met. In the Selective Activation, UE200 may perform a connection to a selected target cell (e.g., an RA procedure to the selected target cell) from among the candidate target cells included in the retained SpCell configuration. The connection to the selected target cell does not require the transmission of a Measurement Report to the network or a trigger from the network. More specifically, UE200 may perform an RA procedure to the selected target cell if the execution condition is met. The execution condition can be considered an example of configuration information received from the network and an example of information elements that are retained in the Selective Activation after the conditional reconfiguration procedure is completed.

[0134] Although not specifically mentioned in the disclosure above, the UE200 may release configuration information (SpCell configuration) in a Selective Activation that retains the configuration information when a release condition is met. The release condition may be a condition in which a certain amount of time has elapsed since receiving an indication from the network (for example, maintainCandidateCellConfig included in RRC Reconfiguration). The certain amount of time may be determined by the expiration of a timer that is activated in response to the receipt of the indication. The release condition may also be a condition in which an explicit or implicit instruction is received from the network.

[0135] Although not specifically mentioned in the disclosure above, gNB100 may release configuration information (such as UE context) when the release condition is met, in cases where it retains configuration information without releasing it. The release condition may be a condition in which a certain amount of time has elapsed since receiving an indication from the source node (for example, a Maintain UE config indication included in an SN Addition request or HO request). The certain amount of time may be determined by the expiration of a timer that is activated in response to the receipt of the indication. Assuming that configuration information is released after a certain amount of time, the certain amount of time used in cases where Selective Activation is applied may be longer than the certain amount of time used in cases where Selective Activation is not applied. The release condition may also be a condition in which an explicit or implicit instruction is received from the source node.

[0136] Here, the release conditions for gNB100 may be as follows. Here, we illustrate with examples of T-SN candidates for CPC. However, the same operation may be performed for T-MN candidates for CHO.

[0137] Firstly, a candidate T-SN may release its UE config if the conditions for canceling all target candidate PSCells (release conditions) are met when it receives a CPAC cancel indication from the MN in an SN modification request. Alternatively, a candidate T-SN may retain its UE config until it receives a CPAC cancel indication.

[0138] Secondly, if a T-SN candidate sends an SN modification required message to the MN and requests CAPC cancellation from the MN when the load of T-SN candidates exceeds a threshold, the UE config may be released if the conditions for canceling all target candidate PSCells (release conditions) are met.

[0139] Thirdly, when an MN sends an SN addition / modification request to a candidate T-SN, it may also send a T_maintainUEconfig to the candidate T-SN at the same time as a maintain UE config indication. The T_maintainUEconfig may include a timer value that defines how long the UE config should be retained. The candidate T-SN may start the timer when it receives the maintain UE config indication (timer value) and release the UE config when the conditions for timer expiration (release conditions) are met. In such cases, in an SN-initiated CPC, the timer value may be set by the SN. For example, the SN may send an SN change required to the MN, and the MN may send the timer value set by the SN to the candidate T-SN.

[0140] Fourth, a candidate for T-SN may already have T_maintainUEconfig. In other words, the timer value may be determined by the candidate for T-SN. The candidate for T-SN may start the timer when it receives a maintain UE config indication, and release the UE config when the conditions for timer expiration (release conditions) are met.

[0141] Fifth, when MN sends RRC Reconfiguration to UE200, it may also send T_maintainCPCconfig to UE200 at the same time as maintainCandidateCellConfig. T_maintainCPCconfig may include a timer value that defines how long the CPC Config should be held. UE200 may start the timer when it receives maintainCandidateCellConfig(timer value) and release the CPC Config when the conditions for timer expiration (release conditions) are met. In such cases, in SN-initiated CPC, the timer value may be set by SN. For example, SN may send SN change required to MN, and MN may send the timer value set by SN to UE200.

[0142] Sixth, UE200 may have a T_maintainCPCconfig pre-configured. In other words, the timer value may be determined by UE200. UE200 may start the timer when it receives maintainCandidateCellConfig, and release the CPC Config when the conditions for timer expiration (release conditions) are met.

[0143] The release conditions described above may include a condition that the UE200's mobility pattern is a specific pattern that disables Selective Activation. For example, in Operation Examples 1 and 5, the MN may send an indication to the UE200 and T-SN candidates to cancel Selective Activation if the UE200's mobility pattern is a specific pattern. In Operation Example 3, the S-SN may send an indication to the MN to cancel Selective Activation if the UE200's mobility pattern is a specific pattern, and the MN may send an indication to the UE200 and T-SN candidates to cancel Selective Activation. In Operation Example 7, the S-MN may send an indication to the UE200 and T-MN candidates to cancel Selective Activation if the UE200's mobility pattern is a specific pattern. In Operation Examples 2, 4, 6, and 8, the UE200 may send an indication to the network to cancel Selective Activation if the UE200's mobility pattern is a specific pattern. Nodes that receive an indication to cancel Selective Activation (UE200, candidate T-SN, candidate T-MN) release their configuration information upon receiving the indication.

[0144] Although not specifically mentioned in the disclosure above, a node may be interpreted as a cell. For example, MN may be interpreted as a cell included in an MCG (e.g., PCell), and SN may be interpreted as a cell included in an SCG (e.g., SCell, PSCell).

[0145] Although not specifically mentioned in the disclosure above, the operation of UE200 may be interpreted as follows: When maintainCandidateCellConfig is set, UE200 retains all entries contained in the variable it holds (VarConditionalReconfig), and otherwise deletes all entries contained in the variable it holds (VarConditionalReconfig). Note that VarConditionalReconfig is the variable that stores the SpCell configuration.

[0146] The block diagrams (Figures 4 and 5) used in the description of the embodiments above show functional units. 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 it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may also be realized by combining the above one device or the above multiple devices with software.

[0147] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In any case, as mentioned above, the method of implementation is not particularly limited.

[0148] Furthermore, the gNB100 and UE200 (the device) described above may function as a computer that processes the wireless communication method of this disclosure. Figure 18 shows an example of the hardware configuration of the device. As shown in Figure 18, the device may be configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, and bus 1007.

[0149] In the following explanation, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the device may include one or more of the devices shown in the diagram, or it may be configured to omit some of the devices.

[0150] Each functional block of the device (see Figure 4) is implemented by any hardware element of the computer device, or a combination of such hardware elements.

[0151] Furthermore, each function in the device is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the memory 1002 and storage 1003.

[0152] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control units, arithmetic units, registers, and so on.

[0153] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. Moreover, the above-mentioned various processes may be executed by one processor 1001, or by two or more processors 1001 simultaneously or sequentially. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from a network via a telecommunications line.

[0154] Memory 1002 is a computer-readable recording medium and may consist of at least one of the following: Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. Memory 1002 may also be called a register, cache, main memory, etc. Memory 1002 can store a program (program code), software modules, etc., that can execute a method according to one embodiment of this disclosure.

[0155] Storage 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disc, a digital multipurpose disc, a Blu-ray® disc), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. Storage 1003 may also be called an auxiliary storage device. The recording medium described above may also be, for example, a database, server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0156] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via at least one of a wired network and a wireless network, and is also called a network device, network controller, network card, communication module, etc.

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

[0158] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

[0159] Furthermore, 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 different buses may be configured for each device.

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

[0161] Furthermore, notification of information is not limited to the embodiments / models described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or combinations thereof. RRC signaling may also be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0162] Each aspect / embodiment described herein may be applied to at least one of the following: 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®, GSM®, CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0163] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0164] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node. 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 can be performed by the base station and at least one other network node (for example, an MME or S-GW, but not limited to these). Although the above example illustrates a case where there is one other network node besides the base station, it may also be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0165] Information and signals (such as data) can be output from a higher layer (or lower layer) to a lower layer (or higher layer). Input and output may occur via multiple network nodes.

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

[0167] The determination may be made by a value represented by 1 bit (0 or 1), by a boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0168] Each aspect / embodiment described herein may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0169] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0170] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or Digital Subscriber Line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

[0171] The information, signals, etc. described in this disclosure may be represented using any of the various 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 voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0172] In addition, terms used in this disclosure and 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 symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

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

[0174] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or corresponding other information. For example, wireless resources may be indicated by an index.

[0175] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, the various names assigned to these various channels and information elements are not restrictive in any way.

[0176] 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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0177] A base station can house one or more (e.g., three) cells (also called sectors). When a base station houses multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0178] The terms "cell" or "sector" refer to a portion or all of the coverage area of ​​at least one of the base stations and base station subsystems that provide communication services in this coverage.

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

[0180] 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 several other appropriate terms.

[0181] 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 mobile body, the mobile body itself, etc. The mobile body may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile 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.

[0182] Furthermore, the term "base station" in this disclosure may be interpreted as "mobile station" (user terminal, hereinafter the same). For example, each aspect / embodiment of this 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 have the functions that a base station has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc. may be interpreted as side channel.

[0183] Similarly, the term "mobile station" in this disclosure may be interpreted as "base station." In this case, the base station may be configured to have the functions that a mobile station has.

[0184] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe.

[0185] A subframe may further consist 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.

[0186] Numerology may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerology may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0187] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols or Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols). A slot may also be a time unit based on neurology.

[0188] A slot may include multiple minislots. Each minislot may consist of one or more symbols in the time domain. Minislots may also be called subslots. Minislots 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.

[0189] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0190] 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 a subframe and a 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 representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0191] Here, TTI refers to, for example, the smallest unit of time for scheduling in wireless communication. For example, in an LTE system, the base station schedules each user terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each user terminal) in TTI units. However, the definition of TTI is not limited to this.

[0192] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block, code block, code word, etc. are mapped may be shorter than the given TTI.

[0193] Furthermore, if one slot or one mini-slot is referred to as TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit of scheduling. In addition, the number of slots (number of mini-slots) that constitute the minimum time unit of scheduling may be controlled.

[0194] A TTI with a time length of 1ms may also be called a normal TTI, long TTI, normal subframe, long subframe, slot, etc. A TTI shorter than a normal TTI may also be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, mini slot, sub slot, slot, etc.

[0195] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0197] Furthermore, the time domain of RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0198] One or more RBs may also be called Physical RBs (PRBs), Sub-Carrier Groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB pairs, etc.

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

[0200] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common resource blocks (RBs) for a given neurology on a given carrier. Here, the common RBs may be identified by an index of the RBs relative to the carrier's common reference point. PRBs may be defined and numbered within a BWP.

[0201] A BWP may include BWPs for UL (UL BWP) and BWPs for DL ​​(DL BWP). One or more BWPs may be configured within a single carrier for a UE.

[0202] At least one of the configured BWPs may be active, and the UE does not need to assume that it will send or receive a given signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0203] The structures described above, such as wireless frames, subframes, slots, minislots, and symbols, are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

[0204] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

[0205] The reference signal can also be abbreviated as Reference Signal (RS), and may be called a pilot depending on the applicable standard.

[0206] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0207] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0208] Any reference to elements using designations such as “First,” “Second,” etc., as 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. Accordingly, references to the First and Second elements do not imply that only two elements may be employed therein, or that the First element must precede the Second element in any way.

[0209] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0210] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0211] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiry (e.g., searching in a table, database, or other data structure), and ascertaining. “Determining” may also include, for example, receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0212] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0213] Figure 19 shows an example of the configuration of vehicle 2001. As shown in Figure 19, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0214] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0215] The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel performed by the user.

[0216] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2027 installed in the vehicle are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0217] Signals from various sensors 2021-2028 include current signals from the current sensor 2021 that senses motor current, front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0218] The Information Services Unit 2012 consists of various devices for providing various types of information, such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Services Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of Vehicle 1.

[0219] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also sends and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

[0220] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via its communication port. For example, the communication module 2013 sends and receives data via its communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028 provided in the vehicle 2001.

[0221] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information to and from external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0222] The communication module 2013 transmits current signals from current sensors input to the electronic control unit 2010 to an external device via wireless communication. The communication module 2013 also transmits, via wireless communication, other signals input to the electronic control unit 2010, including front and rear wheel rotation speed signals obtained by the rotation speed sensor 2022, front and rear wheel air pressure signals obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression signals obtained by the accelerator pedal sensor 2029, brake pedal depression signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, and detection signals obtained by the object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0223] The communication module 2013 receives various information (traffic information, signal information, distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 installed in the vehicle. The communication module 2013 also stores the various information received from external devices in memory 2032, which is available to the microprocessor 2031. Based on the information stored in memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axles 2009, sensors 2021-2028, etc., installed in the vehicle 2001.

[0224] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way. [Explanation of Symbols]

[0225] 10 Wireless communication systems 20 NG-RAN 100 gNB 110 Receiving unit 120 Transmitter 130 Control Unit 200 UE 210 Wireless signal transmission and reception unit 220 Amplifier section 230 Modulation / Demodulation Section 240 Control signal / reference signal processing unit 250 Encoding / Decoding Unit 260 Data transmission / reception unit 270 Control Unit 1001 Processor 1002 memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive Unit 2003 Steering Department 2004 Accelerator pedal 2005 Brake pedal 2006 Shift Lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 Rotation speed sensor 2023 Pneumatic Sensor 2024 Vehicle Speed ​​Sensor 2025 Accelerometer 2026 Brake Pedal Sensor 2027 Shift lever sensor 2028 Object Detection Sensor 2029 Accelerator pedal sensor 2030 Driver Support Systems Department 2031 Microprocessor 2032 memory (ROM, RAM) 2033 Communication Port

Claims

1. A receiving unit that receives a wireless resource control reset message containing configuration information regarding the conditional reset of a secondary node addition or modification, The system comprises a control unit that performs the procedure for conditional resetting, The control unit is a terminal that retains the setting information even after the completion of the procedure for conditional resetting, when the wireless resource control reset message includes setting information for conditional resetting.

2. The terminal according to claim 1, wherein the wireless resource control reset message is received from a master node that sends a secondary node addition or modification message to a secondary node candidate, which includes information indicating the retention of the setting information related to the conditional reset.

3. A transmitting unit that sends a wireless resource control reset message to a terminal containing configuration information regarding the conditional reset of a secondary node addition or modification, The system comprises a control unit that performs the procedure for conditional resetting, The control unit, when including setting information related to the conditional reset in the radio resource control reset message, assumes that the terminal retains the setting information even after the completion of the procedure related to the conditional reset, is a base station.

4. A communication system comprising terminals and base stations, The aforementioned base station is The system includes a transmission unit that sends a wireless resource control reset message to the terminal containing configuration information regarding the conditional reset of a secondary node addition or modification. The aforementioned terminal is A receiving unit that receives the aforementioned wireless resource control reset message from the base station, The system comprises a control unit that performs the procedure for conditional resetting, A wireless communication system in which the control unit retains the setting information even after the completion of the procedure for the conditional reset, if the wireless resource control reset message includes setting information for the conditional reset.

5. The steps include receiving a wireless resource control reset message containing configuration information regarding the conditional reset for the addition or modification of a secondary node, The steps include performing the procedure for the conditional reset, A wireless communication method comprising: if the wireless resource control reset message includes setting information relating to the conditional reset, the step of retaining the setting information even after the completion of the procedure relating to the conditional reset.

Images