terminal

Abstract

To provide a terminal that even when many sub carrier intervals such as 960 kHz are supported in a different frequency band, such as 52.6 to 71 GHz, differing from an FR1 and FR2, can quickly assume a suitable sub carrier interval for specific system information.SOLUTION: A terminal receives a synchronous signal block and specific system information, and assumes that in at least part of a different frequency band area differing from a frequency band including one or more frequency ranges, at least any of candidate values of a sub carrier interval for specific system information linked to a first sub carrier interval for the synchronous signal block and the number of the candidate values differs from at least any of candidate values linked to a second sub carrier interval for the synchronous signal block and the number of the candidate values.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to a terminal that performs wireless communication, and in particular to a terminal that supports wide subcarrier spacing such as 960 kHz. [Background technology]

[0002] The 3rd Generation Partnership Project (3GPP) has developed 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.

[0003] 3GPP Release 15 and Release 16 (NR) specify operation in multiple frequency ranges, specifically bands including FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz).

[0004] Furthermore, in 3GPP Release-17, studies are underway on NR that supports frequencies above 52.6 GHz up to 71 GHz (Non-Patent Document 1). Furthermore, Beyond 5G, 5G Evolution, or 6G (Release-18 and later) aims to support frequency bands above 71 GHz.

[0005] Furthermore, when using such a high frequency band, it is being considered to apply a wide subcarrier spacing (SCS) such as 480 kHz or 960 kHz to a synchronization signal block (SS (Synchronization Signal) / PBCH (Physical Broadcast CHannel) Block) and a specific CORESET (control resource set), specifically, CORESET 0 (Non-Patent Document 2). [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] "New WID on Extending current NR operation to 71 GHz", RP-193229, 3GPP TSG RAN Meeting #86, 3GPP, December 2019 [Non-patent document 2] "Revised WID: Extending current NR operation to 71 GHz", RP-202925, 3GPP TSG RAN Meeting #90-e, 3GPP, December 2020 Summary of the Invention

[0007] When many SCSs are used in the high frequency band as described above, it is difficult for a terminal (User Equipment, UE) to quickly assume an SCS for specific system information such as RMSI (Remaining Minimum System Information) from an SCS for SSB. There is also a problem that it is difficult for a terminal to quickly assume an opportunity (for example, whether or not only initial access is used) when many SCSs are used as described above.

[0008] Therefore, the following disclosure has been made in consideration of this situation, and aims to provide a terminal that can quickly assume an appropriate subcarrier spacing for specific system information, even when many subcarrier spacings, such as 960 kHz, are supported in different frequency bands different from FR1 and FR2, such as 52.6 to 71 GHz.

[0009] One aspect of the present disclosure is a terminal (UE200) comprising a receiving unit (radio signal transceiver unit 210) that receives a synchronization signal block and specific system information, and a control unit (control unit 270) that assumes that, in at least a portion of a different frequency band area that is different from a frequency band including one or more frequency ranges, at least one of a candidate value and the number of candidate values for a subcarrier spacing for the specific system information that is associated with a first subcarrier spacing for the synchronization signal block is different from at least one of a candidate value and the number of candidate values that is associated with a second subcarrier spacing for the synchronization signal block.

[0010] One aspect of the present disclosure is a terminal (UE200) comprising: a receiving unit (radio signal transmitting / receiving unit 210) that receives a synchronization signal block and specific system information; and a control unit (control unit 270) that, in at least a portion of a different frequency band that is different from a frequency band including one or more frequency ranges, assumes only a specific subcarrier spacing as a common setting for the synchronization signal block and the specific system information during initial access, and assumes multiple subcarrier spacings including the specific subcarrier spacing as a common setting for the synchronization signal block and the specific system information during periods other than the initial access.

[0011] One aspect of the present disclosure is a terminal (UE200) having a receiving unit (radio signal transmitting / receiving unit 210) that receives a synchronization signal block, and a control unit (control unit 270) that assumes that a specific pseudo-colocation value is applied to the synchronization signal block in at least a portion of a different frequency band that is different from a frequency band that includes one or more frequency ranges.

[0012] One aspect of the present disclosure is a terminal (UE200) comprising a receiving unit (radio signal transceiver unit 210) that receives a synchronization signal block, and a control unit (control unit 270) that assumes pseudo-colocation of the synchronization signal block based on a method of notifying pseudo-colocation in shared spectrum channel access for the synchronization signal block in at least a portion of a different frequency band that is different from a frequency band including one or more frequency ranges.

[0013] One aspect of the present disclosure is a terminal (UE200) comprising a receiving unit (radio signal transceiver unit 210) that receives a synchronization signal block, and a control unit (control unit 270) that assumes pseudo-colocation of the synchronization signal block based on a notification method that is different from the notification method of pseudo-colocation in shared spectrum channel access, for at least a portion of a different frequency band that is different from a frequency band including one or more frequency ranges. [Brief explanation of the drawings]

[0014] [Figure 1] FIG. 1 is a diagram showing the overall schematic configuration of a wireless communication system 10. As shown in FIG. [Figure 2] FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. As shown in FIG. [Figure 3] 3 shows an example of the configuration of a radio frame, a subframe, and a slot used in the radio communication system 10. Table 1 shows the relationship between the SCS and the symbol period. [Figure 4] Figure 4 is a functional block diagram of gNB100 and UE200. [Figure 5] FIG. 5 is a diagram showing a schematic communication sequence relating to setting of the SCS for SSB and the SCS for RMSI (SIB1). [Figure 6] FIG. 6 is a diagram showing an example of linking an SSB SCS and an RMSI SCS according to operation example 1-1. [Figure 7] FIG. 7 is a diagram showing an example of a method for estimating N_SSB^QCL according to Operation Example 1-2. [Figure 8] FIG. 8 is a diagram showing an example of linking an SSB SCS and an RMSI SCS according to operation example 2-1. [Figure 9] FIG. 9 is a diagram showing an example of a method for estimating N_SSB^QCL according to the operation example 2-2. [Figure 10] FIG. 10 is a diagram showing an example of the hardware configuration of gNB100 and UE200. DETAILED DESCRIPTION OF THE INVENTION

[0015] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0016] (1) Overall configuration of the wireless communication system 1 is a schematic diagram of the overall configuration of a wireless communication system 10 according to this embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter referred to as NG-RAN 20) and a terminal 200 (hereinafter referred to as UE 200, User Equipment, UE). Note that the wireless communication system 10 may also be a wireless communication system conforming to a scheme called Beyond 5G, 5G Evolution, or 6G.

[0017] The NG-RAN 20 includes a radio base station 100 (hereinafter, gNB 100). Note that the specific configuration of the radio communication system 10, including the number of gNBs and UEs, is not limited to the example shown in FIG.

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

[0019] The gNB 100 is a 5G-compliant radio base station that performs 5G-compliant radio communication with the UE 200. The gNB 100 and the UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional antenna beam (hereinafter referred to as beam BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates and uses multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates between the UE and two NG-RAN nodes.

[0020] The gNB 100 can transmit multiple beams BM with different transmission directions (which may also be simply referred to as directions, or radiation directions, or coverages) in a space- and time-division manner. Note that the gNB 100 may transmit multiple beams BM simultaneously.

[0021] The wireless communication system 10 may also support a plurality of frequency ranges (FR).

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

[0023] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0024] Furthermore, the wireless communication system 10 also supports a frequency band higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports a frequency band exceeding 52.6 GHz up to 71 GHz. Such a high frequency band may be referred to as "FR2x" for convenience. The high frequency band may also be referred to as a different frequency band that is different from a frequency band including one or more frequency ranges (FR), and the different frequency band may include a frequency band above 71 GHz and / or a frequency band between FR1 and FR2.

[0025] When using a high frequency band such as FR2x, 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] Furthermore, in high frequency bands such as FR2x, as mentioned above, increased phase noise between carriers becomes an issue, which may necessitate the application of a larger (wider) SCS or a single carrier waveform.

[0027] The larger the SCS, the shorter the symbol / CP (Cyclic Prefix) period and slot period (assuming a 14 symbol / slot configuration is maintained). Figure 3 shows an example of the configuration of a radio frame, subframe, and slot used in the wireless communication system 10. Table 1 also shows the relationship between the SCS and the symbol period.

[0028] [Table 1]

[0029] As shown in Table 1, if the 14 symbol / slot configuration is maintained, the larger (wider) the SCS, the shorter the symbol period (and slot period).

[0030] 3 may be called a time domain, a time region, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a resource block group, a subcarrier, a BWP (Bandwidth part), a subchannel, a common frequency resource, etc.

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

[0032] Furthermore, the wireless communication system 10 may use an SSB (SS / PBCH Block) that is configured from a synchronization signal (SS) and a downlink physical broadcast channel (PBCH).

[0033] SSBs are mainly transmitted periodically from the network to allow UE 200 to detect cell IDs and reception timings when starting communication. In NR, SSBs are also used to measure the reception quality of each cell. The SSB transmission periodicity may be specified as 5, 10, 20, 40, 80, 160 milliseconds, etc. Note that the initial access UE 200 may assume a transmission period of 20 milliseconds.

[0034] The network (NG-RAN 20) can notify the UE 200 of the index indication (ssb-PositionsInBurst) of the actually transmitted SSBs by system information (SIB1) or signaling of the radio resource control layer (RRC).

[0035] The SS is composed of a primary synchronization signal (PSS: Primary SS) and a secondary synchronization signal (SSS: Secondary SS).

[0036] The PSS is a known signal that the UE 200 first attempts to detect in the cell search procedure, and the SSS is a known signal that is transmitted to detect a physical cell ID in the cell search procedure.

[0037] The PBCH includes information necessary for UE200 to establish frame synchronization with the NR cell formed by gNB100 after detecting the SS / PBCH block, such as the radio frame number (SFN: System Frame Number) and an index for identifying the symbol positions of multiple SS / PBCH blocks within a half frame (5 milliseconds).

[0038] The PBCH may also include system parameters required for receiving system information (SIB, which may include a Master Information Block (MIB)). Furthermore, the SSB also includes a broadcast channel demodulation reference signal (DMRS for PBCH). The DMRS for PBCH is a known signal transmitted to measure the wireless channel condition for PBCH demodulation.

[0039] Downlink (DL) radio resources used for transmitting a PDCCH (Physical Downlink Control Channel) can be specified by a control resource set (CORESET). That is, a CORESET may be interpreted as a set of physical resources (specifically, a specific region on a DL resource grid) and parameters used to transmit a PDCCH (which may include downlink control information (DCI)).

[0040] The UE 200 can assume the particular region to which the CORESET is assigned based on the timing and periodicity indicated by the Common Search Space (CSS).

[0041] Additionally, the CORESET may include the following parameters:

[0042] Resource Element (RE): The smallest unit of the resource grid, consisting of one subcarrier in the frequency domain and one OFDM symbol in the time domain. Resource Element Group (REG): Consists of one resource block (12 resource elements in the frequency domain) and one OFDM symbol in the time domain. REG bundle: Consists of multiple REGs. The bundle size can be specified by the parameter 'L', and L can be determined by the Radio Resource Control layer (RRC) parameter (reg-bundle-size).

[0043] Control Channel Element (CCE): Consists of multiple REGs. The number of REG bundles included in a CCE may be variable.

[0044] Aggregation Level (AL): Indicates the number of CCEs allocated to the PDCCH. 3GPP Release-15 and 16 specify 1, 2, 4, 8, and 16, but the wireless communication system 10 may use even larger values.

[0045] If UE 200 determines that a CORESET for Type 0-PDCCH CSS exists based on the received Master Information Block (MIB), UE 200 determines several consecutive resource blocks (RBs) and symbols for the CORESET (which may be referred to as CORESET 0 or Remaining Minimum System Information (RMSI) CORESET). Based on the determined RBs and symbols, UE 200 sets a monitoring occasion (MO) of the PDCCH, specifically, the Type 0 PDCCH for decoding the system information block (SIB).

[0046] CORESET 0 is a special CORESET that is different from a normal CORESET. Such a specific CORESET may be interpreted as a CORESET that transmits a PDCCH for SIB1 scheduling. CORESET 0 cannot be specified by RRC because it is used before RRC signaling is transmitted.

[0047] RMSI may be interpreted as meaning System Information Block 1 (SIB1). RMSI may consist of system information that a device (UE 200) needs to know before accessing the system. SIB1 may be broadcast periodically throughout the cell at all times. SIB1 may provide information that UE 200 needs to perform an initial random access (RA).

[0048] SIB1 is provided by a regular scheduled Physical Downlink Shared Channel (PDSCH) transmission with a periodicity of 160 ms. The PBCH / MIB may provide information about the numerology used for SIB1 transmission and the search space and corresponding CORESET used for scheduling SIB1. Within this CORESET, UE 200 may monitor the scheduling of SIB1, indicated by a special System Information RNTI (SI-RNTI).

[0049] (2) Functional block configuration of wireless communication system Next, a description will be given of the functional block configuration of the wireless communication system 10. Specifically, the functional block configurations of the gNB 100 and the UE 200 will be described.

[0050] 4 is a functional block diagram of the gNB 100 and the UE 200. The UE 200 will be described below.

[0051] As shown in FIG. 4, 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.

[0052] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0053] In addition, in this embodiment, the radio signal transceiver 210 can receive a synchronization signal block (SSB) and / or system information.

[0054] Specifically, the radio signal transmitting / receiving unit 210 receives an SSB transmitted using a beam BM (see FIG. 1) from the gNB 100. Note that the beam BM may be a directional beam or an omnidirectional beam.

[0055] The maximum number of beams used for SSB transmission is, for example, 64 (in the case of 3GPP Release 15 (FR2)). However, the maximum number of beams may be extended to cover a certain geographical area with narrow beams. In this case, the number of SSBs may also be 64 or more, and the index identifying the SSB (SSB index) may also be a value greater than or equal to 64.

[0056] The system information may include a MIB and a plurality of SIBs including RMSI (SIB1). In particular, in this embodiment, RMSI (SIB1) may be referred to as specific system information.

[0057] In this embodiment, the wireless signal transceiver 210 may constitute a receiver that receives a synchronization signal block and / or specific system information.

[0058] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0059] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (e.g., gNB 100). 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 uplink (UL) but also for downlink (DL).

[0060] The control signal / reference signal processor 240 performs processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0061] Specifically, the control signal / reference signal processor 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. The control signal / reference signal processor 240 also transmits various control signals to the gNB 100 via a predetermined control channel.

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

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

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

[0065] The channels include a control channel and a data channel. The control channels may include a PDCCH, a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel, DCI including a Random Access Radio Network Temporary Identifier (RA-RNTI)), a Physical Broadcast Channel (PBCH), etc.

[0066] Furthermore, the data channel includes a PDSCH, a PUSCH (Physical Uplink Shared Channel), etc. Data may refer to data transmitted via a data channel. Note that data may refer to user data, and control may refer to various control signals transmitted via a control channel.

[0067] The PUCCH may be interpreted as an UL physical channel used to transmit UCI (Uplink Control Information). The UCI can be transmitted via either the PUCCH or the PUSCH depending on the situation. Note that the DCI may always be transmitted via the PDCCH and does not necessarily have to be transmitted via the PDSCH.

[0068] The UCI may include at least one of an ACK / NACK of a Hybrid Automatic Repeat Request (HARQ), a Scheduling Request (SR) from the UE 200, and Channel State Information (CSI).

[0069] In addition, the timing and radio resources for transmitting the PUCCH may be controlled by DCI in the same way as the data channel.

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

[0071] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0072] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (Hybrid ARQ).

[0073] The control unit 270 controls each functional block constituting the UE 200. In particular, in this embodiment, the control unit 270 executes control related to setting of the subcarrier spacing (SCS) for the synchronization signal block (SSB) and the SCS for the system information.

[0074] Specifically, the control unit 270 can execute control related to the setting of the SCS in a different frequency band different from the frequency band including FR1 and FR2, for example, FR2x (see FIG. 2). More specifically, the control unit 270 may assume the following regarding the setting of the SCS in at least a part of FR2x (which may include a higher frequency band as described above, the same applies below).

[0075] It is assumed that at least one of the candidate values and the number of candidate values of the SCS for RMSI (specific system information) associated with a specific SCS for SSB (called the first subcarrier spacing, for example, 120 kHz) is different from at least one of the candidate values and the number of candidate values of the SCS for RMSI (specific system information) associated with another SCS for SSB (called the second subcarrier spacing, for example, 240 kHz).

[0076] In other words, a specific SCS for SSB may differ from another SCS for SSB in at least one of the candidate values or the number of candidate values for the SCS for RMSI associated with the SCS.

[0077] The candidate SCS value may be any of the SCS values shown in Table 1, but may be substantially limited to 120 kHz or higher when considering the use of a high frequency band such as FR2x. The number of candidate values may be one or more.

[0078] The SCS for SSB may refer to the SCS applied to SSB transmission, and similarly, the SCS for RMSI may refer to the SCS applied to RMSI transmission. RMSI may refer to SIB1 as described above, but here, RMSI may be interpreted as CORESET 0 (RMSI CORESET). Furthermore, the term "associated" in the SCS for RMSI associated with the SCS for SSB may mean that the SCS for RMSI can be assumed once the SCS for SSB is determined, and may be replaced with terms such as "associated" or "related."

[0079] There may be multiple SCSs for RMSI associated with the SCS for SSB. In this case, an RRC information element, for example, subCarrierSpacingCommon, may be used to notify multiple SCSs for RMSI. This information element (subCarrierSpacingCommon) may be included in the MIB.

[0080] Furthermore, the control unit 270 may assume the following regarding the SCS settings in at least a part of the FR2x.

[0081] During initial access, only a specific SCS (e.g., 120 kHz) is assumed to be common for SSB and RMSI.

[0082] - Except for initial access, multiple SCSs, including a specific SCS, are assumed to be common for SSB and RMSI.

[0083] Initial access may refer to a series of processes performed between UE200 and gNB100, etc., in order for UE200 to acquire uplink (UL) synchronization and obtain an ID designated for radio access communication.

[0084] More generally, initial access may be referred to as a RACH process, or initial access may refer to downlink (DL) synchronization and RACH.

[0085] Common for SSB and RMSI may mean that the same SCS applies to SSB and RMSI, and SCS that are not supported by RMSI may be excluded.

[0086] Note that, when any of the above-mentioned assumptions regarding the SCS for RMSI is applied, the SCS assumed at the time of initial access may be limited to a specific SCS (e.g., 120 kHz). Also, in cases other than initial access, it may be assumed that the gNB 100 sets any one of the above-mentioned specific SCSs and / or SCSs other than the specific SCS as the SCS for SSB.

[0087] Furthermore, the control unit 270 may assume that a specific Quasi-Colocation (QCL) value is applied to SSB in at least a portion of FR2x.

[0088] Specifically, the control unit 270 may always assume a specific value (for example, 64) for the QCL parameter for SSB (N_SSB^QCL) in the frequency band.

[0089] QCL means that two antenna ports are pseudo-co-located if, for example, the characteristics of the channel through which symbols on one antenna port are carried can be inferred from the channel through which symbols on the other antenna port are carried.

[0090] When the SSBs are different, specifically, SSBs with different SSB indices (which may be interpreted as beams BM used for SSB transmission) may be interpreted as having different QCL assumptions.

[0091] In other words, it can be interpreted that SSBs with the same SSB index are assumed to be QCLs, and other SSBs (i.e., different SSB indexes) should not be assumed to be QCLs. Note that QCLs may also be called quasi-collocated. Also, QCL / TCI (Transmission Configuration Indication) state / beam may be interpreted interchangeably.

[0092] Additionally, the control unit 270 may assume a specific value (eg, 64) for N_SSB̂QCL until notified by system information (SIB1) or higher layer parameters of RRC (eg, parameters such as ssb-PositionQCL).

[0093] Alternatively, in at least a portion of FR2x, the control unit 270 may assume the QCL of the SSB based on a QCL notification method for shared spectrum channel access (SCA) for the SSB. Shared channel access may be interpreted as shared channel access in FR1, or as a type of Licensed-Assisted Access (LAA) that expands the available frequency band using unlicensed spectrum. Such shared channel access may be referred to as New Radio-Unlicensed (NR-U).

[0094] Specifically, the control unit 270 may estimate the QCL of the SSB based on a combination of subCarrierSpacingCommon and the LSB of ssb-SubcarrierOffset.

[0095] Alternatively, in at least a part of FR2x, the control unit 270 may assume the QCL of the SSB based on a notification method that is different from the QCL notification method in shared channel access for the SSB.

[0096] For example, control unit 270 may estimate the QCL of the SSB based on information notified using at least one of a part of the system frame number, a higher-level parameter (pdcch-ConfigSIB1) related to the PDCCH configuration, and spare bits.

[0097] The pdcch-ConfigSIB1 is included in the MIB and is used to determine the CORESET, common search space, and required PDCCH parameters.

[0098] (3) Operation of the wireless communication system Next, a description will be given of the operation of the wireless communication system 10. Specifically, a description will be given of an example of operation relating to setting an SCS for SSB and an SCS for RMSI (SIB1).

[0099] (3.1) Premise In 3GPP Release 15, 120 kHz and 240 kHz are specified as candidates for SSB SCS in the case of FR2, and both possibilities may be considered at the time of initial access.

[0100] On the other hand, 60 kHz and 120 kHz are specified as candidates for the RMSI SCS, and all of the following combinations of SSB and RMSI SCS may be supported: {120, 60}, {120, 120}, {240, 60}, and {240, 120}.

[0101] In the RMSISCS, 60 kHz or 120 kHz is specified by one bit of subCarrierSpacingCommon included in the MIB. In addition, the candidate values for the subcarrier offset between the SSB RB and the Common PRB (Physical Resource Block) are 0 to 11, and are notified using four bits of ssb-SubcarrierOffset in the MIB.

[0102] In addition, in NR-U (shared channel access) of 3GPP Release 16, candidates for SSB SCS are 15 kHz or 30 kHz, and 30 kHz may be assumed at the time of initial access.

[0103] As candidates for RMSI SCS, 15 kHz and 30 kHz are specified, and only {15, 15} and {30, 30} are supported as SCS combinations for SSB and RMSI.

[0104] In this case, one bit of subCarrierSpacingCommon is used together with the LSB (least significant bit) of ssb-SubcarrierOffset to signal N_SSB^QCL (i.e., for a purpose other than that specified for Rel-15 / licensed carriers). In addition, the candidate values for the subcarrier offset between the SSB RB and the Common PRB are 0 to 22 (even numbers only), and are signaled using four bits of ssb-SubcarrierOffset in the MIB.

[0105] (3.2) Operation overview 5 shows a schematic communication sequence for setting the SCS for SSB and the SCS for RMSI (SIB1). Note that the following operation may be applied when using a high frequency band such as FR2x (or an even higher frequency band).

[0106] As shown in Fig. 5, the network (NG-RAN 20) transmits an SSB to the UE 200 (step 1). The SSB (PBCH) may include an MIB.

[0107] Based on the received SSB, the UE 200 can detect the SCS applied to the SSB (SSB SCS) (step 2).

[0108] Based on the detected SSB SCS, the UE 200 may determine the SCS to be applied to the RMSI (RMSI SCS) (step 3).

[0109] Specifically, the UE 200 may determine, based on the value of the SSB SCS, the value of the RMSI SCS associated with the value of the SSB SCS.

[0110] UE 200 may set CORESET based on the determined RMSI SCS and receive (detect) the PDCCH (step 4).

[0111] (3.3) Example 1 In this operation example, in at least a portion of FR2x (or even higher frequency bands), assumptions regarding the candidate values and / or number of candidate values for the SCS of the RMSI associated with an SSB using a specific SCS are changed from those for an SSB using a different SCS.

[0112] (3.3.1) Example 1-1 UE200 may assume that at least one of the candidate values and the number of candidate values of the SCS for RMSI (specific system information) associated with a specific SCS for SSB (called the first subcarrier spacing, for example, 120 kHz) is different from at least one of the candidate values and the number of candidate values of the SCS for RMSI (specific system information) associated with another SCS for SSB (called the second subcarrier spacing, for example, 480 kHz).

[0113] 6 shows an example of linking SSB SCS and RMSI SCS according to operation example 1-1. As shown in FIG. 6, in the case of FR2x, at least either the candidate value of RMSI SCS or the number of candidate values may differ depending on the SSB SCS.

[0114] Specifically, if SSB SCS=120 kHz, only RMSI SCS=120 kHz may be assumed, and if SSB SCS=240 kHz, only RMSI SCS=120 kHz may be assumed.

[0115] If SSB SCS=480 kHz, RMSI SCS=120 kHz or 480 kHz may be assumed, and if SSB SCS=960 kHz, RMSI SCS=120 kHz or 960 kHz may be assumed.

[0116] When multiple (two) candidate SCS values are specified as RMSISCS, which SCS is applied may be notified using one bit of subCarrierSpacingCommon.

[0117] The RMSI SCS associated with the SSB SCS may not be particularly limited, but the RMSI SCS may be the same as or smaller than the SSB SCS. Also, the minimum value of the RMSI SCS may be limited to 120 kHz, as shown in the example of FIG. 6.

[0118] The number of candidate RMSI SCS values associated with each SSB SCS may be limited to two, which can be signaled with one bit, and one of the candidate values may be the same SCS as the SSB SCS, and the other of the candidate values may be the SCS assumed at the time of initial access.

[0119] The SCS assumed during initial access may be limited to a specific SCS (e.g., 120 kHz). On the other hand, in cases other than initial access (e.g., when neighboring cell measurement is configured, or when CGI (Cell Global Identifier) measurement / reporting is configured for ANR (Automatic Neighbor Relation) in addition to neighboring cell measurement), it may be assumed that an SSB SCS other than the specific SCS described above is configured to be measured (e.g., 120 kHz, 480 kHz, or 960 kHz).

[0120] According to this example of operation, the SSB SCS and RMSI SCS can be aligned to the same SCS, or the UE load can be reduced by assuming only the 120 kHz SSB SCS for initial access, while other UEs that are not initial accessing can use the 480 kHz or 960 kHz SSB SCS while assuming the SCS for initial access as the RMSI.

[0121] (3.3.2) Example 1-2 As in the above-mentioned operational example 1-1, in at least a part of FR2x, if the assumptions regarding the candidate values and / or number of candidate values of the SCS of the RMSI associated with an SSB are different between an SSB using a specific SCS and an SSB using another SCS, UE200 may assume the QCL parameters for the SSB, specifically, N_SSB^QCL, as follows:

[0122] 7 shows an example of a method for assuming N_SSB^QCL according to operation example 1-2. As shown in FIG. 7, when UE 200 uses FR2x and assumes a change in the association between a specific SSB SCS and an RMSI SCS, UE 200 may assume N_SSB^QCL according to any of the options.

[0123] (Option 1): The MIB signaling method for N_SSB^QCL (subCarrierSpacingCommon + LSB of ssb-SubcarrierOffset) assumed for FR1 operation with shared channel access is not assumed for this frequency band. A specific value (e.g., 64) may be assumed for N_SSB^QCL until a higher layer parameter such as ssb-PositionQCL (tentative name) is signaled by SIB1 or RRC.

[0124] (Option 2): A different MIB notification method for N_SSB^QCL is assumed for FR1 operation with shared channel access (subCarrierSpacingCommon + ssb-SubcarrierOffset LSB).

[0125] The different notification methods may include at least one of the following:

[0126] Part of systemFrameNumber (SFN) In this case, the SFNs in which SSBs can be allocated may be limited to a certain number (for example, only even-numbered SFNs). Part of pdcch-ConfigSIB1 Spare bits As described above, pdcch-ConfigSIB1 is included in the MIB and may be used to determine the CORESET, common search space, and required PDCCH parameters.

[0127] (Option 3): In that frequency band, a specific value (e.g., 64) is always assumed for N_SSB^QCL.

[0128] In this case, assumptions for N_SSB^QCL other than that particular value can be abandoned.

[0129] Note that, although the operation example 1-2 is premised on the operation example 1-1, only the operation example 1-2 may be applied regardless of whether the operation example 1-1 is applied or not.

[0130] (3.4) Example 2 In this operation example, in at least a part of FR2x (or even higher frequency bands), only a specific SCS is assumed to be common to SSB and RMSI during initial access, and multiple SCSs including the specific SCS are assumed to be common to SSB and RMSI during non-initial access.

[0131] (3.4.1) Example 2-1 The UE 200 may assume only a specific SCS as a common SSB and RMSI during initial access, whereas the UE 200 may assume multiple candidate SCSs, including the specific SCS, as common SSB and RMSI during cases other than initial access.

[0132] Fig. 8 shows an example of linking an SSB SCS and an RMSI SCS according to operation example 2-1. As shown in Fig. 8, in initial access, only a specific SCS may be assumed to be common to the SSB and RMSI.

[0133] Specifically, if SSB SCS=120 kHz, only RMSI SCS=120 kHz may be assumed, and SSB SCS=240 kHz may be assumed not to be supported in at least a part of FR2x (or even higher frequency bands).

[0134] If SSB SCS=480 kHz, RMSI SCS=480 kHz may be assumed, and if SSB SCS=960 kHz, RMSI SCS=960 kHz may be assumed. In this case, one bit of subCarrierSpacingCommon in the MIB may be used for a purpose other than reporting RMSI SCS.

[0135] Also, similar to Operation Example 1-1, the SCS assumed at the time of initial access may be limited to a specific SCS (for example, 120 kHz). On the other hand, in cases other than the initial access (for example, when neighboring cell measurement is configured, or when CGI measurement / reporting is configured for ANR in addition to neighboring cell measurement), it may be assumed that an SSB SCS other than the above-mentioned specific SCS is configured to be measured (for example, 120 kHz, 480 kHz, or 960 kHz).

[0136] According to this operation example, by aligning the SCS of SSB and RMSI to the same SCS, the subCarrierSpacingCommon in the MIB can be used for other purposes. Also, for initial access, the 120 kHz SCS can be set to assume only SSB, reducing the load on the UE.

[0137] (3.4.2) Example 2-2 As in the above-described operation example 2-1, when only a specific SCS is assumed to be common to SSB and RMSI during initial access, UE200 may assume the QCL parameters for SSB, specifically, N_SSB^QCL, as follows:

[0138] 9 shows an example of a method for assuming N_SSB^QCL according to operation example 2-2. As shown in FIG. 9, when UE 200 uses FR2x and assumes a common SCS for SSB and RMSI in initial access, UE 200 may assume N_SSB^QCL according to any of the options.

[0139] (Option 1): The same method as the N_SSB^QCL MIB notification method (subCarrierSpacingCommon + ssb-SubcarrierOffset LSB) assumed for FR1 operation with shared channel access is assumed for the frequency band.

[0140] (Option 2): Assume a different MIB notification method for N_SSB^QCL than the one assumed for FR1 operation with shared channel access (subCarrierSpacingCommon + LSB of ssb-SubcarrierOffset).

[0141] The different notification methods may include at least one of the following:

[0142] Part of systemFrameNumber (SFN) In this case, the SFNs in which SSBs can be allocated may be limited to a certain number (for example, only even-numbered SFNs). Part of pdcch-ConfigSIB1 Spare bits (Option 3): In that frequency band, a specific value (e.g., 64) is always assumed for N_SSB^QCL.

[0143] In this case, subCarrierSpacingCommon may be used for purposes other than notifying N_SSB^QCL.

[0144] Note that, although the operation example 2-2 is premised on the operation example 1-1, regardless of whether the operation example 2-1 is applied or not, only the operation example 2-2 may be applied.

[0145] (4) Actions and Effects According to the UE 200 according to the above-described exemplary operation, even when many SCSs, such as 960 kHz, are supported in a different frequency band, such as 52.6 to 71 GHz (FR2x), which is different from FR1 and FR2, an appropriate SCS for RMSI can be quickly determined from the SCS for SSB. This reduces the load on the UE 200, and allows flexible setting of the RMSI SCS based on the SSB SCS.

[0146] (5) Other embodiments Although the embodiments have been described above, it will be obvious to those skilled in the art that the present invention is not limited to the description of the embodiments and that various modifications and improvements are possible.

[0147] For example, in the above-described embodiment, an example in which multiple SCSs are used in FR2x has been described, but the above-described operational example may also be applied when multiple SCSs are used in a frequency band other than FR2x, for example, a frequency band higher than FR2x or a frequency band lower than FR2x. Also, some SCSs may not necessarily be used.

[0148] Also, in the above description, "configure," "activate," "update," "indicate," "enable," "specify," and "select" may be interchangeable. Similarly, "link," "associate," "correspond," and "map" may be interchangeable, and "allocate," "assign," "monitor," and "map" may also be interchangeable.

[0149] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0150] In the present disclosure, terms such as "precoding," "precoder," "weight (precoding weight)," "Quasi-Co-Location (QCL)," "Transmission Configuration Indication state (TCI state)," "spatial relation," "spatial domain filter," "transmit power," "phase rotation," "antenna port," "antenna port group," "layer," "number of layers," "rank," "resource," "resource set," "resource group," "beam," "beam width," "beam angle," "antenna," "antenna element," "panel," etc. may be used interchangeably.

[0151] Furthermore, the block diagram (FIG. 4) used in the description of the above-described 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 a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional block may also be realized by combining the single device or the multiple devices with software.

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

[0153] Furthermore, the gNB100 and UE200 described above may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 10 is a diagram showing an example of the hardware configuration of the gNB100 and UE200. As shown in Fig. 10, the gNB100 and UE200 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, a bus 1007, etc.

[0154] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the gNB100 and the UE200 may be configured to include one or more of the apparatuses shown in the figures, or may be configured to exclude some of the apparatuses.

[0155] Each functional block of gNB100 and UE200 (see Figure 4) is realized by any hardware element of the computer device or a combination of such hardware elements.

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

[0157] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, a register, and the like.

[0158] The processor 1001 also reads 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 in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-mentioned embodiments. Furthermore, the various processes described above 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.

[0159] The memory 1002 is a computer-readable recording medium and may be configured by, for example, at least one of 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 also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 can store a program (program code), a software module, etc., that can execute a method according to an embodiment of the present disclosure.

[0160] 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate medium including at least one of memory 1002 and storage 1003.

[0161] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0162] 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).

[0163] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0164] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to 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.

[0165] 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.

[0166] Furthermore, 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 thereof. Furthermore, 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, or the like.

[0167] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 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), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

[0168] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. 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.

[0169] In the present disclosure, a specific operation described as being performed by a base station may also 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 another network node other than the base station (for example, an MME or an 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, a combination of multiple other network nodes (for example, an MME and an S-GW) may also be used.

[0170] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0171] The input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added to. The output information may be deleted. The input information may be sent to another device.

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

[0173] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

[0174] 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.

[0175] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if 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), then these wired and / or wireless technologies are included within the definition of transmission media.

[0176] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, 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.

[0177] Note that terms explained 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

[0179] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0180] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions 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 intended to be limiting in any way.

[0181] In this disclosure, terms such as "base station (BS)," "radio 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.

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

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

[0184] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0185] 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.

[0186] 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 object, or the mobile object itself. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (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 also include devices that do not necessarily move during communication operations. 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.

[0187] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "side"). For example, terms such as uplink channel and downlink channel may be read as side channel.

[0188] 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.

[0189] Numerology may be a communication parameter applied to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by a transceiver in the frequency domain, and specific windowing operations performed by a transceiver in the time domain.

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

[0191] A slot may include multiple minislots. Each minislot may consist of one or more 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.

[0192] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

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

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

[0195] The TTI may be a transmission time unit for a channel-encoded 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) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0196] 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 for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

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

[0198] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0199] 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 numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0200] 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. Each TTI, subframe, etc. may be composed of one or more resource blocks.

[0201] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

[0202] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0203] A Bandwidth Part (BWP) (which may also be referred to as a fractional 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 their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0204] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0205] 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."

[0206] The above-described structures of the radio frame, subframe, slot, minislot, and symbol 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, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, and other configurations can be changed in various ways.

[0207] The terms "connected," "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 one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

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

[0209] 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."

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

[0211] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing 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.

[0212] When used in this disclosure, the terms "include," "including," and variations thereof are intended to be inclusive, similar to the term "comprising." Furthermore, when used in this disclosure, the term "or" is not intended to be an exclusive or.

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

[0214] 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. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0215] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0216] 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. [Explanation of symbols]

[0217] 10. Wireless communication systems 20 NG-RAN 100 gNB 200 UE 210 Radio signal transmitter / receiver 220 Amplifier section 230 Modulation and Demodulation Unit 240 Control signal / reference signal processing section 250 Encoding / Decoding Unit 260 Data transmission and reception unit 270 Control Unit 1001 processor 1002 memory 1003 Storage 1004 Communication equipment 1005 Input Device 1006 Output Device 1007 Bus

Claims

1. a receiving unit for receiving a synchronization signal block; a control unit that assumes quasi-co-location of the synchronization signal blocks in shared spectrum channel access of a second frequency band different from the first frequency band based on a notification method different from a notification method of quasi-co-location of the synchronization signal blocks in shared spectrum channel access of a first frequency band; A terminal comprising:

2. receiving a synchronization signal block; assuming quasi-co-location of the synchronization signal block in the shared spectrum channel access of a second frequency band different from the first frequency band based on a notification method different from a notification method of quasi-co-location of the synchronization signal block in the shared spectrum channel access of a first frequency band; A communication method for a terminal including:

3. a transmitter for transmitting the synchronization signal block to a terminal; a control unit configured to notify the terminal of quasi-co-location in the synchronization signal block in shared spectrum channel access; The control unit notifies the quasi-colocation of the synchronization signal block in the shared spectrum channel access of a second frequency band different from the first frequency band by a notification method different from a notification method of the quasi-colocation of the first frequency band. Base station.

4. The base station is a transmitter for transmitting the synchronization signal block to a terminal; a control unit configured to notify the terminal of quasi-co-location in the synchronization signal block in shared spectrum channel access; the controller notifies the quasi-co-location of the synchronization signal blocks in the shared spectrum channel access of a second frequency band different from the first frequency band by a notification method different from a notification method of the quasi-co-location of the first frequency band; The terminal a receiving unit that receives the synchronization signal block from the base station; a control unit that assumes quasi-colocation of the synchronization signal block in the shared spectrum channel access of the second frequency band based on a notification method that is different from a notification method of quasi-colocation of the first frequency band. Communication system.

Images